It was noticed many times on the forum that customers paste snapshots with missing Static parameters or with outdated values from previously connected batteries. It then requires continiously to ask them to reread values and to update screenshots. Such an extra interaction (explaining same thing hundreds of times) lead to extra hours in resolving the issues and is counterproductive way of support work. It eats the time on both sides. Mixing Static and Dynamic values from different batteries could even confuse support team to make wrong decisions and advices on resolving the issue.
So the feature request is to update Static parameters synchronously with Dynamic parameters reading (solution 1) or to update them in smart way when battery on the wire is changed (solution 2) to save some milliseconds on bus transactions.
Additional feature request is to make Smbus Chip Detection checkbox to be checked by default. It was noticed many customers not use this feature, which require additionally to spend the time on asking them to reread static values with switched On detection. Some of them continue to miss this request even after explanation.
If such a feature will be implemented, the buttons like "Read Static data", "Clear Static data" could be even removed from the GUI to save some space.
The side effect of reading Static Parameters together with Dynamic parameters is the waiting time needed for reading Static Parameters. If I want to monitor the cells voltage or the current in real-time then I have to wait every time to read the same values for Static Parameters. Maybe a new button Read All Parameters will be more comfortable, when it is pressed, all parameters will be read dynamic and static, so we can request on the forum: Read All Parameters in the first tab and the use should get it.
Related to the chip detection on SMBus option, I added the tick option because for some Maxim chips the SMBus communication could be lost and the user could get confused. It is true that the number of such cases it is reduced but that was my decision at the implementation time. I can enabled it by default but we will have the mentioned side effect.
I added the tick option because for some Maxim chips the SMBus communication could be lost and the user could get confused. It is true that the number of such cases it is reduced but that was my decision at the implementation time. I can enabled it by default but we will have the mentioned side effect.
I have a lot of MAXIM chips with different firmwares, i wiill test it and let you know.
I also think it's better to have SMbus detection enabled by default since we have to keep reminding this to users when analyzing issues.
The side effect of reading Static Parameters together with Dynamic parameters is the waiting time needed for reading Static Parameters
For straightforward implementation yes (solution 1 in first post), but smart synchronisation (solution 2) is free from this side-effect. It uses dynamic parameters fingerprints to check if battery on the wire is the same or not. Static parameters read only once when battery connected, then this group is skipped to save time on full read. As soon as fingerprint is changed (another battery connected) Static parameters updated in background one time.
Such approach used in our software and working like a charm. Me could help you with porting this solution from our app to NLBA1 project.
I prefer option one. Option 2 requires a good analysis, good test coverage, etc.
Feature added in NLBA1 version 3.5.4 https://www.laptopu.ro/community/nlba-pc-software-version-history/nlba-pc-software-revisions .
Latest Post: Asus A32F52 battery has 0V cell 3 voltage after replacing old cells Our newest member: Nazir Ahmed Khwaja Recent Posts Unread Posts
