Connecting a build table and chart VI

[crockengineer]

I am trying to preform a very simple task of displaying my DAQ signal onto a chart (which I can scroll back and look at the history) while at the same time display my DAQ signal in a table.  I have tried several different methods with each one having a different issue.  When I connect my DAQ data straight to the chart with no table in the code it runs fine.  Then if I connect a wire straight from my DAQ to chart wire to a build table function and run the program the chart and table run fine for about 30 seconds and then the chart will clear and all the data is gone from the chart but not the table.  If I disconnect this build table from my code the chart runs for many minutes and I can scroll back and look at all the data history.  Then if I use a data splitter express VI to split my DAQ data  between the chart and the table the table will run and display the data but the chart will not run at all.  If anyone has an explanation/solution for this I would be much obliged.

[Broken_Arrow]

editor ate my post

[Broken_Arrow]

I do this by wiring directly to the Chart with as DBL. I then write the DBL to an array (table) as required using Replace Array Subset.

I don't have 8.6 installed yet, so I can't open your VI, and I don't use Express VI's, but if you post it in 8.5, I might could help.

[Dennis_Knutson]

You seem to lack a basic knowledge of LabVIEW. First, whether you have the table connected or not, the chart behaves exactly the same way. Second, a chart has a history buffer. Once the buffer is filled, it drops the old data and new data is appended to the end. The size of the buffer is settable by right clicking on the chart and selecting Chart History Length. Lastly, the Split Signal function would separate the data into info from ch1 and ch2. since you only have a single channel, then obviously you won't get anything displayed in the chart.

[Broken_Arrow]

The Chart History can also be had via Property Node, and there you have free "table" to look at. Almost no code needed.

[crockengineer]

I actually have a fairly thorough knowledge of labview, and the chart behaves very differently when wired to a table.  I have experimented numerous times between the two attachments below and as I stated before, with everything else held constant the chart without the table connected runs continuously maintaining all history for as long as I have ran it.  However when wired as the second attachment with the table, all the chart data clears after approx. 30 sec. 

[Dennis_Knutson]

As I said, using the split signal function is just plain wrong. It does not do what you think it does. There is absolutely no reason to use it. If you want to wire the same signal to both the table and chart, you just have a common wire going to both. A chart cannot maintain a history forever. In your second example, you are writing exactly nothing to the chart.

[crockengineer]

I appologize, I did not mean to post the program with the data splitter.  The same post above applies to these two VI's.

[crockengineer]

Well for some reason the program is attaching differently then what I have saved on my computer.  For the program with the table wired just pretend like there is no data splitter there and the wire goes straight to the other wire.  These two programs run as I stated before.  I don't see why connecting the table has any effect on the chart but it certainly does everytime.

[Dennis_Knutson]

Sorry, but when I use a single wire, I do not see any differences. I had to change the DAQ Assistant to not use a custom scale but I don't see why that would make a difference.