Tree: 292c90af6d

main

master

my1.12

my1.12-iic

pr-sensor-distance

release/1.12

sbg

tf-1.12

tf-1.12-print_test

tf-iic2uart

tf_driver-1.12

tf_i2c-1.12

tf_i2c_collis_pre

v1.13.0-BW

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '292c90af6d'

${ noResults }

Commit Graph

4 Commits (292c90af6de5d54c4506fa4a8a36334e0a65c0c4)

Author	SHA1	Message	Date
Daniel Agar	d5839e2dd5	optical flow sensor pipeline overhaul ... - all sources of optical flow publish sensor_optical_flow - sensor_optical_flow is aggregated by the sensors module, aligned with integrated gyro, and published as vehicle_optical_flow Co-authored-by: alexklimaj <alex@arkelectron.com>	3 years ago
Matthias Grob	8ca28f3796	Separate message for trajectory setpoint	3 years ago
Christian Llanes	6423ea50e6	add sensor_combined to urtps_bridge_topics.yaml	4 years ago
TSC21	c478e2985a	microRTPS: simplify the attribution of the RTPS IDs by makiing it automatic ... 1. The RTPS IDs are now automatically assigned to the topics 2. Only the topics that get defined to be sent or received in the urtps_bridge_topics.yaml (renamed, since now it doesn't contain IDs) receive the IDs 3. Any addition or removal on the urtps_bridge_topics.yaml file might update the topic IDs - this will require that the agent and the client ID list has to be in sync. This will further require a robustification of the way we check the IDs and the message definitions when starting the bridge.	4 years ago