Background:
Running LV2020 + RT/FPGA suite 20.5. I have been using this board for development for about a year now.
The project is for real time control and data acquisition for our different valves (which have analog or SENT sensor outputs).
It's been sitting at my work desk on mounting screws connected to an interface board through the breakout board that I got with the Dev KIt.
The interface board has a DC Motor driver, signal conditioning circuits (i.e. J2716 SENT interface), signal selection relays,...etc
The SBRIO was working perfectly fine until recently.
The project is relatively mature with all functions implemented.
Issue #1: Board running hot (I think) and analog inputs not working
Recently the sbRIO has been getting up to 60degC.
If I start from a cold with no test software running (room temp start from powered off), the board reaches 60degC within a couple mins.
It will run ~30% CPU load without anything test software running.
But I didn't really pay attention to the temp/CPU load with no test software running before, so I don't know if this is abnormal.
Along with this noted behavior, all the analog inputs now do not work correctly.
--> Some of the inputs seemed to be mapped incorrectly (note, wiring was not changed) --> i.e. one channel's voltage reading show up on another channel.
--> Many of the other SBRIO analog inputs are behaving like an analog 0V output: if I connect them to the interface board which has filtered analog outputs, these SBRIO analog inputs drag the voltage level down to 0V.
-->The status light is normal (not on), green power light OK.
--> Nothing else abnormal is reported in MAX
The digital input/outputs and everything else appear to work OK (i.e. I can run closed loop control of valves with digital SENT output).
I don't believe this is a PC software or driver issue issue, as I have a CRIO 9056 that runs the same project without issue.
That CRIO also connects to an identical custom interface board.
Anyway, I have another 9629 I could use that is going to be installed in the formal test stand soon (to confirm it's a hardware failure), but I wanted to get some ideas what might be causing this...
Issue #2: Cannot connect in DAQMX mode after upgrading DAQmx and downgrading
Unfortunately, I'm unable to connect in DAQ MX mode to check the analog inputs this way.
This is because I installed LV 2023 for another project, which installed DAQ MX 2023.
When I tried to connect I get a DAQ MX version mismatch error (as the SBRIO has DAQMX 20.1).
I uninstalled DAQ MX 2023, rebooted, reinstalled DAQ MX 20.1 on my PC.
However, the issue persists: when I tried to connect in DAQ MX mode, I get a version mismatch error despite 20.1 installed on PC and SBRIO/CRIO.
I tried uninstalling DAQ MX 20.1 from the SBRIO and CRIO.
Now, when I try to reinstall DAQ MX 20.1 from my PC onto the device, it shows that I do not have V20.1 at all available (even though I clearly do, and it shows up in Package Manager).
Any tips would be most welcome!
Thanks.
Matt Lawson
Test Engineer
