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

Application stuck on "Waiting for device" #79

Open
Cagdas4 opened this issue Sep 20, 2023 · 5 comments
Open

Application stuck on "Waiting for device" #79

Cagdas4 opened this issue Sep 20, 2023 · 5 comments

Comments

@Cagdas4
Copy link

Cagdas4 commented Sep 20, 2023

Issue template

Steps to reproduce the issue

Run the application on an Ubuntu 22.04.3 VM on a Windows 11 machine
Launch the application normally through "Docker-compose up -d"

Expected behavior

Board is recognized

Actual behavior

App stuck on "Waiting for device"

Additional information

I've tried everything that came to mind, the connection is there, the firmware is properly configured and the board is recognized. I granted every access permission I could think of, as well.

I'd really appreciate any help or advice, and please let me know if you'd like me to provide more information.

Update: After days of trying, it magically seems to have resolved itself. However, when I list the ros2 topics in my terminal, nothing seems to appear. When I try to publish on the LEDs, it can't find any subscriptions either.

@Cagdas4
Copy link
Author

Cagdas4 commented Sep 20, 2023

I'm having issues with micro-ros-agent as well. Though I don't know if they're related. When I try to launch it with my board attached, it says "error 13 please run with superuser privileges. Error while starting serial agent!". Again, I tried to give it any permission I could think of.

@pablogs9
Copy link
Member

Hello @Cagdas4,

  • As far as I understand you have managed to flash your board and run the micro-ROS Client in the MCU. Is that right?
  • The permissions error in the micro-ROS Agent is just a matter of providing your user enough Linux privileges to open a serial port, not really related to micro-ROS. A quick look drives me to a possible solution consisting in adding your user to dialout group (check here). Another option is running the micro-ROS Agent with sudo
  • Finally, the repository you are using is archived and deprecated, probably this will be a source of problems. The recommended option for running micro-ROS on top of Zephyr RTOS is using the micro-ROS Zephyr module

@Cagdas4
Copy link
Author

Cagdas4 commented Sep 26, 2023

Hi @pablogs9

Thank you for your reply. I guess I forgot to mention I already tried adding the user to dialout as well as using sudo. No results there.

I'll give the up to date repository a shot too. Thanks for the heads up.

@Cagdas4 Cagdas4 closed this as completed Sep 26, 2023
@Cagdas4 Cagdas4 reopened this Sep 26, 2023
@pablogs9
Copy link
Member

The serial permission problem shall be solved with one of this options: https://stackoverflow.com/a/27886201

@Cagdas4
Copy link
Author

Cagdas4 commented Sep 26, 2023

I did follow that post when dealing with this problem initially. But I don't think I tried the one using vim. I'll go over them and give vim a shot. Thanks!

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