Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VU+ Duo 4k SE with 2x DVB-S2 FBC: Only First 8 Tuners (1 FBC) work #210

Open
foehlmann opened this issue Feb 5, 2024 · 51 comments
Open
Labels
Fixed Testers Wanted If like to help out, please test this

Comments

@foehlmann
Copy link

foehlmann commented Feb 5, 2024

Hello everyone,

I have the problem that only the first 8 tuners of my box work. I have a VU+ Duo 4k SE with 2x DVB-S2 FBC. The first 8 frontends work without any problems. But from number 9 onwards no packets are transmitted, no matter what settings I make. Does anyone have any tips? I have already checked out the latest source from Github and started cross compiled on the box.
Capture-2024-02-05-171101
Capture-2024-02-05-171123

@Barracuda09
Copy link
Owner

Hi @foehlmann

Thanks for you interest in SatPI.

I know of this problem, but have so far not come up with a solution. Issues #203 #187 seem to have (or look to have) the problem.

Unfortunately I can not test this myself, as I do not own this hardware.

@foehlmann
Copy link
Author

If you need a tester for that ☺️ feel free to contact me

@Barracuda09
Copy link
Owner

Could you try for frontend 9 to enable this (see image) and set Delay before write and Delay after write to 100:
image

@foehlmann
Copy link
Author

Unfortunately the same problem... 1-8 running, from 9 no packages.

image

@Barracuda09
Copy link
Owner

Which version do you use of SatPI (Home Page)

@foehlmann
Copy link
Author

1.6.2.146~g91dabfb

@Barracuda09
Copy link
Owner

That is quite an old version, which image are you using?

@foehlmann
Copy link
Author

OpenPLi 9.0-release (2023-12-27-release-9.0)

I had cross compiled an binary from the git today. That causes the same error 😒

@Barracuda09
Copy link
Owner

Barracuda09 commented Feb 5, 2024

Yes I know, but I was curious which image used on older SatPI version.

I honestly do not know at this point how to resolve this issue.

@Barracuda09
Copy link
Owner

What if you shutdown the box and switch it Off and On again?

@foehlmann
Copy link
Author

The same.

I have already considered reflashing an image and not configuring the tuners in Enigma at all. Do you have any recommendations on which image works best with SatPI?

@Barracuda09
Copy link
Owner

OpenPLi 9.0 should be ok.

Do you know how to replace the SatPI binary? So I can give you an test version?
So you can give me a log?

@foehlmann
Copy link
Author

Sure..

@Barracuda09
Copy link
Owner

could you try this version satpi_1.6.2.188~g19b05a3 Enigma(Debug).zip and give me the log of the startup of SatPI?

@foehlmann
Copy link
Author

foehlmann commented Feb 6, 2024

Starting satpi:/usr/bin/satpi: /usr/lib/libstdc++.so.6: version GLIBCXX_3.4.29' not found (required by /usr/bin/satpi) /usr/bin/satpi: /lib/libc.so.6: version GLIBC_2.34' not found (required by /usr/bin/satpi)

I think you are using some newer versions than the openpli 9 image

find /lib -iname "libc-*" /lib/libc-2.33.so

@Barracuda09
Copy link
Owner

Yes sorry with GCC12. Use this version satpi_1.6.2.188~g19b05a3 Enigma(Debug).zip

@foehlmann
Copy link
Author

/usr/bin/satpi: cannot execute binary file

need to leave for an appointment for about 1,5hrs .. will start later with that

@Barracuda09
Copy link
Owner

It is compiled with libdvbcsa, maybe you need to install that too?

@foehlmann
Copy link
Author

Thats installed:
libdvbcsa1 - 1.1.0-r0.0

@Barracuda09
Copy link
Owner

i assume it has the correct rights to execute the program?

@foehlmann
Copy link
Author

It has +x , yes.

If i try to start it direct without the init.d service:
./satpi: cannot execute binary file: Exec format error

@Barracuda09
Copy link
Owner

It is ARM cpu?

@foehlmann
Copy link
Author

