stustunz Wrote:im a dumb ass sorry for wasting your time
i was putting in 11200 instead of 11300 bugger it i cant believe i didnt pick up on it
No worries, glad you worked it out.
Ah sweet vindication ...this job can be pretty frustrating when people are sure you're wrong, so its nice when things sort themselves out without GB-PVR being at fault.
Well I can now scan channels using the SimpleA DisEqc setting.
After much pulling of my hair out I noticed the config.xml was ignoring my LNB setting for the DisEqc. The following line: <BDATwinhanDiseqcMethod>1</BDATwinhanDiseqcMethod> would not change from 1 (DisEqc A?) despite my changes using the config gui. So I manually changed it to "5" hoping this corresponds to "SimpleA" and that worked, I can scan hundreds of channels!
I'm not yet certain the "SimpleB" is working for my second sat (dp twin lnb). I am able to scan channels but I am not sure if they are from the same sat or the second sat...
.
HTPC Server: AMD Athlon XP 3200+, 768Mb RAM, Gigabyte 6200 AGP, Hauppauge 500MCE Capture Tuner, WinXP Pro SP3 (concurrent users), NPVR 2.5.9 Client1: PCH A110 Client2: AMD Opteron 2.6Ghz, 2Gb DDR, ATI 1650, WinXP Pro SP3, NPVR 2.5.9Client3: Intel E6420, 2Gb RAM, XFX Radeon HD 7850, WinXP Pro SP3, NPVR 2.5.9Client 4: Intel E2120, 4Gb DDR2, Nvidia 7600GS, Vista SP1 32-bit, NPVR 2.5.9
observer_11 Wrote:Well I can now scan channels using the SimpleA DisEqc setting.
After much pulling of my hair out I noticed the config.xml was ignoring my LNB setting for the DisEqc. The following line: <BDATwinhanDiseqcMethod>1</BDATwinhanDiseqcMethod> would not change from 1 (DisEqc A?) despite my changes using the config gui. So I manually changed it to "5" hoping this corresponds to "SimpleA" and that worked, I can scan hundreds of channels!
I'm not quite sure what is happen when you set it to "5". The only valid values are 0,1,2. I think "5" will force it to make no attempt to contro a diseqc switch.
"0" uses the old deprecated Twinhan method.
"1" uses the new Twinhan method.
"2" sends raw diseqc commands
sub Wrote:I'm not quite sure what is happen when you set it to "5". The only valid values are 0,1,2. I think "5" will force it to make no attempt to contro a diseqc switch.
"0" uses the old deprecated Twinhan method.
"1" uses the new Twinhan method.
"2" sends raw diseqc commands
:confused:
I don't understand, the config gui has six different possible diseqc settings A,B,C,D,SimpleA,and SimpleB and there are only 3 valid values in the config.xml? I am missing something basic... does the diseqc setting in the config gui correspond to another line in the config.xml?
.
HTPC Server: AMD Athlon XP 3200+, 768Mb RAM, Gigabyte 6200 AGP, Hauppauge 500MCE Capture Tuner, WinXP Pro SP3 (concurrent users), NPVR 2.5.9 Client1: PCH A110 Client2: AMD Opteron 2.6Ghz, 2Gb DDR, ATI 1650, WinXP Pro SP3, NPVR 2.5.9Client3: Intel E6420, 2Gb RAM, XFX Radeon HD 7850, WinXP Pro SP3, NPVR 2.5.9Client 4: Intel E2120, 4Gb DDR2, Nvidia 7600GS, Vista SP1 32-bit, NPVR 2.5.9