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

[ERROR] [1609744879.430792]: Unable to sync with device; possible link problem or link software version mismatch such as hydro rosserial_python with groovy Arduino #33

Open
deepchand41 opened this issue Jan 4, 2021 · 4 comments

Comments

@deepchand41
Copy link

Using STM32F030 R8 Nucleo Board
Using Ubuntu 20.04, ROS Noetic

@tahakenar
Copy link

I am also facing the same issue with STM32F303RE Nucleo board using Ubuntu 18.04, ROS Melodic.
Couldn't find a solution yet... Also, if I try to use rosserial_server I get "Socket asio error..." and I cannot see the topics that I'm supposed to be publishing from the microcontroller

@Wayne-DWA
Copy link

@tahakenar @deepchand41
check the DMA settings, set the mode to normal and then have a try.
cheers!
cfg

@JinK2000
Copy link

JinK2000 commented May 9, 2023

@tahakenar @deepchand41 check the DMA settings, set the mode to normal and then have a try. cheers! ![cfg](https://user-images.githubusercontent.com/90710539/149395538-a66dc40f-1d64-4bc6-bfe3-13ffe66bf438.pn

it seems doesn't work :STM32F407+ubuntu20.04(notetic)

  • Only in rare cases does it work:

[INFO] [1683649672.768868]: Requesting topics...
[INFO] [1683649673.098597]: Note: publish buffer size is 512 bytes

  • Most of the time it reports an error like this and i don't know how to solve:

[INFO] [1683650864.691406]: Requesting topics...
[ERROR] [1683650879.695435]: Unable to sync with device; possible link problem or link software version mismatch such as hydro rosserial_python with groovy Arduino

@Hbbbbbby
Copy link

I encounter the same issues. Has it been solved now? I found that when the server sent a clock syn signal to the stm32 node, the usart of the node would be interrupted, causing that the message transmits incompletely which might be root of this problem.

But I have no any clear train of thought about it.

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

5 participants