processor	: 0
model name	: ARMv7 Processor rev 3 (v7l)
BogoMIPS	: 54.00
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm 
CPU implementer	: 0x42
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0x00f
CPU revision	: 3

processor	: 1
model name	: ARMv7 Processor rev 3 (v7l)
BogoMIPS	: 54.00
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm 
CPU implementer	: 0x42
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0x00f
CPU revision	: 3

processor	: 2
model name	: ARMv7 Processor rev 3 (v7l)
BogoMIPS	: 54.00
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm 
CPU implementer	: 0x42
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0x00f
CPU revision	: 3

processor	: 3
model name	: ARMv7 Processor rev 3 (v7l)
BogoMIPS	: 54.00
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm 
CPU implementer	: 0x42
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0x00f
CPU revision	: 3

@Barracuda09
Copy link
Owner

Strange... what does file ./satpi say

@foehlmann
Copy link
Author

Just flashed the box again... now your new binary works - and uses all tuners (the first 10 for now)

image

@Barracuda09
Copy link
Owner

could you give me the log of the startup of satpi or enable log to syslog and startup included

@foehlmann
Copy link
Author

foehlmann commented Feb 6, 2024

Enables log to syslog and started over:

Feb  6 15:09:08 vuduo4kse local1.info SatPI[26465]: [                           src/HttpServer.cpp:058] Setting up HTTP server
Feb  6 15:09:08 vuduo4kse local1.info SatPI[26465]: [                           src/RtspServer.cpp:048] Setting up RTSP server
Feb  6 15:09:09 vuduo4kse local1.info SatPI[26465]: [                     src/upnp/ssdp/Server.cpp:105] Setting up SSDP server with BOOTID: 14  annouce interval: 60 Sec  TTL: 1
Feb  6 15:09:10 vuduo4kse local1.info SatPI[26465]: [                    src/socket/SocketAttr.cpp:156] HTTP Connection from 192.168.1.192 Port 63653 with fd: 8
Feb  6 15:09:12 vuduo4kse local1.info SatPI[26465]: [                    src/socket/SocketAttr.cpp:156] HTTP Connection from 192.168.1.192 Port 63654 with fd: 9
Feb  6 15:09:12 vuduo4kse local1.info SatPI[26465]: [                    src/socket/SocketAttr.cpp:156] HTTP Connection from 192.168.1.192 Port 63656 with fd: 10
Feb  6 15:09:12 vuduo4kse local1.info SatPI[26465]: [                    src/socket/SocketAttr.cpp:156] HTTP Connection from 192.168.1.192 Port 63655 with fd: 11
Feb  6 15:09:12 vuduo4kse local1.info SatPI[26465]: [                    src/socket/SocketAttr.cpp:156] HTTP Connection from 192.168.1.192 Port 63657 with fd: 12
Feb  6 15:09:12 vuduo4kse local1.info SatPI[26465]: [                    src/socket/SocketAttr.cpp:156] HTTP Connection from 192.168.1.192 Port 63658 with fd: 13
Feb  6 15:09:13 vuduo4kse local1.info SatPI[26465]: [                     src/socket/TcpSocket.cpp:109] HTTP Client 192.168.1.192:63655 Connection closed with fd: 11
Feb  6 15:09:13 vuduo4kse local1.info SatPI[26465]: [                     src/socket/TcpSocket.cpp:109] HTTP Client 192.168.1.192:63653 Connection closed with fd: 8
Feb  6 15:09:13 vuduo4kse local1.info SatPI[26465]: [                     src/socket/TcpSocket.cpp:109] HTTP Client 192.168.1.192:63654 Connection closed with fd: 9
Feb  6 15:09:13 vuduo4kse local1.info SatPI[26465]: [                     src/socket/TcpSocket.cpp:109] HTTP Client 192.168.1.192:63658 Connection closed with fd: 13
Feb  6 15:09:13 vuduo4kse local1.info SatPI[26465]: [                     src/socket/TcpSocket.cpp:109] HTTP Client 192.168.1.192:63656 Connection closed with fd: 10
Feb  6 15:09:13 vuduo4kse local1.info SatPI[26465]: [                     src/socket/TcpSocket.cpp:109] HTTP Client 192.168.1.192:63657 Connection closed with fd: 12
Feb  6 15:09:14 vuduo4kse local1.info SatPI[26465]: [                    src/socket/SocketAttr.cpp:156] HTTP Connection from 192.168.1.192 Port 63659 with fd: 8
Feb  6 15:09:20 vuduo4kse local1.info SatPI[26465]: [                    src/socket/SocketAttr.cpp:156] HTTP Connection from 192.168.1.192 Port 63660 with fd: 9
Feb  6 15:09:20 vuduo4kse local1.info SatPI[26465]: [                    src/socket/SocketAttr.cpp:156] HTTP Connection from 192.168.1.192 Port 63662 with fd: 10
Feb  6 15:09:20 vuduo4kse local1.info SatPI[26465]: [                    src/socket/SocketAttr.cpp:156] HTTP Connection from 192.168.1.192 Port 63661 with fd: 11
Feb  6 15:09:20 vuduo4kse local1.info SatPI[26465]: [                    src/socket/SocketAttr.cpp:156] HTTP Connection from 192.168.1.192 Port 63664 with fd: 12
Feb  6 15:09:20 vuduo4kse local1.info SatPI[26465]: [                    src/socket/SocketAttr.cpp:156] HTTP Connection from 192.168.1.192 Port 63663 with fd: 13
Feb  6 15:09:22 vuduo4kse local1.info SatPI[26465]: [               src/input/dvb/delivery/FBC.cpp:104] Frontend 1:  Root 1  Index 0  Offset 0  Connected 0  Linked 0
Feb  6 15:09:22 vuduo4kse local1.info SatPI[26465]: [               src/input/dvb/delivery/FBC.cpp:104] Frontend 2:  Root 1  Index 1  Offset 0  Connected 0  Linked 1
Feb  6 15:09:22 vuduo4kse local1.info SatPI[26465]: [               src/input/dvb/delivery/FBC.cpp:104] Frontend 3:  Root 0  Index 2  Offset 0  Connected 0  Linked 1
Feb  6 15:09:22 vuduo4kse local1.info SatPI[26465]: [               src/input/dvb/delivery/FBC.cpp:104] Frontend 4:  Root 0  Index 3  Offset 0  Connected 0  Linked 1
Feb  6 15:09:22 vuduo4kse local1.info SatPI[26465]: [               src/input/dvb/delivery/FBC.cpp:104] Frontend 5:  Root 0  Index 4  Offset 0  Connected 0  Linked 1
Feb  6 15:09:22 vuduo4kse local1.info SatPI[26465]: [               src/input/dvb/delivery/FBC.cpp:104] Frontend 6:  Root 0  Index 5  Offset 0  Connected 0  Linked 1
Feb  6 15:09:22 vuduo4kse local1.info SatPI[26465]: [               src/input/dvb/delivery/FBC.cpp:104] Frontend 7:  Root 0  Index 6  Offset 0  Connected 0  Linked 1
Feb  6 15:09:22 vuduo4kse local1.info SatPI[26465]: [               src/input/dvb/delivery/FBC.cpp:104] Frontend 8:  Root 0  Index 7  Offset 0  Connected 0  Linked 1
Feb  6 15:09:23 vuduo4kse local1.info SatPI[26465]: [               src/input/dvb/delivery/FBC.cpp:104] Frontend 9:  Root 1  Index 8  Offset 8  Connected 9  Linked 0
Feb  6 15:09:23 vuduo4kse local1.info SatPI[26465]: [               src/input/dvb/delivery/FBC.cpp:104] Frontend 10:  Root 1  Index 9  Offset 8  Connected 9  Linked 1
Feb  6 15:09:23 vuduo4kse local1.info SatPI[26465]: [               src/input/dvb/delivery/FBC.cpp:104] Frontend 11:  Root 0  Index 10  Offset 8  Connected 9  Linked 1
Feb  6 15:09:23 vuduo4kse local1.info SatPI[26465]: [               src/input/dvb/delivery/FBC.cpp:104] Frontend 12:  Root 0  Index 11  Offset 8  Connected 9  Linked 1
Feb  6 15:09:23 vuduo4kse local1.info SatPI[26465]: [               src/input/dvb/delivery/FBC.cpp:104] Frontend 13:  Root 0  Index 12  Offset 8  Connected 9  Linked 1
Feb  6 15:09:23 vuduo4kse local1.info SatPI[26465]: [               src/input/dvb/delivery/FBC.cpp:104] Frontend 14:  Root 0  Index 13  Offset 8  Connected 9  Linked 1
Feb  6 15:09:23 vuduo4kse local1.info SatPI[26465]: [               src/input/dvb/delivery/FBC.cpp:104] Frontend 15:  Root 0  Index 14  Offset 8  Connected 9  Linked 1
Feb  6 15:09:23 vuduo4kse local1.info SatPI[26465]: [               src/input/dvb/delivery/FBC.cpp:104] Frontend 16:  Root 0  Index 15  Offset 8  Connected 9  Linked 1
Feb  6 15:09:23 vuduo4kse local1.info SatPI[26465]: [                src/decrypt/dvbapi/Client.cpp:545] Connection closed with Not connected
Feb  6 15:09:23 vuduo4kse local1.info SatPI[26465]: [                           src/Properties.cpp:074] Setting HTTP Port to: 8875
Feb  6 15:09:23 vuduo4kse local1.info SatPI[26465]: [                           src/Properties.cpp:081] Setting RTSP Port to: 554
Feb  6 15:09:23 vuduo4kse local1.info SatPI[26465]: [                           src/Properties.cpp:086] Setting WEB Path to: /usr/share/satpi/web
Feb  6 15:09:23 vuduo4kse local1.info SatPI[26465]: [                           src/Properties.cpp:090] Setting App Data Path to: /usr/bin

