Running Robot

[WalnutsAndBolts]

Hi
I have been trying to make my robot work for over 2 hours now. My radio is working and I have tried the screen steps instructions with no luck. How do I get this thing working and how do I program it? Thank you for your help!

[engunneer]

are you programming with labview, java or C++? which instructions are you using as a guide (link please so we can help you more quickly)

[WalnutsAndBolts]

Originally Posted by engunneer

are you programming with labview, java or C++? which instructions are you using as a guide (link please so we can help you more quickly)

We are using LabView and here is a link:
http://wpilib.screenstepslive.com/s/...ogram-wireless

[engunneer]

your team number and battery voltage show up?

Are the communication, robot code and joystick lights all green?

those will say where to start.

also, other people that might read this thread, please jump in because i won't be available anymore pretty soon.

[WalnutsAndBolts]

Originally Posted by engunneer

your team number and battery voltage show up?

Are the communication, robot code and joystick lights all green?

The communications and robot code are not coming up green.The team number is up, but I think that I manually entered it? I also did bridge my radio.

[engunneer]

ok, focus on communications first. can you get to the roborio configuration page in a web browser (even if you don't have silverlight, you should at least get something)

verify your ip addresses or mDNS setup. http://wpilib.screenstepslive.com/s/...rio-networking

specifically the troubleshooting link http://wpilib.screenstepslive.com/s/...anual-id=24193

[Mark McLeod]

Your radio should be setup as a 2.4GHz access point, not as a bridge, but if your selection had 2.4GHz in it anywhere, then it's okay.

Does your team number show up in your PC's wireless selection list and did you connect to it (example attached)?

[WalnutsAndBolts]

Originally Posted by Mark McLeod

Your radio should be setup as a 2.4GHz access point, not as a bridge, but if your selection had 2.4GHz in it anywhere, then it's okay.

Does your team number show up in your PC's wireless selection list and did you connect to it (example attached)?

I have that connected, but I can't drive the bot. I have attached an image of the driver station. The image is of our computer connected to the roboRIO via Ethernet dongle. I uploaded the basic code, but the robot is not responding.

[WalnutsAndBolts]

Originally Posted by WalnutsAndBolts

I have that connected, but I can't drive the bot. I have attached an image of the driver station. The image is of our computer connected to the roboRIO via Ethernet dongle. I uploaded the basic code, but the robot is not responding.

Here is the link:
https://photos.google.com/search/_tr...0_QYCN8MhSqEnh

[WalnutsAndBolts]

Originally Posted by WalnutsAndBolts

I have that connected, but I can't drive the bot. I have attached an image of the driver station. The image is of our computer connected to the roboRIO via Ethernet dongle. I uploaded the basic code, but the robot is not responding.

Here is the image

[WalnutsAndBolts]

Originally Posted by Mark McLeod

Your radio should be setup as a 2.4GHz access point, not as a bridge, but if your selection had 2.4GHz in it anywhere, then it's okay.

Does your team number show up in your PC's wireless selection list and did you connect to it (example attached)?

Actual Link here:
https://goo.gl/photos/8RejK5yHUt5hNfBM9

[rich2202]

Originally Posted by WalnutsAndBolts

How do I get this thing working and how do I program it?

"how do I program it" is the first step. You have to install the preferred environment on your Programming Computer (which can also be your Driver's Station). Write the Code. Compile it.

At that point, you are ready to attempt communicating with the Robot.

Do the basic robot setup (battery, pdp, crio). Also attache a motor controller, and put a Volt Meter on the output. Alternatively, you can setup the pneumatic system (compressor, pressure sensor).

Program and setup the radio. Update the cRio firmware.

Establish communications with the robot (I suggested tethered for the first time until you are sure it works).
Deploy the code.
Enable the robot.

What you want to do with your code is energize the Motor Controller (without the motor attached), or enable the pneumatic system and hear the compressor start up. Have it cycle on and off (1 second on, 1 second off).

At that point, you have gotten code to run on your robot.

[Mark McLeod]

With Ethernet from your picture, it looks like your robot is running fine.
Does it not respond to your joystick?

Check the USB tab in the Driver Station (on the left-the tab with a USB symbol) to see where your joystick has been connected. For the basic LabVIEW project it should be in the USB 0 position, it should be green, and it should brighten whenever a button is pushed.

[WalnutsAndBolts]

Originally Posted by Mark McLeod

With Ethernet from your picture, it looks like your robot is running fine.
Does it not respond to your joystick?

Check the USB tab in the Driver Station (on the left-the tab with a USB symbol) to see where your joystick has been connected. For the basic LabVIEW project it should be in the USB 0 position, it should be green, and it should brighten whenever a button is pushed.

Yes, the bot is not responding to the joystick. The joystick comes up in USB 0, and I can see the xyz axis things. Do we need to write code in order for this to connect, or should the robotmain file work?

[Mark McLeod]

Check that your motor controllers for the left side are connected with a PWM cable to the roboRIO PWM 0 port, while the right side motor controller is connected to PWM 1. If you have two motors per side then use a PWM splitter on each side.
The default code assumes one motor per side and the left side motor controller connected to PWM 0 on the roboRIO, the right side motor controller connected to PWM 1.

The default project described in screensteps should just work.
The joystick will be in arcade mode y-axis is forward and back, x-axis causes turns.

P.S.
I should have asked what the status lights are doing on your motor controllers (and which model motor controllers you are using-white Spark ones?)?