LabVIEW
Re-initializing my array with reset button
Solved!
@Jarrold wrote:
Now that I have managed to do the real time update of my indicator, I have another similar problem just that it is a little different.This time, I observed that my wavechart does not receive real time updates as well. However, this information is from the "DAQ Assistant". I do not really have an idea how to implement the same technique.
Can you clarify what you mean? It looks like your DAQ Assistant node should update the chart each time it iterates, which I think should be 50 samples at a time every 20ms. Do you mean that when you reset your measurements, the chart continues with old data, or do you mean that the chart isn't receiving data properly?
@cbutcher wrote:
@Jarrold wrote:Now that I have managed to do the real time update of my indicator, I have another similar problem just that it is a little different.This time, I observed that my wavechart does not receive real time updates as well. However, this information is from the "DAQ Assistant". I do not really have an idea how to implement the same technique.Can you clarify what you mean? It looks like your DAQ Assistant node should update the chart each time it iterates, which I think should be 50 samples at a time every 20ms. Do you mean that when you reset your measurements, the chart continues with old data, or do you mean that the chart isn't receiving data properly?
Hey cbutcher,
What I mean is that the wavechart is suppose to have data coming in constantly, but now it only update once after the timer ends.
Here is the latest VI. Should be a lot alot neater 
I can't see what might be the cause for that - perhaps (although I'm doubtful) there's some issue in your ClockVI.vi. If you upload that VI, I can take a look.
Failing that, your graph does not have auto-scaling enabled for the X-axis. Is it possible that the scale just doesn't show the full range?
As an additional comment, outside of your case structure you have a Build Cluster Array node creating your Load.cluster, but this has no data dependency with the arrays of references. This creates a 'race condition' which essentially means that there is no guarantee that your arrays contain values when you create the cluster. As a result, when you use the result, it might not contain references.
Solutions to this are a Flat Sequence Structure (generally best avoided) or alternatively, and much simpler in this case, wire the hidden array indicator wires directly into the Build Cluster Array node. You can then wire the cluster directly into a shift register if you want (it doesn't currently look like you're using the cluster? Maybe I just missed a local variable).
Aha! So I was trying to look through your wires regarding the problem you're describing - I'm guessing you're now talking about the "Logging Volt" case and the DBL Graphs?
I noticed (can't believe I didn't look closely earlier!) that you have a large number of charts all overlapping one another. You definitely don't need to do this! I was trying to work out how to read around all of the many wires you have connected to "ModBus Data VI.vi" (side note - generally people try to avoid having more than the 5-3-3-5 connector pane as it becomes very hard to work out what's going on once you have so many wires. 4-2-2-4 is the good default! 🙂 ) and I noticed your Control Panel radio button controls which chart to display.
All you need to do here is plot ALL of the data to one Waveform Chart, and then adjust which plot is visible (assuming you only want one visible at a time). You can also adjust the label or caption of the Chart if you want to have it display like it does now, with a label describing what is being plotted.
This will allow you to output only one wire with all of the data from the ModBus Data VI.vi which will be another leap forward for your VI (again, congrats on progressive improvements - it all fits on one monitor nicely now. Just the overlapping that really still hurts!!).
The relevant section of the Detailed Help that you would want to create a multi-plot Waveform Chart is pasted below. I have made some parts bold - I'm not certain if you get equally spaced data for each wire at present:
To pass data for multiple plots to a waveform chart, you can bundle the data together into a cluster of scalar numeric values, where each numeric represents a single point for each of the plots.
If you want to pass multiple points per plot in a single update, wire an array of clusters of numeric values to the chart. Each numeric represents a single y value point for each of the plots.
You can use the waveform data type to create multiple plots on a waveform chart. Use the Build Waveform function to plot time on the x-axis of the chart and automatically use the correct interval between markers on the x-scale of the chart. A 1D array of waveforms that each specify t0 and a single-element Y array is useful for plotting data that is not evenly sampled because each data point has its own time stamp.
If you cannot determine the number of plots you want to display until run time, or you want to pass multiple points for multiple plots in a single update, wire a 2D array of numeric values or waveforms to the chart. By default, the waveform chart treats each column in the array as a single plot. Wire a 2D array data type to the chart, right-click the chart, and select Transpose Array from the shortcut menu to treat each row in the array as a single plot.
This lists all of the ways to plot multiple plots in one chart.
To select which is visible, use the property nodes:
Here you choose the plot index and wire it to ActPlot, then the boolean for Visible. You could consider using a For loop and an Equals node, along with your control loop, if you wire the data in the appropriate order. You'd need to also wire the iteration count, this should be a constant equal to the number of plots you have.
To address your actual question, I can't see why the charts wouldn't be updated each time the ModBus VI finishes, but maybe that's what you see and you meant you wanted something else?
Perhaps you can upload the ModBus VI (preferably after reducing the number of inputs and outputs!) and we could take a look at that?
