LNB Unicable II Inverto 5520 setup

[Peter M]

I am running the OpenBH 5.6 image on a VU+ Solo 4K. After connecting the Unicable II LNB Inverto 5520 (IDLU‑32L412‑UNBRR‑OPN) to the LNB1 (Tuner A) input, the receiver operates correctly only when Tuner A is configured in Simple mode.
When I switch Tuner A to Advanced mode and configure it for Unicable/JESS (see attached configuration), the system boots normally, but after a full system restart the tuner is able to lock only a single transponder — 12.012 GHz (vertical). All other transponders fail to tune.
This behavior indicates that the tuner is not sending EN50607 (Unicable II / JESS) commands to the LNB.
I have tested multiple User Bands (UBs), including UB5 (984 MHz) and others, but the result is identical in all cases.

 

[Peter M]

I'm back after a while.

I tested this configuration - LNB Unicable II Inverto 5520 and Vu+ Solo 4K.

I tested the LNB Unicable II Inverto 5520 (IDLU-32L412-UNBRR-OPN) connected with a single coax cable (up to 20 m) to the Vu+ Solo 4K receiver (multiboot image – OpenBH 5.6 008, OpenBH 5.5 or OpenATV 7.6). The satellite cable was connected to the LNB1 port A. The cable to LNB2 port B was not connected.
A detailed description of the configuration and test procedure can be found in the attached document.

The Inverto 5520 works correctly in simple (legacy) mode. The problem occurs when the Inverto 5520 is set to extended Unicable II mode. After a cold reboot of the receiver (power disconnected for 15–30 seconds) and reconnecting the power supply, not all channels work. After some time, only a single transponder becomes available — specifically the one corresponding to the channel that was selected after the reboot.

After replacing the receiver with a Vu+ Uno 4K SE (image 5.6 008), all channels work correctly. The cabling and tuner configuration remained exactly the same.

In this tested setup, the issue is clearly caused by the Vu+ Solo 4K. I honestly did not expect that.

So where exactly did the error occur?

Any idea?