REV Spark Flex CAN Timeout. Periodic Status 2

Technical CAN
21

I tried calling setReference directly, but it didn’t make any difference. I added a debug print to see if it was doing any retries and it’s not. That means in our case it is reporting kOk but reporting a timeout error to the DS. That sounds like a different situation than what @Nigelientje was seeing. @jan

22

I was very wrong about this, but REVLib 2025.0.1 has been released with a fix for this.

However, we are still investigating the status frame timeouts. From further testing, I am confident in saying that this is limited to Flex.

1 Like
23

We are having similar issues. Although we are not running YAGSL but the Advantage kit Spark Swerve template. We are seeing the Periodic status 2 error as well as a Periodic Status 0 error.

The CPU Utilization was solved with the new REVLib version (went from 95% to 45%

https://www.chiefdelphi.com/t/revlib-2025-cpu-utilization-increases/481295/7?u=paniclemming

24

We’re having the same issues. Both our rear motors will have CAN timeouts and then disconnect/lose pose estimation.

Tried with the REV MAX swerve template that’s been adapted, YAGSL, and the AdvantageKit REV template.

25

We were able to fix this by disabling the check in the SparkOdometry file if you comment out this line: “if (sparks.get(i).getLastError() != REVLibError.kOk) {
isValid = false;” It will allow you to use your odometry and we haven’t seen any errors so far in that odometry. However once rev does release a fix for this issue I would reccomend adding this back in

1 Like