@foehlmann
Copy link
Author

Strange things happening: Now i have packets on all frontends, but cant get the tuner locked.. so no stream

@Barracuda09
Copy link
Owner

16 frontends at the same time?

What does top show?

@foehlmann
Copy link
Author

foehlmann commented Feb 6, 2024

About nothing on load.. seems like that there is no data to work on... cause it doesn't get a single lock.
But why it's counting packets if there is no lock 🙈

@Barracuda09
Copy link
Owner

That are "keep alive" packets, you can see that they will not increase that quickly.

But could you recap what is working like

  • Does only frontend 1 working?
  • Does only frontend 8 working?

@foehlmann
Copy link
Author

For now: It's not working... no lock on any frontend.
Until this morning the old version keeps running on frontend 1-8.

I replaced the binary again with the old one - no luck..
Can't think of anything that can cause this.
Rebooted, reset settings, ...

If i stop satpi and try locally on the receiver it tunes fine... lock on all channels.

@Barracuda09
Copy link
Owner

Did you enable Send DiSEqC Via Linked Root Tuner

@Barracuda09
Copy link
Owner

You need to update the web folder with current one of github

@foehlmann
Copy link
Author

Did you enable Send DiSEqC Via Linked Root Tuner

yes

@Barracuda09
Copy link
Owner

