CANdle acts as if there is loss of signal

We are experiencing an interesting issue with our CANdle, where the associated LEDs only display color for a moment, and then turn off. We were able to determine that this is due to the “loss of signal” behavior. If we configure configLOSBehavior(false), then the LEDs will remain on, and it will function as intended. However, with configLOSBehavior(true), the LEDs will turn off immediately after turning on, as if a loss of signal was immediately detected.

Everything else seems to be working fine. However, we want the behavior where loss of signal is evident due to the LEDs turning off. On a previous team I mentored, we were able to set configLOSBehavior(true) without any issues.

Do you have any advice to us on why the CANdle might be detecting “it loses communications to the Controller” immediately, and what we might be able to do about it?

Thank you in advance.

We are experiencing the same issue as well, but the configLOSBehavior didn’t do it for us. Can you share your code?

@cantogr07 Well, I completely lost track of this question. I don’t know if you ever solved it, but we stuck with configLOSBehavior(true) and never got a chance to revisit it. Our code is here: Robot/src/main/java/frc/robot/subsystems/LEDSubsystem.java at main · LynkRobotics/Robot (github.com)

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.