Kodi Community Forum

Full Version: VDR VNSI Client - Channel: no data
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hello everyone,

For a couple of days I have a huge problem running my Raspberry v2 with VDR and ProfTuners 7500 any TV channel. I think there was an update of VDR Backend and the VNSI client packages and since I made clean setup of Openelec 5.95.2 I can't run anything.

First of all, the dvb card is detected properly:
Code:
[   50.112889] usb 1-1.4: new high-speed USB device number 6 using dwc_otg
[   50.206453] usb 1-1.4: New USB device found, idVendor=3034, idProduct=7500
[   50.206516] usb 1-1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   50.286359] dvb-usb: found a 'Prof 7500 USB DVB-S2' in cold state, will try to load a firmware
[   50.301009] dvb-usb: downloading firmware from file 'dvb-usb-p7500.fw'
[   50.301051] dw2102: start downloading DW210X firmware
[   50.416002] dvb-usb: found a 'Prof 7500 USB DVB-S2' in warm state.
[   50.417782] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[   50.418282] DVB: registering new adapter (Prof 7500 USB DVB-S2)
[   50.425219] usb 1-1.4: USB disconnect, device number 6
[   50.428839] dvb-usb: MAC address: c0:c0:c0:c0:c0:c0
[   50.461483] stv0900_init_internal
[   50.461526] stv0900_init_internal: Create New Internal Structure!
[   50.479985] stv0900_st_dvbs2_single
[   50.480023] stv0900_stop_all_s2_modcod
[   50.480089] stv0900_activate_s2_modcod_single
[   50.480245] stv0900_set_ts_parallel_serial path1 3 path2 0
[   50.480426] stv0900_set_mclk: Mclk set to 135000000, Quartz = 27000000
[   50.480471] stv0900_get_mclk_freq: Calculated Mclk = 4500000
[   50.492714] stv0900_get_mclk_freq: Calculated Mclk = 4500000
[   50.492746] stv0900_attach: Attaching STV0900 demodulator(0)
[   50.492775] dw2102: Attached STV0900+STB6100A!
[   50.492775]
[   50.492816] usb 1-1.4: DVB: registering adapter 0 frontend 0 (STV0900 frontend)...
[   50.539275] Registered IR keymap rc-tbs-nec
[   50.539977] input: IR-receiver inside an USB DVB receiver as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/rc/rc0/input4
[   50.540298] rc0: IR-receiver inside an USB DVB receiver as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/rc/rc0
[   50.540318] dvb-usb: schedule remote query interval to 150 msecs.
[   50.540339] dvb-usb: Prof 7500 USB DVB-S2 successfully initialized and connected.
[   50.540572] usbcore: registered new interface driver dw2102
[   50.603471] stv0900_release
[   50.603574] stv0900_release: Actually removing
[   50.611466] dvb-usb: Prof 7500 USB DVB-S2 successfully deinitialized and disconnected.
[   52.159440] usb 1-1.4: new high-speed USB device number 7 using dwc_otg
[   52.252998] usb 1-1.4: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 2
[   52.253415] usb 1-1.4: New USB device found, idVendor=3034, idProduct=7500
[   52.253439] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   52.253449] usb 1-1.4: Product: DVB-S USB
[   52.253460] usb 1-1.4: Manufacturer: Prof Group
[   52.254326] dvb-usb: found a 'Prof 7500 USB DVB-S2' in cold state, will try to load a firmware
[   52.254497] dvb-usb: downloading firmware from file 'dvb-usb-p7500.fw'
[   52.254509] dw2102: start downloading DW210X firmware
[   52.362641] dvb-usb: found a 'Prof 7500 USB DVB-S2' in warm state.
[   52.363238] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[   52.363506] DVB: registering new adapter (Prof 7500 USB DVB-S2)
[   52.483228] dvb-usb: MAC address: 22:ab:10:28:43:ff
[   52.485310] stv0900_init_internal
[   52.485338] stv0900_init_internal: Create New Internal Structure!
[   52.566536] stv0900_st_dvbs2_single
[   52.566581] stv0900_stop_all_s2_modcod
[   52.570819] stv0900_activate_s2_modcod_single
[   52.582242] stv0900_set_ts_parallel_serial path1 3 path2 0
[   52.594959] stv0900_set_mclk: Mclk set to 135000000, Quartz = 27000000
[   52.597516] stv0900_get_mclk_freq: Calculated Mclk = 135000000
[   52.610406] stv0900_get_mclk_freq: Calculated Mclk = 135000000
[   52.610438] stv0900_attach: Attaching STV0900 demodulator(0)
[   52.610623] dw2102: Attached STV0900+STB6100A!
[   52.610623]
[   52.610670] usb 1-1.4: DVB: registering adapter 0 frontend 0 (STV0900 frontend)...
[   52.611738] Registered IR keymap rc-tbs-nec
[   52.612751] input: IR-receiver inside an USB DVB receiver as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/rc/rc0/input5
[   52.615312] rc0: IR-receiver inside an USB DVB receiver as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/rc/rc0
[   52.615341] dvb-usb: schedule remote query interval to 150 msecs.
[   52.615369] dvb-usb: Prof 7500 USB DVB-S2 successfully initialized and connected.
[   53.771860] stv0900_init
[   53.786039] stv0900_read_status:
[   53.786705] stv0900_status: locked = 0
[   53.788775] stv0900_get_mclk_freq: Calculated Mclk = 135000000
[   53.788793] TS bitrate = 272 Mbit/sec
[   53.788925] DEMOD LOCK FAIL
[   54.799276] stv0900_read_status:
[   54.799927] stv0900_status: locked = 0
[   54.801754] stv0900_get_mclk_freq: Calculated Mclk = 135000000
[   54.801767] TS bitrate = 270 Mbit/sec
[   54.801900] DEMOD LOCK FAIL

