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

[teleop]: Unknown mode none #572

Open
ddwy opened this issue Sep 26, 2024 · 1 comment
Open

[teleop]: Unknown mode none #572

ddwy opened this issue Sep 26, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@ddwy
Copy link

ddwy commented Sep 26, 2024

When I run the following command, the following error occurs:

ros2 launch crazyflie launch.py

bitcraze@bitcraze-vm:~$ ros2 launch crazyflie launch.py 
[INFO] [launch]: All log files can be found below /home/bitcraze/.ros/log/2024-09-26-11-23-54-513825-bitcraze-vm-30460
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [motion_capture_tracking_node-1]: process started with pid [30462]
[INFO] [crazyflie_server-2]: process started with pid [30464]
[INFO] [teleop-3]: process started with pid [30466]
[INFO] [joy_node-4]: process started with pid [30468]
[INFO] [gui.py-5]: process started with pid [30470]
[teleop-3] [ERROR] [1727349835.433534344] [teleop]: Unknown mode none
[motion_capture_tracking_node-1] logClouds=0
@knmcguire
Copy link
Collaborator

thanks for notifying us! This is indeed something we need to look at, but it shouldn't block you. You can use the launch argument teleop:=false after the launch command to not enable the node at all

@knmcguire knmcguire added the bug Something isn't working label Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants