luismgh
Vu+ Newbie
Hi there,
I'm having a problem with my VU+ Duo in what concern to scan channels.
I already have an extensive channel list with almost all satellites that can be viewed in Portugal.
My system is a motorised dish with an actuator and a quad lnb. Both tuners are connected, tuner A in advanced mode and tuner B in simple mode (Hispasat 30º W). The tuner A receives signal bypassed by an external positioner that receives signal from the actuator and converts them in diseq signal.
Everything is fine in what concern to view channels that are already present in the channel list but when i try to choose to scan (update) the entire satellite (ex, Astra 19º E) the VU+ tell me that "nothing to scan. Please review tuner config and try again". If i choose to scan single transponder instead of full satelite it takes a few seconds and say that "0 channels found" even when i know that there is new channels on that transponder.
I've changed nothing in the configs since this problem appeared.
Anyone with a clue to solve this problem?
Can a firmware update bypass this issue?
Regards from Portugal
I'm having a problem with my VU+ Duo in what concern to scan channels.
I already have an extensive channel list with almost all satellites that can be viewed in Portugal.
My system is a motorised dish with an actuator and a quad lnb. Both tuners are connected, tuner A in advanced mode and tuner B in simple mode (Hispasat 30º W). The tuner A receives signal bypassed by an external positioner that receives signal from the actuator and converts them in diseq signal.
Everything is fine in what concern to view channels that are already present in the channel list but when i try to choose to scan (update) the entire satellite (ex, Astra 19º E) the VU+ tell me that "nothing to scan. Please review tuner config and try again". If i choose to scan single transponder instead of full satelite it takes a few seconds and say that "0 channels found" even when i know that there is new channels on that transponder.
I've changed nothing in the configs since this problem appeared.
Anyone with a clue to solve this problem?
Can a firmware update bypass this issue?
Regards from Portugal