11-23-2015 04:45 PM
I'm working with a cRIO 9068 with three modules, 9205 ADC, 9263 DAC, 9403 TTL DIO. My VI is currently fairly basic; reading a couple channels on the ADC and displaying their values, etc. I'm running in scan mode, using a timed timed loop to read the 9205, and a non-timed loop for GUI elements, and a single-process shared library to pass values. Everything was working just fine until the afternoon of Nov 20th 2015, when I could no longer appear to get non-zero values from the 9205 ADC. I can verify voltages are being placed on the input (with a DMM). I'm getting no errors or warnings. I've tried loading an earlier version of the project, know to be working, to no avail.
The only thing that changed was I installed an update that day - LabVIEW 2015 f2 patch 15.0.2. I suspect(ed) the upate was the issue, but I've also tried running the VI on a different computer. The second computer has a fresh install of LV and related components; however, I haven't run the updated on it. Did this update on the 20th possibly also install some updates on the cRIO? I'm really at loss here as to what has caused this issue. I can set output voltages with the DAC and read inputs on the DIO, so I know the scan engine and my loops are working. I've tried power-cycling the system, and even moving the ADC to a different slot.
I've attached my project, if that's helpful.
Thanks!
11-24-2015 11:03 AM
Hi jdosher,
It does seem strange that the only change to the system was the LabVIEW update. It's possible that the update manipulated the drivers in some fashion. We could try repairing NI-RIO and any other drivers and reformatting the cRIO. I would also suggest downgrading LabVIEW and trying the project on the version of LabVIEW you were operating on previously. You could also try other cRIOs or even testing the 9205 on a cDAQ if it is available. Hopefully some of these suggestions will reveal where the problem is being generated from.
11-24-2015 12:36 PM - edited 11-24-2015 01:02 PM
Thanks for the response Andy!
So far I've tried:
We don't have any other cRIO units to swap the ADC into. All other I/O is working. Is it possible that the 9205 has simply stopped working? I don't get any errors, but I also don't get anything but zero values from it. I've verifed the DIO and DAC units are working as before.
I can't seem to find instructions as to how to downgrade LabVIEW (and/or remove/uninstall the 11/20/2015 update). I've been using LV for all of about two weeks now, so I'm still early on in the learning curve.
ADDENDUM! I created another new project, and when I add in the cRIO the 9205 is NOT showing up in the chassis. The other two modules are, but not the ADC. I've tried three different slots in the chassis, an no luck. So it looks like there's something wrong with the 9205. I can manually add it though, so I'm not sure if my assumptions are correct.
11-25-2015 08:18 AM
Hi Jesse,
Are you running the project in scan mode or FPGA?
It would seem that from your description you might be running in Scan mode.
In Scan mode you can get some useful information about the modules from the Distributed System Manager as it can interface with the scan engine.
It is possible that the 9205 has failed and that you need to contact NI regarding it.
What age and revision is your 9205 (the letter at the end of the model number)?
They do take quite a lot of power during the boot up process so you might want to check your power supply. I had 8 9206 (basically the same as a 9205) in a 9014/9004 system that did not have an adequate power supply and on booting the system only a few of the modules were recognised. Improving the power supply enabled all of the modules to be recognised.
Cheers
Stephen