progdvb.com

problem with signal detectoin from diseq and LOF 1 , LOF 2 , switch
iam used lifeview dvbs the problem in diseq and LOF 1 , LOF 2 , switch in Default mode problem in arabsat 3A and hotbird with
12520 v 27500 3/4 not detection
12692 H 27500 3/4 not detection

problem with
LOF 1 : 9750 MHz

Switch : 11700 MHz

LOF 2 : 10600 MHz
plz help my and thank you

when change Switch : 11700 MHz to Switch : 11600 MHz some freq work but not all
this not work
12520 v 27500
12654 H 27500
12692 H 27500
not work on hotbird
befor this change ch no. on hotbird 1730 after 1827 ch

When using devices with WDM drivers, you can set the switch value to any value between 11550 and 11900 MHz, without losing anything, as the bands overlap in that region.

For BDA devices, things may differ, as those rely on tuning space registry entries (and perhaps more), and ProgDVB may use but not change them.

So, if you're systematically losing transponder on each other than the default switch value, simply don't try.
Perhaps the original software can set that, but ProgDVB obviously can't.


BTW, PC based DVB-S applications and devices don't detect DiSEqC, that would be part of DiSEqC 2.x, and require special hardware.
Regarding LOF values, those have to reproduce true LNB hardware parameters (that normally are to be found on it's label and specs). If an LNB is not aligned properly by it's manufacturer, or deviates by temperature, the entries can be corrected by you. But this would then effect all frequencies on the band, the LOF is used for.
Defaults are made for standard European equipment, suit 99+ % therefore, over here.


Hotbird 12520V is working fine here.
But that frequency can be suffering from DECT or celluar phone services AFAIK.
Calculate transponder frequency minus LOF, for the frequency, that's used on the LNB cable and DVB tuner.

Rergarding arabsat, no idea.
I don't understand Klingonian, that's why I don't even think about pointing an LNB there to.
Lingual and mental limitations of mine...

Juergen wrote:When using devices with WDM drivers, you can set the switch value to any value between 11550 and 11900 MHz, without losing anything, as the bands overlap in that region.

For BDA devices, things may differ, as those rely on tuning space registry entries (and perhaps more), and ProgDVB may use but not change them.

So, if you're systematically losing transponder on each other than the default switch value, simply don't try.
Perhaps the original software can set that, but ProgDVB obviously can't.


BTW, PC based DVB-S applications and devices don't detect DiSEqC, that would be part of DiSEqC 2.x, and require special hardware.
Regarding LOF values, those have to reproduce true LNB hardware parameters (that normally are to be found on it's label and specs). If an LNB is not aligned properly by it's manufacturer, or deviates by temperature, the entries can be corrected by you. But this would then effect all frequencies on the band, the LOF is used for.
Defaults are made for standard European equipment, suit 99+ % therefore, over here.


Hotbird 12520V is working fine here.
But that frequency can be suffering from DECT or celluar phone services AFAIK.
Calculate transponder frequency minus LOF, for the frequency, that's used on the LNB cable and DVB tuner.

Rergarding arabsat, no idea.
I don't understand Klingonian, that's why I don't even think about pointing an LNB there to.
Lingual and mental limitations of mine...

thank you but
Hotbird 12520V is working fine here (yes work but quality:is low 5 %
my dvb card BDA LIFEVIEW LR:300
iam try Twinhan 1027 but not good loss in signal very high temperature but the remote control work good with progdvb and the same problem with diseqc