It struck me that the samples/s scale, or the Hz scale, does not follow the standard steps that are accustomed with oscilloscopes: 1,2,5,10,20,50, etc.. Here and there in-between values are used, and here and there the step suddenly is quite large. Would it be possible to change the time scale to the standard 1,2,5 step sequence?
Even nicer would be to have a standard 1,2,5 time/div scale in stead of a samples/s or Hz scale. Time/div is what everyone is used to with oscilloscopes. The app can calculate and display the samples/s it is going to use with the selected time/div setting. It could be an option that the user can still change the sample/s setting.
For instance the OpenHantek6022 Linux/Mac/Windows app works like this ... the user selects a time/div, the app calculates samples/s, the user can still change this if wanted.
Category: nice to have / improvement.
It struck me that the samples/s scale, or the Hz scale, does not follow the standard steps that are accustomed with oscilloscopes: 1,2,5,10,20,50, etc.. Here and there in-between values are used, and here and there the step suddenly is quite large. Would it be possible to change the time scale to the standard 1,2,5 step sequence?
Even nicer would be to have a standard 1,2,5 time/div scale in stead of a samples/s or Hz scale. Time/div is what everyone is used to with oscilloscopes. The app can calculate and display the samples/s it is going to use with the selected time/div setting. It could be an option that the user can still change the sample/s setting.
For instance the OpenHantek6022 Linux/Mac/Windows app works like this ... the user selects a time/div, the app calculates samples/s, the user can still change this if wanted.