VU+ Uno 4K SE with FBC DVB-C tuner and TVHeadend

[LITUATUI]

Hi everyone.

Just out of curiosity, has anyone found the "perfect" configuration for this setup?

Sometimes the SAT>IP server works fine for a whole day, sometimes it only works for a few hours. This happens with both SATPI and MiniSatIP servers.

My setup:

• VU+ Uno 4K SE with FBC DVB-C tuner
• OpenPLI (development builds)
• MiniSatIP (latest version)
• TVHeadend + Cloudflared (docker compose in a N100 mini PC)

Then I export the m3u file on TVHeadend and use it in different IPTV players. The problem is that I have to restart the Enigma2 receiver when the SAT>IP server fails (no longer detects tuners).

Disabling Enigma2 with init 4 command doesn't help.

Can the VU+ Uno 4K SE receiver with FBC DVB-C tuner be used to make a stable SAT>IP server? Thanks!

After a few hours I get the "No tuner found/active" error:

[catalinii]

Can you upload a log?
./minisatip -f -l http,dvb

[LITUATUI]

Sure, want me to stop logging when the "no tuner" error appears? It's gonna be a long log :)

[catalinii]

Yes

[LITUATUI]

The full log is here, only 31 MB :D

The SAT>IP tuners are no longer available, but TVHeadend continues to work fine with the USB tuners that I have directly connected to the N100 mini PC.

[catalinii]

[19/07 22:38:12.713 main]: BW 7627 KB/s, DMX 7605 KB/s, Buffered 0.6 MB, Dropped: 0.0 MB, ns/read 312, r: 148, w: 181 fw: 0, tt: 46 ms, memory 43 MB
[19/07 22:38:14.475 main]: BW 10264 KB/s, DMX 10237 KB/s, Buffered 1.7 MB, Dropped: 0.0 MB, ns/read 432, r: 149, w: 185 fw: 0, tt: 64 ms, memory 43 MB
[19/07 22:38:16.763 main]: BW 3973 KB/s, DMX 3963 KB/s, Buffered 0.4 MB, Dropped: 0.0 MB, ns/read 398, r: 65, w: 118 fw: 0, tt: 25 ms, memory 43 MB
[19/07 22:38:18.866 main]: BW 8 KB/s, DMX 0 KB/s, Buffered 0.0 MB, Dropped: 0.0 MB, ns/read 0, r: 1, w: 56 fw: 0, tt: 0 ms, memory 43 MB
[19/07 22:38:21.233 main]: BW 10 KB/s, DMX 0 KB/s, Buffered 0.0 MB, Dropped: 0.0 MB, ns/read 0, r: 1, w: 73 fw: 0, tt: 0 ms, memory 33 MB
[19/07 22:38:23.728 main]: BW 11 KB/s, DMX 0 KB/s, Buffered 0.0 MB, Dropped: 0.0 MB, ns/read 0, r: 1, w: 81 fw: 0, tt: 0 ms, memory 33 MB
[19/07 22:38:26.191 main]: BW 9 KB/s, DMX 0 KB/s, Buffered 0.0 MB, Dropped: 0.0 MB, ns/read 0, r: 1, w: 66 fw: 0, tt: 0 ms, memory 33 MB

Also this:

