Eco Levels
Re: FYI. Battery power saving
Scanning and Dual watch need the CPU and the Rx constantly, so the Eco level is currently disabled for those operations
I may be able to make Dual Watch operate with the Eco Levels system, but it would almost certainly be pointless for scanning, as the scanning speed would be about 20 times slower on Level 4. Even Level 1 would require the scan speed would need to be a lot slower.
I may be able to make Dual Watch operate with the Eco Levels system, but it would almost certainly be pointless for scanning, as the scanning speed would be about 20 times slower on Level 4. Even Level 1 would require the scan speed would need to be a lot slower.
Re: FYI. Battery power saving
Hi Roger!VK3KYY wrote: ↑Sun Feb 07, 2021 9:40 pmI have now fixed the Hotspot bug, I think
Also, there have been some changes to reduce the number of different levels from 10 to 4.
With level 4 now being the same as the old level 8
https://github.com/rogerclarkmelbourne/ ... 080837.zip
Unfortunately, this version doesn't boot on my GD77. Nothing happens after power-on. Reflashing the previous version works. Tested two-times, it really doesn't work.
With regards / 73, Pavel
Re: FYI. Battery power saving
Values are approximately...
Battery fully charged.
No backlight
Wait time is the time since the last signal was received or last key was pressed, before the radio activates power saving
Latency is the average time to detect a signal
Code: Select all
Level Wait time(secs) Current (mA) Latency (ms)
0 N/A 62 N/A
1 10 40 320
2 8 33 420
3 6 27 600
4 4 23 900
No backlight
Wait time is the time since the last signal was received or last key was pressed, before the radio activates power saving
Latency is the average time to detect a signal
Re: FYI. Battery power saving
I there was a problem with one of my uploads.
The latest is this one
https://github.com/rogerclarkmelbourne/ ... 080859.zip
I re-tested it, and the file in that zip is now OK
The latest is this one
https://github.com/rogerclarkmelbourne/ ... 080859.zip
I re-tested it, and the file in that zip is now OK
Re: FYI. Battery power saving
Thank you, Roger,VK3KYY wrote: ↑Mon Feb 08, 2021 5:27 amI there was a problem with one of my uploads.
The latest is this one
https://github.com/rogerclarkmelbourne/ ... 080859.zip
I re-tested it, and the file in that zip is now OK
yes, this version boots properly.
73, Pavel
Re: FYI. Battery power saving
BTW. I still need to do the voice prompt for this menu, but I need to post the translation files first and get all the language translations, as it takes ages to process the VP files and I don't want to keep having to release a new VP version every time I get another translation
-
- Posts: 43
- Joined: Sun Nov 24, 2019 12:10 pm
Re: FYI. Battery power saving
So far everything normal.
Re: FYI. Battery power saving
I've done some more analysis and the official firmware somehow seems to achieve even lower current demand than I have so far been able to replicate
I'm trying to track down what the official firmware is doing.
It looks like its something to do with the C6000 chip, and that chip is used for both DMR and FM.
I'm trying to track down what the official firmware is doing.
It looks like its something to do with the C6000 chip, and that chip is used for both DMR and FM.
Re: FYI. Battery power saving
Anyway, amazing progress so far. This work is really appreciated, you are saving thousands of hours of battery lifes in the future. Thanks for that.
Please, will you also document what impact will some eco levels have? E.g. why and when not to use even level 1 etc...
Please, will you also document what impact will some eco levels have? E.g. why and when not to use even level 1 etc...
Re: FYI. Battery power saving
I will document the impact in the User Guide, but this work is far from complete.
I discovered yesterday when comparing the current consumption pulses taken by the official Radioddity firmware and the OpenGD77, that the official firmware takes 20% less currently.
I took many more readings when running the official firmware, trying different modes and different frequency bands, to try to see any variation in the current pulses, but I could not find anything that conclusively proved why the official firmware was much better.
I now need to solder several more test points onto a GD77 which is now just a PCB, without a case etc, to attempt to monitor some more of the internal control signals between the CPU and the C6000 and the RF sections etc, in an attempt to understand how the official firmware achieves the lower current usage.
However, this is probably several days of work, because even soldering the wires onto the QFP 80 pin devices is exceedingly difficult.