CopterExpress / clover

ROS-based framework and RPi image to control PX4-powered drones 🍀
https://clover.coex.tech
MIT License
399 stars 261 forks source link

Error: No connection to FCU #485

Open shourez opened 1 year ago

shourez commented 1 year ago

The same PC as in https://github.com/CopterExpress/clover/issues/484.

In VM, block programming interface doesn't connect to Gazebo No connection to FCU

okalachev commented 1 year ago

Can you please provide the full launch command output, from the terminal?

shourez commented 1 year ago

Here it is

[Msg] Waiting for master. [Msg] Connected to gazebo master @ http://127.0.0.1:11345 [Msg] Publicized address: 192.168.238.129 [ INFO] [1678127390.344030690]: Finished loading Gazebo ROS API Plugin. [ INFO] [1678127390.351515672]: waitForService: Service [/gazebo_gui/set_physics_properties] has not been advertised, waiting... [Msg] Waiting for master. [Msg] Connected to gazebo master @ http://127.0.0.1:11345 [Msg] Publicized address: 192.168.238.129 [Msg] Loading world file [/home/clover/catkin_ws/src/clover/clover_simulation/resources/worlds/clover_aruco.world] [ INFO] [1678127391.916267973]: waitForService: Service [/gazebo/set_physics_properties] is now available. [INFO] [1678127391.973745, 0.000000]: wait_for_service(/gazebo/spawn_urdf_model): finally were able to contact [rosrpc://clover-dev:35257] [INFO] [1678127391.986251, 0.000000]: Calling service /gazebo/spawn_urdf_model [INFO] [1678127392.989377, 0.004000]: Spawn status: SpawnModel: Successfully spawned entity [ INFO] [1678127393.105277662, 0.004000000]: Physics dynamic reconfigure ready. [spawn_clover_dev_3051_7709871114269057712-4] process has finished cleanly log file: /home/clover/.ros/log/382a859e-bc4b-11ed-a7bf-93a94191dd8e/spawn_clover_dev_3051_7709871114269057712-4*.log [ INFO] [1678127394.532303295, 0.004000000]: Camera Plugin: Using the 'robotNamespace' param: '/' [ INFO] [1678127394.567942426, 0.004000000]: Camera Plugin (ns = /) , set to "" [Msg] Connecting to PX4 SITL using TCP [Msg] Lockstep is enabled [Msg] Speed factor set to: 1 [ INFO] [1678127395.738227341, 0.004000000]: LedController has started (as server) in namespace '' [Wrn] [gazebo_mavlink_interface.cpp:152] No identifier on joint. Using 0 as default sensor ID [Msg] Using MAVLink protocol v2.0 INFO [simulator] Simulator connected on TCP port 4560. [ INFO] [1678127395.983872749, 0.004000000]: Initialize LED Controller [ INFO] [1678127396.007141743, 0.008000000]: ros.roscpp: waitForService: Service [/led/set_leds] is now available. [ INFO] [1678127396.261686602, 0.044000000]: ros.clover: ready INFO [commander] LED: open /dev/led0 failed (22)

okalachev commented 1 year ago

So you got the same errors in the VM image and after the manual installation?

shourez commented 1 year ago

So you got the same errors in the VM image and after the manual installation?

Looks so. But VM at least starts Gazebo, while manual installation doesn't do even that. It may be somehow connected to hardware.