We are trying to switch outputs on the solenoid breakout, but get nothing out. We are providing 24V in (verified via meter on the breakout, and the LED is on). The module is in slot 7 (we tried it in slot 8 - with appropriate changes to the code - with no difference in results). The code initializes the solenoid outputs so that outputs 7 and 8 should always be on, however, there is no voltage at the pins, and the LEDs on the module don’t come on. All of this is tested without any connections to the outputs (ensuring we are not shorting any outputs). My only thought is that we have a bad NI 9472 module. Anyone have any suggestions or experience with modules going bad?
I hope you don’t mind if I piggyback on your question.
Our 9472 seems to be working OK some of the time, but occasionally all of the LED’s on top will cut off, and then a second or so later will come back on.
When the lights are on, we can control them with our code and the module works to control our pneumatic solenoids, but when the lights are out nothing happens.
Sorry I can’t help with the original question, but maybe someone can chime in with something we can do to test the 9472 to see if it is operating properly.
The LED lights on the Solenoid Module 9472 should work even without the breakout board attached, so don’t worry yet about the other wiring just get the LEDs blinking first.
Software:
The best test of of the code is to run just the built-in LabVIEW solenoid example accessible from the lower-right corner of the Getting Started screen.
Hardware:
Check the pins in the bottom of the cRIO where the Solenoid Module plugs in.
If any are bent or if there is metal dust or other detritus, clean it out.
The lights intermittently cutting out can be caused by a cRIO reboot, so when it happens watch the cRIO power light and the status light (will turn yellow during reboot). Check to see the module is properly seated in the cRIO chassis, and consider moving it to the alternate slot (7 or 8) to see if the problem follows.
I always suggest running the example code on each element as it is wired onto the board. If the example runs, you know that the wiring is correct. If it doesn’t, there aren’t very many variables.
Also, look for errors in the diagnostic tab on the DS. I spent some time chasing a similar problem. When I finally looked for error messages, we were getting device reference errors. The real problem was a trailing blank in the name going into the set dev ref that wasn’t in the get. Almost impossible to see, it doesn’t work, and no broken arrow.
We’ve had this issue as well, more than a few times. Whenever we have changes to references in our code, we try to make sure to check the Diagnostics for reference name issues.
The lights intermittently cutting out can be caused by a cRIO reboot
Doesn’t it take about 20 seconds for the cRIO to reboot? So, if the lights come back on after only a second, that is probably not it?
Or is a reboot much faster than a cold boot?
What might be causing it to reboot?
I will try pulling out the module and re-seating it, or switching it to another slot.
Thanks for the help.