SW ver 2.3.4. When I try to zoom out for more than 14 seconds the top chart goes black. It happens in Acquisition tab as well as in Profiling tab. It happens also when moving the coarse time to the right
Please advise how can I see the graph beyond 14 sec.
We recommend to perform the profiling after the acquisition is completed. With this you can see the graph beyond 14 sec. Upto 20 seconds is possible in one view. Beyond that you can use the slider bar to move across in time.
please acquire and wait for acquisition to stop by pressing the STOP button. Then the session can be zoomed in and out without any issues.
We are checking out the screen going blank. It looks like if you load the same session and try to view it as it is getting written to the disk, the problem arises.
Please use a different session name for each capture so that the other session can be viewed.
Also note that in order to view the session, you would need to go to the Sessions Tab and load the session which was captured. Without this, the older session would be displayed.
Or else, you may enable the Auto Load Session checkbox in the acquisition tab. This will automatically load the last captured session.
Whenever I start a new capture, when it is completed, the proofing displays both voltage/current at the top window, but in the detailed view there is no way to view the voltage.
Also it always captures D0 and D1 as digital input channels. How can I enable this when nothing is connected to those channels (and how enable more than those 2 if needed)?
The middle window is to view the current waveform only as the voltage waveform has very limited information (it remains mostly constant during the capture).
We would add this as an option in the coming release. Thanks for pointing this out.
For the digital capture you could click on multiple IO as shown above and all of them would be displayed on the screen. Please select them in the right order. For e.g. select all between D0 and D3..
All 8 bits are captured in all captures. Only the 2 bits are shown by default to reduce the screen clutter.
Even if you have nothing connected on the Digital IO, it still captures all zeros.
Just for your info, I am using a real system with its battery as power source. Because of that, during radio TX, my voltage drops due to the high current demand out of the battery.
The IoT power profiler is an amazing tool since it actualy shows the voltage drop.
So it does contain very usefull info...
Or I am using this in a non-intended way and I should not connect non-constant voltage sources....
Or you have discovered another great usage feature of the device!
As for the digital capture, I run this tool on a older laptop (i7) and it kind of struggles. So my idea was to give the laptop a break and limit the stored data when not using the digital inputs.
But, good to know that it captures them anyway. I assume that the compression gets rid of all that data if nothing is connected since it is a constant '0' value.
For constant digital data, the file size is very small. May be few kB per minute. On the i7, how much of the CPU % is taken by the GUI. We test it on a very old laptop with core i3 processor which runs at 1.8GHz and it still manages to run though.
You could select the slow PC option from the Acquisition tab as it reduces some graphics updates during the capture. This can help with very slow processors.
Regarding the voltage display, it is shown only in the top chart as of now. It can be easily added to the middle chart and we would add that for the next release.
We thank you for your valuable feedback. Great to know that the tool is useful for you.
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.
@anglercircuits Can you update the latest GUi from github. It has some fixes for this problem. The issue is mostly from a loose USB connector on the laptop or desktop. It could also be due to signal integrity issues on the port.
To view the files, there is a IOT power viewer software included in the package. Please run this to view the files without the hardware.
@anglercircuits Can you update the latest GUi from github. It has some fixes for this problem. The issue is mostly from a loose USB connector on the laptop or desktop. It could also be due to signal integrity issues on the port.
To view the files, there is a IOT power viewer software included in the package. Please run this to view the files without the hardware.
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.
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.
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.
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, 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 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.
SW ver 2.3.4. When I try to zoom out for more than 14 seconds the top chart goes black. It happens in Acquisition tab as well as in Profiling tab. It happens also when moving the coarse time to the right
Please advise how can I see the graph beyond 14 sec.
Thank you
Hello,
We recommend to perform the profiling after the acquisition is completed. With this you can see the graph beyond 14 sec. Upto 20 seconds is possible in one view. Beyond that you can use the slider bar to move across in time.
please acquire and wait for acquisition to stop by pressing the STOP button. Then the session can be zoomed in and out without any issues.
We are checking out the screen going blank. It looks like if you load the same session and try to view it as it is getting written to the disk, the problem arises.
Please use a different session name for each capture so that the other session can be viewed.
Also note that in order to view the session, you would need to go to the Sessions Tab and load the session which was captured. Without this, the older session would be displayed.
Or else, you may enable the Auto Load Session checkbox in the acquisition tab. This will automatically load the last captured session.
Whenever I start a new capture, when it is completed, the proofing displays both voltage/current at the top window, but in the detailed view there is no way to view the voltage.
Also it always captures D0 and D1 as digital input channels. How can I enable this when nothing is connected to those channels (and how enable more than those 2 if needed)?
The middle window is to view the current waveform only as the voltage waveform has very limited information (it remains mostly constant during the capture).
We would add this as an option in the coming release. Thanks for pointing this out.
For the digital capture you could click on multiple IO as shown above and all of them would be displayed on the screen. Please select them in the right order. For e.g. select all between D0 and D3..
All 8 bits are captured in all captures. Only the 2 bits are shown by default to reduce the screen clutter.
Even if you have nothing connected on the Digital IO, it still captures all zeros.
Great feedback.
Just for your info, I am using a real system with its battery as power source. Because of that, during radio TX, my voltage drops due to the high current demand out of the battery.
The IoT power profiler is an amazing tool since it actualy shows the voltage drop.
So it does contain very usefull info...
Or I am using this in a non-intended way and I should not connect non-constant voltage sources....
Or you have discovered another great usage feature of the device!
As for the digital capture, I run this tool on a older laptop (i7) and it kind of struggles. So my idea was to give the laptop a break and limit the stored data when not using the digital inputs.
But, good to know that it captures them anyway. I assume that the compression gets rid of all that data if nothing is connected since it is a constant '0' value.
For constant digital data, the file size is very small. May be few kB per minute. On the i7, how much of the CPU % is taken by the GUI. We test it on a very old laptop with core i3 processor which runs at 1.8GHz and it still manages to run though.
You could select the slow PC option from the Acquisition tab as it reduces some graphics updates during the capture. This can help with very slow processors.
Regarding the voltage display, it is shown only in the top chart as of now. It can be easily added to the middle chart and we would add that for the next release.
We thank you for your valuable feedback. Great to know that the tool is useful for you.
Gregory
We have added the voltage plot on the middle chart to show the dip in voltage. Will soon be added in the next release. Stay tuned...
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!
@anglercircuits Can you update the latest GUi from github. It has some fixes for this problem. The issue is mostly from a loose USB connector on the laptop or desktop. It could also be due to signal integrity issues on the port.
To view the files, there is a IOT power viewer software included in the package. Please run this to view the files without the hardware.
@anglercircuits Can you update the latest GUi from github. It has some fixes for this problem. The issue is mostly from a loose USB connector on the laptop or desktop. It could also be due to signal integrity issues on the port.
To view the files, there is a IOT power viewer software included in the package. Please run this to view the files without the hardware.
@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!
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
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, 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 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.
We have added an excel sheet to the github which allows users to create their own battery models from the battery datasheets.
Awesome - thanks!