I'm experimenting with the minisatip, but I have the issue that the scan does not find services (no signal)
I build the minisatip 0.5.58 on ubuntu 16.04 server with no issues.
I have a pctv DVB-S2 USB tuner. The tuner has been tested with different Sw and I verified that there is signal on the cable (Astra 28.2)
As a Client I use Elgato Sat>IP client on Android.
The issue is that I do not manage to get any services captured by the scan.
I attach a full verbose log
Any advice is welcome
Francesco
NO Signal with PCTV DVB-S2 Stick
NO Signal with PCTV DVB-S2 Stick
- Attachments
-
- logsatip.txt.zip
- (109.52 KiB) Downloaded 415 times
Re: NO Signal with PCTV DVB-S2 Stick
Hi,
this is what I see everywhere minisatip is trying to tune:
[31/08 17:05:46.809 main]: send_diseqc: FE_SET_TONE failed for fd 7: Bad address
[31/08 17:05:46.861 main]: send_diseqc: FE_DISEQC_SEND_MASTER_CMD committed failed for fd 7: Bad address
[31/08 17:05:46.946 main]: send_diseqc: FE_DISEQC_SEND_BURST failed for fd 7: Bad address
[31/08 17:05:46.961 main]: send_diseqc: FE_SET_TONE failed for fd 7: Bad address
When you say different software you mean on Linux (same OS as where you run minisatip) ?
Because this makes me thing it might be a driver issue.
this is what I see everywhere minisatip is trying to tune:
[31/08 17:05:46.809 main]: send_diseqc: FE_SET_TONE failed for fd 7: Bad address
[31/08 17:05:46.861 main]: send_diseqc: FE_DISEQC_SEND_MASTER_CMD committed failed for fd 7: Bad address
[31/08 17:05:46.946 main]: send_diseqc: FE_DISEQC_SEND_BURST failed for fd 7: Bad address
[31/08 17:05:46.961 main]: send_diseqc: FE_SET_TONE failed for fd 7: Bad address
When you say different software you mean on Linux (same OS as where you run minisatip) ?
Because this makes me thing it might be a driver issue.
Re: NO Signal with PCTV DVB-S2 Stick
Hi Cata,
No when I mention different Sw, I mean a a different program executed on a different OS, Windows.
In relation to the Driver, I can see the device when I give the command lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 001 Device 003: ID 13d3:3410 IMC Networks
Bus 001 Device 002: ID 2013:024c PCTV Systems
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
and from dmsg:
[ 3.020492] usb 1-1: New USB device found, idVendor=2013, idProduct=024c
[ 3.025423] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.030306] usb 1-1: Product: PCTV 460e
[ 3.035499] usb 1-1: Manufacturer: PCTV Systems
[ 3.040368] usb 1-1: SerialNumber: 00000010YWUF
...
[ 9.972450] em28xx: New device PCTV Systems PCTV 460e @ 480 Mbps (2013:024c, interface 0, class 0)
[ 9.972456] em28xx: DVB interface 0 found: isoc
[ 9.972524] em28xx: chip ID is em28174
...
[ 10.313012] em28174 #0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x436222f8
[ 10.313016] em28174 #0: EEPROM info:
[ 10.313019] em28174 #0: microcode start address = 0x0004, boot configuration = 0x01
[ 10.319948] em28174 #0: No audio on board.
[ 10.319952] em28174 #0: 500mA max power
[ 10.319955] em28174 #0: Table at offset 0x39, strings=0x1aa0, 0x14ba, 0x1ace
[ 10.320099] em28174 #0: Identified as PCTV DVB-S2 Stick (460e) (card=80)
[ 10.320103] em28174 #0: dvb set to isoc mode.
...
[ 10.320168] usbcore: registered new interface driver em28xx
...
[ 10.863600] em28174 #0: Binding DVB extension
No when I mention different Sw, I mean a a different program executed on a different OS, Windows.
In relation to the Driver, I can see the device when I give the command lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 001 Device 003: ID 13d3:3410 IMC Networks
Bus 001 Device 002: ID 2013:024c PCTV Systems
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
and from dmsg:
[ 3.020492] usb 1-1: New USB device found, idVendor=2013, idProduct=024c
[ 3.025423] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.030306] usb 1-1: Product: PCTV 460e
[ 3.035499] usb 1-1: Manufacturer: PCTV Systems
[ 3.040368] usb 1-1: SerialNumber: 00000010YWUF
...
[ 9.972450] em28xx: New device PCTV Systems PCTV 460e @ 480 Mbps (2013:024c, interface 0, class 0)
[ 9.972456] em28xx: DVB interface 0 found: isoc
[ 9.972524] em28xx: chip ID is em28174
...
[ 10.313012] em28174 #0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x436222f8
[ 10.313016] em28174 #0: EEPROM info:
[ 10.313019] em28174 #0: microcode start address = 0x0004, boot configuration = 0x01
[ 10.319948] em28174 #0: No audio on board.
[ 10.319952] em28174 #0: 500mA max power
[ 10.319955] em28174 #0: Table at offset 0x39, strings=0x1aa0, 0x14ba, 0x1ace
[ 10.320099] em28174 #0: Identified as PCTV DVB-S2 Stick (460e) (card=80)
[ 10.320103] em28174 #0: dvb set to isoc mode.
...
[ 10.320168] usbcore: registered new interface driver em28xx
...
[ 10.863600] em28174 #0: Binding DVB extension
Re: NO Signal with PCTV DVB-S2 Stick
Just to give some more details:
the Usb tuner is directly connected to the LNB, no DISEQ devices in between t support multiple dishes,
the Usb tuner is directly connected to the LNB, no DISEQ devices in between t support multiple dishes,
Re: NO Signal with PCTV DVB-S2 Stick
Problem Solved.
The issue was that I was missing a firmware file specific for the 460E.
The funny thing is that the firmware controls only some specific functionalities (as DISEQC), but the device itself was recognized OK by Linux and by the minisatip.
Thanks Anyway for the quick reply.
The MiniSatIP software look to work well and is quick in the channel change, very low load of the processor.
I'll provide updates on my test.
The issue was that I was missing a firmware file specific for the 460E.
The funny thing is that the firmware controls only some specific functionalities (as DISEQC), but the device itself was recognized OK by Linux and by the minisatip.
Thanks Anyway for the quick reply.
The MiniSatIP software look to work well and is quick in the channel change, very low load of the processor.
I'll provide updates on my test.