Hi all,
I recently got a stone-aged Digibit R1 to replace an even older PCI-E card. My satellite antenna points at Astra S19.2E and Hotbird S13E, 2 Dual LNBs in Quad configuration. However, the Digibit device seems not to find anything on S13E.
Not sure if I need DiSeQC with SATIP but I set:
in sources.conf
S19.2E 1 Astra 1KR/1L/1M/2C S19.2E 2 Astra 1KR/1L/1M/2C S13E 3 Eutelsat Hot Bird 13B/13C/13D S13E 4 Eutelsat Hot Bird 13B/13C/13D
and in diseqc.conf
1 2: S19.2E 11700 V 9750 t v W15 [E0 10 38 F0] W15 A W15 t S19.2E 99999 V 10600 t v W15 [E0 10 38 F1] W15 A W15 T S19.2E 11700 H 9750 t V W15 [E0 10 38 F2] W15 A W15 t S19.2E 99999 H 10600 t V W15 [E0 10 38 F3] W15 A W15 T
3 4: S13.0E 11700 V 9750 t v W15 [E0 10 38 F4] W15 B W15 t S13.0E 99999 V 10600 t v W15 [E0 10 38 F5] W15 B W15 T S13.0E 11700 H 9750 t V W15 [E0 10 38 F6] W15 B W15 t S13.0E 99999 H 10600 t V W15 [E0 10 38 F7] W15 B W15 T
This has worked with a DD Cine S2 V6.5 PCI-E card earlier.
conf.d/50-satip.conf goes like,
[satip] -d 4 # -s 192.168.20.4|DVBS2-4:S19.2E,S13E|DIGIBIT
in order to detect 4 tuners. The -s line is apparently not needed and the params are autodetected. syslog says,
Sep 17 19:21:12 seneca vdr: [5163] SATIP discover thread started (pid=5159, tid=5163, prio=high) Sep 17 19:21:12 seneca vdr: [5159] SATIP: Creating device CardIndex=0 DeviceNumber=0 [device 0] Sep 17 19:21:12 seneca vdr: [5164] SATIP#0 tuner thread started (pid=5159, tid=5164, prio=high) Sep 17 19:21:12 seneca vdr: [5159] new device number 2 (card index 2) Sep 17 19:21:12 seneca vdr: [5159] SATIP: Creating device CardIndex=1 DeviceNumber=1 [device 1] Sep 17 19:21:12 seneca vdr: [5166] device 1 section handler thread started (pid=5159, tid=5166, prio=low) Sep 17 19:21:12 seneca vdr: [5165] SATIP#0 section handler thread started (pid=5159, tid=5165, prio=high) Sep 17 19:21:12 seneca vdr: [5167] SATIP#1 tuner thread started (pid=5159, tid=5167, prio=high) Sep 17 19:21:12 seneca vdr: [5159] new device number 3 (card index 3) Sep 17 19:21:12 seneca vdr: [5159] SATIP: Creating device CardIndex=2 DeviceNumber=2 [device 2] Sep 17 19:21:12 seneca vdr: [5170] SATIP#2 tuner thread started (pid=5159, tid=5170, prio=high) Sep 17 19:21:12 seneca vdr: [5159] new device number 4 (card index 4) Sep 17 19:21:12 seneca vdr: [5159] SATIP: Creating device CardIndex=3 DeviceNumber=3 [device 3] Sep 17 19:21:12 seneca vdr: [5173] SATIP#3 tuner thread started (pid=5159, tid=5173, prio=high) Sep 17 19:21:12 seneca vdr: [5169] device 2 section handler thread started (pid=5159, tid=5169, prio=low) Sep 17 19:21:12 seneca vdr: [5174] SATIP#3 section handler thread started (pid=5159, tid=5174, prio=high) Sep 17 19:21:12 seneca vdr: [5171] SATIP#2 section handler thread started (pid=5159, tid=5171, prio=high) Sep 17 19:21:12 seneca vdr: [5172] device 3 section handler thread started (pid=5159, tid=5172, prio=low) Sep 17 19:21:12 seneca vdr: [5175] device 4 section handler thread started (pid=5159, tid=5175, prio=low) ... other stuff Sep 17 19:21:12 seneca vdr: [5168] SATIP#1 section handler thread started (pid=5159, tid=5168, prio=high) Sep 17 19:21:13 seneca vdr: [5163] SATIP: Adding server '192.168.20.4|DVBS2-4|DIGIBIT-002F2A:SAT>IP' Bind: default Filters: none CI: no Quirks: SessionId,ForcePilot
However, when I set UpdateChannels = 5 to run channel full scan, all I get on devices 2 and 3 is
Sep 17 19:22:34 seneca vdr: [5170] SATIP-ERROR: Tuning timeout - retuning [device 2] Sep 17 19:22:34 seneca vdr: [5173] SATIP-ERROR: Tuning timeout - retuning [device 3]
over and over. What am I missing?
TIA!
Ciao, hm
Hi Harald!
On Sun, 17 Sep 2023 19:49:39 +0200 Harald Milz hm@seneca.muc.de wrote:
Hi all,
I recently got a stone-aged Digibit R1 to replace an even older PCI-E card.
[...] There is an alternative firmware for this box
https://github.com/perexg/satip-axe/blob/master/dist/README https://github.com/Jalle19/satip-axe/
Sep 17 19:22:34 seneca vdr: [5170] SATIP-ERROR: Tuning timeout - retuning [device 2] Sep 17 19:22:34 seneca vdr: [5173] SATIP-ERROR: Tuning timeout - retuning [device 3]
over and over. What am I missing?
I can't tell off hand, but maybe more debugging taps can help to narrow it down?
Torsten
Hi Torsten,
long time no hear! Good you're still around!
On Tue, Sep 19, 2023 at 10:43:01AM +0200, Torsten Duwe wrote:
There is an alternative firmware for this box
In fact I tried to boot satip-axe from a USB stick but for unknown reasons the box stuck to the original FW. :-(
After digging a bit more, it seems that the signal on the two cables coming from the Hotbird LNB is dead. Also, my other DVB-S2 card refuses to tune in on these cables. :-(
No idea why. But this would definitely explain these messages.
Sep 17 19:22:34 seneca vdr: [5170] SATIP-ERROR: Tuning timeout - retuning [device 2] Sep 17 19:22:34 seneca vdr: [5173] SATIP-ERROR: Tuning timeout - retuning [device 3]
Ciao, Harald
On Wed, 20 Sep 2023 10:09:29 +0200 Harald Milz hm@seneca.muc.de wrote:
In fact I tried to boot satip-axe from a USB stick but for unknown reasons the box stuck to the original FW. :-(
You must not partition the medium, but use it in "USB floppy disk mode". Put a fat32 on it, with idl4k.scr in the root dir, that should be enough to intercept the boot flow.
HTH, Torsten
On Thu, 21 Sep 2023 08:28:51 +0200 Torsten Duwe duwe@lst.de wrote:
On Wed, 20 Sep 2023 10:09:29 +0200 Harald Milz hm@seneca.muc.de wrote:
In fact I tried to boot satip-axe from a USB stick but for unknown reasons the box stuck to the original FW. :-(
You must not partition the medium, but use it in "USB floppy disk mode". Put a fat32 on it, with idl4k.scr in the root dir, that should be enough to intercept the boot flow.
Oh, and you have to use the *upper* USB-A receptacle, it seems.
HTH, Torsten