Just reimaged it with another computer and deployed the project template code. The only change in the code was in the begin.vi where the open motor is set to victor instead of jaguar. No PWM signal, no RSL signal.
I just noticed after reading what other problems people are having that our driver station is reading 0 Volts. This might be of some significance as to what the problem is.
Given that all 3 power LEDs are brightly lit, 2 relays are lit, and the RSL is not, I would guess that there is a problem with the Digital Sidecar, DB-37 Cable, Digital Module, or the connection between the cRIO and the Digital Module.
None of the other things you mentioned would matter.
This means that one of the conditions in R70 isn’t met, but does not affect driving motors.
Teams run LabVIEW and the Driver Station simultaneously all the time. What’s keeping you from doing it?
I therefore compiled the code deployed the code to the robot to run on start up and then open the driver station.
If you’re trying to run the Simple Motor Control example, you must run it interactively. You have to be able to change the front panel control while it is executing in order to change the value being sent to the motor.
If you’re doing a Compile followed by a Run as Startup, then you’re not running the example. You’re running Robot Main, which calls all the other Team Code.
originally, when running lab view, I got an error message about trying to connect to the CRIO when opening the driver station. I assumed they couldn’t both connect at the same time. Since that time I have retried it with success. In fact the last few pics I posted of the driver station was when it was running with lab view open with the robot main open and running continuously. I have tried compiling and run as startup on the example code after changing the variable to a constant of .5 with no success but otherwise I am just running it and manipulating the variable on the front panel of lab view.
The battery voltage is measured using the first slot and the analog module. Until that is installed, the DS will not know the voltage.
The bigger cRIO and smaller cRIO are not that different. The processor in both is a 32 bit Freescale processor. The performance is slightly different due to cache size, the RAM was increased, and physical elements like the power connector, second enet port, and dip switches were removed.
The imaging tool can read the dip switches just to help diagnose broken ones – happens more often than you’d think. For the 4-slot, it can also set them. The one begin set determines whether the serial port is used to output console print statements or used to communicate with another serial device, like a sensor.
As Alan said, simply pushing run on the VI will be the faster way to run your VI. Be sure that the VI contains the safety info. If you run a lower level VI, it will indeed run, but without established communications with the driver station, the outputs will be disabled and that safety feature can cause confusion.
There should be no issue running DS and any other development environment or tool. If you get an error, please post it so I can better understand what is going on.
To make further progress on getting your motors to run, I’m with Joe. Focus on getting the RSL LED to light up or blink. I’d start with the cable, but it could be the digital breakout board. If that doesn’t fix it, work backwards and try another digital module. Also, remove the module in the cRIO and inspect that the backplane pins aren’t bent and don’t have debris shorting them. Also make sure that the module is fully inserted and the side clips engage. The imaging tool shows that it is recognized, so I doubt that there is an issue with engagement or pins.
Greg McKaskle
Just wanted to let everyone know that the problem was the digital sidecar. Here is what happened. I had no RSL light for the test robot that we had set up. After verifying that the code was right I started swapping parts out. When I swapped out the digital sidecar I also swapped the power for it. The power cable was not properly installed so the sidecar did not get enough voltage. The test rig that I brought home to work on had the digital sidecar that I took off the test robot. That sidecar is bad and did not work. When I got back to school and worked on the test robot I simply adjusted the power cable in the breaker panel and the sidecar started working. I also replaced the side car on the test rig and it too started working. Very unlikely circumstances lead to a very troubling problem. Thanks to everyone who helped figure it out.
Congrats, and thanks for the update.
Greg McKaskle