Error 200477

[Yamaeda]

It looks from your 1st picture like there's no information in Data Neighborhood. That's nice in this case, no declared signals to lose. If the module names are the same things should work now.

[mjhartwig]

So I got it to run on my old test engineers laptop running of the application file.  But when I go back the small PC in the control panel I still get the same error. From the same application file.   I have re-installed a bunch of drivers and u made some updates no luck.

[NIquist]

Honestly, I would advise you to NOT start resetting, defaulting and/or updating things randomly hoping for a fix.  This error indicates you have a DAQmx resource control that is empty or is set incorrectly.  You may be changing things now that will cause other errors after you figure out the main problem.

     Did you look through the Dev's laptop for INI or CONFIG files where the project/VIs are stored?

     Check the front panel of the code for any controls related to DAQ hardware like "Physical Channels", "Device In", or "Task In"?

     Look at the start of the code for any initialization code that has the wrong settings?

Most important, now that you found the code, can you post it here?  Even screenshots of the main panel and diagram might give us a clue, although the actual project zipped up would be best.

[NIquist]

---

@Yamaeda wrote:

It looks from your 1st picture like there's no information in Data Neighborhood. That's nice in this case, no declared signals to lose. If the module names are the same things should work now.

---

+1.  Good point.  Since there are no pre-configured channels or tasks, the hardware config must happen in the code.  

[mjhartwig]

[mjhartwig]

  

[NIquist]

You are on the right track.  The developer is just using block diagram constants to setup the channels.  Constantly opening and closing DAQ tasks is not the best way to code, but at least it's simple.

The strange thing here is how could anything have changed if it's all block diagram constants?  They should stay the same once you build an EXE.  

You said the program works when running the on the Dev's laptop right?   Carefully compare the NI-MAX Devices Names from both PCs and ensure they all match exactly including the locations (mod#) in the cDAQ chassis.  

But before you do anything else, I would back-up your original Dev's code base completely.  If you don't use an SVN, at least copy their whole project and all related files to somewhere safe!

[AnalogKid2DigitalMan]

Testing lifts?

https://www.skyjack.com/product/sj519-th

-AK2DM

[mjhartwig]

Nothing too Exciting Testing Oil Lights, Wipers,Fans,  Key Switches and Fuel Gauges things like that for the Cab. of the Telehandler  

[mjhartwig]

This is Day one for me looking at this Code.  I finally got access from NI.

Would Not having The Connectivity Toolkit Cause me not to be able to utilized/Communicate the DAQ 9178 an the other 4 Cards?

Product:	LabVIEW Database Connectivity Toolkit
Version:	2020

Product:

LabVIEW Report Generation Toolkit for Microsoft Office

Office Toolkit I assume would defiantly not allow it to Generate a Report if I could Run it.