-
Notifications
You must be signed in to change notification settings - Fork 25
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
1104 input signal issue #3
Comments
OK, it was frame corruption that was causing the issue. The 1104 input signal is the same as dshot number 256. When a corrupt frame would happen the dshot number was calculated a 8 bits less and the crc did not pick it up. The dshot number would be read as a 0 which would stop the esc until the zero cross time out happens and the esc restart. I have worked around by just requiring two correct signals in a row for the dshot numbers 0 - 47. I will push changes when i have tested a bit more. |
@conuthead |
OK, the fixed code is up for the signal corruption in dshot and proshot. The next plan I will decrease the buffer length to capture a single signal instead of a double length buffer. |
@conuthead
running at 1104 input , has breaks from time to time (motor stops spinning for ca 120ms)
if you spin slightly higher or lower it does not happen !
yellow is proshot imput
light blue is computeProshotDMA (at function begin)
magenta is calcCRC == checkCRC
dark blue is motor output
Originally posted by @adrianmiriuta in #1 (comment)
The text was updated successfully, but these errors were encountered: