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