-
My non-Create robot worries a lot about his battery voltage and charging state both on and off his ancient iRobot dock.
The Create3 sim /battery_state topic is reporting 0v, 0 current, and 0 capaci…
-
**Describe the bug**
After base_footprint was removed, base_link was moved to compensate.
All links that have base_link as a parent need to be readjusted
![frames_wrong](https://user-images.githu…
-
I'm guessing you all will get to implementing the wall follow action described in the docs in time:
>ROS 2 Actions
>You can see the ROS 2 action servers exposed by the Create® 3 robot running the …
-
# Handle
robee
# Vulnerability details
The following functions could be set external to save gas and improve code quality.
External call cost is less expensive than of public functions.
…
-
the topic /ir_opcodes should publish some predetermined codes to describe what the robot's forward facing IR receiver and Omni receiver see from the dock's IR emitters.
The table below describe wha…
-
The Create 3 dock does not produce op code 173 when the robot is within all three zones (2 buoys + forcefield) as older docks used to do. Instead, it cycles between buoy and forcefield codes. A code s…
-
**Description of the problem/feature request**
A clear and concise description of the problem, or the proposed new feature.
Add four new templates (shown in **bold** in the table below) and checks…
-
-
**Is your feature request related to a problem? Please describe.**
The behavior of the ir opcodes is more of the robot's beacon being a receiver of the dock emissions as opposed to the intersection o…
-
Create3 battery was run down to 3% then docked successfully.
```
$ ./dock_it.sh
1636292626.039450 [0] ros2: using network interface wlan0 (udp/10.0.0.29) selected arbitrarily from: wlan0, …