NI MAX device specified

[HankZ]

Hi folks,

I'm new to LabVIEW and the NI MAX system.
We recently had to replace our NI 9237 module due to a hardware issue. After updating the new device, our deployed LabVIEW executable started throwing an error saying the device is "specified." NI MAX shows a similar error. Please see the attached screenshots for reference.

How can I update the configuration to recognize the new device and resolve this error?

Thanks in advance!

[Bob_Schor]

Try sending the Screen Shot without using "Invisible Ink".  You might also attach the LabVIEW code that has the DAQmx Task (or Read, or Close) function in it (please, if you are using LabVIEW 2025, do a "Save for Previous Version and specify, say, LabVIEW 2021).

Another "useful" screen shot would be to open NI MAX and expand the "Devices and Interfaces" entry under "My Systems" and show us what is "attached".  Do you see the new device that replaces the NI 9237?  [If not, did you install the driver for your new Device?].

Bob Schor

[HankZ]

Hi Bob,

I don't have the Labview source code since we bought the lab-scale machine with executable from another company. Do you know how to extract the executable?

Yes, I can saw my new NI 9237 as Dev2 under "Devices and interfaces" tab. 

[Bob_Schor]

---

@HankZ wrote:

After updating the new device, our deployed LabVIEW executable started throwing an error saying the device is "specified." NI MAX shows a similar error. Please see the attached screenshots for reference.

---

Please also attach the "missing" screen shot referred to above that shows the Error Message.  I notice MAX now refers to two devices, one (probably) refers to the original Device, one to the new Device.  I'm "guessing" (since I don't see the actual Error message) that it's looking for Device 1 (which, I'm guessing, is the Old device) and should be using Device 2.

I didn't realize that you don't have the source LabVIEW code.  Somewhere in there I think there is a DAQmx "Create Task" or "Create Channel" that is looking for "Dev2/ai0:", when it really needs "Dev2_catalent/ai0:".  Maybe before you go renaming things, you could attach the Error Message picture so we can "see for ourselves" ...

Bob Schor

[HankZ]

I am not sure if you are talking about this error message (See below).

You are right, theDev2 is the new one and Dev_2catalent is the original device.

[Bob_Schor]

I took a closer look at the MAX picture you showed previously:

If you look closely at the second device ("Dev2_c"), you can see a red symbol with a white "X" in the middle over the "connection" icon (compare with device "Dev2".  I'm not 100% certain who makes up the names, but this picture says (to me) that MAX sees "Dev2" but doesn't see "Dev2_c".

The Error Message says it really wants to connect to "Dev2_c".  I also just noticed that the code mentions the Dreaded DAQ Assistant (my "enhanced" name for what NI calls the "DAQ Assistant"), which makes me a little suspicious of the quality of the original code (which, I gather, you don't have -- can you get access to it, or purchase it?).

Something you could try is to open MAX and change the name of Device "Dev2" to "Dev2_c" (you probably want to get MAX to delete the non-existent "Dev2_c" first).  If that doesn't work, try renaming to "Dev2_catalent".

In all cases, getting your hands on the actual LabVIEW project and re-building the Executable with the correct name of the device (and NOT using the Dreaded DAQ Assistant, or DDA, for short).  If you haven't learned how easy DAQmx can be, do a Web search for "Learn 10 Functions in NI-DAQmx and Handle 80% of your Data Acquisition Applications", or something close to that (it will probably pop up when you type "Learn 10 Functions").  If you still get stuck, we're here to help.

Bob Schor

[HankZ]

Hi Bob,

Yes I tried to rename the Dev2 to Dev2_c and Dev2_catalent to match the task specification. Since the device do note require two same name devices, the task specified name will auto change after I rename. I have both devices on hand, the red symbol with X will disappear when I connect the original device. I attached the NI MAX configData for your reference.

I tried to extract the vi code from the executable following this tutorial.

I attached the project file. Some of them (the name under SMAC) cannot open due to error "Unable to display the front panel of the VI, the VI's front panel may be removed". I am not sure if this caused by missing some packages or code broken.

Thank you in advanced.

Hank

[Bob_Schor]

That is the strangest (meaning "it looks different from mine") Project File I've ever open (read the earlier parenthetical remark).  Each of my Projects live in a (named) Folder that typically is the name of the Project (for example, "Excel Demo", a Project that runs a Demo I submitted a long time ago to the Forum showing an example of making an Excel Report using the Report Generation Toolkit).  The folder "Excel Demo" contains a Project File (called "PROJECT Excel Demo.lvproj" and a single VI, called "Excel Demo.vi".  [I typically turn on the Filter Views to also show Project entries for Dependencies and Build Specifications, but these are normally turned off].  The point is that I keep the Project files (.lvproj) inside a "Project Folder" that also has the Top Level VI (here "Excel Demo.vi"), all sub-VIs (none here), all Type Defs (none here), and all other files/folders that belong to this Project alone.  If I were to Zip up this Project folder, I would get the Project file, all the VIs and sub-VIs, all the TypeDefs, all the Documentation, all the (project-specific) data and configuration files, etc. that I needed to run the Project and make it work in a consistent manner when built as an executable.

Your Project Folder, however, has no LabVIEW code inside it -- it has only a Project File (pointing to LLBs inside a missing folder called SMAC, plus calls to DAQmx and other NI stuff).  There is also a reference to a folder called "Bounce Back V3" that has such things as "Glucagon Actuator Test Move.vi" and calls to "SMAC Servo"  routines.  However, entries for both "Dependencies" and "Build" have what appear to be encrypted names (the encryption seems to be pretty simple -- might be able to "break" it).

So where did you get this Project file?  Who built the LabVIEW Project, and how were you supposed to use the SMAC files within the code you were trying to write?

Bob Schor