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

wrong checksum for topic id and msg #47

Open
corvusoul opened this issue Feb 23, 2024 · 2 comments
Open

wrong checksum for topic id and msg #47

corvusoul opened this issue Feb 23, 2024 · 2 comments

Comments

@corvusoul
Copy link

Anytime I publish anything I keep getting "[INFO] [timestamp]: wrong checksum for topic id and msg"

I have messed around with delays in code and baud rates and versions of ROS but of no use. I know it's not an error but it is annoying and it would be nice if I can fix this.

@yoneken
Copy link
Owner

yoneken commented Feb 28, 2024

"[INFO] [timestamp]: wrong checksum for topic id and msg"

This message often appears when messages are sent frequently, so could you try adding a wait after sending messages?
The problem may also be resolved by increasing the buffer size.

@bdking3
Copy link

bdking3 commented Apr 12, 2024

I am having the same issue and have verified that buffer size and delay size does not change the behavior. HAL_Delay of 1 or 1000 and buffer size of 512 or 2048, the issue remains.
In fact, the check sum failure occurs for the same number of packets regardless of loop time. If you poll faster, it occurs faster, if you poll slower, it happens slower. In both cases, the same number of packets go by before the first checksum fails. This then happens rhythmically forever. I am running on an STM32L476VGT6U.

I will add that a day later, I have ported everything over to a STM32F413ZHT6U, hoping that moving from a L4 device to an F4 device would put me more in line hardware wise with this library, I still get the same issue.

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

3 participants