AMUX 64T does not support Virtual Channels under either Labview or Nidaq, any VBA examples?

[mrmw]

Given that the AMUX 64T does not support Virtual Channels under either Labview or Nidaq as per this link,

http://forums.ni.com/ni/board/message?board.id=250&message.id=6455&requireLogin=False

...are there examples of how AMUX 64T multi-channel thermocouple data can be acquired via Traditional Nidaq, compensated for with AMUX 64T based CJC, the binary data converted to voltage and voltage converted to temperatures, then displayed in Excel...all thru the use of Nidaq function calls from within VBA or VB?

Environment:

Hardware:
AMUX 64T
AT-MIO-16XE-50

Software
Win 98 SE
Nidaq 6.8
Measure 1.2C

Its clear that the solution lies in using Nidaq32.dll based functioin calls. We have the online manual and Windows help file which detail the functions and arguments. We have fragments that address portions of the problem.

We have defined an architecture:
1.Create (Excel) command button ONE to read all the AMUX channels (zero through eleven) using a traditional Nidaq function such as scan_op, which the manual says places the info into an array.

2. convert channel zero CJC reading from binary to voltage (a callable function)

3. convert channels one through ten binary readings to voltages (a callable function)

4. add the cjc voltage value to channel one through ten voltage values

5. convert the channels one through ten voltages to temps (a callable function one of whose arguments may eliminate the need for the previous step 4. To be determined )

6. display the array, where the display would be one row of ten cells, each cell displaying the reading of one thermocouple, rounded to zero significant digits, degrees F. No need to display the cjc that came in on AMUX channel zero.

6b Create command buttons TWO and THREE which write their array contents to successive Excel rows.

'Comment: three buttons, three rows of temp reading...a 3D graph!!!

8. Create a fourth Command Button to read the temp only from thermocouple one, and display it in large font

It jseems antideluvian to have to re-roll this solution when its now the 21st century. Or to drop hefty money on Labview and then have to program it anyway.

Anyone?

[Paul_C.]

Hi Mrmw,

I'd like to keep this issue all collected in your other thread found here.  This helps future readers of our forums search easier to find solutions.  I will add this information to the other thread.

Thanks,
Paul C.