[19/07 22:38:10.969 main]: BW 10301 KB/s, DMX 9639 KB/s, Buffered 1.6 MB, Dropped: 0.0 MB, ns/read 284, r: 194, w: 268 fw: 0, tt: 55 ms, memory 43 MB
[19/07 22:38:12.713 main]: BW 7627 KB/s, DMX 7605 KB/s, Buffered 0.6 MB, Dropped: 0.0 MB, ns/read 312, r: 148, w: 181 fw: 0, tt: 46 ms, memory 43 MB
[19/07 22:38:14.475 main]: BW 10264 KB/s, DMX 10237 KB/s, Buffered 1.7 MB, Dropped: 0.0 MB, ns/read 432, r: 149, w: 185 fw: 0, tt: 64 ms, memory 43 MB
[19/07 22:38:16.213 AD6]: no data sent for more than 1s sid: 1 for 192.168.0.100:54154
[19/07 22:38:16.213 AD3]: no data sent for more than 1s sid: 4 for 192.168.0.100:46014
[19/07 22:38:16.213 AD5]: no data sent for more than 1s sid: 2 for 192.168.0.100:40400
[19/07 22:38:16.313 AD7]: no data sent for more than 1s sid: 0 for 192.168.0.100:39518
[19/07 22:38:16.414 AD4]: no data sent for more than 1s sid: 3 for 192.168.0.100:39982
[19/07 22:38:16.763 main]: BW 3973 KB/s, DMX 3963 KB/s, Buffered 0.4 MB, Dropped: 0.0 MB, ns/read 398, r: 65, w: 118 fw: 0, tt: 25 ms, memory 43 MB
[19/07 22:38:17.215 AD6]: no data sent for more than 1s sid: 1 for 192.168.0.100:54154
[19/07 22:38:17.315 AD5]: no data sent for more than 1s sid: 2 for 192.168.0.100:40400
[19/07 22:38:17.315 AD3]: no data sent for more than 1s sid: 4 for 192.168.0.100:46014
[19/07 22:38:17.416 AD7]: no data sent for more than 1s sid: 0 for 192.168.0.100:39518
[19/07 22:38:17.416 AD4]: no data sent for more than 1s sid: 3 for 192.168.0.100:39982
[19/07 22:38:18.217 AD6]: no data sent for more than 1s sid: 1 for 192.168.0.100:54154
[19/07 22:38:18.317 AD3]: no data sent for more than 1s sid: 4 for 192.168.0.100:46014
[19/07 22:38:18.317 AD5]: no data sent for more than 1s sid: 2 for 192.168.0.100:40400
[19/07 22:38:18.418 AD7]: no data sent for more than 1s sid: 0 for 192.168.0.100:39518
[19/07 22:38:18.418 AD4]: no data sent for more than 1s sid: 3 for 192.168.0.100:39982
[19/07 22:38:18.866 main]: BW 8 KB/s, DMX 0 KB/s, Buffered 0.0 MB, Dropped: 0.0 MB, ns/read 0, r: 1, w: 56 fw: 0, tt: 0 ms, memory 43 MB

I went thru the logs and there is nothing happening before (just a tune and adding some pids) but no errors on any ioctls.

minisatip can also work with enigma (to use enigma to pull the stream from there).
./minisatip -N -s dvbc:localhost:8554 -s ... -s ..

can u reproduce the issue that way ? if yes, maybe ask support from enigma2 folks, to get some support from VU related to the drivers.

[LITUATUI]

Thanks. I'll test it, but I can say that if I stream directly from Enigma2 (without a SAT>IP software as a middleman) I have no problem with tuners getting offline. The problem with tuners getting offline also happens with SATPI, not only MiniSatIP.

When streaming directly from Enigma2, I do get into a different and well-known problem, I get audio and video out of sync on the IPTV player of my Android TV box.

[LITUATUI]

I must be doing something stupid...

root@vuuno4kse:~# /usr/bin/minisatip -R /usr/share/minisatip/html -N -s dvbc:localhost:8554 -s dvbc:localhost:8554 -s dvbc:localhost:8554 -s dvbc:localhost:8554 -s dvbc:localhost:8554 -s dvbc:localhost:8554 -s dvbc:localhost:8554 -s dvbc:localhost:8554 [21/07 14:41:15.149 main]: Listening configuration RTSP:192.168.0.4:554 (bind address: (null)), HTTP:192.168.0.4:8080 (bind address: (null)) root@vuuno4kse:~#

[catalinii]

If enigma2 does not break, play with -1 argument (try each option and let me know)

[LITUATUI]

No luck.

I see TVHeadend trying all 8 tuners, one by one, but no valid response from the SAT>IP server.

Also tried to play a stream directly from MiniSatIP, without luck.

mpv http://192.168.0.4:8080/?freq=354&sr=6900&msys=DVBC&mtype=256qam&pids=1611,1618,1612,1613,0,1,1610,17,16

[LITUATUI]

