I don't know if these issues are specific to the linux version of Waveforms, but i'm mentioning the OS and Waveforms version in which these issues occur, in case that's needed for replication.
The issues are:
1. Curve tracer auto scale shows a useless curve for a schottky diode(not sure if the behaviour of other devices would result in the same problem, a zener diode is properly traced in auto scale mode), the status of the auto scale is also not immediately obvious, as the indicator is just a slight change in the color of the auto button.
This curve is useless in the -5v to 5v voltage range(only when set to auto) and behaves counterintuitively when selecting a narrower range(the curve is flipped, and auto selects the display range backwards, from positive voltage on the left, to negative voltage on the right side of the window) as shown in this screenshot
2. The order in which you open instruments breaks the size of the main waveforms window when maximised. In this particular case, if you open the scope, then wavegen, then tracer, the waveforms window will go beyond the display, whether you have multiple monitors or just one connected to the computer. what "fixes" this is running the curve tracer, and then the window will go back to normal maximised size.
3. This one is more a moderately disruptive behaviour than a problem. At least in this particular workspace configuration, with scope, wavegen and curve tracer open, when you bring up the second channel vertical scale, or the toolbar for the scope, the horizontal size of the XY and time domain scope windows, as well as the curve tracer window will be permanently changed, and you'll have to manually resize it again. Ideally, the windows would return to their previously set size when hiding channel scale and toolbar again.
I haven't tried the new beta versions, but seeing as there is no mention in the change log about general fixes, i presume this remains the same in those versions.
Thank you!
Edit: I'd also like to point out that i don't know if this behaviour was present in previous versions as i didn't use a workspace with that layout before.
Edited by Anthocyanina clarifying why i mentioned version and OS
Question
Anthocyanina
I don't know if these issues are specific to the linux version of Waveforms, but i'm mentioning the OS and Waveforms version in which these issues occur, in case that's needed for replication.
The issues are:
1. Curve tracer auto scale shows a useless curve for a schottky diode(not sure if the behaviour of other devices would result in the same problem, a zener diode is properly traced in auto scale mode), the status of the auto scale is also not immediately obvious, as the indicator is just a slight change in the color of the auto button.
This curve is useless in the -5v to 5v voltage range(only when set to auto) and behaves counterintuitively when selecting a narrower range(the curve is flipped, and auto selects the display range backwards, from positive voltage on the left, to negative voltage on the right side of the window) as shown in this screenshot
2. The order in which you open instruments breaks the size of the main waveforms window when maximised. In this particular case, if you open the scope, then wavegen, then tracer, the waveforms window will go beyond the display, whether you have multiple monitors or just one connected to the computer. what "fixes" this is running the curve tracer, and then the window will go back to normal maximised size.
3. This one is more a moderately disruptive behaviour than a problem. At least in this particular workspace configuration, with scope, wavegen and curve tracer open, when you bring up the second channel vertical scale, or the toolbar for the scope, the horizontal size of the XY and time domain scope windows, as well as the curve tracer window will be permanently changed, and you'll have to manually resize it again. Ideally, the windows would return to their previously set size when hiding channel scale and toolbar again.
I haven't tried the new beta versions, but seeing as there is no mention in the change log about general fixes, i presume this remains the same in those versions.
Thank you!
Edit: I'd also like to point out that i don't know if this behaviour was present in previous versions as i didn't use a workspace with that layout before.
Edited by Anthocyaninaclarifying why i mentioned version and OS
Link to comment
Share on other sites
6 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now