Secondly, I installed VDR backend and VNSI client. VDR PVR Backend is in 6.0.1 version while the VNSI client is in 1.10.10 version.
In the TV section I am sometimes able to scan one transponder - in this case I choose HotBird 10.775 H, since it's DVB-S and has a couple of FTA Italian channels. But even now it's very hard to scan more than one transponder without reseting the whole hardware.
After I scan and save the channels, I always make the "clear data" in the general TV options in order to reset the channel list in OpenELEC.
The channels are on the list so when I choose any FTA channel I get the error message as in the topic, i.e. "VDR VNSI Client - Channel: no data" and that's it.

The tuner turns on the green LED when it locks to a certain tranponder but here there is no green light like the tuner is not turned on to catch the signal.

I was also testing the stuff with encrypted channels and using OSCAM as a logger. I can clearly see that there is no "movement" in oscam like the tuner is not turned on and no signal is received.

I checked a couple of tutorials, I upgraded the priority in VNSI configuration panel but still no difference. I also switched couple of times between 5.95.2 and 6.0.0 versions of OpenELEC by making clean installs but it also doesn't matter as the whole stuff behaves the same.

I am now sure that the repository of these VDR Backend and VNSI client is kinda unstable in terms of my receiver. The packages which were delivered in July this year (for Opeelec 5.95) were much better and stable as I was able to watch the TV without any issues. The worst thing is that I can't find the previous packages now.

I did a thing:
1) I installed a clean openelec 5.95
2) I installed VNSI client and then later VDR backend
3) after a reboot I enabled TV and went into the client specific options.
4) I was able to run the scan of one transponder - i found all services in this transponder
5) i entered TV tab and ran the FTA channel
6) VOILA, it worked for a number of minutes
7) I switched channel to another FTA and guess what...
8) VDR VNSI Client - Channel: no data

Then I removed both VDR backend and the client and installed TVHeadend - I was able to scan plenty of Hotbird's transponders without any issues. So this is not the driver issue, nor the openelec/kodi itself. but in my opinion it's a problem of the VDR packages.

Now here's the question: If I have got Kodi 15.2, can I somehow install the previous versions of the VDR packages manually? Or am I forced to use the one and only which are provided by the GUI of the XBMC/Kodi for Raspberry's Openelec 5.95 or 6.0? What else can I provide to you in order to get some more details about this issue? What should I look for in the config files or anywhere else to solve this problem?
You need to ask this on the OE forum. I don't have a clue what versions (+ patches) get pulled in what versions of OE. "no data" means that vnsi does not get anything from vdr. I don't think this is an issue of vnsi or vdr but some kernel / driver issue of OE.
Hi @FernetMenta,
Many thanks for answer. Could you please tell me how can I log the communication between VNSI and VDR?
I think that the new version of VDR is incompatible with the OE as previous version worked. The VDR package is not strictly related to Kodi or OE but the new version might have problem of being able to work with the kernel or the DVB driver.

Unfortunately, I haven't got any teply on OE forum yet.

Best regards,
P.
By setting VDR log level to 3 you get more info in syslog (not sure how OE has named this file).