Picolog-HRDL.vi (ADC20/24): How to deal with collecting data from several channels?

[bockdoug]

Hey, I am writing a program in LabVIEW 15, and as part of that I need to measure pressure using the Picolog ADC20/24. The example vi provided by picolog (see attachment below, driver 64-bit LabVIEW : https://www.picotech.com/downloads/_lightbox/pico-software-development-kit-64bit and driver 32-bit LabVIEW : https://www.picotech.com/downloads/_lightbox/pico-software-development-kit-32-bit) seems to do most of the work. What I dont understand is the "channel enabled?"-property. On the front panel, they placed 16 switches, one for each of the 16 channels. From this I assumed that when I only want to record, say, channel 2,7, and 14, I can turn off the other channels. The code in the vi, however, does not seem to do this. It looks like it runs through all 16 channels, regardless of them being turned on or not? Could someone shed some light onto this? Thanks in advance!

[Blokk]

This VI is a bit mess, possible race conditions, hidden control used with local variable, using dynamic data (why???), etc... I guess the programmer at the company was asked to make a LabVIEW variant of their software, but he/she had very little experience with LV...

You could create your own VI by using their DLLs. Try to examine how you should call these DLLs, I guess there is even a documentation for the available functions in the SDK?

[yamadj]

Hello bockdoug,

As for you orignial question about the functonality of channel enabled you might be able to figure out what is going on in this VI by using the Highlight Execution funciton. I agree with Blokk that this may not be following best practices, but at least you can possibly gain some insights on those DLL calls from Highlight Execution.

 You can find more information about how to use Highlight Execution in the link below.

Debugging Tools in LabVIEW - http://www.ni.com/getting-started/labview-basics/debug

Debugging Techniques - https://zone.ni.com/reference/en-XX/help/371361J-01/lvconcepts/debug_techniques/