Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CRC not matching: Message 120 (MSP_SERVO_CONF) #22

Open
primetoxinz opened this issue May 31, 2018 · 3 comments
Open

CRC not matching: Message 120 (MSP_SERVO_CONF) #22

primetoxinz opened this issue May 31, 2018 · 3 comments

Comments

@primetoxinz
Copy link

As you can see in this output for msp_read_test the CRC for this message is incorrect.

@christianrauch
Copy link
Owner

Which firmware and version are you using? Are you actually using the servo configuration message?

It might be that the message is truncated because it expects more or less servos than those provided in the message. I.e. the N_SERVO in the message is hard coded to 8, since this is the original message definition from MultiWii. Can you check in the code of your firmware, that it actually sends the right amount of servo configurations?

@primetoxinz
Copy link
Author

This is MultiWii v2.4.
I am not personally using the servo configuration message, just wanted to report the error in the test.
I check in the firmware and it definitely looks like so servo_conf_ servoConf[8];

@christianrauch
Copy link
Owner

I can only reproduce this CRC issue with the msp_read_test on MultiWii. It does not occur with fcu_test+MultiWii or msp_read_test+Betaflight.
If I change the copter type in MultiWii from QUADX to TRI, AIRPLANE or DUALCOPTER, I still receive messages with an expected CRC of 56, i.e. the message will have different payload but the same CRC. I haven't figured out yet why the CRC is constantly set to 56, which is also the message size (8 states * 7 byte).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants