Telestar Digibit Twin SAT/IP (solved!)

Do you want advice about what hardware to buy for use with MythTV? Ask here.

Moderator: Forum Moderators

Post Reply
jksj
Senior
Posts: 107
Joined: Thu Feb 13, 2014 7:53 pm
Great Britain

Telestar Digibit Twin SAT/IP (solved!)

Post by jksj » Thu Nov 12, 2020 12:54 pm

Attempting to get a this SAT/IP box working with master Mythtv. v32-Pre-1660-g3a243d67f1
Setup detects the device fine but there is no way to configure the LNB.
The setup utility that comes with the box does not support this either but it is connected to a normal Sky type LNB so there should not be an issue.
Only the second of the two inputs worked and packets were being dropped so I am returning the device which is a shame because it is a well packaged nice little device.
The addressing might have been wrong as the box shows sat connections 1 and 2 and setup recognises 0 and 1 which might explain why only one input worked but the dropped packets caused noticeable glitching which would drive me crazy. Note it was connected to an Intel NUC through Gbit Ethernet on a local switch.
So in setup only the second input would scan and in normal live tv only the second input worked.
Lots of protocol errors and dropped packets but the two issues may be linked if the inputs are not being addressed correctly.
Log fragments in the next post
Last edited by jksj on Thu Nov 19, 2020 3:04 pm, edited 2 times in total.

jksj
Senior
Posts: 107
Joined: Thu Feb 13, 2014 7:53 pm
Great Britain

Re: Telestar Digibit Twin SAt/IP

Post by jksj » Thu Nov 12, 2020 2:04 pm

Backend log fragment

Code: Select all

