robin 73cca7ee8f Fix TF tree conflict via AMCL tf_broadcast off + camera_init->map bridge, raise rosbridge message size limit
- amcl: tf_broadcast:false so AMCL no longer fights the camera_init->odom static bridge for odom's parent (AMCL still publishes /amcl_pose)
- Add a sibling camera_init->map static bridge so global_costmap's map frame keeps resolving with AMCL's TF broadcast disabled
- serial_bridge_node (C++): broadcast odom->base_link TF from wheel odometry, since nothing else in the stack was providing it
- rosbridge_websocket: raise max_message_size to 20MB so large messages (e.g. /map) are sent whole instead of split into 'fragment' messages roslib.js can't reassemble
2026-08-27 11:43:54 +09:00
S
Description
fori_ws fori 자율주행 코드입니다
22 MiB
Languages
C++ 65.6%
Python 22.4%
JavaScript 4%
CMake 3.1%
CSS 2%
Other 2.9%