View Full Version : yes comunication, yes code but no response by robot
DaBossToss
14-09-2010, 18:35
the driver station shows that we have communication and that we have code on the CRIO and that we have input from the joysticks. When we push the controls on the joysticks nothing happens. please help and by the way we were able to connect and run stuff directly after the competition but not wirelessly.why?
You did enable the robot on the Driver Station correct?
Assuming your using the older gaming adapter:
You need to disable the encryption on the wireless gaming adapter. At a competition it gets set up with a special networking key, that needs to be removed. This can be done by directing your browser to 10.xx.yy.1. The user-name and password are "admin" Then go to basic, then wireless. Then at the bottom you should see a section labeled encryption or something similar. There should be an option to disable it. Once that's done, hit save settings and restart now. Then you should be able to connect via wireless.
There's a bunch of things to check here.
Is the robot enabled?
Are the motor controllers hooked up correctly? (Is the PWM cable plugged in the right way on the controller? On the digital sidecar? Are they in the correct ports?)
Are the motors hooked up correctly?
Has anything changed since the last time the robot ran?
DaBossToss
16-09-2010, 11:26
There's a bunch of things to check here.
Is the robot enabled?
Are the motor controllers hooked up correctly? (Is the PWM cable plugged in the right way on the controller? On the digital sidecar? Are they in the correct ports?)
Are the motors hooked up correctly?
Has anything changed since the last time the robot ran?
every thing here has been done
DaBossToss
16-09-2010, 11:32
You did enable the robot on the Driver Station correct?
Assuming your using the older gaming adapter:
You need to disable the encryption on the wireless gaming adapter. At a competition it gets set up with a special networking key, that needs to be removed. This can be done by directing your browser to 10.xx.yy.1. The user-name and password are "admin" Then go to basic, then wireless. Then at the bottom you should see a section labeled encryption or something similar. There should be an option to disable it. Once that's done, hit save settings and restart now. Then you should be able to connect via wireless.
i have physically reset the gaming adapter, but not have done anything about encyption i will try it and get back to you.
Radical Pi
16-09-2010, 16:58
Look in the Diagnostics tab of the Driver Station and check if there are any errors listed in the text box
Joe Ross
16-09-2010, 17:28
i have physically reset the gaming adapter, but not have done anything about encyption i will try it and get back to you.
What do you mean by "physically reset the gaming adapter"? If you reset it to factory default, you will need to go through the entire configuration process in the control system manual.
DaBossToss
16-09-2010, 18:18
What do you mean by "physically reset the gaming adapter"? If you reset it to factory default, you will need to go through the entire configuration process in the control system manual.
I pressed the reset button on the back of the gaming adapter
RoboMaster
18-09-2010, 16:17
Yeah, then you're going to have to reconfigure it manually. The good news is that resetting it gets rid of the competition encryption setting.
Follow the instructions from the Control System manual #2 (http://frcdirector.blogspot.com/) on configuring the gaming adapter (setting the IP address, changing some settings, etc.)
Just wondering, since it isn't clear yet: Do you have the old robot radio/gaming adapter that looks like a black, square box? Because there is a new one that some rookies used and that would change the process a little bit...
DaBossToss
27-09-2010, 11:53
I reconfigured it manually and i can connect wirelessly now(which is what i originally wanted), but we now realize that our robot does not work. Is there a way to tell if the CRIO is outputting our code to the digital sidecar or if it is the digital sidecar that does not work. we have tried to test the sidecar with a multimeter and it does not give out signal.
Alan Anderson
27-09-2010, 12:55
Is there a way to tell if the CRIO is outputting our code to the digital sidecar or if it is the digital sidecar that does not work.
Look at the three green power LEDs on the Digital Sidecar. Also pay attention to the Robot Signal Light. Tell us what you see.
The RSL is intended to give an indication of what the cRIO is doing. If your big orange flashy light isn't doing anything, look at the little green flashy light on the digital sidecar where the big light is supposed to connect.
A general suggestion: when you describe what you've been doing, please give a little more detail. For example, saying "every thing here has been done" is not the best response to a list of questions, especially if the final question was whether you had changed something since the last time things worked. We also don't know exactly what you mean when you say "test the sidecar with a multimeter." Being more specific will help us to help you.
DaBossToss
27-09-2010, 18:06
Look at the three green power LEDs on the Digital Sidecar. Also pay attention to the Robot Signal Light. Tell us what you see.
The RSL is intended to give an indication of what the cRIO is doing. If your big orange flashy light isn't doing anything, look at the little green flashy light on the digital sidecar where the big light is supposed to connect.
A general suggestion: when you describe what you've been doing, please give a little more detail. For example, saying "every thing here has been done" is not the best response to a list of questions, especially if the final question was whether you had changed something since the last time things worked. We also don't know exactly what you mean when you say "test the sidecar with a multimeter." Being more specific will help us to help you.
The 3 indicator lights on the digital sidecar are all in indicating that the sidecar is receiving power. As described, the small green blinky light does not seem to flash anymore as it did in competition. The light subsequently does not seem to be receiving the signal to turn on and off.
This either means there is a problem with your DB37 cable, or there is a problem with the image on the cRIO, or that the LED is burnt out.
The light should always be flashing or on.
Your orange light (Robot Signal Light) should be plugged into the two pins by this flashing LED on the Digital Sidecar. What is it doing? If it is flashing or solid on, then your little green LED is burnt out.
You can measure resistance with a meter to determine if the cable is at fault. The Robot Signal Light is multiplexed off the serial Relay Output data. You want to check pins 18, 19, 20, and 21.
If the cable turns out good, then try re-imaging your cRIO, and deploy the default code to test.
Alan Anderson
27-09-2010, 22:05
This either means there is a problem with your DB37 cable, or there is a problem with the image on the cRIO, or that the LED is burnt out...
...or the DIO module is faulty, or not plugged in, or plugged in to the wrong slot...or the DB15 connector in Slot 4 of the cRIO is broken, or shorted by debris, or not making contact properly because of a foreign object...or the cRIO is broken...
At this point, it would probably be easiest to start swapping out components until you find one that makes things work.
The little green LED will still flash regardless of whether the DIO module has 12v power or not. It will simply flash much dimmer without the external power.
Just swapping out components is a good way to break things. (The Digital Sidecar supposedly has reverse-voltage protection, but who knows if it was implemented?)
However, you are correct I was making assumptions about the functionality of other parts. A good test for the digital sidecar would be to to use a digital input or output. (If you want to test the motor controllers that way, a 1.75ms pulse should be about 50% full speed)
DaBossToss
29-09-2010, 13:29
...or the DIO module is faulty, or not plugged in, or plugged in to the wrong slot...or the DB15 connector in Slot 4 of the cRIO is broken, or shorted by debris, or not making contact properly because of a foreign object...or the cRIO is broken...
At this point, it would probably be easiest to start swapping out components until you find one that makes things work.
We have swapped out the modules already and tested different cables and sidecars and tested the voltage on each sidecar and it is getting power but not a signal.
When you say module you are referring to the Digital Sidecar correct?
If so, then the problem seems to be with your Crio. If you have a different digital module you should try swapping that in.
Radical Pi
29-09-2010, 16:24
Is the analog module properly installed with the jumper? If so, is the battery voltage showing on the classmate?
What happens if the Digital module is moved to the other slot (slot 6 I think) and your code is updated to output to that slot?
Alan Anderson
29-09-2010, 16:35
We have swapped out the modules already and tested different cables and sidecars and tested the voltage on each sidecar and it is getting power but not a signal.
Did you try a different cRIO?
Look closely at the DB15 connector for Slot 4. Make sure none of the pins are broken or bent. Use a good strong light to check for debris between the pins.
You're still being a bit vague in your descriptions of what you did. How have you "tested the voltage on each sidecar"? Which points did you measure? What do you see that indicates to you that it's not getting a signal?
DaBossToss
01-10-2010, 11:32
We do not have a different CRIO but i re imaged it and now when i try to upload code to the CRIO i get the error from windriver saying that It failed to launch to target server and that it could possilbly be caused by back end not connected and idk how to read this or what it means.
As Alan Anderson has said multiple times, if you could provide more information on WHAT you have done, we would be able to help you more.
The error you received is because Wind River was unable to connect to the robot. This could be because the I.P. address of your computer is incorrect or you weren't connected to the robot properly elsewhere.
Did you input your team number correctly in the imaging tool?
Did you select the correct language?
DaBossToss
04-10-2010, 11:34
As Alan Anderson has said multiple times, if you could provide more information on WHAT you have done, we would be able to help you more.
The error you received is because Wind River was unable to connect to the robot. This could be because the I.P. address of your computer is incorrect or you weren't connected to the robot properly elsewhere.
Did you input your team number correctly in the imaging tool?
Did you select the correct language?
I did both of those things correctly and i was able to reimage it into java and download code to the robot like that through netbeans but not through windriver. The laptops ip was dynamic so it should not have been that. any other suggestions?
Alan Anderson
04-10-2010, 15:15
The laptops ip was dynamic so it should not have been that.
It could definitely have been that!
What is assigning the IP address? How is the IP range determined? What address is the laptop actually ending up with?
Please, PLEASE try to understand that direct answers to some of the questions we're asking will be very useful to us. We're asking the questions in order to find out information that can help us help you. In many cases, you have answered a simple request not with the actual information or observation requested, but with your interpretation of what you think you observed. In others, you have simply failed to respond to the request. It's hard enough to troubleshoot something remotely when there is perfect communication between the remote "experts" and the person actually able to touch the system.
DaBossToss
05-10-2010, 11:34
It could definitely have been that!
What is assigning the IP address? How is the IP range determined? What address is the laptop actually ending up with?
Please, PLEASE try to understand that direct answers to some of the questions we're asking will be very useful to us. We're asking the questions in order to find out information that can help us help you. In many cases, you have answered a simple request not with the actual information or observation requested, but with your interpretation of what you think you observed. In others, you have simply failed to respond to the request. It's hard enough to troubleshoot something remotely when there is perfect communication between the remote "experts" and the person actually able to touch the system.
BY the CRIO it is determined
we messed around with it but it was 10.13.18.6
i dont know what the IP range is
Alan Anderson
05-10-2010, 13:33
What is assigning the IP address? How is the IP range determined? What address is the laptop actually ending up with?
BY the CRIO it is determined
The cRIO doesn't assign IP addresses.
You said that the laptop was using a dynamic IP address, which means there has to be a DHCP server somewhere on the network, most likely the router. Who configured it?
we messed around with it but it was 10.13.18.6
i dont know what the IP range is
The phrase "messed around" gives no information on what you actually did.
Assuming your cRIO is at 10.13.18.2, the 10.13.18.6 address was correct for the computer you intend to use as a dashboard, and should not have been changed. Set the laptop to have a static IP address of 10.13.18.6 with a subnet mask of 255.255.255.0 and a default gateway address of 10.13.18.4 as specified in the control system manual.
If you want to use the laptop as a replacement for the Classmate, and use it as the Driver Station, you need to set the IP to 10.13.18.5. Again only use 10.13.18.5 if this computer is going to be the DS.
If you could explain your entire setup it would be very useful to us in helping you.
DaBossToss
06-10-2010, 13:29
If you want to use the laptop as a replacement for the Classmate, and use it as the Driver Station, you need to set the IP to 10.13.18.5. Again only use 10.13.18.5 if this computer is going to be the DS.
If you could explain your entire setup it would be very useful to us in helping you.
I dont want to do that but to download code to the robot we use a direct connection with an ethernet cable.
DaBossToss
06-10-2010, 13:30
The cRIO doesn't assign IP addresses.
You said that the laptop was using a dynamic IP address, which means there has to be a DHCP server somewhere on the network, most likely the router. Who configured it?
The phrase "messed around" gives no information on what you actually did.
Assuming your cRIO is at 10.13.18.2, the 10.13.18.6 address was correct for the computer you intend to use as a dashboard, and should not have been changed. Set the laptop to have a static IP address of 10.13.18.6 with a subnet mask of 255.255.255.0 and a default gateway address of 10.13.18.4 as specified in the control system manual.
i configured it just as you said above.
This however is not the problem anymore because we can download code to the CRIO now. We set one solenoid to true and set a motor to .5 and we know that the solenoid worked but the motor did not turn on. any suggestions?
Alan Anderson
06-10-2010, 14:22
If you could explain your entire setup it would be very useful to us in helping you.
I dont want to do that...
Then it's not going to be very easy for us to help.
any suggestions?
Just the same suggestion I've been trying to give all along: give some more detail about what you're doing. For example, are you using a Victor or a Jaguar to control the motor? What does your code look like? What is the status LED on the speed controller doing? What is the speed controller wired to? What kind of motor are you trying to control? Is the Dashboard showing anything for the PWM output you are using?
DaBossToss
07-10-2010, 11:36
Then it's not going to be very easy for us to help.
Just the same suggestion I've been trying to give all along: give some more detail about what you're doing. For example, are you using a Victor or a Jaguar to control the motor? What does your code look like? What is the status LED on the speed controller doing? What is the speed controller wired to? What kind of motor are you trying to control? Is the Dashboard showing anything for the PWM output you are using?
you misunderstood i meant i dont want to use it as the driver station.
The code is just s.set(true); with declarations.
and roller.set(.5); with declarations.
the led on the jaguar is flashing an orange light.
trying to control a cim motor.
I dont know how to check the driver station for the PWM output. how would i do that?
Finally, some information...
More questions for you, How are you communicating with the jaguars? I assume via PWM, but if you could verify this it would be helpful.
If you are running the default dashboard, and the dashboard sender is running on the robot, there are bars in the center of the dashboard that show the output via PWM.
Alan Anderson
08-10-2010, 09:46
Let's back up a little and look at one of the reported symptoms in detail.
As described, the small green blinky light does not seem to flash anymore as it did in competition.
The only time the RSL should remain off is while the cRIO is starting up. This will take about twenty seconds after power is applied or after the cRIO has been reset. If it is not blinking after half a minute, something is very wrong.
Is the RSL still not lighting up, or is it now blinking as it should? The answer to this question will determine the next step in troubleshooting.
DaBossToss
12-10-2010, 11:49
Finally, some information...
More questions for you, How are you communicating with the jaguars? I assume via PWM, but if you could verify this it would be helpful.
If you are running the default dashboard, and the dashboard sender is running on the robot, there are bars in the center of the dashboard that show the output via PWM.
Yes it is pwm and yes we are running standard dashboard. I however do not know how to read the bars can u explain
DaBossToss
12-10-2010, 11:50
Let's back up a little and look at one of the reported symptoms in detail.
The only time the RSL should remain off is while the cRIO is starting up. This will take about twenty seconds after power is applied or after the cRIO has been reset. If it is not blinking after half a minute, something is very wrong.
Is the RSL still not lighting up, or is it now blinking as it should? The answer to this question will determine the next step in troubleshooting.
Yes it is still not lighting up or blinking
Alan Anderson
12-10-2010, 13:09
Yes it is still not lighting up or blinking
Okay, that points to one of three things. Either the cRIO is not properly imaged, one or more of its switches is on where it should be off, or there is an electrical problem.
What is the state of each the cRIO's DIP switches?
On the Diagnostics Tab of the Driver Station application, what is it reporting as the DS Version and cRIO image?
DaBossToss
14-10-2010, 12:25
Okay, that points to one of three things. Either the cRIO is not properly imaged, one or more of its switches is on where it should be off, or there is an electrical problem.
What is the state of each the cRIO's DIP switches?
On the Diagnostics Tab of the Driver Station application, what is it reporting as the DS Version and cRIO image?
We have the most current CRIO image and DS version.
i dont know the state of the switches can u be more specific.
i dont know if this helps or not but we can put code on the CRIO and send signals to solenoids which does not go through the digital sidecar
If the RSL isn't blinking........you probably don't have power going to the Digital Sidecar and/or the cable from the cRio to the DS isn't connected well. We have seen it loosened if there isn't a positive connection to the module in the cRio or the DS.
Alan Anderson
14-10-2010, 13:02
We have the most current CRIO image and DS version.
That's not a helpful answer. How can we know that you know what "the most current" is?
--> Please look at the Driver Station app's Diagnostics Tab and relay what it reports as the DS Version and cRIO image.
i dont know the state of the switches can u be more specific.
The cRIO has a bank of DIP switches between the LEDs and the Reset Button.
Each of the six switches can be either on or off.
--> Is SAFE MODE selected on or off?
--> Is CONSOLE OUT selected on or off?
--> Is IP RESET selected on or off?
--> Is NO APP selected on or off?
--> Is USER1 selected on or off?
--> Is NO FPGA selected on or off?
While you're at it, look at the cRIO's LEDs.
--> Is POWER indicating lit or dark?
--> Is FPGA indicating lit or dark?
--> Is STATUS indicating lit or dark?
--> Is USER1 indicating lit or dark?
i dont know if this helps or not but we can put code on the CRIO and send signals to solenoids which does not go through the digital sidecar
So parts of the robot do respond to the code? That narrows things down a lot. I assume you're talking about using the digital output module in cRIO Slot 8, with the Solenoid Breakout on it, but I'd like to make sure.
---> Is the appropriate LED on the module lighting up when you activate the solenoid?
Let's try confirming that the problem is isolated to the Digital Sidecar.
---> Does the Driver Station report the battery voltage correctly?
It would help a lot if we could see your system. Is there any way you can take a photo of your Digital Sidecar, showing all of its connections? If so, specifically show both ends of the 37-pin cable to the cRIO, both ends of the power connection to the Power Distribution board, and both ends of the PWM cable to your speed controller. Please do it while the system is powered up and enabled, so we can try to interpret what the LEDs are trying to say.
Joe Ross
14-10-2010, 13:57
If the RSL isn't blinking........you probably don't have power going to the Digital Sidecar and/or the cable from the cRio to the DS isn't connected well. We have seen it loosened if there isn't a positive connection to the module in the cRio or the DS.
Or you have the digital I/O module connected to the wrong port in the cRIO.
DaBossToss
14-10-2010, 18:51
That's not a helpful answer. How can we know that you know what "the most current" is?
--> Please look at the Driver Station app's Diagnostics Tab and relay what it reports as the DS Version and cRIO image.
The cRIO has a bank of DIP switches between the LEDs and the Reset Button.
Each of the six switches can be either on or off.
--> Is SAFE MODE selected on or off?
--> Is CONSOLE OUT selected on or off?
--> Is IP RESET selected on or off?
--> Is NO APP selected on or off?
--> Is USER1 selected on or off?
--> Is NO FPGA selected on or off?
While you're at it, look at the cRIO's LEDs.
--> Is POWER indicating lit or dark?
--> Is FPGA indicating lit or dark?
--> Is STATUS indicating lit or dark?
--> Is USER1 indicating lit or dark?
So parts of the robot do respond to the code? That narrows things down a lot. I assume you're talking about using the digital output module in cRIO Slot 8, with the Solenoid Breakout on it, but I'd like to make sure.
---> Is the appropriate LED on the module lighting up when you activate the solenoid?
Let's try confirming that the problem is isolated to the Digital Sidecar.
---> Does the Driver Station report the battery voltage correctly?
It would help a lot if we could see your system. Is there any way you can take a photo of your Digital Sidecar, showing all of its connections? If so, specifically show both ends of the 37-pin cable to the cRIO, both ends of the power connection to the Power Distribution board, and both ends of the PWM cable to your speed controller. Please do it while the system is powered up and enabled, so we can try to interpret what the LEDs are trying to say.
ds version 10.02.08.00
crio image java-2010_v20
all switches on
power led on
all other leds off
Radical Pi
14-10-2010, 19:57
all switches on
That's your problem. For normal operation, all of them (except for possibly Console Out) should be off. No App and No FPGA are disabling user code on the cRIO as well as the I/O. Safe Mode and IP Reset should be kept off as well.
Although if you are getting outputs through the solenoid, it probably means you're just misreading the switches and they are all off
If you're still having trouble after you get the DIP switches corrected, try something on the digital sidecar other than PWM. The Relay Outputs are nice because they have built-in LEDs. However, the digital inputs do not require the watchdog to be enabled.
I would recommend trying both.
Remember that the digital inputs are pulled HIGH, so the switch you connect needs to go between signal and 0v.
DaBossToss
18-10-2010, 11:42
Acctually they were all one way can someone please explain how to tell if they were all on of all off
Mark McLeod
18-10-2010, 11:54
The word "OFF" is printed on the left side of the DIP switches. If the toggle switch is down on that side it is off. You can see it in this picture (http://www.chiefdelphi.com/forums/attachment.php?attachmentid=9275&d=1283032713) another person posted. All these switches are OFF.
There is also a picture on page 33 of the Getting Started (http://usfirst.org/uploadedFiles/Community/FRC/Game_and_Season__Info/2010_Assets/2-2010FRCControl%20System-Getting%20Started-Rev-0.7.pdf) control system manual where the SAFE MODE switch is the only one ON, the others are all OFF.
Alan Anderson
18-10-2010, 11:55
Acctually they were all one way can someone please explain how to tell if they were all on of all off
The word "OFF" should be visible next to switch #1. If the DIP switch is activated in that direction, the switch is off. If the DIP switch is activated in the other direction, where the switch numbers are visible, the switch is on.
If they were all in the same direction and the robot was still at least partially functional, it's a good bet they were all off.
So, how about those other questions I asked a while back?
You said you could control a solenoid.
---> What is the solenoid connected to?
---> When you change the state of the solenoid, do any LEDs also change state? If so, which one(s)?
I'd like to get as specific as possible about what is working and what is not.
---> What is the Driver Station reporting for the battery voltage?
DaBossToss
19-10-2010, 12:02
The word "OFF" should be visible next to switch #1. If the DIP switch is activated in that direction, the switch is off. If the DIP switch is activated in the other direction, where the switch numbers are visible, the switch is on.
If they were all in the same direction and the robot was still at least partially functional, it's a good bet they were all off.
So, how about those other questions I asked a while back?
You said you could control a solenoid.
---> What is the solenoid connected to?
---> When you change the state of the solenoid, do any LEDs also change state? If so, which one(s)?
I'd like to get as specific as possible about what is working and what is not.
---> What is the Driver Station reporting for the battery voltage?
a module in number 8 of cRIO
yes the leds on the side of module change depending on which solenoids we turn on
and i cant answer your last question because ever since i switched all the switches to off except console out i have not been able to communicate.
Alan Anderson
19-10-2010, 13:07
yes the leds on the side of module change depending on which solenoids we turn on
Unless I'm misunderstanding you, that pretty much rules out any remaining possibility of fundamental system software problems, but...
and i cant answer your last question because ever since i switched all the switches to off except console out i have not been able to communicate.
Do you mean that you moved all the switches (except CONSOLE OUT) over to the other side from where they were before? If you had communication with the robot when the switches were where they were originally, they were probably already off, and you've just turned them on instead. Rocker-style DIP switches need to be pushed down on the side nearest the end of the cRIO, where the word "OFF" is.
Are you saying that you can control solenoids without communication working between the Driver Station and the robot? That shouldn't be possible. What exactly isn't working? When you describe the symptoms, don't just say "not...able to communicate." Please indicate the state of the red and green status indicators on the Driver Station display, and tell us the actual words that the Driver Station displays.
DaBossToss
19-10-2010, 18:04
they are all off except console out and so what kind problem is it
Alan Anderson
19-10-2010, 20:26
they are all off except console out and so what kind problem is it
If you can't give the details necessary to diagnose the problem, I can't help further, sorry.
DaBossToss
20-10-2010, 13:50
you asked what position it was in and i told you tell me what else you need
Alan Anderson
20-10-2010, 14:13
you asked what position it was in and i told you tell me what else you need
I'm not seeing answers to many of the questions addressed to you. Here's a repeat of the most recent thing I asked:
Are you saying that you can control solenoids without communication working between the Driver Station and the robot? That shouldn't be possible. What exactly isn't working? When you describe the symptoms, don't just say "not...able to communicate." Please indicate the state of the red and green status indicators on the Driver Station display, and tell us the actual words that the Driver Station displays.
Just so I have a handle on what the person-to-person communication problem might be, is English your first language? Do you have vision problems? I'd be willing to cut you some slack if it's something more than just inattention on your part.
versedaaron
20-10-2010, 16:07
Have you changed the code since it was last working? And have you tried basic vanilla code on it.
DaBossToss
22-10-2010, 12:25
I'm not seeing answers to many of the questions addressed to you. Here's a repeat of the most recent thing I asked:
Just so I have a handle on what the person-to-person communication problem might be, is English your first language? Do you have vision problems? I'd be willing to cut you some slack if it's something more than just inattention on your part.
We have had communication and we can control solenoids but we sent in our cRIO because another team said port 1 was fried so we sent it in to get it fixed.
Do you mean slot 1 of the cRIO chassis? The one that holds your first analog input module?
At any rate, this means you currently do not have a cRIO, and you will tell us the result when you get it back. Am I correct?
DaBossToss
25-10-2010, 11:30
Do you mean slot 1 of the cRIO chassis? The one that holds your first analog input module?
At any rate, this means you currently do not have a cRIO, and you will tell us the result when you get it back. Am I correct?
you are correct and i will let you know when we get it back
DaBossToss
15-11-2010, 12:01
I got the CRIO back and it still does not work but this time new problem we can not deploy code in java using netbeans or in C++ using windriver
--on windriver we get the error message
-failed to connect to target server possibly caused by back end not connected.
--on Netbeans
-we get a socket exception error
i dont know what these errors mean i dont care which one you could help me with but either would work.
Alan Anderson
15-11-2010, 12:57
I got the CRIO back and it still does not work...
Did whoever you got it back from tell you what they did to it? Was there actually a problem that they fixed, or did they just test it and find that it already worked as expected?
but this time new problem we can not deploy code...
The errors suggest that the cRIO's IP address is not compatible with the computer you're trying to connect to it with. Your first step should be to reformat the cRIO using the latest (v20?) image.
The zeroth step should be to browse http://www.usfirst.org/frccontrolsystem and familiarize yourself with what it offers. At the very least, get a printed copy of Chapter 2 (the Getting Started document). You'll want to start with step 2.6, setting up the cRIO.
DaBossToss
16-11-2010, 12:06
Did whoever you got it back from tell you what they did to it? Was there actually a problem that they fixed, or did they just test it and find that it already worked as expected?
The errors suggest that the cRIO's IP address is not compatible with the computer you're trying to connect to it with. Your first step should be to reformat the cRIO using the latest (v20?) image.
The zeroth step should be to browse http://www.usfirst.org/frccontrolsystem and familiarize yourself with what it offers. At the very least, get a printed copy of Chapter 2 (the Getting Started document). You'll want to start with step 2.6, setting up the cRIO.
They said that they fixed a problem with the power supply of the components. thats what the message on the paper they sent back said.
The Crio does have v20 and i have reformatted it and i still get the same error message. for both when i try to deploy and i looked at the guide an i am familiar with the system and it has been set up like that but for my purpose i just have a motor attached to a jaguar in slot 1 on the sidecar. any other suggestions??
acctually now i cant ping it either but i could before
Greg McKaskle
16-11-2010, 19:53
As pointed out earlier, pwm is generated by the digital modules, not the analog. The motor controller should be connected to a digital breakout, and that to a digital module in slot four.
Greg McKaskle
DaBossToss
17-11-2010, 13:32
i know i under stand the set up and do have the sidecar connected to the Crio in module in slot 2 to PWM to the Crio but do you understand what soket exception:Connection reset in netbeans and failed to connect to target server in c++.
Alan Anderson
17-11-2010, 14:08
i know i under stand the set up...
You aren't giving a clear indication that you do understand it. For example:
and do have the sidecar connected to the Crio in module in slot 2 to PWM to the Crio
Greg just told you that the Digital Sidecar should be connected to the module in slot 4.
but do you understand what soket exception:Connection reset in netbeans and failed to connect to target server in c++.
It tells me that the computer you are using is unable to establish a network connection with the cRIO. There could be problems with the physical network (a faulty patch cable or broken ethernet connector, for instance), or one or more of the devices on the network could have a misconfigured address. It is also possible that you have multiple network interfaces enabled, and Windows is unable to determine the proper path to talk to the cRIO.
When you formatted the cRIO, what team number did you give it?
What is the IP address of the computer you are using to try to communicate with the cRIO?
Can you tell us exactly how your network is wired, describing where each cable is connected?
DaBossToss
18-11-2010, 11:42
You aren't giving a clear indication that you do understand it. For example:
Greg just told you that the Digital Sidecar should be connected to the module in slot 4.
It tells me that the computer you are using is unable to establish a network connection with the cRIO. There could be problems with the physical network (a faulty patch cable or broken ethernet connector, for instance), or one or more of the devices on the network could have a misconfigured address. It is also possible that you have multiple network interfaces enabled, and Windows is unable to determine the proper path to talk to the cRIO.
When you formatted the cRIO, what team number did you give it?
What is the IP address of the computer you are using to try to communicate with the cRIO?
Can you tell us exactly how your network is wired, describing where each cable is connected?
gave it 1318 as team number.
10.13.18.7 is the laptops ip adress.
it is a direct connection from our laptop to the router and a direct connection between the router and the cRIO and a direct connection between our netbook and the router.
and btw we can ping the cRIO.
When you say netbook, are you referring to the Classmate given out by FIRST that is used as the Driver Station?
If so, can the Driver Station see the robot?
This can be determined by connecting everything as you said you had it, then looking at the circles in the bottom left of the driver station, one of them says "Connection" or something similar. This circle will be bright green if the Software can see a cRIO.
Is it bright green?
DaBossToss
19-11-2010, 11:46
yes the it is the classmate and it can communicate with the cRIO.
You said you're using Java.
When you open the cRIO re-imager, what language does it say the cRIO is formatted for?
(LaVIEW, C++, or Java?)
DaBossToss
02-12-2010, 11:53
java
did you feed the watchdog?
vBulletin® v3.6.4, Copyright ©2000-2017, Jelsoft Enterprises Ltd.