Nov 12 09:30:05 tv mythbackend: mythbackend[13462]: E CoreContext recorders/satiprtsp.cpp:451 (ReadPending) SatIPRTCP_RH(rtsp://192.168.0.41:554/?fe=1&freq=10847.00&pol=v&ro=0.20&msys=dvbs2&mtype=8psk&sr=23000&fec=34&plts=auto): Invalid RTCP packet received
Nov 12 09:30:05 tv mythbackend: mythbackend[13462]: E CoreContext recorders/satiprtsp.cpp:451 (ReadPending) SatIPRTCP_RH(rtsp://192.168.0.41:554/?fe=2&freq=10847.00&pol=v&ro=0.20&msys=dvbs2&mtype=8psk&sr=23000&fec=34&plts=auto): Invalid RTCP packet received

Code: Select all

 N ProcessRequest mainserver.cpp:7279 (HandleSetVerbose) MainServer: Verbose mask changed, new mask is:  general channel record
Nov 12 12:21:37 tv mythbackend: mythbackend[7069]: I MythSocketThread(80) mainserver.cpp:7842 (connectionClosed) Playback sock(55d62f4fb3c0) 'tv' disconnected
Nov 12 12:21:37 tv mythbackend: mythbackend[7069]: I MythSocketThread(82) mainserver.cpp:7842 (connectionClosed) Monitor sock(55d62f407b40) 'tv' disconnected
Nov 12 12:21:59 tv mythbackend: mythbackend[7069]: I CoreContext recorders/satiprtsp.cpp:358 (timerEvent) SatIPRTSP[4]: Sending KeepAlive timer 4
Nov 12 12:22:00 tv mythbackend: mythbackend[7069]: I CoreContext recorders/satiprtsp.cpp:516 (timerEvent) SatIPRTSP_WH[5]: Sequence number mismatch 57341!=56908
Nov 12 12:22:00 tv mythbackend: mythbackend[7069]: W CoreContext recorders/dtvrecorder.cpp:1616 (ProcessAVTSPacket) DTVRec[5]: A/V PID 0x905 discontinuity detected ((15+1)%16!=12)  0.00%
Nov 12 12:22:00 tv mythbackend: mythbackend[7069]: W CoreContext recorders/dtvrecorder.cpp:1616 (ProcessAVTSPacket) DTVRec[5]: A/V PID 0x906 discontinuity detected ((3+1)%16!=6)  0.00%
Nov 12 12:22:00 tv mythbackend: mythbackend[7069]: W CoreContext recorders/dtvrecorder.cpp:1488 (ProcessTSPacket) DTVRec[5]: PID 0xf01 discontinuity detected ((10+1)%16!= 0) 0.00337548%
Nov 12 12:22:00 tv mythbackend: mythbackend[7069]: E CoreContext mpeg/pespacket.cpp:84 (AddTSPacket) AddTSPacket[5]: Out of sync!!! Need to wait for next payloadStart PID: 0x11, continuity counter: 1 (expected 6)
Nov 12 12:22:00 tv mythbackend: mythbackend[7069]: E CoreContext mpeg/pespacket.cpp:84 (AddTSPacket) AddTSPacket[5]: Out of sync!!! Need to wait for next payloadStart PID: 0x12, continuity counter: 13 (expected 5)
Nov 12 12:22:00 tv mythbackend: mythbackend[7069]: W CoreContext recorders/dtvrecorder.cpp:1488 (ProcessTSPacket) DTVRec[5]: PID 0xf02 discontinuity detected ((10+1)%16!= 9) 0.00364872%
Nov 12 12:22:00 tv mythbackend: mythbackend[7069]: I CoreContext recorders/satiprtsp.cpp:358 (timerEvent) SatIPRTSP[5]: Sending KeepAlive timer 6
Nov 12 12:22:01 tv mythbackend: mythbackend[7069]: W CoreContext recorders/dtvrecorder.cpp:1488 (ProcessTSPacket) DTVRec[5]: PID 0xf04 discontinuity detected ((13+1)%16!=15) 0.00390646%
Nov 12 12:22:01 tv mythbackend: mythbackend[7069]: I CoreContext recorders/satiprtsp.cpp:516 (timerEvent) SatIPRTSP_WH[5]: Sequence number mismatch 58271!=57888
Nov 12 12:22:01 tv mythbackend: mythbackend[7069]: W CoreContext recorders/dtvrecorder.cpp:1616 (ProcessAVTSPacket) DTVRec[5]: A/V PID 0x906 discontinuity detected ((15+1)%16!=6)  0.00%
Nov 12 12:22:01 tv mythbackend: mythbackend[7069]: W CoreContext recorders/dtvrecorder.cpp:1616 (ProcessAVTSPacket) DTVRec[5]: A/V PID 0x905 discontinuity detected ((11+1)%16!=1)  0.00%
Nov 12 12:22:01 tv mythbackend: mythbackend[7069]: W CoreContext recorders/dtvrecorder.cpp:1488 (ProcessTSPacket) DTVRec[5]: PID 0xf01 discontinuity detected (( 7+1)%16!=15) 0.00473597%
Nov 12 12:22:01 tv mythbackend: mythbackend[7069]: W CoreContext recorders/dtvrecorder.cpp:1488 (ProcessTSPacket) DTVRec[5]: PID 0xf03 discontinuity detected ((14+1)%16!= 3) 0.0050143%
Nov 12 12:22:01 tv mythbackend: mythbackend[7069]: E CoreContext mpeg/pespacket.cpp:84 (AddTSPacket) AddTSPacket[5]: Out of sync!!! Need to wait for next payloadStart PID: 0x12, continuity counter: 12 (expected 6)
Nov 12 12:22:01 tv mythbackend: mythbackend[7069]: W CoreContext recorders/dtvrecorder.cpp:1488 (ProcessTSPacket) DTVRec[5]: PID 0xf02 discontinuity detected ((12+1)%16!=10) 0.00526939%
Nov 12 12:22:29 tv mythbackend: mythbackend[7069]: I CoreContext recorders/satiprtsp.cpp:358 (timerEvent) SatIPRTSP[4]: Sending KeepAlive timer 4
Nov 12 12:22:30 tv mythbackend: mythbackend[7069]: I CoreContext recorders/satiprtsp.cpp:516 (timerEvent) SatIPRTSP_WH[5]: Sequence number mismatch 20927!=20505
Nov 12 12:22:30 tv mythbackend: mythbackend[7069]: W CoreContext recorders/dtvrecorder.cpp:1616 (ProcessAVTSPacket) DTVRec[5]: A/V PID 0x905 discontinuity detected ((2+1)%16!=10)  0.00%
Nov 12 12:22:30 tv mythbackend: mythbackend[7069]: W CoreContext recorders/dtvrecorder.cpp:1488 (ProcessTSPacket) DTVRec[5]: PID 0xf01 discontinuity detected ((11+1)%16!= 0) 0.00391389%
Nov 12 12:22:30 tv mythbackend: mythbackend[7069]: E CoreContext mpeg/pespacket.cpp:84 (AddTSPacket) AddTSPacket[5]: Out of sync!!! Need to wait for next payloadStart PID: 0x11, continuity counter: 6 (expected 10)
Nov 12 12:22:30 tv mythbackend: mythbackend[7069]: W CoreContext recorders/dtvrecorder.cpp:1488 (ProcessTSPacket) DTVRec[5]: PID 0xf03 discontinuity detected (( 1+1)%16!= 4) 0.00410013%
Nov 12 12:22:30 tv mythbackend: mythbackend[7069]: W CoreContext recorders/dtvrecorder.cpp:1488 (ProcessTSPacket) DTVRec[5]: PID 0xf02 discontinuity detected ((13+1)%16!=10) 0.00428634%
Nov 12 12:22:30 tv mythbackend: mythbackend[7069]: E CoreContext mpeg/pespacket.cpp:84 (AddTSPacket) AddTSPacket[5]: Out of sync!!! Need to wait for next payloadStart PID: 0xf02, continuity counter: 10 (expected 14)
Nov 12 12:22:30 tv mythbackend: mythbackend[7069]: I CoreContext recorders/satiprtsp.cpp:358 (timerEvent) SatIPRTSP[5]: Sending KeepAlive timer 6
Nov 12 12:22:31 tv mythbackend: mythbackend[7069]: W CoreContext recorders/dtvrecorder.cpp:1488 (ProcessTSPacket) DTVRec[5]: PID 0xf04 discontinuity detected (( 9+1)%16!=11) 0.00444887%
Nov 12 12:22:31 tv mythbackend: mythbackend[7069]: I CoreContext recorders/satiprtsp.cpp:516 (timerEvent) SatIPRTSP_WH[5]: Sequence number mismatch 21850!=21479
Nov 12 12:22:31 tv mythbackend: mythbackend[7069]: W CoreContext recorders/dtvrecorder.cpp:1616 (ProcessAVTSPacket) DTVRec[5]: A/V PID 0x905 discontinuity detected ((0+1)%16!=15)  0.00%
Nov 12 12:22:31 tv mythbackend: mythbackend[7069]: W CoreContext recorders/dtvrecorder.cpp:1488 (ProcessTSPacket) DTVRec[5]: PID 0xf03 discontinuity detected ((15+1)%16!= 4) 0.00481424%
Nov 12 12:22:31 tv mythbackend: mythbackend[7069]: W CoreContext recorders/dtvrecorder.cpp:1616 (ProcessAVTSPacket) DTVRec[5]: A/V PID 0x906 discontinuity detected ((2+1)%16!=7)  0.00%
Nov 12 12:22:31 tv mythbackend: mythbackend[7069]: W CoreContext recorders/dtvrecorder.cpp:1488 (ProcessTSPacket) DTVRec[5]: PID 0xf01 discontinuity detected (( 7+1)%16!= 0) 0.00518438%
Nov 12 12:22:31 tv mythbackend: mythbackend[7069]: E CoreContext mpeg/pespacket.cpp:84 (AddTSPacket) AddTSPacket[5]: Out of sync!!! Need to wait for next payloadStart PID: 0x12, continuity counter: 0 (expected 10)
Nov 12 12:22:31 tv mythbackend: mythbackend[7069]: I CoreContext mpeg/pespacket.cpp:179 (VerifyCRC) PESPacket[5] pid(0x11): Failed CRC check 0x01058101 != 0xa4fe3e83 for ID = 0x4a
Nov 12 12:22:31 tv mythbackend: mythbackend[7069]: E CoreContext mpeg/mpegstreamdata.cpp:234 (AssemblePSIP) MPEGStream[5](0x7f8dd8045858): Discarding broken PSIP packet on PID 0x11
Nov 12 12:22:31 tv mythbackend: mythbackend[7069]: W CoreContext recorders/dtvrecorder.cpp:1488 (ProcessTSPacket) DTVRec[5]: PID 0xf02 discontinuity detected (( 2+1)%16!=13) 0.00536621%
Nov 12 12:22:59 tv mythbackend: mythbackend[7069]: I CoreContext recorders/satiprtsp.cpp:358 (timerEvent) SatIPRTSP[4]: Sending KeepAlive timer 4
Nov 12 12:23:00 tv mythbackend: mythbackend[7069]: I CoreContext recorders/satiprtsp.cpp:516 (timerEvent) SatIPRTSP_WH[5]: Sequence number mismatch 50063!=49643
Last edited by jksj on Thu Nov 12, 2020 5:51 pm, edited 1 time in total.

jksj
Senior
Posts: 107
Joined: Thu Feb 13, 2014 7:53 pm
Great Britain

Re: Telestar Digibit Twin SAt/IP

Post by jksj » Thu Nov 12, 2020 2:11 pm

setup log fragment

Code: Select all

2020-11-12 10:47:13.098548 I  SatIP: Using UPNP to search for Sat>IP servers (3 secs)
2020-11-12 10:47:16.391898 I  SatIP: Found 1 possible Sat>IP servers
2020-11-12 10:47:16.391981 I  SatIP: Found uuid:20667d30-1dd2-11b2-80b7-a1a05ef25d82 DigibitTwin 192.168.0.41 0 DVBS2
2020-11-12 10:47:16.392002 I  SatIP: Found uuid:20667d30-1dd2-11b2-80b7-a1a05ef25d82 DigibitTwin 192.168.0.41 1 DVBS2
2020-11-12 10:47:16.436227 W  DiSEqCDevTree: No device tree for cardid 5
2020-11-12 10:47:16.440837 W  DiSEqCDevTree: No device tree for cardid 5
2020-11-12 10:47:16.450624 E  ProbeAudioInputs() -> couldn't open device
2020-11-12 10:47:16.468802 E  V4L2(): Could not open 'uuid:20667d30-1dd2-11b2-80b7-a1a05ef25d82:DVBS2:0': 
			eno: No such file or directory (2)
2020-11-12 10:47:16.638477 I  CardUtil(/dev/dvb/adapter0/frontend0): dvb api version 5.11
2020-11-12 10:47:16.638532 I  CardUtil(/dev/dvb/adapter0/frontend0): Delivery systems: DVB-S DVB-S2
2020-11-12 10:47:16.699430 I  CardUtil: Current delivery system: DVB-S
2020-11-12 10:47:16.699478 I  CardUtil: Supported delivery systems: DVB-S DVB-S2
2020-11-12 10:47:16.699500 I  CardUtil: Changing delivery system from DVB-S to DVB-S2
2020-11-12 10:47:16.701477 W  DiSEqCDevTree: No device tree for cardid 5
2020-11-12 10:47:16.710426 W  DiSEqCDevTree: No device tree for cardid 5
2020-11-12 10:48:03.306341 I  VBox: Using UPNP to search for Vboxes (3 secs)
2020-11-12 10:48:06.359754 I  SatIP: Using UPNP to search for Sat>IP servers (3 secs)
2020-11-12 10:48:09.410551 I  SatIP: Found 1 possible Sat>IP servers
2020-11-12 10:48:09.410640 I  SatIP: Found uuid:20667d30-1dd2-11b2-80b7-a1a05ef25d82 DigibitTwin 192.168.0.41 0 DVBS2
2020-11-12 10:48:09.410660 I  SatIP: Found uuid:20667d30-1dd2-11b2-80b7-a1a05ef25d82 DigibitTwin 192.168.0.41 1 DVBS2
2020-11-12 10:48:09.470879 E  ProbeAudioInputs() -> couldn't open device
2020-11-12 10:48:09.486951 E  V4L2(): Could not open 'uuid:20667d30-1dd2-11b2-80b7-a1a05ef25d82:DVBS2:0': 
			eno: No such file or directory (2)
2020-11-12 10:48:09.550032 E  ProbeAudioInputs() -> couldn't open device
2020-11-12 10:48:09.565882 E  V4L2(): Could not open 'uuid:20667d30-1dd2-11b2-80b7-a1a05ef25d82:DVBS2:1': 
			eno: No such file or directory (2)
2020-11-12 10:48:19.567894 I  XMLTVGrabber::Load: Running 'tv_find_grabbers baseline'.
2020-11-12 10:48:23.918280 I  XMLTVGrabber::Load: Finished running tv_find_grabbers
2020-11-12 10:48:44.956876 I  XMLTVGrabber::Load: Running 'tv_find_grabbers baseline'.
2020-11-12 10:48:49.080497 I  XMLTVGrabber::Load: Finished running tv_find_grabbers
2020-11-12 10:49:00.307603 I  InputHandler: Locking input devices
2020-11-12 10:49:00.307634 N  Suspending idle timer
2020-11-12 10:49:00.319409 I  XMLTVGrabber::Load: Running 'tv_find_grabbers baseline'.
2020-11-12 10:49:04.447659 I  XMLTVGrabber::Load: Finished running tv_find_grabbers
2020-11-12 10:49:04.497079 I  InputHandler: Unlocking input devices
2020-11-12 10:49:04.497095 N  Resuming idle timer
2020-11-12 10:49:20.954871 I  InputHandler: Locking input devices
2020-11-12 10:49:20.954883 N  Suspending idle timer
2020-11-12 10:49:20.966606 I  XMLTVGrabber::Load: Running 'tv_find_grabbers baseline'.
2020-11-12 10:49:25.086623 I  XMLTVGrabber::Load: Finished running tv_find_grabbers
2020-11-12 10:49:25.133082 I  InputHandler: Unlocking input devices
2020-11-12 10:49:25.133104 N  Resuming idle timer
2020-11-12 10:49:32.531297 I  InputHandler: Locking input devices
2020-11-12 10:49:32.531308 N  Suspending idle timer
2020-11-12 10:49:32.543687 I  XMLTVGrabber::Load: Running 'tv_find_grabbers baseline'.
2020-11-12 10:49:36.680097 I  XMLTVGrabber::Load: Finished running tv_find_grabbers
2020-11-12 10:49:36.729978 I  InputHandler: Unlocking input devices
2020-11-12 10:49:36.729997 N  Resuming idle timer
2020-11-12 10:52:26.908472 I  SatIP: Using UPNP to search for Sat>IP servers (3 secs)
2020-11-12 10:52:30.049254 I  SatIP: Found 1 possible Sat>IP servers
2020-11-12 10:52:30.049400 I  SatIP: Found uuid:20667d30-1dd2-11b2-80b7-a1a05ef25d82 DigibitTwin 192.168.0.41 0 DVBS2
2020-11-12 10:52:30.049422 I  SatIP: Found uuid:20667d30-1dd2-11b2-80b7-a1a05ef25d82 DigibitTwin 192.168.0.41 1 DVBS2
2020-11-12 10:52:30.076604 I  SatIPSH[4](uuid:20667d30-1dd2-11b2-80b7-a1a05ef25d82:DVBS2:0): Tune 10714000
2020-11-12 10:52:31.484882 E  SatIPRTCP_RH(rtsp://192.168.0.41:554/?fe=1&freq=10714.00&pol=h&ro=0.35&msys=dvbs&mtype=qpsk&sr=22000&fec=auto&plts=auto): Invalid RTCP packet received
2020-11-12 10:52:38.331346 I  ChanImport: No channels to process..
2020-11-12 10:54:08.221218 I  SatIP: Using UPNP to search for Sat>IP servers (3 secs)
2020-11-12 10:54:11.439509 I  SatIP: Found 1 possible Sat>IP servers
2020-11-12 10:54:11.439641 I  SatIP: Found uuid:20667d30-1dd2-11b2-80b7-a1a05ef25d82 DigibitTwin 192.168.0.41 0 DVBS2
2020-11-12 10:54:11.439663 I  SatIP: Found uuid:20667d30-1dd2-11b2-80b7-a1a05ef25d82 DigibitTwin 192.168.0.41 1 DVBS2
2020-11-12 10:54:11.462359 I  SatIPSH[5](uuid:20667d30-1dd2-11b2-80b7-a1a05ef25d82:DVBS2:1): Tune 10714000
2020-11-12 10:54:29.783774 I  SatIPSH[5](uuid:20667d30-1dd2-11b2-80b7-a1a05ef25d82:DVBS2:1): Tune 11758500
2020-11-12 10:54:47.403422 I  SatIPSH[5](uuid:20667d30-1dd2-11b2-80b7-a1a05ef25d82:DVBS2:1): Tune 11778000
Normal tuning output follows

User avatar
kmdewaal
Developer
Posts: 189
Joined: Wed Dec 07, 2016 8:01 pm
Netherlands

Re: Telestar Digibit Twin SAT/IP

Post by kmdewaal » Thu Nov 12, 2020 8:38 pm

Sorry that it does not work right out of the box... It is more likely that this is a MythTV software issue than a broken box but to be explicit, there is no guarantee that native SatIP support will ever work correct with your box.

A few notes, maybe this gives you some ideas.

0. UPnP device detection looks OK.
1. There is support in MythTV for SatIP boxes using the External Recorder, as described in the Wiki in https://www.mythtv.org/wiki/SAT2IP_play ... ture_cards. If this work your box is OK.
2. The box I have can be configured with a web interface, using the IP address from the mythtv-setup log. In your case 192.168.0.41. I have never used a configuration utility.
3. With the web interface of my box the LNB configuration is done. For me the default did work. All LNBs must be equal. MythTV does not do anything with the LNB setting, that is completely in the box. The numbers as specified on my box count from 1 to 4, the "fe=x" parameter counts also from 1 to 4 but the numbers as reported in the"SatIP: Found..." messages count from 0 to 3. All numbers in MythTV go from 0 to 3.
5. The "Invalid RTCP packet" messages from your first log fragment should never be there.
6. The "Sequence Number mismatch" messages occur after a channel change, this does give a discontinuity in the sequence. In normal operation these message do come only when the MythTV system cannot keep up with the flow of packets. This happens here when I do tests on my lowest-power machine, a RPi3B, but even the RPI3B can do a successful channel scan. With my normal development box (Intel i7) does not have this problem. I expect your Intel NUC to be fast enough.
7. The "DiSEqCDevTree: No device tree" should not be there. This looks like a software bug but I need to figure out which configuration triggers this. It should only happen with real /dev/dvb/.... DVB-S/S2 devices that do not have the LNB configured, not with SatIP. I have not seen it here.
8. The "V4L2" message are harmless and need to be fixed one of these days....
9. I have, via the web interface of the box, done channel scans to check if the box did work. This is needed if you want to use the "External recorder" option but it should not make any difference if you use the SatIP native interface.

Hope this helps,
Klaas.

jksj
Senior
Posts: 107
Joined: Thu Feb 13, 2014 7:53 pm
Great Britain

Re: Telestar Digibit Twin SAT/IP

Post by jksj » Fri Nov 13, 2020 9:34 am

Thanks for the response.
By configuration utility I meant the web interface.
This device is really simple it does not have the Network and m3ulist items on the 'System' menu that the Digibit B1 does (looking at the latter's manual)
So it looks like its got to be returned.
The device did successfully scan on the second input using mythtv-setup.
So even if you can fix the interface the dropped packets implies that my configuration just cant keep up, so its looking like this solution is unsuitable for me.

jksj
Senior
Posts: 107
Joined: Thu Feb 13, 2014 7:53 pm
Great Britain

Re: Telestar Digibit Twin SAT/IP

Post by jksj » Thu Nov 19, 2020 3:03 pm

Had second thoughts - the potential to get rid of some wiring spaghetti was just too great so. Sent it back and exchanged it for the Digibit R1 quad recever a much better device that works out of the box with master v32-Pre-1707-gf328b56be9.
Still some minor issues whicjh I will start a new thread on.

As far as the Digibit Twin goes its known to work in TV Headend but I think that has been changed to cope with a minor divergence from the SAT/IP standard. The quad device has far more facilities, its worth the extra.

Post Reply