Hi,
I'm wondering if there is any way to trace down locking errors on that driver modules.
There are two muxes on Hispasat 30°W on 11491 V (CLM) and 11496 H (TVA) that use physical layer scrambling (PLS). When entering the right PLS code I can lock both on windows using crazyscan.
However on linux using the tbsdtv tree or crazycats linux_media tree I can lock CLM but TVA fails with the same HW. I tried both TBS 5980 (stv090x driver) and TBS 6903 (stv0910 driver) and the behavior between is exactly the same.
The muxes use similar parameters, 8psk, fec 8/9 only difference is the symbolrate and CLM has pilots off while TVA has pilots on.
So how can I trace / debug the locking procedure?
I'm wondering if there is any way to trace down locking errors on that driver modules.
There are two muxes on Hispasat 30°W on 11491 V (CLM) and 11496 H (TVA) that use physical layer scrambling (PLS). When entering the right PLS code I can lock both on windows using crazyscan.
However on linux using the tbsdtv tree or crazycats linux_media tree I can lock CLM but TVA fails with the same HW. I tried both TBS 5980 (stv090x driver) and TBS 6903 (stv0910 driver) and the behavior between is exactly the same.
The muxes use similar parameters, 8psk, fec 8/9 only difference is the symbolrate and CLM has pilots off while TVA has pilots on.
So how can I trace / debug the locking procedure?
Category: Computer and USB Satellite Receivers and Recording
