Robot doesn't drive when code is deployed.

[swaglord2000]

We are 1st time programmers and have no mentors that know how to program. We were able to format the cRIO and upload the default code to the robot. The only changes we made were that we changed to mechanum wheels, and we switched the jaguars to talons. We received this error message. I don't not really know a lot about labview, but I have been reading beginners guides, and watching tutorials. If it is not a easy problem to explain just pm me and I would be happy to talk through skype or email.


Warning <Code> 44002 occurred at Ping Results: link-bad, DS radio(.4)-bad, robot radio(.1)-bad, cRIO(.2)-GOOD, FMS-bad Driver Station
<time>1/23/2014 7:04:14 PM<unique#>9
FRC: Driver Station ping status has changed.
Warning <Code> 44002 occurred at Ping Results: link-bad, DS radio(.4)-bad, robot radio(.1)-bad, cRIO(.2)-GOOD, FMS-bad Driver Station
<time>1/23/2014 7:03:36 PM<unique#>8
FRC: Driver Station ping status has changed.
Watchdog Expiration: System 5, User 1
ERROR <Code> -44009 occurred at Driver Station
<time>1/23/2014 7:02:03 PM<unique#>7
FRC: A joystick was disconnected while the robot was enabled.
Watchdog Expiration: System 4, User 1
ERROR <Code> -44009 occurred at Driver Station
<time>1/23/2014 7:01:50 PM<unique#>6
FRC: A joystick was disconnected while the robot was enabled.
Warning <Code> 44002 occurred at Ping Results: link-bad, DS radio(.4)-bad, robot radio(.1)-bad, cRIO(.2)-GOOD, FMS-bad Driver Station
<time>1/23/2014 7:00:18 PM<unique#>5
FRC: Driver Station ping status has changed.
Watchdog Expiration: System 3, User 1
WARNING <Code> 44008 occurred at FRC_NetworkCommunications <radioLostEvents> 1574.395 <radioSeenEvents>
FRC: Robot radio detection times.
WARNING <Code> 44007 occurred at FRC_NetworkCommunications <secondsSinceReboot> 1572.132
Warning <Code> 44001 occurred at Modified Network Configuration: Set
FRC: Time since robot boot.

Driver Station
<time>1/23/2014 6:59:56 PM<unique#>4
Warning <Code> 44002 occurred at Ping Results: link-bad, DS radio(.4)-bad, robot radio(.1)-bad, cRIO(.2)-bad, FMS-bad Driver Station
<time>1/23/2014 6:59:55 PM<unique#>3
FRC: Driver Station ping status has changed.
Warning <Code> 44004 occurred at Driver Station
<time>1/23/2014 6:59:53 PM<unique#>2
FRC: The Driver Station has lost communication with the robot.
Warning <Code> 44006 occurred at Driver Station
<time>1/23/2014 6:59:52 PM<unique#>1
FRC: Custom I/O is not enabled or is not connected to the driver station.

[bvisness]

Those messages probably mean that something in your code is causing it to crash or hang. Or, you possibly don't have any communications with the robot at all. What does your Driver Station look like? Which lights are green and which are red? (Check the Diagnostics tab too.)

[swaglord2000]

All of them were green in both the diagnostics and in the operations tab. I figured the default code would allow is to drive somewhat to make sure it is all working. I can say that we were directly connected to the robot and not using the router. Any suggestions on what is going wrong? In the upper part of the drive station we can see that it is reading our joystick and our buttons, but we are not getting any response from the robot its self.

[Greg McKaskle]

Those messages tell you that over about four minutes, you launched the DS without a Cypress I/O board. You connected to a robot that was booted about 25 minutes prior. You enabled the robot and presumably because it wouldn't drive, you disconnected joysticks a few times.

My suspicion is that the code was running fine but you have an electrical issue. What do the motor controller LEDs show, what do the LEDs on the digital breakout look like?

Greg McKaskle

[swaglord2000]

Our talons flash yellow the whole time and everything else flashes green.

[geomapguy]

