[vdr-plugin-satip] this and that

Thank you Rolf for the great work!

I cannot see an issue at all in the syslog that concerns me, by using the Octopus Net.

But for most of the users around the Octopus Net isn't an option. because of price.

Is there one chap around to run a test drive with a Zinwell ZM-1800 clone, like the the Kathrein EXIP 414. Schwaiger MS41IP 031, Triax TSS-400, MegaSat SAT>IP Server
or the Elgato EyeTV Netstream (looks like a ZM-1800 clone, but with two USB ports on the back).

Even it would be great to see the syslog output generated by the latest Inverto Firmware v 1.17.0.120.

3PO would it be possible to you, to upgrade the firmware?

This is just a hope that Zinwell and Inverto not using the the same hardware and firmware.

Kind regards

Zitat von SED9

[...] 3PO would it be possible to you, to upgrade the firmware? ...

Sure, If you can tell me, where i can get a new FW.

HERE i can find only V 1.16.0.120.

Zitat von SED9

Even it would be great to see the syslog output generated by the latest Inverto Firmware v 1.17.0.120.

3PO would it be possible to you, to upgrade the firmware?

This is just a hope that Zinwell and Inverto not using the the same hardware and firmware.

I tested 1.17.0.120 with Telestar Digibit and the Upgrade does not solve anything. All Inverto based Devices are using the same firmware. I flashed the Inverto rom to the Digibit.

glotzipapa: Wie ich sehe, hast du sat>ip auch auf der Himbeere. Hast du dort vtunerc/sat>ip installiert? Ich komme hier mit dem aktuellen kernel-3.12.35 das Modul nicht lauffähig.... Eventuell hättest du einen Tipp?!

Aktuell benutzte ich das Satip-Plugin (steht auch in meiner Sig). Vor Version 1.0.0 habe ich vtuner benutzt, geht auch, erzeugt aber deutlich höhere Last und geht nur Overclocked. Fragen zu vtuner sind hier aber Offtopic.

Thanks for the new version. Is it possible to run two boxes somehow? With 8 Devices? Or that's possible but I do not know how?

Regards

Hi,

Zitat von zwick der agent

Thanks for the new version. Is it possible to run two boxes somehow? With 8 Devices? Or that's possible but I do not know how?

Give it a try:

cp libvdr-satip.so.VERSION libvdr-satip2.so.VERSION
-Psatip -Psatip2

That could do the job, just a stupid thinking.

Kind regards

Without this now to try I do not think it works.

Satip plugin has new options:

satip (1.0.0) - SAT>IP Devices


  -d <num>, --devices=<number>  set number of devices to be created
  -s <ipaddr>|<model>|<desc>, --server=<ipaddr1>|<model1>|<desc1>;<ipaddr2>|<model2>|<desc2>
                                define hard-coded SAT>IP server(s)

You can use -s with more then one satip server.

Many thanks for the reply, I 'll try it

EDIT: WORKS!!

Regards

Just tried to build 1.0.0 against vdr-2.1.6 but get an error when compiling:

g++ -g -O3 -Wall -Werror=overloaded-virtual -Wno-parentheses -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c -DPLUGIN_NAME_I18N='"satip"' -DUSE_TINYXML -I/usr/local/src/vdr-2.1.6/include  -o socket.o socket.c
socket.c: In member function ‘int cSatipSocket::ReadMulti(unsigned char*, unsigned int*, unsigned int, unsigned int)’:
socket.c:145: error: elements of array ‘mmsghdr mmsgh [(((unsigned int)(((int)elementCountP) + -0x00000000000000001)) + 1)]’ have incomplete type
socket.c:145: error: storage size of ‘mmsgh’ isn't known
socket.c:158: error: ‘recvmmsg’ was not declared in this scope
make[1]: *** [socket.o] Fehler 1

Did anyone else get this error? Might be related to TinyXML, I'll try with PugiXML next...

EDIT:
Not related to TinyXML, getting the same error with PugiXML. Here some additional info, next guess: building 32bit on a 64bit system?

# gcc -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.4.5-8' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.4 --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-targets=all --with-arch-32=i586 --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
Thread model: posix
gcc version 4.4.5 (Debian 4.4.5-8) 
# uname -a
Linux nas 3.4.6 #1 SMP Sat Nov 1 00:24:36 CST 2014 x86_64 GNU/Linux

Hi,

