Robot Help ASAP Please

[pr3ciousangel21]

Team 375 (From Staten Island Tech) Needs Robot Advice and Expertise ASAP

Our off-season event is this Saturday and today our robot stopped responding to all programming codes.
So we need help now please

Basically, we tested with different laptops and connections but the robot doesn't respond.

We concluded that there is nothing wrong with:
• Code
• Laptop (driver station)
• Electronics
• Crio
• Anything connected to the Crio

---- Our only possibility at the moment is the windriver installation so we are reinstalling windriver on a laptop.

Everything was working fine until today and we continuously tested on our current robot and a basic robot.....but nothing happens


What do you suggest we do now?

[timytamy]

You seem to have found that there is nothing wrong with almost everything. If this is the case then it should work

Are you sure you have your networking and subnetting set up between the lapto-router-cRIO? Are you able to ping the cRIO? Have you deployed code and it's not running or are you not getting any conection at all? Is the DS giving no communication, no robot code, or working fine? Are you sure the robot is being enabled?

Without knowing much more I'd just advise that you try to do everything tethered for now, and eliminate another link in the chain.

[Mk.32]

So... you are getting the green lights in the Driver Station on the laptop?
And you can upload code to the robot and it says that it completed?
In the Driver Station are all our joysticks/IO showing up and being responsive?
Is your battery charged?

Saying that there is "nothing" wrong but one thing doesn't really provide us with a lot of room to help. Any more info would be able to help us narrow down what the problem is.

[F22Rapture]

Try re-flashing the cRIO image, if you haven't already.

Then go into command prompt and type "ping 10.xx.yy.2" where the xx and yy is your team number, hence 3737 would be "ping 10.37.37.2"

If you can ping it, you would then at least know that the cRIO is responding on the network, and that would be a good place to start.

[pr3ciousangel21]

It is difficult to say exactly what's wrong but nothing seems to respond

We will continue all the trouble shooting topics you gave us and that we came up with such as rechecking:
1.) check code
2.) redownload Driver station
3.) Call NI instruments and ask
4.) "No robot code" likelier the driver station then the code.

Thank you

If you're bringing your bot to CalGames today, and have still not resolved the problems, we'd be more than happy to send over some students and mentors to come help fix your bot. Just come to 256's pit and ask for Andrew.