Continuity counter error

[schumi2004]

Since i re-installed my Sundtek MediaTV Pro on my Synology NAS today after a driver upgrade i'm having almost every +/- 15 minutes a logging item saying:

Continuity counter error

This also effects playback, crappy image, as if it is paused.
After a few seconds it is back to normal again.

Is this a driver issue or is there something wrong with my 6 months old stick?

[Sundtek]

First of all check your signal strength, in case of weak signal strength or drop-outs try to reconnect the DVB-C cable (to the wall and to the stick)
Acceptable BER is below 10 for DVB-C with those devices.

/opt/bin/mediaclient --readsignal=0 -d /dev/dvb/adapter0/frontend0

[schumi2004]

I checked a few things but for some reason muxes get disabled after a period of time.
To get it working i need to do the following commands

DS211> export LD_PRELOAD=/opt/lib/libmediaclient.so
DS211> /var/packages/tvheadend/scripts/start-stop-status restart

This is what i see in log

0.20 [ xbmc | XBMC Media Center ]": Probing adapter "_dev_dvb_adapter0_Sundtek_DVB_C586750000" without stealing for service "Sundtek DVB-C/Ziggo Brabant Limburg: 586,750 kHz/SBS 6"
Dec 29 23:59:19 Service: Subscription "10.0.0.20 [ xbmc | XBMC Media Center ]": Unable to use "Sundtek DVB-C/Ziggo Brabant Limburg: 586,750 kHz/SBS 6" -- Mux not enabled

This never happened before until i needed to re-install sundtek on my Synology NAS today.


Edit:
DS211> /opt/bin/mediaclient --readsignal=0 -d /dev/dvb/adapter0/frontend0
== reading digital TV signal ==
invalid device

Edit2:
To get it working again i needed to do the following.

DS211> cd /volume1/@tmp
DS211> wget http://www.sundtek.de/media/sundtek_installer.sh
--2012-12-30 00:05:19--  http://www.sundtek.de/media/sundtek_installer.sh
Resolving www.sundtek.de... 85.10.198.106
Connecting to www.sundtek.de|85.10.198.106|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 84838 (83K) [text/x-sh]
Saving to: `sundtek_installer.sh'

100%[=============================================================>] 84,838      --.-K/s   in 0.1s    

2012-12-30 00:05:19 (596 KB/s) - `sundtek_installer.sh' saved [84838/84838]

DS211> chmod 755 sundtek_installer.sh
DS211> ./sundtek_installer.sh

[Sundtek]

Try to contact us via Skype (sundtek) or Chat (http://chat.sundtek.de ) to sort out your issue.

[Sundtek]

* the driver installer is updated to match the new tvheadend scripts.

* the USB Stack of those NAS Systems is a little bit weak, the next driver will automatically tweak the devices to improve that (unfortunately we had that included in the past but it was disabled due some other debugging in the past so it will be re-enabled again with the next update).

[schumi2004]

Looks like the problem returned today.

After i needed to reinstall TVHeadend the same symptoms occur.
Drivers changed?

Edit:
Seems it's loosing it's signal on a certain frequency for no reason. Nothing changed on hardware/cables only a re-install and now it looks like it has signal quality issues and is loosing connection to Sundtek stick?

DS211> /opt/bin/mediaclient --readsignal=0 -d /dev/dvb/adapter0/frontend0
== reading digital TV signal ==
invalid device
DS211>

[Sundtek]

To check if a device is available:
/opt/bin/mediaclient -e

To manually stop the driver:
/opt/bin/mediaclient --shutdown

To manually start the driver:
/opt/bin/mediaclient -e

To read the signal statistics for DVB-S/S2
/opt/bin/mediaclient --readsignal=0 -d /dev/dvb/adapter0/frontend0 --band UNIVERSAL

To read the signal statistics eg. for DVB-C or DVB-T
/opt/bin/mediaclient --readsignal=0 -d /dev/dvb/adapter0/frontend0


also check the "dmesg" output.

[schumi2004]

Thanks for the commands.

I'll check when i' near the device.
Strange thing is that it works for 15 minutes and then the device is lost.

[Sundtek]

Check the memory usage, and USB Connection.

We've had that issue previously already, the customer fixed his problem by using an active USB Hub. We recommend to use another USB Port. It seems that your device vanishes during operation - which means the USB Port disconnected the device.

Without having all the logfiles it's just a rough guess though.

[schumi2004]

Check the memory usage, and USB Connection.

We've had that issue previously already, the customer fixed his problem by using an active USB Hub. We recommend to use another USB Port. It seems that your device vanishes during operation - which means the USB Port disconnected the device.

Without having all the logfiles it's just a rough guess though.

Memory usage is stable nothing strange there.
I even downgraded DSM firmware back to 4.1 because it worked perfect there.

And after activation muxes (because they were suddenly disabled) it suddenly stopped working.

This is what i saw when it happend
http://pastebin.com/7RAKeXLv

Nothing changed, no hardware, no software just out of nothing it stops.
DS211> cd /opt/bin
DS211> ./mediaclient -e
Driver is currently not running, please start it as root
mediaclient --start

[Sundtek]

Well you might contact us via Skype (sundtek) to see what's going on on your system.
We don't see any change on our system which might be related to that.

[schumi2004]

Well you might contact us via Skype (sundtek) to see what's going on on your system.
We don't see any change on our system which might be related to that.

Currently i'm IRC but i'm thinking what could be the cause of this happening and i compared my actions from a few months ago with recent and there is 1 difference in it.

I always bootstrap my Synology otherwise sundtek installer returned an error.

The difference with both situations is that i needed to comment 2 lines in /root/.profile
See 8. NEW:
http://forum.synology.com/wiki/index.php/Overview_on_modifying_the_Synology_Server,_bootstrap,_ipkg_etc#How_to_install_ipkg

I never did in the past and i think that is causing all this.
Id i undo change and reboot NAS mediaclient starts as expected but not with TVH start script with this change in /root/.profile