Error -200220 Device Identifier Is Invalid When Deploying System Definition File in VeriStand

Updated May 11, 2023

Reported In


  • VeriStand
  • Measurement & Automation Explorer (MAX)


  • NI-DAQmx

Issue Details

When I try to deploy my System Definition file in VeriStand I get message similar to the following error message:

Error -200220 occurred at Project Window.lvlib:Project >> Project Window.lvlib:Command >> NI_VS Workspace ExecutionAPI.lvlib:NI VeriStand - Connect to 

Possible reason(s): 

Device identifier is invalid. 


This error occurs when your DAQ hardware does not have the same name in both NI Measurement and Automation Explorer (NI MAX) and your System Definition file. 

Follow the steps below to ensure the device identifier is valid:

1. Ensure the name given to the hardware in NI MAX matches the name of the device name being specified in your VeriStand System Definition file. In this example, we will name our device as Newdevice

2. When you are trying to add a new device to your System Definition file, the same rule applies. Make sure that on the Device name section, you enter the same name as it is in NI MAX.

3. To check whether your device is added to the System Definition file correctly, try to deploy our project. If the status shows Connected and you received the message Target synchronization complete as shown below, it means everything is running correctly.
connectedtarget device synchronized

Additional Information

VeriStand will try and use the name of the device in the System Definition file as the physical address for the device. For example, take the following error message: 

Device identifier is invalid. 
NI VeriStand: NIVS_DAQ Measurement Types Plugins.lvlib:DAQmx Create Channel (AI-Voltage-Basic).vi:1780001<append> 
Device Specified: usb-6259 
Suggested Device(s): Dev1 

Task Name: usb-6259_AI 


In this example, we can see that in the System Definition, the device name was specified as usb-6259. However, in NI MAX, there is only a device named Dev1. This error occurs because VeriStand tries to access usb-6251/AI0 which doesn't exist, whereas if it tried to access Dev1/AI0 there would be no issue.

By ensuring that the device name in both the System Definition and NI MAX is the same, we can avoid this error.