LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Data Management Triggering

Solved!
Go to solution

No, the DAQ is working just fine and the Write to Measurement is working just fine for one row at a time. The error in the VISA Read causes the loop to stop so there is only one row in the file that was attached.

0 Kudos
Message 11 of 14
(443 Views)

Hi,

 

Really appreciate the help. I was receiving an error because it wasn't detecting my scale for some reason. It is now back to a calibrated 0.0. So VISA is fully functional. Now I tried changing it again using On Demand, test 7 shows what happened. That is exactly what I want, except now my x_value (time) isn't showing up. Test 10 shows when I run it continously and x_value (time) shows up. My VIs haven't changed, all I did as of now was replug my scale. So on demand is somehow doing what I want, but not completely. Thank you very much.

 

 

Download All
0 Kudos
Message 12 of 14
(435 Views)
Solution
Accepted by topic author tiki12revolt

That is to be expected. When you acquire multiple points, the Write to Measurement File is going to use the dt of the waveform to calculate the time between samples and writes that to the file. When you use a single point acquisition, the waveform has a single value so there is no dt to calculate. The 0 in the file is a result of this. The Write to Measurement File would require extensive modifications to write the delta between the t0 values being passed instead of from the dt and number of samples. You can open the block diagram of Write to Measurement to see if the modification is something you would want to tackle. Otherwise, you can keep track of the elapsed time between single samples with a shift register and the tick count function, for example. Then you could use the Write to Spreadsheet or at an even lower level, Write to Text File.

0 Kudos
Message 13 of 14
(429 Views)

So what I did now was I used the comment section on the write to measurement file and used that for my timestamp. What its doing now is I could either use a tick count for every row value or simply just use the computer time. Either one will work for my case but problem solved. Something trivial but good to know. Thanks a lot guys. 

0 Kudos
Message 14 of 14
(422 Views)