Awesome - thanks!

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.

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.

@ZSCircuits Support Thanks for the response. I updated to 2.7.1 and that seems to have somewhat reduced but not eliminated the issue. It still crashes but less often. The USB connection looks solid, I'll try switching to a different system and see if that helps. I did try running the viewer app but it also won't operate without connecting to the hardware, so no real difference and at this point I can't make it past the license process to get the viewer to work. When I hit the connect key I get a dialog box that says the device model is not found and then it can't access what it needs off of the USB key, and then throws a .Net error. This seems a little silly as the Power Profiler app launches and works, so clearly it can see the model and key data. Suggestions?

Folks, I recently got my ZS-1100-A and have to say the measurement capability is really impressive. I do have some feedback regarding an issue I'm having as well as a question. I am having issues with repeated errors that cause the software to immediately exit (see image). This error is happening frequently and repeatedly and I am hoping there are some procedures to debug this behavior or a work-arounds. Is there a particular class of PC that is needed to keep this app from crashing due to the error? Either way I think it would be beneficial if the UI worked for displaying and reviewing session date without need to connect to the ZS-1100-A as it is only when I connect that the app error occurs. The question I have is around the default battery Model library. I can not find any reference to LiPo batteries in the model library. As there are multiple obscure parameters to input for a new battery model, it would be great if you guys could post a sample LiPo config or point us at a place to get these model parameters. Thanks!

Folks, I recently got my ZS-1100-A and have to say the measurement capability is really impressive. I do have some feedback regarding an issue I'm having as well as a question. I am having issues with repeated errors that cause the software to immediately exit (see image). This error is happening frequently and repeatedly and I am hoping there are some procedures to debug this behavior or a work-arounds. Is there a particular class of PC that is needed to keep this app from crashing due to the error? Either way I think it would be beneficial if the UI worked for displaying and reviewing session date without need to connect to the ZS-1100-A as it is only when I connect that the app error occurs. The question I have is around the default battery Model library. I can not find any reference to LiPo batteries in the model library. As there are multiple obscure parameters to input for a new battery model, it would be great if you guys could post a sample LiPo config or point us at a place to get these model parameters. Thanks!

Hi Folks, Thanks for the quick response. Glad to hear that compatibility to standard banana posts was the goal. I would really love it if there was an upgrade path - might there be an option for those of us with the current unit to buy the panel face from the next build?

I'm wondering why the jack spacing on the ZS-1100-A is just off from standard BNC to dual-banana jacks - see attached image . I use these on all of my bench supplies and DVM and have an array of cables and clips I can use with them. Unless this discrepancy was intentional, it would be great if this could be addressed on the next hardware rev.