LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Need help with program using a USB Pressure Transducer and String Pot simultaneously

Hi, 

I am needing help with this program. Like many posts before me, I am a newbie and this is my first LabVIEW program. 

Below are the hardware specs and software I am using:

Hardware:

USB-6001 DAQ

0-5k ohm string pot; 24V

ESI Dynamic 0 to 1000 barg pressure transducer; serial USB

 

Software: 

LabView 2018 Version 18.0.1f4 (64 bit)

NI Max Version 18.50f0

 

So we were able to get the manufacture to send us a LabVIEW program for the USB pressure transducer and I wanted to modify it to include my stringpot program in it. After a while stumbling around, I finally got something I thought worked, but as I applied pressure, the indicator on my front panel stayed at the initial pressure reading. Tested this out several times with different pressures and it stays stuck at that initial reading. So prior to modifying the program, the indicator would work well. After editing their program, it seems like my program is interrupting their looping process and doesn't allow for the next set of pressure readings to occur. Any suggestions would be greatly appreciated.

I have included the ESI files for the Library referencing and for original program.

Added to Program.JPGstore pressure.JPG



Sincerely,
agarza1211

 

Download All
0 Kudos
Message 1 of 4
(2,712 Views)

Your Insert into Array at the bottom of the picture looks wrong.  It looks like you are putting the same array in N times, generally ahead of the data coming from the feedback node.  You probably just need a regular Build Array  (I use Build Array 99.9% of the time, and Insert Array rarely when I actually want to put something into the MIDDLE of an array).  Make sure you are building your new data onto the correct end of the array.

Message 2 of 4
(2,706 Views)

Thank you. I will try that and let you know what happens. I guess I was trying to build an array by using an insert array and looping those values back in (or those were my thoughts anyway)? 

0 Kudos
Message 3 of 4
(2,640 Views)

It turns out that the code that the ESI company wrote isn't working like it should and that is why I was having trouble changing my reading intervals from .01 seconds to .1 seconds. 

0 Kudos
Message 4 of 4
(2,608 Views)