07-18-2008 07:21 AM
07-18-2008 08:52 AM
07-18-2008 09:37 AM
07-24-2008 05:10 AM
Hi,
In the front panel i am using a table control. Table consists of maximum 100 rows each row is having duration, frequency, duty cycle values as shown below.
Duration (msec) Frequency (hz) Duty cycle (%)
400 5000 10
500 4000
07-24-2008 05:10 AM
Hi,
In the front panel i am using a table control. Table consists of maximum 100 rows each row is having duration, frequency, duty cycle values as shown below.
Duration (msec) Frequency (hz) Duty cycle (%)
400 5000 10
500 4000
07-24-2008 05:15 AM
Hi,
In the front panel i am using a table control. Table consists of maximum 100 rows each row is having duration, frequency, duty cycle values as shown below.
Duration (msec) Frequency (hz) Duty cycle (%)
400 5000 10
500 4000 10
............................................. upto 100 rows.
While running my code i am observing a delay between 1st row and 2nd row.
I am checking my code with NI PXI-6229 Multi function DAQ and from the counter output pin i am connecting the positive and negative terminals to the buzzer circuitry.
I want to solve that delay when the control is switching form 1st row to the 2nd
07-24-2008 05:16 AM
Hi,
For more clarity see the attached Query.vi
07-24-2008 08:42 AM
The reason for the lockup is due to your code. You have not fully grasped the use of an Event Structure. To learn more about LabVIEW, I suggest you try looking at some of these tutorials.
There are ways of having a single loop that contains the Event Structure, but that would require a very lenghty discussion. You should change your architecture to a Producer Consumer loops where the Event Structure is your Producer loop and feeds a state machine which is your consumer / communication loop. The basic reason for that is that you have nested loops within an Event Case. That's a big "no... no".. Because as you try & try to stop the operation, unless all the triggers align, it will start a new iteration and reset the triggers, over & over again, which will lock up your PC. I do realize that you are ORing all those booleans.. But your Event Case wants to process the stop event which will start the whole process again... You could try removing it from your event case..
Also, you do not need a Case Statement wrapping your code.
R
07-24-2008 08:44 AM - edited 07-24-2008 08:44 AM
see image...
07-24-2008 11:36 PM