Scan speed versus sensitivity
Re: Scan speed versus sensitivity
Sounds like the best way to go
Ian
Ian
Re: Scan speed versus sensitivity
There appears to be a bug in the latest v3 version of this firmware that is causing me to get an error when uploading a code plug.
It is also causing any changes I make to VFO-B to not be saved permanently and is affecting at least one other normal channel even when pressing sk2 along with the green button.
The v2 version doesn't seem to have this issue.
It is also causing any changes I make to VFO-B to not be saved permanently and is affecting at least one other normal channel even when pressing sk2 along with the green button.
The v2 version doesn't seem to have this issue.
Re: Scan speed versus sensitivity
I just retested the V3 file, and I can save bot VFO A and B e.g.KI5GZK wrote: ↑Tue Mar 30, 2021 6:13 pmThere appears to be a bug in the latest v3 version of this firmware that is causing me to get an error when uploading a code plug.
It is also causing any changes I make to VFO-B to not be saved permanently and is affecting at least one other normal channel even when pressing sk2 along with the green button.
The v2 version doesn't seem to have this issue.
Select VFO mode
Select VFO B
Set 145Mhz
Turn off radio
Turn on radio
VFO B is still displayed and reads 145Mhz
Repeat for 146Mhz
Value of 146Mhz is shown OK
Repeat for VFO A
Still works OK
Select VFO A
Set 144 Mhz
Select VFO B
Select 431Mhz
Select VFO A
Confirmed 144Mhz is displayed
Select VFO B
Confirmed 431Mhz is displayed
Power cycled the radio
Both VFO's still show 144 and 431Mhz as expected
Re: Upload problems
Changes to reduce the excessive current consumption of the radio prior to the eco modes, required changes to the CPS
If you didn't update your CPS recently, it would fail occasionally during uploads
See
https://github.com/rogerclarkmelbourne/ ... S/releases
Re: Scan speed versus sensitivity
There does seem to be some potential problem the the VFOs when the settings are reset.
My radio now sets VFO A to 0.000Mhz when I reset the settings, which is obviously a bug.. Which I will investigate.
Edit.
Umm.
Some of my radios seem to have this problem, but not all. Very odd.
My radio now sets VFO A to 0.000Mhz when I reset the settings, which is obviously a bug.. Which I will investigate.
Edit.
Umm.
Some of my radios seem to have this problem, but not all. Very odd.
Re: Scan speed versus sensitivity
I just installed the March 2nd CPS software and flashed the v4 firmware and I still cannot upload any of my code plugs into my GD-77.
The error occurs when writing to the eeprom.
I am also still having problems with VFO-B. I can change the frequency and then turn the radio off and then back on, and it reverts back to the previous frequency.
If I flash the v2 release there are no problems with uploading a code plug or VFO-B.
So I am at a loss to explain why you cannot duplicate this issue.
My radio also has the problem you just mentioned with VFO-A when I reset it.
The error occurs when writing to the eeprom.
I am also still having problems with VFO-B. I can change the frequency and then turn the radio off and then back on, and it reverts back to the previous frequency.
If I flash the v2 release there are no problems with uploading a code plug or VFO-B.
So I am at a loss to explain why you cannot duplicate this issue.
My radio also has the problem you just mentioned with VFO-A when I reset it.
Re: Scan speed versus sensitivity
Can you try this version
https://github.com/rogerclarkmelbourne/ ... 253_v5.zip
There seems to be some problems with reading the VFO data from the EEPROM.
At the moment I'm not sure why the VFO should have this problem and not the rest of the settings, but I've rolled back a change which speeded up one of the internal bus data speeds and I think this has resolved the EEPROM problem.
Albeit, I think I will need to increase the speed again, and try to understand why the VFO bug exists at these higher speeds
https://github.com/rogerclarkmelbourne/ ... 253_v5.zip
There seems to be some problems with reading the VFO data from the EEPROM.
At the moment I'm not sure why the VFO should have this problem and not the rest of the settings, but I've rolled back a change which speeded up one of the internal bus data speeds and I think this has resolved the EEPROM problem.
Albeit, I think I will need to increase the speed again, and try to understand why the VFO bug exists at these higher speeds
Re: Scan speed versus sensitivity
I just installed v5 and it appears to have solved the issues. I am able to flash my code plugs now, and the problems with both VFO's also appear to be resolved. Resetting my radio didn't reset VFO-A like it did before.
Looks like you found the culprit.
Thank you.
Looks like you found the culprit.
Thank you.
Re: Scan speed versus sensitivity
Well, I did find the culprit, but I'm not entirely sure why the EEPROM speed setting needs to be 1/10 th of the max speed setting, according to its data sheet, for the EEPROM to work correctlyKI5GZK wrote: ↑Wed Mar 31, 2021 2:34 amI just installed v5 and it appears to have solved the issues. I am able to flash my code plugs now, and the problems with both VFO's also appear to be resolved. Resetting my radio didn't reset VFO-A like it did before.
Looks like you found the culprit.
Thank you.
Re: Scan speed versus sensitivity
Don’t forget that we have seen before that some radios had EEPROMs that were slow to write. We had to add the code to wait until the write was completed. Maybe speeding up the bus has caused the write to fail again.
Colin.
Colin.