Look into Spark Max status frames

[CoolSpy3]

This issue is for continued discussion about the points brought up in this Mattermost post.

Basic summary:

• [Spark Max Status Frames]
• Status frame 0 can probably be slower
• Status frames 3/4 can probably be way slower
• Status frames 5/6 should be faster in some instances
• Maybe we should add an argument to MotorControllerFactory.createSparkMax to specify timings

[CoolSpy3]

Sorry, I thought I put a note here about progress, but back in July, we tested this and found that setting the status frame rate to <~150ms caused the Spark Max to drop status frames and the encoder value to occasionally read 0.

We communicated this to REV. Their reply is below:

Thanks for your patience while our software team looks into this issue! From our initial findings, it looks like if you are using the SPARK MAX's onboard PID for Closed Loop Control, then you should not encounter any issues with dropping status frames in your absolute encoder readings.

We understand that this is not ideal for every robot's application and are working to find a way to resolve the issue for using data from your Absolute Encoder over CAN. Unfortunately, I do not have a firm timeline of when we will have a solution for you, but I will keep you updated with any other information we find!