LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

swapping c-DAQ 9188 chassis

Solved!
Go to solution

**disclaimer, I am not a programmer, I am very green to using LV**

Trying to troubleshoot my LabView program.  I switched one chassis for another, NI Max finds the hardware through the IP address, and is communicating with the computer.  My card (cdaq9205) is located in NI Max under my new chassis. 

In my program and I don't know if I need to call out the new chassis.   

In "Edit config" the I/Os are assigned to my cdaq9205, but I don't know if they are looking for my old chassis, or old IP address associated to my old hardware. 

When I try to run my program, I have the time going crazy, so I know something is out of wack. 

0 Kudos
Message 1 of 5
(810 Views)

NI-DAQmx locates the devices by their Alias name. You can change the Alias name of the new cDAQ in NI MAX to match the name in LabVIEW, or vice versa. 

How Do I Find or Modify My Device's Name?

-------------------------------------------------------
Control Lead | Intelline Inc
0 Kudos
Message 2 of 5
(808 Views)

The old cDAQ and the new cDAQ look to have the same name. The only difference is the end (14FF0A5 and 16209C6).  I feel like I should be calling out the location in the program.  

mars333_0-1682956575499.png

 

0 Kudos
Message 3 of 5
(786 Views)

The 7 hexadecimal characters are the serial number of the cDAQ chassis. By default, NI MAX assigns an Alias name of "Model + Serial Number" to a new device. The Alias names look the same but they are two separate devices from the point of view of the DAQmx driver.

If you want to reuse your LabVIEW code for a different cDAQ, you should rename it with some common or meaningful name, e.g simply "cDAQ". When you swap a different cDAQ, just rename the new cDAQ chassis to the same Alias name.

-------------------------------------------------------
Control Lead | Intelline Inc
0 Kudos
Message 4 of 5
(777 Views)
Solution
Accepted by mars333

I believe the solve was going into NI Max and then to data neighbourhood, finding my channels and changing the physical channel.  

0 Kudos
Message 5 of 5
(713 Views)