Our talons flash yellow the whole time and everything else flashes green.

PWM cables plugged in???

Power to digital sidecar plugged in??

If it's not too hard, please post a picture of your wiring.

[swaglord2000]

I will be able to post pictures tomorrow. I appreciate the help and I hope we can figure this out! Thanks again. Team 4073

[geomapguy]

I will be able to post pictures tomorrow. I appreciate the help and I hope we can figure this out! Thanks again. Team 4073

Make sure to take many different angles and up close pics :)

[Alan Anderson]

Our talons flash yellow the whole time and everything else flashes green.

Flashing green? Nothing should be flashing green except the little RSL repeater light by the connector for the big RSL.

If the three power LEDs on the Digital Sidecar are not all brightly lit, the problem is probably simple and trivially fixed: you don't have battery voltage going from the Power Distribution Board to the Digital Sidecar's power input.

[Pratik Kunapuli]

Something that our team ran into during the offseason was that code would appear to deploy fine but not run if the actual source file isn't in the correct folder that is being deployed or the "main project". I'm not sure if this is the entire solution to your problem, so yoyo should still check all of the electrical wiring etc. Could you copy and paste the code so we can look at it?

[swaglord2000]

Some updates. We tried reversing all of our pwm's and that didnt help I needed to correct that only the talon's flash orange and the other green lights are constant. I will also include some pictures in this post. *The pictures were too big to post so I put them in a album that you can view in this link.

http://imgur.com/a/e9Wy1

[LFRobotics]

Our team is having the same issue - we have not figured it out yet - the only difference is that we do not get anything in the DS in response to moving the joysticks.

[DDSLoan96]

best bet would be to take pictures of your wiring and post your code either here or link on github(or similar)

[swaglord2000]

We actually found our issue! The modules on the cRIO were opposite what they needed to be so when we put them in the right order we were able to get a response.

[geomapguy]

We actually found our issue! The modules on the cRIO were opposite what they needed to be so when we put them in the right order we were able to get a response.

Great!!

[DaboRoss]

This is happening to us, except for it only happens when in game mode, and it stops responding around 10 seconds after autonomous ends. It doesn't happen when just enabling practice-teleop. It's pretty much the exact same error as posted above, which is why I responded to this thread.

Do you think that this error could be caused by the same stuff, even if it works when not in game mode.

[Greg McKaskle]

What is game mode?

Pretty much the same errors is probably a different error. Please post your error messages.

If your robot moves in teleop and auto, then it is not an issue with swapped modules -- unless something is swapping them on the robot while code is executing.

Greg McKaskle

[ekapalka]

We actually found our issue! The modules on the cRIO were opposite what they needed to be so when we put them in the right order we were able to get a response.
Did the imaging tool indicate that they were in the correct location before fixing it, though? My team's off-season robot is having unexplainable issues similar to the ones mentioned here in this thread, except the robot shows absolutely no indication of functionality other than printing button states (not axis states) from the controller to the DriverStation. The imaging tool says that all of the modules are green (in the correct location, I assume), and reformatting / re-imaging it doesn't help in the slightest. We've reduced our code down to the absolute minimum, but nothing has worked...

[xXhunter47Xx]

Did the imaging tool indicate that they were in the correct location before fixing it, though? My team's off-season robot is having unexplainable issues similar to the ones mentioned here in this thread, except the robot shows absolutely no indication of functionality other than printing button states (not axis states) from the controller to the DriverStation. The imaging tool says that all of the modules are green (in the correct location, I assume), and reformatting / re-imaging it doesn't help in the slightest. We've reduced our code down to the absolute minimum, but nothing has worked...

Don't assume just because it's green that it's in the right location. Check connections physically please, software fails too (something I hate hearing when we're working on the robot, it's always easy to point the finger at the programmer :ahh: :ahh: :ahh: :p ), make sure Analog is in port 1, ribbon cable module is in port 2, and solenoid module is in port 3. Can't wait for the roboRIO, when all these problems will vanish and new ones will arise.