Errors with CTRE Can and Pneumatics!

So, we are setting up some of our code and after deploying we have gotten some errors. Could you please take a look at our code and error and see if you can figure out the problem.

Thank you!

Error:
ERROR 1 CTRE CAN Receive Timeout java.lang.Thread.run(Thread.java:748)
edu.wpi.first.wpilibj.hal.SolenoidJNI.getSolenoid(Native Method)
edu.wpi.first.wpilibj.DoubleSolenoid.get(DoubleSolenoid.java:134)
edu.wpi.first.wpilibj.DoubleSolenoid.lambda$initSendable$1(DoubleSolenoid.java:173)
edu.wpi.first.wpilibj.smartdashboard.SendableBuilderImpl.lambda$addStringProperty$6(SendableBuilderImpl.java:234)
edu.wpi.first.wpilibj.smartdashboard.SendableBuilderImpl.updateTable(SendableBuilderImpl.java:82)
edu.wpi.first.wpilibj.livewindow.LiveWindow.updateValues(LiveWindow.java:282)
edu.wpi.first.wpilibj.IterativeRobotBase.loopFunc(IterativeRobotBase.java:227)
edu.wpi.first.wpilibj.TimedRobot.lambda$new$0(TimedRobot.java:30)
edu.wpi.first.wpilibj.Notifier.lambda$new$0(Notifier.java:97)
java.lang.Thread.run(Thread.java:748)

Error at java.lang.Thread.run(Thread.java:748): CTRE CAN Receive Timeout
edu.wpi.first.wpilibj.hal.SolenoidJNI.getSolenoid(Native Method)
edu.wpi.first.wpilibj.DoubleSolenoid.get(DoubleSolenoid.java:134)
edu.wpi.first.wpilibj.DoubleSolenoid.lambda$initSendable$1(DoubleSolenoid.java:173)
edu.wpi.first.wpilibj.smartdashboard.SendableBuilderImpl.lambda$addStringProperty$6(SendableBuilderImpl.java:234)
edu.wpi.first.wpilibj.smartdashboard.SendableBuilderImpl.updateTable(SendableBuilderImpl.java:82)
edu.wpi.first.wpilibj.livewindow.LiveWindow.updateValues(LiveWindow.java:282)
edu.wpi.first.wpilibj.IterativeRobotBase.loopFunc(IterativeRobotBase.java:227)
edu.wpi.first.wpilibj.TimedRobot.lambda$new$0(TimedRobot.java:30)
edu.wpi.first.wpilibj.Notifier.lambda$new$0(Notifier.java:97)
java.lang.Thread.run(Thread.java:748)

Code: https://github.com/Phred7/PneumaticIssues

Huh, that looks similar to what shows up when it can’t see a PCM; have you checked the web dashboard to see if it’s visible on the CAN bus?

yes, It is device #2

So, we changed it in the code to device 0, and in the web dashboard to 0 and it works now. Not sure why that is a problem