Barracuda09 commented Feb 6, 2024

Could you zip and post XML file http://192.168.1.13:8875/SatPI.xml (change to your Server IP)

@foehlmann
Copy link
Author

SatPI.xml.zip

@foehlmann
Copy link
Author

You need to update the web folder with current one of github

done that

@Barracuda09
Copy link
Owner

Could you give a beter "mental" picture of the connections which inputs is connected to which LNB (satelliet) So:

  • Tuner in slot A
    • Input A -> Which sat?
    • input B -> Which sat?
  • Tuner in slot B
    • Input A -> Which sat?
    • input B -> Which sat?

@foehlmann
Copy link
Author

Tuner in slot A
Input A -> Astra 19.2
input B -> None
Tuner in slot B
Input A -> None
input B -> None

@Barracuda09
Copy link
Owner

Ok, so no psychical connection to tuner in slot B

I see that you have for frontend 1:

  • Channel Freq (MHz) = 1210 (I assume this is SCR1 of JESS LNB)
  • Channel Slot (0-32) = 1 (Then this should be 0. So always subtract 1)

Please take a look at: https://github.com/Barracuda09/SATPI/wiki/Setup-Unicable-and-JESS

I am not sure if it is possible (at this point in SatPI) to connect Tuner Slot B software whise to Tuner Slot A - Input A. But I assume this works in Enigma2

