From SW coder standpoint:
- you have program's variables with initial value (usually 0, but it's your choice - the problem is to distinguish in other routines the init value from a result of reading into it)
- you have reading results, where is your program must make a decision: good data or a return from cmd is not correct or missing; usually (I don't know for batteries) data from DUT have bit/byte (what say ERROR) what would tell you if the data have meaning of just empty values.
It would be not easy to deduct all the points from just a screenshot ... especially if you don't know what part of the log corresponding to different cmds.
Probably you wanted to say "From a beginner coder".
Actually, there are not enough colors and messages to show warnings, errors, sentences, novels in NLBA1 software to satisfy all customers. If you don't believe me just try it.
Probably you wanted to say "From a beginner coder".
Actually, there are not enough colors and messages to show warnings, errors, sentences, novels in NLBA1 software to satisfy all customers. If you don't believe me just try it.
I couldn't agree more. Users want a software flashing like a disco ball with the colors of the rainbow where they press one button and the magic happens. A professional can diagnose the core of the problem straight from the dynamic data page for less than a minute. No need to flood a perfectly working software with garbage data.
Not necessary to make personal attacks here, we are talking professionally. If not, then continue flaming posters.
Lets Make NLBA Great ! Together.
You did not paste all parameters.
These were pasted only parameters that looks valid and so could be confused.
Well, BatStatus, Design Capacity and FCC could be added to the list. They typically reported as zeros for many original Dell batteries which is locked.
For any user, it should be clear that there is a communication issue
No, not for any. This topic proves it, otherwise customer did not ask the question.
Its clear for experienced customer but not for newbie.
As far as I know,
Exactly, you know, but someone new to battery world could not know this.
Error says temp is out of limits while actual issue is loss of communication at all which is confusing for NEWBIES customers.
Check ManufacturerName, DeviceName
Yes, they missing. Same way should be displayed all other parameters if battery is not detected. Then its pretty clear something wrong with connection not with a sensor.
Or they were read as 0?
For Smbus nothing read and zero values read is completely different things.
The idea around this discussion was to add proper error handling so even not experienced users could understand what is the issue.
You did not paste all parameters.
These were pasted only parameters that looks valid and so could be confused.
When you read a report you need to read, analyze and interpret it completely.
Well, BatStatus, Design Capacity and FCC could be added to the list. They typically reported as zeros for many original Dell batteries which is locked.
See above comment.
For any user, it should be clear that there is a communication issue
No, not for any. This topic proves it, otherwise customer did not ask the question.
Are you 100% sure the customer would have been understood the error message ? Maybe he would complain about the color of the message...
Its clear for experienced customer but not for newbie.
Newbies have to learn. As I already said in another topic, adding more and more and more messages maybe will help maybe not. Maybe it adds more confusion maybe not. One thing is sure, I will never ever satisfy all customers.
As far as I know,
Exactly, you know, but someone new to battery world could not know this.
Error says temp is out of limits while actual issue is loss of communication at all which is confusing for NEWBIES customers.
At the end of the day, this is a device that requires minimum know-how (electronics) to operate. More, that's why I created a forum, to offer support. As in this topic, the customer got the response faster and I am pretty sure he learned a lot (at least I hope:)). NLBA1 is not just software, it is a complete solution, hardware + software + support. We can look at the overall product and I would say that the forum fixed many issues which are missing/gaps in the Software.
Check ManufacturerName, DeviceName
Yes, they missing. Same way should be displayed all other parameters if battery is not detected. Then its pretty clear something wrong with connection not with a sensor.
Or they were read as 0?
In the Battery Information when a battery is not connected the textboxes are not populated. In the Reset Tab, there are no textboxes, there is simple text. I used default values. I can add the check and print a message but this will not fix our "newbie" issues. I prefer to answer questions and help customers on forum, in this way they have a good chance to understand better the battery world.
Are you 100% sure the customer would have been understood the error message ?
Me 100% sure that message "Battery not detected" is much accurate describe actual issue then "Reset disabled due to temp out of limit" so its more understandable.
As in this topic, the customer got the response faster
At least he spent a time to connect 5 batteries to get same error, then he spent a time to register on a forum and ask a question, then wait a time until we responded.
Is it a faster then getting proper response just on first connected battery by correct error message?
As in this topic, the customer got the response faster
At least he spent a time to connect 5 batteries to get same error, then he spent a time to register on a forum and ask a question, then wait a time until we responded.
Is it a faster then getting proper response just on first connected battery by correct error message?
Yes, it is faster and it is according to the recommendations, to use the forum to get support. There is nothing planned to be implemented.
If I would be the coder of NBLA software, the issue would be fixed same day. I give up to see any change in SW what is not in Nicusor's minds. Same time as a customer who paid for the device with SW, I'm willing to post my opinions and suggestions, not counting how many times I did offer my help in coding ...
If you have a suggestion use the right category. Posts that are not related to this topic could be deleted.
You paid for a device and for the software that was released at that moment. You did not pay for improvements.
There is nothing planned to be implemented
This answer was expected.
Sometimes Its frustrating that constructive critics or suggestions completely refused.
There is nothing planned to be implemented
This answer was expected.
Sometimes Its frustrating that constructive critics or suggestions completely refused.
If you have a suggestion then post it in the right section. I didn't "completely refused", I said "nothing planned", add it into the right category and I will analyze it.
Since all updates are free, what and when they will be implemented cannot be guaranteed. More, after checking the software history I can see that almost every month a new release was made: 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
