|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Ok sorry its been a while since i've been on. We smelled stuff burning last time we turned on our robot, so we took a further look and saw that several wires had slashes in them like someone had missed with the wire cutters...so we took apart all the wiring and are redoing it. (Yes that was serious.) And my question now is how on earth do you wire a PWM to a Jaguar? As i recall from my rushed intro last year the PWM can either hook into the sidecar or the cRIO slot??? And then go to either Jaguar or sensor??? (My knowledge on this part is REALLY fuzzy) I would prefer a diagram but if you have some words to post that will be very clear that would be great.
![]() |
|
#2
|
|||||
|
|||||
|
Re: Code Problems
See if these wiring diagrams help explain where what goes.
|
|
#3
|
||||
|
||||
|
Re: Code Problems
Quote:
EDIT: Definitely use the diagrams above |
|
#4
|
||||
|
||||
|
Re: Code Problems
Thank You those diagrams are amazingly helpful! I'll be able to let you know if I need help with anything else after next wednesday.
|
|
#5
|
||||
|
||||
|
Re: Code Problems
We have completely rewired our robot and it will turn on and thats as far as it will go. I need help with the ethernet cable wiring. The situation is as follows:
When we connect an ethernet cable from the laptop to the wireless router, and another one from the bridge to the cRIO, we recieve no robot communication but the ethernet and radio signals on the driver station are both green and the light on the 1st ethernet slot on the cRIO is lit up. However, when we tether the ethernet cable, (directly from the laptop to the cRIO) we get the same green radio and ethernet signals but the light on the cRIO slot does not light up. That probably didn't make sense so i've put together some diagrams that might make a little more sense, they are attached. This probably isn't really clear but if you have any quesions please ask thank you. I am confused and my coach is not that familiar with the wiring on our robot. Any help would be great. |
|
#6
|
||||
|
||||
|
Re: Code Problems
Quote:
2nd: I don't know if you did it just for the picture or what, but are all the modules in for the cRio? In my experience it is generally bad to take them out. 3rd: Try to reset the bridge. It may just be a "frazzled up" in there and need some tuning. 4th: This one seems like the most likely one to me. What did you put as the ip address for your robot? It should be 10.xx.yy.2 , XX and YY being your team number (ex XXYY=3413). 5th: Read through the posts before. Some of those may be it too (router encryption being a big one) Hope this helps! |
|
#7
|
|||||
|
|||||
|
Re: Code Problems
Can you say crossover ethernet cable?
|
|
#8
|
||||
|
||||
|
Re: Code Problems
The fact that the Status light on the cRio stays on indicates a problem there. Check out these Troubleshooting documents http://www.team358.org/files/program...olSystem2009-/
You might have to re-image the cRio. |
|
#9
|
||||
|
||||
|
Re: Code Problems
All you have to do for this is just input the team number into the text box on the driver station, correct? If so, then I have done this. However, I waould like to make sure there isn't more to it.
|
|
#10
|
||||
|
||||
|
Re: Code Problems
There sure is.
You can change the cRIO IP address with the re-imaging tool. (You don't even need to reformat the cRIO to do this) |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Problems Combining Camera Code and Driving Code | cmurdoch | Programming | 20 | 10-02-2007 16:34 |
| Problems integrating CMUCAM code and IFI Default Code | Windward | Programming | 2 | 06-02-2007 16:48 |
| Problems when combine ADC code && camera code | nirhaim1942 | Programming | 1 | 24-01-2007 06:58 |
| problems using gyro/adc code with camera default code | tanstaafl | Programming | 7 | 22-01-2006 23:09 |
| Labview problems and code problems | ajsetter | Programming | 25 | 18-01-2006 17:07 |