Device Setup Bug

[kylebrophy]

Hi There,

Have been doing a bit of testing of this beta and have found the following:

nPVR doesnt save the device setup if the LOF Switch is set to 0.

For the diseq multiswitch i use - the LOF Switch value will be either 0 or 22000.

Optus D1 in my case is 10700 / 22000 / 10700 - this does save and i can scan successfully

Optus D2 in my case is 10700 / 0 / 10700 - this never saves and never scans successfully.

nPVR effectively wipes all those settings and when i next go into the device setup again - everything is 11300 / 11300 / 11300 (note the LOF Switch is 11300).

Also i cant seem to get nPVR to save multiple satellites when i use the diseq 1.x A/B/C/D under type specific settings.

Hope this helps others - maybe just test the parameters under the single lnb option - and wait for the next build maybe for this to be resolved

So far this is the only major issue ive found.

[Jaggy]

Have been doing a bit of testing of this beta and have found the following:
nPVR doesnt save the device setup if the LOF Switch is set to 0.

Optus D2 in my case is 10700 / 0 / 10700 - this never saves and never scans successfully.

nPVR effectively wipes all those settings and when i next go into the device setup again - everything is 11300 / 11300 / 11300 (note the LOF Switch is 11300).

I mentioned the not saving the settings during beta testing but didn't realise it was only when the LOF is set to "0" that it happens as I only have one Lnb, but I was able to scan successfully it was only when I went back into the settings it had changed.

[kylebrophy]

I mentioned the not saving the settings during beta testing but didn't realise it was only when the LOF is set to "0" that it happens as I only have one Lnb, but I was able to scan successfully it was only when I went back into the settings it had changed.

ok thanks.

have also found that when have the lnb types set to either 22khz A/B or the diseq 1.1 A/B/C/D - it only saves the parameters for the Satellite A (and even then only if LOF switch not 0).

If you try to put any data into the other 3 remaining satellites - the data will never save back to the database - ive confirmed this by using SQLLite Spy and querying the table concerned before and after making changes in device setup.

[sub]

This patch should fix it (on today's 1.5.21 release).

[DanielP]

Hi,

i haven't got DISEQC to behave so far on my Nova S2, even with the new version posted today. The scan doesn't seem to behave (lots of missed transponders), then when it seems to find something, I get crash.

I'll post logs when I get upstairs again.

The other card S350 is working like a dream on the new version.

Daniel

[sub]

Hi,

i haven't got DISEQC to behave so far on my Nova S2, even with the new version posted today. The scan doesn't seem to behave (lots of missed transponders), then when it seems to find something, I get crash.

If you get crashes, post the crash.mdmp and I'll take a look. For missing transponders, check its scanning the frequency/symbolrate/polarity - the .ini files may not be correct.

[kylebrophy]

This patch should fix it (on today's 1.5.21 release).

thanks for this... the diseq settings now hold.

however still cant scan the other satellites for some reason.

in the log ive found the following when i try to scan C1

as you will see it does have signal strength which must mean its getting sumwhere??