LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Timing Issues when running as a sub VI

I am having issues when running the program by calling the PWM as a sub VI.

When I run the programs separately, but at the concurrently, the PWM signal is not affected and runs as expected. However, when we run the PWM.Vi as a sub VI and feed values through to it the PWM signal outputted by the DAQ card is slowed down significantly. Is there any particular reason/ way around this?

  Another issue Im having is related to the graphing of voltage vs current, acquired through the USB 6008 DAQ card. Since we cannot use the switching frequency of 10khz, due to limitations of the DAQ card, we are switching at 10Hz. This results in the graph waveforms been so slow that it appears as a square/oscillating waveform, is there any way to take only the peak of the waveform, as those are the values we require. 

The VI’s are attached however the loop around the PWM code should be removed.

Download All
0 Kudos
Message 1 of 3
(2,451 Views)

 Although i don't have DAQ... 

There is nothing to slow down your vi.

Wiring a 0.1 value to "milliseconds to wait " has no meaning.  The smaller value is 1 (or even 0) but NOT 0.1

Maybe this is the problem (although i doubt)

0 Kudos
Message 2 of 3
(2,428 Views)

PWM wont update until the loop in Main is finished, i.e. when you press the stop button.

 

If you want it to update more often you must have PWM inside Main's loop.

 

/Y

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 3 of 3
(2,427 Views)