Tvheadend

Well I reply to myself with some news:

I opened a ticket to Digital Devices about two problems:

1) SNR and Signal Strength columns are empty with OctopusNET S2 device
2) A lot of Uncorrected/Transport/Continuity Errors on the four tuners

They assumed the first problem that will be resolved with next firmware (no Idea when)
but
they returned me to tvheadend staff for point number 2.

Before opening an issue, I'll ask again:

Nobody else using an OctopusNET S2/4 device with tvheadend?

Thanks
Gigius

Hello

I have the same problem with an OctopusNET C2/4. Which Parameters are correct for the Advanced Settings of the OctopusNet and for the single Tuner? My actual Settings for the the OctopusNet are on Picture 1 and for the Single Tuner on Picture 2

Guys, please DO open a bug ticket

Hi Gigius,

I use a DD Octopus NET S2/4 V2. Runs fine so far. SNR and signal strength is not empty and gives me a good indicator about the signal.

Have some Uncorrected/Transport/Continuity Errors too, but not really a big issue. Did you checked your network setup?
I had some big trouble before with a Intel Q chipset motherboard. Buying a separate network interface card solved the issue.

Hi Jose,

DD support told me that SNR and signal strength are known problem that will be resolved with next firmware. I'm using 1.0.55 what firmware are you using?

I already moved the octopus from my production system (supermicro X10SLL-F , Xeon E3-1220 v3, 8GB ECC Ram, ubuntu 14.04) to a VMware virtual machine (HP DL380 G6 based) for testing and the problem is the same. Tuning the card parameters may be an idea, but the card itself is not the cause.

BUT, I have two switches between the Octopus and my servers, one cisco small business SG200-26 (house distribution) and a catalyst 2960G-48 (TOR). maybe I should check some settings there.

Thanks
Gigius

Hi Gigius,

using firmware 1.0.55 too. If you would test beta firmwares on your OcotopusNet use this URL http://ip-of-octopusnet/beta.html and "Select Beta Update Server". You can revert back to Standard Update Server later.

Could you also try to connect your tvheadend server directly to the OctopusNet? No other switch between.

Jose

Hi Jose,

upgraded the Octopus to beta firmware 1.0.67. Signals bars are now there, bur errors and lost UDP packets are always there.
I'll try the direct connection Octopus-TVHeadend Server this week-end (have to move the Octopus near the server with at least 40 meters coax, or build a 40meters cat6 network cable :-)

Regards
Gigius

Hi Jose,

as explained on the issue, I bypassed one of the switches without result and I'm waiting for a network card to bypass the second.
Anyway I saw on your previous post (specially on the status.jpg image) that you have Uncorrected blocks too!

Regards
Gianni

Hi Gigius,

yes, that was my Docker container.

Look here if you use your Tvheadend server in a container with a satip device:
https://tvheadend.org/issues/3810#note-12