i just received a Triax TSS400 and tried the satip plugin. I used the lastest version(1.0.0) and vdr 2.1.6.
Sady to say but i don´t get a picture. Not shur if it is a misconfiguration or just not working.
The SatIP Serve ris found by the plugin as active server, with the yellow "Devices" button it show 4 devices, with card index, has lock strenght and quality but i don´t get a picture.
Log says:

Dec 30 21:15:20 vdr: [10682] SATIP: Malfunctioning 'Triax SatIP Converter' server detected! Please, fix the firmware.
Dec 30 21:15:34 vdr: [10686] SATIP-ERROR: Detected invalid status code 454: rtsp://192.168.0.66/ [device 1]
Dec 30 21:15:34 vdr: [10686] SATIP-ERROR: Pid update failed - retuning [device 1]
Dec 30 21:15:34 vdr: [10686] SATIP-ERROR: Detected invalid status code 454: rtsp://192.168.0.66/ [device 1]
Dec 30 21:15:34 vdr: [10686] SATIP-ERROR: Connect failed [device 1]
Dec 30 21:15:34 vdr: [10599] [softhddev]GrabImage: 0, 1, 80, 729x480
Dec 30 21:15:35 vdr: [10686] SATIP-ERROR: Detected invalid status code 454: rtsp://192.168.0.66/ [device 1]
Dec 30 21:15:35 vdr: [10686] SATIP-ERROR: Connect failed [device 1]
De

Do i have to set any spcial configuration? I didn`t change sources.conf or channels.conf

UPDATE: Configured sources.conf, now it is working

Regards

Well, you need sell your TSS400 on Ebay and buy a working device, or fix the plugin to include all the required workarounds for your Triax. However, I've heard that the vTuner/satip driver would work with that device, so I recommend to use that solution at the moment.

Is it really that crappy? For now it is running fine (sources.conf was the issue), but i can still send the receiver back if there is be bedder supported one with similar price..

Zitat von Razorblade

Just tried to build 1.0.0 against vdr-2.1.6 but get an error when compiling:

Please, verify that you'll have kernel version 2.6.33 or greater and a proper header file (sys/socket.h) for it containing the recvmmsg() syscall.

Zitat von bolzerrr

Is it really that crappy? For now it is running fine (sources.conf was the issue), but i can still send the receiver back if there is be bedder supported one with similar price..

It's really working fine? Have a look into the syslog on channel switch. Are there any curl errros? The OctopusNet ist the only known working device with the satip-plugin until now.

The only error i get is: Dec 30 22:22:24 vdr: [16814] SATIP: Malfunctioning 'Triax SatIP Converter' server detected! Please, fix the firmware.
But i get this all the time not only on channel switch.

One thing not working yet: I configured satip with 4 devices, all are recognized but i cannot stream (streamdev) from different transponders. The triax shows that he tuned the other channel, looking fine but picture stays black. Log: Dec 30 22:25:46 vdr: [16813] SATIP: Detected 3 RTP packet errors [device 1]
Ocassionally even this is working, but i couldn´t find out yet why. Output on tv isn`'t touched by this and running stable for the moment.

Zitat von bolzerrr

The only error i get is: Dec 30 22:22:24 vdr: [16814] SATIP: Malfunctioning 'Triax SatIP Converter' server detected! Please, fix the firmware.
But i get this all the time not only on channel switch.

Interesting, which firmware version is running on the triax?

Zitat von rofafor

Please, verify that you'll have kernel version 2.6.33 or greater and a proper header file (sys/socket.h) for it containing the recvmmsg() syscall.

I'm running Kernel 3.4.6 (as per supplied "uname -a" output) and have the appropriate Kernel sources as well as some standard Debian header packages (2.6.32 and 3.2.0). But wouldn't <sys/socket.h> include /usr/include/sys/socket.h which is supplied by libc6 rather than kernel headers?

Edit: /usr/include/sys/socket.h contains recvmsg

extern ssize_t recvmsg (int __fd, struct msghdr *__message, int __flags);

but not recvmmsg.

Edit2:

The recvmmsg() system call was added in Linux 2.6.33.  Support in glibc was added in version 2.12.

Debian Squeeze uses 2.11, so I'm on a dead-end here. For now I'd suggest to update the requirements to demand 2.6.33 and glibc 2.12

@bolzerrr

What was the problem with the sources.conf?

Regards