09-05-2014 07:24 AM
Doug, there are a few things, maybe I am confusing you:
the Pulse code I posted is for my counter, which works. I simply need to figure out how to get it to not 'freeze' my UI and program when it is running..
The analog voltage I speak of, is something that I have yet to add, and is what I ask in the first post of this thread. I need to add the ability of my program to control the analog out on the DAQ board.
09-05-2014 07:30 AM
09-05-2014 07:35 AM
Living and learning 🙂 Thanks..
Doug
Got more information about the power supply:
There are 4 pins on the power supply that is being controlled.
2 of them go to DAQ analog inputs - voltage and current, they are called 'test points' on the power supply.
2 of them go to DAQ analog outputs - voltage and current, thses are called 'V program input' and 'current program input'
What my next task is is to write voltage and current via my AO0 and AO1 to the power supply 'program inputs'
09-05-2014 07:48 AM
'You choose to use an example without any understanding of LabVIEW. The example was NOT intended to be used as a subVI. The reason it hangs your main is because of the while loop. Simple as that.'
I tried the example without the while loop and I do not get a proper pulse. For testing, could I physically wire my counter output to an analog in to see what happens in NIMax?
09-05-2014 08:29 AM
Create functional global variable vi's based on the code I showed for both your pulse train and for your analog output. Your don't need or want the while loop as you have shown as Dennis said.
Your app with all the features needs to be packaged in a state machine or consumer/producer architecture.
09-05-2014 08:41 AM
A consumer/producer is basically 2 separate loops? I have that, i believe.
I have 1 loop that is the 'main' program and then my 2nd loop contains the even structure that handles the UI clicks..