We’re having trouble getting out Jaguar and Victor to get any signal from our driver station recently. We recently updated the cRIO to firmware v11. We think the possible causes could be that the driver station is faulty or that the cRIO could have been affected by an interruption during the update (our wireless bridge has a faulty power supply and shuts down randomly). We’ve switched out our jaguar and sidecar to see if they were damaged and they were not. If it turns out to be a faulty cRIO/driver station, I really don’t think we’ll end up competing this year. Any help you can offer is appreciated.
By the way, this is a team account, so random changes in the posting style are probably attributed to that. In response to a rather rude comment from one of our other threads, our main poster is dyslexic and has trouble spelling, so don’t bother commenting about that again. Thanks.
You should follow the the control system manualexactly. If you had, you would not have programmed the cRIO using the wireless link- you would have used ethernet cables and connected the Driver Station directly to the cRIO and your computer directly to the Driver Station.
With that being said, I can tell you that I have programmed the cRIO wirelessly and it’s not reliable. The first time I did, it went half way through and told me it couldn’t find the cRIO and displayed an error indicating it might be on a different subnet (it wasn’t.) The second time, it worked… so my reccomendation is to go wired.
1.) What exactly does the battery status say on the driver station?
If it say’s “No Comms” you have a communication issue. Perhaps the team number isn’t set correctly on the cRIO (set during imaging) or the driver station.
If it says “No Code” you should re-image the cRIO using a wired link.
If it says a reasonable voltage than we have to start looking in other places for the problem and will need additional information.
2.) What is the robot signal light doing on the digital sidecar?
It’s getting awfully late in the build, but it might be a good idea for you to start at the beginning and redo your control system while following the instructions to the letter. It sounds like you might have skipped a step or two, since you don’t have the battery voltage being sensed properly.
There is a trio of pins at the end of the Analog Breakout opposite the power connection. You need to install a jumper between the two pins nearest the edge of the board in order to connect the battery sense circuit to the required analog input pin.
The lights are constantly solid green. We’re not really sure what they mean though.
Which “lights” are solid green? There is only one Robot Status Light, and it is only solid when the robot is running code and enabled. Otherwise it is flashing.
We are having the same problem as discribed in this post.
If the analog breakout is not on the crio, will this cause the problem. We don’t have the analog breakout on and we don’t have the jumper on. What is the jumper, what does it look like, and can you give me very detailed instructions of how to wire it. thanks
The good news is that your cRIO does have code on it, and that it is talking to the DS because your battery says 00.00V.
Your problem may be in the wiring. Make sure that all the slots on the cRIO are in the correct spots (Your digital sidecar should be connected to slot 4). Make sure that the digital sidecar has power. Though it seems pretty hard to overlook, teams have forgotten to do so this year. Finally, make sure that the pwms are hooked up correctly. They should be on PWM 1-4.