LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 200477

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.

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
Message 11 of 37
(375 Views)

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.

0 Kudos
Message 12 of 37
(363 Views)

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.

LabVIEW Pro Dev & Measurement Studio Pro (VS Pro) 2019
Message 13 of 37
(352 Views)

@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.  

LabVIEW Pro Dev & Measurement Studio Pro (VS Pro) 2019
0 Kudos
Message 14 of 37
(350 Views)

mjhartwig_0-1715272557562.png

 

0 Kudos
Message 15 of 37
(332 Views)

2nd.png

  

1st.png

0 Kudos
Message 16 of 37
(332 Views)

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!

LabVIEW Pro Dev & Measurement Studio Pro (VS Pro) 2019
0 Kudos
Message 17 of 37
(324 Views)

Testing lifts?

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

 

-AK2DM

~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~
0 Kudos
Message 18 of 37
(318 Views)

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

0 Kudos
Message 19 of 37
(309 Views)

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.

0 Kudos
Message 20 of 37
(308 Views)