LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Recorded output data has a delay between input and output readings

Solved!
Go to solution

Hey,

Thanks for reporting back.

The new screenshot does not show enough data to tell what the exact issue is. Please attach your VI instead.

 

Generally, you'll run into an issue here (if I understand correctly): You are trying to set up our output task all at once. However, your input is live (at 5Hz), so it needs to run repeatedly. Therefore, the output needs to be moved outside of the loop, while your input needs to stay in there. Also, as the output is now a task fully running in hardware, you cannot have "live" values written to your logfile anymore.


Ingo – LabVIEW 2013, 2014, 2015, 2016, 2017, 2018, NXG 2.0, 2.1, 3.0
CLADMSD
0 Kudos
Message 11 of 12
(356 Views)

Hello again,

I have to admit that I had implemented this solution already out of curiosity before my first reply, however deleted it, so I had to create it again.

Attached is how I would solve your task. Or let's better say: As far as I know your requirements.

I am fully relying on the DAQ chassis to do all the I/O. This has the advantage that I can use its power and precise timing. When I run it here, the "steps" are exactly at multiples of 0.1s. I commented the code, but it for sure does not explain everything.

 

I just implemented the DAQmx I/O tasks, no logging or additional controlling, as you already have that in your code.

 

I don't know if you need the 0.1V steps indeed, but it not, you can simply adjust the step size and sampling rates to have a smooth ramp.


Ingo – LabVIEW 2013, 2014, 2015, 2016, 2017, 2018, NXG 2.0, 2.1, 3.0
CLADMSD
0 Kudos
Message 12 of 12
(349 Views)