yes comunication, yes code but no response by robot

[Bot190]

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]

Let's back up a little and look at one of the reported symptoms in detail.

Originally Posted by DaBossToss

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]

Originally Posted by Bot190

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]

Originally Posted by Alan Anderson

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]

Originally Posted by DaBossToss

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]

Originally Posted by Alan Anderson

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

[Jon236]

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]

Originally Posted by DaBossToss

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]

Originally Posted by Jon236

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]

Originally Posted by Alan Anderson

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]

Originally Posted by DaBossToss

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

[kamocat]

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]

Acctually they were all one way can someone please explain how to tell if they were all on of all off

[Mark McLeod]

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 another person posted. All these switches are OFF.

There is also a picture on page 33 of the Getting Started control system manual where the SAFE MODE switch is the only one ON, the others are all OFF.

[Alan Anderson]

Originally Posted by DaBossToss

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?