Just changed the port from 8554 to 554:

Command line: /usr/bin/minisatip -R /usr/share/minisatip/html -N -s dvbc:localhost:554 -s dvbc:localhost:554 -s dvbc:localhost:554 -s dvbc:localhost:554 -s dvbc:localhost:554 -s dvbc:localhost:554 -s dvbc:localhost:554 -s dvbc:localhost:554

Still no image, but it seems that now MiniSatIP can access the tuners...

[catalinii]

I meant try:
./minisatip -f -l http -1 0 ….
./minisatip -f -l http -1 1 ….
./minisatip -f -l http -1 2 ….
./minisatip -f -l http -1 3 ….
With enigma2 stopped

[LITUATUI]

So far so good, running for 16 hours now with Enigma2 off (init 4) and this command:

/usr/bin/minisatip -R /usr/share/minisatip/html -f -l http -1 0

If it crashes I'll try the next mode (-1 1).

[LITUATUI]

Almost 22 hours now and still going. I think we can conclude that the mode "-1 0" with Enigma2 disabled is stable with the FBC DVB-C tuner.

@catalinii is there any advantage in trying other modes? I don't mind testing things for the community.

I still get a lot of continuity errors, probably because I'm using TVHeadend on docker inside a LXC in Proxmox... Next step is to try TVHeadend installed on my OpenWRT router or Amlogic TV Box with CoreELEC.

The dropped MBs happen when streaming more than 2 channels on the same frequency/tuner. It's probably a limitation of the FBC tuner regarding PIDs.

[catalinii]

I think it depends on which mode works for you.

Try to see if other modes work better for you and if CC is specific to the mode that you use or no.

buffered and dropped are a network congestion issue.

[LITUATUI]

Thanks @catalinii

Mode 0 is stable for 36 hours now, but I'm going to try the other modes just out of curiosity.

I'll also try to solve the network problems by installing TVHeadend natively (without containers) on other machine.

[LITUATUI]

Found out that I can only scan channels on TVHeadend with mode 2 and 3, otherwise most frequencies fail.

DeepSeek recommends to use mode 2.

Still not sure if I should enable "Full mux RX mode supported" on TVHeadend or not.

[Jimbo888888]

I solved the problem differently. I set the receiver to restart every morning at 4:00 a.m. and then go directly into standby mode. Since then, I've had no problems with inactive tuners. I have OpenATV (latest version) installed.

[LITUATUI]

Nice to know. What's your receiver and tuner?

[Jimbo888888]

Hello. Its an Vu+ UNO 4K SE and DVBS2X Tuner.

[LITUATUI]

We have the same machine :)

You can try MiniSatIP with "mode 0" and Enigma2 disabled (init 4), it's very stable.

/usr/bin/minisatip -R /usr/share/minisatip/html -1 0

If you want to check the log:

/usr/bin/minisatip -R /usr/share/minisatip/html -f -l http -1 0 > /tmp/minisat_mode_0.log

Next step is to try MuMuDVB and use multicast.

[LITUATUI]

More tests.

I tried the mode 2 to be able to scan channels on TVHeadend, but eventually the whole system crashes.

Fortunately, the mode 0 is super stable, so I'll only use mode 2 temporarily when need to scan channels.

[MartB]

Yeah mode 2 seems to be causing issues here too, do you have the crash message per chance?

[LITUATUI]

I'm now testing mode 1 with enigma2 enabled, it's running stable for more than a day now.

I'll try mode 2 again - with and without enigma2 enabled - later this weekend and deliver a log.

[catalinii]

For me on gigablue the default works, but other modes lead to continuity errors

[MartB]

Which one do you have? My UE 4k crashes with the default mode (Kernel oops causes by some ioctl proxying crap) Mode 0 works fine but causes significantly higher CPU usage.

[LITUATUI]

@catalinii Further testing results.

While both mode 0 (dvrX device ) and mode 1 (demuxX device) are extremely stable, I now get a lot less CC errors on mode 1. I didn't even disable enigma2.

Right now it seems that the mode 1 (demuxX device) is the best for VU+ receivers with FBC tuners.