@foehlmann
Copy link
Author

Ok, so no psychical connection to tuner in slot B

I see that you have for frontend 1:

  • Channel Freq (MHz) = 1210 (I assume this is SCR1 of JESS LNB)
  • Channel Slot (0-32) = 1 (Then this should be 0. So always subtract 1)

Please take a look at: https://github.com/Barracuda09/SATPI/wiki/Setup-Unicable-and-JESS

That was working in the old setup, strange - will correct that.

I am not sure if it is possible (at this point in SatPI) to connect Tuner Slot B software whise to Tuner Slot A - Input A. But I assume this works in Enigma2

Works fine in enigma2, yes. So probably an splitter would help me out?

@Barracuda09
Copy link
Owner

Ok, so no psychical connection to tuner in slot B
I see that you have for frontend 1:

  • Channel Freq (MHz) = 1210 (I assume this is SCR1 of JESS LNB)
  • Channel Slot (0-32) = 1 (Then this should be 0. So always subtract 1)

Please take a look at: https://github.com/Barracuda09/SATPI/wiki/Setup-Unicable-and-JESS

That was working in the old setup, strange - will correct that.

  • I am not sure this has changed over time

I am not sure if it is possible (at this point in SatPI) to connect Tuner Slot B software whise to Tuner Slot A - Input A. But I assume this works in Enigma2

Works fine in enigma2, yes. So probably an splitter would help me out?

  • Could you give a screen capture of how this setup is handled in Enigma.
  • Yes a splitter you could try, I give that a better chance.

@foehlmann
Copy link
Author

Feedback: With splitter everything is working fine. Can stream with all 16 Frontends 🙂

Maybe i just didn´t notice that it wasn´t working in enigma2 with just one cable? 😳
It´s not that common that i use more than 8 transponders at a time.

So with the version you send me, the issue is fixed for me.

@Barracuda09
Copy link
Owner

Hi @foehlmann

Thanks for the feedback, that is appreciated!

Could you try this version satpi_1.6.2.188~g19b05a3 Enigma.zip, it is a release version without debug info and should be a bit faster.

@foehlmann
Copy link
Author

@Barracuda09 sure, tomorrow 😊

If I change the version now, it will be the last thing I do. Then the TV will cut out for my wife... that's not good.

@foehlmann
Copy link
Author

I´ve replaced the binary. Let´s see how it goes today 🙂
Test in production environment ...

@Barracuda09
Copy link
Owner

Do you, by the way, use satipclient?

@foehlmann
Copy link
Author

foehlmann commented Feb 10, 2024

I'll try to... for now i'm using tvheadend + player on apple tv.

satipclient stutters ... i have just compiled your newest fork and moved the binary to a vuzero4k and give it a try.

Edit: Just found out my debian bookworm doesn't support older versions than gcc12... which leads to
version GLIBC_2.34 not found

@Barracuda09
Copy link
Owner

I use it on OpenPLi 9.0 which you can adjust vtuner for satipclient with a dialog. Which you can set for TCP mode.

How did you compile it?

@Barracuda09
Copy link
Owner

Barracuda09 commented Feb 10, 2024

Here is the bin I use for my vuzero4k satipclient.zip

I build it with stbgcc-8.3-0.4 see https://github.com/Barracuda09/SATPI/wiki/Cross-Compiling-SatPI

@Barracuda09 Barracuda09 changed the title Only 8 Tuners (1 FBC) works VU+ Duo 4k SE with 2x DVB-S2 FBC: Only First 8 Tuners (1 FBC) work Feb 29, 2024
@Barracuda09 Barracuda09 added Fixed Testers Wanted If like to help out, please test this labels Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fixed Testers Wanted If like to help out, please test this
Projects
None yet
Development

No branches or pull requests

2 participants