LabVIEW
data to graph problem
Hello peda,
I could not find a quick solution to your problem, as testing your program without hardware isn't that easy...
But I made some changes:
- You should use more subvis: you do several tasks more than once -> put them in subvis...
- use the error cluster more often: you will not need sequences at all (look at my changes, it's not perfect but a start...)
- I would recommend not to use the "default value for outputs" on case structures. In my opinion you should do some error checking in this case (doing device communication with undefined device isn't recommended, you do this after selection with "Belastung").
- recommendation: change "Belastung" to integer or change your device selection: comparing a floating point number with an integer (as the case statement does) can lead to problems (you will find many threads on this in the forum). Even setting data range/coercion may not help...
Hope this may help you.
I could not find a quick solution to your problem, as testing your program without hardware isn't that easy...
But I made some changes:
- You should use more subvis: you do several tasks more than once -> put them in subvis...
- use the error cluster more often: you will not need sequences at all (look at my changes, it's not perfect but a start...)
- I would recommend not to use the "default value for outputs" on case structures. In my opinion you should do some error checking in this case (doing device communication with undefined device isn't recommended, you do this after selection with "Belastung").
- recommendation: change "Belastung" to integer or change your device selection: comparing a floating point number with an integer (as the case statement does) can lead to problems (you will find many threads on this in the forum). Even setting data range/coercion may not help...
Hope this may help you.
Hello peda,
do you want to show the graphs after OR while the data collection (device communication)? The problem could arise from your case structures with undefined (default) values...
Have a look at my changes. Now the measured data are collected in shift registers...
do you want to show the graphs after OR while the data collection (device communication)? The problem could arise from your case structures with undefined (default) values...
Have a look at my changes. Now the measured data are collected in shift registers...
Hella peda,
you want to show data, but not (necessarily) directly after the measurement. So you have to remember the data until you show them! And shift registers are a convenient way to remember data from one loop iteration to the next. Other possibilities: using global variables, using files (saving to/reading from disk) and surely some other...
Your problem was: if you pressed "Auswertung" then most probably there was no device communication in the same loop iteration. So your graph display got only the default values from case "0, default", and default for arrays are empty arrays...
you want to show data, but not (necessarily) directly after the measurement. So you have to remember the data until you show them! And shift registers are a convenient way to remember data from one loop iteration to the next. Other possibilities: using global variables, using files (saving to/reading from disk) and surely some other...
Your problem was: if you pressed "Auswertung" then most probably there was no device communication in the same loop iteration. So your graph display got only the default values from case "0, default", and default for arrays are empty arrays...
