From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
09-26-2016 01:13 PM - edited 09-26-2016 01:17 PM
The Chasis is and NI model cDAQ-9171
Oh and Matt, the .exe file comes up first!
09-26-2016 01:16 PM
@matt198717 wrote:The snippets are of the front panel, helpful but not as helpful as the block diagram. Can you prodive the code or at least a snippet of the block diagram? Is this an executable file?
[Edit]: What is the difference between the snippets as well? Are they different labview versions or ran on different computers?
Actually Matt, the .pngs are quite informative if you look for the subtle clues.
"Bad" is an *.exe "Good" is in the IDE (NOTE: the icons upper left) The Graph etc.."Greyed" in "Bad" is in a subpanel! So, likely the path to the subpanel is absolute or the vi for the subpanel is not encluded in the build spec.
09-26-2016 01:30 PM
Good catch on both of those! Im still having a hard time seeing the differences in the upper left icon, but i wouldnt have looked for it either. If this is a new computer that doesnt have the daq drivers then he would need to install those either way.
Did the application come with an installer?
09-26-2016 02:38 PM
Im still having a hard time seeing the differences in the upper left icon
You have to zoom way in on it and expect the bluish border on the default exe icon and the simple black backround in the IDE
09-26-2016 03:10 PM
Jeff,
Thanks for the input. I never knew that.
As for beachmanmans problem, wouldnt it be possible that the insert vi sub panel node could be post the daq functions and in that case the sub panel wouldnt load? The error occurs at the daq timing on a new computer, which lead me to believe it is a driver problem. I think ensuring that the device is functional should be the first step. If he needs to fix the path he may need to find the source code.
09-26-2016 07:20 PM
I had downloaded the MAX software which when I checked included the driver for this NI DAQ Card. The card was also recently tested and good. So only other two hardware components are car chasis and usb.
Also, I had various versions of Labview installed on my computer (2011-2015) the card AutoDAQ program just needed 2012 or comptatible. However when I first installed just 2015 it didn't work. So downloaded other versions, and 2011 finally worked.
-> Could having all these versions of LabVIEW be affecting this / should I uninstall the uncessary versions of labview?
-> When I plug in the DAQ system, the light on the card chasis reads ready (but not active) fyi.
09-26-2016 07:35 PM
09-26-2016 10:53 PM
09-27-2016 03:36 PM
Hi Matt,
I have MAX downloaded, but how could I confirm if it is a hardware problem with this? The "active" light on the card chasis is on but not the ready light and the NI DAQ card was just calibrated so that should be good too. I'm currently checking if I can get this code, thank you.
09-27-2016 03:36 PM
Hi Matt,
I have MAX downloaded, but how could I confirm if it is a hardware problem with this? The "active" light on the card chasis is on but not the ready light and the NI DAQ card was just calibrated so that should be good too. I'm currently checking if I can get this code, thank you.