PDP - LED's

[Robo Hamsters]

I don't think you would pass inspection like that. I would ask on the official Q&A though.

[jds2001]

Do you see battery voltage on the driver station at all? That's useful and something that you probably do use.

Also, I don't see how you can demonstrate compliance with R72 in this state, so it will definitely be problematic at inspection.

Hopefully CTRE support can help.

[AllenGregoryIV]

Originally Posted by jds2001

Do you see battery voltage on the driver station at all? That's useful and something that you probably do use.

Also, I don't see how you can demonstrate compliance with R72 in this state, so it will definitely be problematic at inspection.

Hopefully CTRE support can help.

Battery voltage on the Dashboard is determined internal to the RoboRIO not the PDP. R72 would be the problem however.

[MrForbes]

did it work, then quit working? or did it always not work?

do you have the two little fuses installed, and pressed in ALL the way?

[crollison]

Support got back to me, identified that it was dead and would have to be repaired or replaced. Will have to wait and see. Thanks.

[cartwrig]

Does anyone know if there is an internal fuse or fuseable link (resistor looking device) on the circuit board. Ours is dead too; and, we'll have to get it off the robot to begin unscrewing top/bottom to see for ourselves.

Getting some insight on this would be helpful; before we proceed.

Thanks,
- Rob

[Mark McLeod]

I've opened up the case for a couple of these failures and both times several circuit components have been fried. Pretty much requiring a new PDP.
The burnt ones worked fine for dumb power distribution on a practice, experimental, or previous year's robot.

Repair is best handled by contacting Cross the Road Electronics

Here's a closeup of a burnt board.

[Bluman56]

Originally Posted by Mark McLeod

I've opened up the case for a couple of these failures and both times several circuit components have been fried. Pretty much requiring a new PDP.
The burnt ones worked fine for dumb power distribution on a practice, experimental, or previous year's robot.

Repair is best handled by contacting Cross the Road Electronics

Here's a closeup of a burnt board.

Our PDP is also acting up (works but doesn't show up in RoboRio Web Interface). We had some issues with the red 10 amp breaker slot. Would opening it up prevent CTRE from having to repair/replace it?

[ATannahill]

Originally Posted by Bluman56

Our PDP is also acting up (works but doesn't show up in RoboRio Web Interface). We had some issues with the red 10 amp breaker slot. Would opening it up prevent CTRE from having to repair/replace it?

Can you expand on what you mean by "works"? What do the LEDs do when it is powered? Is your roboRIO power slot outputting the proper 12 volts?

If you think you might want CTRE to replace it, I would suggest you call them on Monday before opening it up.

[Bluman56]

Originally Posted by rtfgnow

Can you expand on what you mean by "works"? What do the LEDs do when it is powered? Is your roboRIO power slot outputting the proper 12 volts?

If you think you might want CTRE to replace it, I would suggest you call them on Monday before opening it up.

The robot runs but can be intermittent at times, showing a "No Robot Code" error then going back to "Teleoperated Disabled" suggesting a power cycle occurred. At our regional, we had a CSA help us with it (I think he even asked Mark McLeod about the behavior) and ended up suggesting that the problem stemmed from our 10 amp red fuse slot being "jammed". We were issued a temporary replacement and all worked well with it.

If I'm not mistaken the two LEDs flash orange/green (it's been a while). We got in contact with CTRE after the regional and they said it was a software issue with the device ID being set too high last year (2015)? They told us to "Disconnect CAN bus between the robot controller and the missing-ID-device. Then power-cycle or reboot the roboRIO. Navigate to the roboRIO's webpage and wait until page fully renders. Now reconnect CAN bus and manually-refresh the browser until device appears."

That didn't solve it either.

[ATannahill]

Originally Posted by Bluman56

The robot runs but can be intermittent at times, showing a "No Robot Code" error then going back to "Teleoperated Disabled" suggesting a power cycle occurred. At our regional, we had a CSA help us with it (I think he even asked Mark McLeod about the behavior) and ended up suggesting that the problem stemmed from our 10 amp red fuse slot being "jammed". We were issued a temporary replacement and all worked well with it.

If I'm not mistaken the two LEDs flash orange/green (it's been a while). We got in contact with CTRE after the regional and they said it was a software issue with the device ID being set too high last year (2015)? They told us to "Disconnect CAN bus between the robot controller and the missing-ID-device. Then power-cycle or reboot the roboRIO. Navigate to the roboRIO's webpage and wait until page fully renders. Now reconnect CAN bus and manually-refresh the browser until device appears."

That didn't solve it either.

According to the user guide, orange/green LEDs indicate you need to upgrade the firmware, but you cannot do that if you cannot see it in the web dashboard.

Important things to check are that you have the wires stripped to the proper length before inserting them into the weidmuller connectors, the wires are going into the right ports based on high/low (yellow/green) and you have a terminating resistor. If this is all correct I would again contact CTRE.

I am doubtful that the issues with CAN communication are related to the odd behavior you saw from your robot. The 10 amp fuse and slot could cause the roboRIO to reboot if there was an intermittent connection. If you only saw "No Robot Code" but not "No Robot Communication" than I would evaluate your code for any place where an error would be thrown instead of looking for a case of the roboRIO rebooting.