Thanks for following up with the added information, I think that would be helpful to ignore the bad/unexpected data. In my case active sampling is not required to throw the error.
Regarding the USB error, we have seen this vary from PC to PC. The error is shown when the device receives un-expected data on the USB bus. (For e.g. we check for all zeros, all ones, all constant data, sync pattern error etc ) We will check if we can improve the error correction by skipping the samples in error and just letting the users know this information by appending the log file. That way the GUI does not stop working, but continues to collect the data. If the user looks at the log file, they would know that there was an error at a certain time of the data. If possible, we would show this on the chart as well to indicate that the measurement during a certain time period may have erroneous data.
Thanks for the followup. I'll run down the hardware issues you listed, but I don't think those are the root cause. That said, I'll try moving to a different system and see if there is a difference.
Regarding the battery, I'm using somewhat generic LiPo's out of Shenzhen, so the data sheets are not always complete. I'll look forward to the Spreadsheet, hopefully it will have a LiPo example in it.
Regarding the USB error, does it occur during the data collection or when it is idling and just analyzing the data?
We have seen the error mostly in slow laptops, USB slot with loose contact, front panel USB connectors on a desktop, a bad USB cable, or very noisy environment. Can you rule out any of these?
We will look into the error in the Viewer and get back in couple of days. It should be an easy error to fix. We are able to get the viewer to work without the hardware. So there should be some settings needed.
Regarding the addition of a new model, please refer to the user guide. It details the method to model any battery. You only need 4 key parameters for the battery which can be easily found from the datasheet. If you have a particular model in mind, please share it here. we can extract the model and post is online so that others may also benefit.
In the coming week, we would share an excel sheet which will make it easy to model any battery. That should work fine for most users.
Note that we have moved to Github for all new releases and bug reports. That way, the data is preserved till eternity and it is far more easier to keep track of versions. You may report issues also on github.
Awesome - thanks!
We have added an excel sheet to the github which allows users to create their own battery models from the battery datasheets.
Thanks for following up with the added information, I think that would be helpful to ignore the bad/unexpected data. In my case active sampling is not required to throw the error.
Regarding the USB error, we have seen this vary from PC to PC. The error is shown when the device receives un-expected data on the USB bus. (For e.g. we check for all zeros, all ones, all constant data, sync pattern error etc ) We will check if we can improve the error correction by skipping the samples in error and just letting the users know this information by appending the log file. That way the GUI does not stop working, but continues to collect the data. If the user looks at the log file, they would know that there was an error at a certain time of the data. If possible, we would show this on the chart as well to indicate that the measurement during a certain time period may have erroneous data.
Thanks for the followup. I'll run down the hardware issues you listed, but I don't think those are the root cause. That said, I'll try moving to a different system and see if there is a difference.
Regarding the battery, I'm using somewhat generic LiPo's out of Shenzhen, so the data sheets are not always complete. I'll look forward to the Spreadsheet, hopefully it will have a LiPo example in it.
I'll move to GitHub for issues from here on out.
Regarding the USB error, does it occur during the data collection or when it is idling and just analyzing the data?
We have seen the error mostly in slow laptops, USB slot with loose contact, front panel USB connectors on a desktop, a bad USB cable, or very noisy environment. Can you rule out any of these?
We will look into the error in the Viewer and get back in couple of days. It should be an easy error to fix. We are able to get the viewer to work without the hardware. So there should be some settings needed.
Regarding the addition of a new model, please refer to the user guide. It details the method to model any battery. You only need 4 key parameters for the battery which can be easily found from the datasheet. If you have a particular model in mind, please share it here. we can extract the model and post is online so that others may also benefit.
In the coming week, we would share an excel sheet which will make it easy to model any battery. That should work fine for most users.
Note that we have moved to Github for all new releases and bug reports. That way, the data is preserved till eternity and it is far more easier to keep track of versions. You may report issues also on github.
Please find the link below