Pablo Garrido comments

Results 465 comments of


                                            Pablo Garrido

Adding custom message to Teensy micro-ROS using the docker image fails

Found no problem, cannot replicate: https://asciinema.org/a/AurgtciFlcFTkzAaDn0oomqx5

terminate called after throwing an instance of 'std::bad_alloc'

Hello @Ryanf55, this is a well-known problem and IMO not really a micro-ROS issue. The key is that the ROS 2 `ros_discovery_info` topic has a significant change on its type...

terminate called after throwing an instance of 'std::bad_alloc'

You have the very same error that we found some weeks ago. How are you building the micro-ROS Agent? Are any docker in your system? Because of this line `#26...

terminate called after throwing an instance of 'std::bad_alloc'

Can you provide a Dockerfile with a replicator without the Ardupilot part?

terminate called after throwing an instance of 'std::bad_alloc'

That would be acceptable as far as everything runs inside a Docker.

Behavior of micro-ROS when losing the connection to the micro-ROS-agent

> But also it prints “Failed status on line 36: 1. Continuing” every 1000 ms. You are printing it here `#define RCSOFTCHECK(fn) { rcl_ret_t temp_rc = fn; if((temp_rc != RCL_RET_OK)){printf("Failed...

Behavior of micro-ROS when losing the connection to the micro-ROS-agent

Yes, it seems that somewhere inside our RMW is waiting too long when dealing with DDS entities. Let me check

Fix header location for zephyr 3.2 for udp.

@mergify backport main foxy galactic

Fix header location for zephyr 3.2 for udp.

This will be merged when Zephyr 3.2 is supported

Fix header location for zephyr 3.2 for udp.

@Acuadros95 do we support 3.1 right? Is possible to update to 3.2 as @cmorganBE mentions?