yes comunication, yes code but no response by robot

[DaBossToss]

Originally Posted by Alan Anderson

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]

Originally Posted by DaBossToss

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]

they are all off except console out and so what kind problem is it

[Alan Anderson]

Originally Posted by DaBossToss

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]

you asked what position it was in and i told you tell me what else you need

[Alan Anderson]

Originally Posted by DaBossToss

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:

Originally Posted by Alan Anderson

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]

Have you changed the code since it was last working? And have you tried basic vanilla code on it.

[DaBossToss]

Originally Posted by Alan Anderson

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.

[kamocat]

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]

Originally Posted by kamocat

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]

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]

Originally Posted by DaBossToss

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]

Originally Posted by Alan Anderson

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]

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]

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++.