-
Notifications
You must be signed in to change notification settings - Fork 8
Cheatsheet
ros2 launch mep3_bringup robot_launch.py color:=purple namespace:=big bt:=false nav:=false regulator:=false strategy:=first_strategyWhile testing there is no need to run the whole ROS stack, it is safer and faster.
For example, if you are testing the motion then you can turn off the behavior tree (bt:=false).
Or, if you are testing a strategy with servos only then you don't need the navigation (nav:=false regulator:=false).
Mounting the strategy folder is probably the easiest approach to change a strategy:
nautilus sftp://[email protected]/home/ubuntu/ros2_ws/src/mep3/mep3_behavior_tree/assets/strategiesThe command should open Nautilus (a file explorer) with all available strategies.
To execute the strategy run the robot_launch.py file (ros2 launch mep3_bringup robot_launch.py strategy:=first_strategy ...).
Given that the strategy executor is an independent node and ROS 2 allows nodes to interact anywhere on a network we can start the strategy executor independently:
ros2 run mep3_behavior_tree mep3_behavior_tree first_strategy --ros-args -r __ns:=/bigThis should significantly speed up the development process, especially considering that you can start the strategy on a PC (no need to run on Raspberry Pi). Note that you have to start the rest of the system on the Raspberry Pi:
ros2 launch mep3_bringup robot_launch.py bt:=false ...
sudo apt install avahi-discoversudo hostnamectl set-hostname $NEW_HOSTNAME
hostnamectlsudo useradd --create-home $NEW_USERNAME
sudo passwd $NEW_USERNAMEsudo vim /etc/netplan/*.yaml
sudo netplan applyYou don't need a password to login into a Raspberry Pi, you can use a public-private key pair. Append the content of the ~/.ssh/id_rsa.pub file (host) to the ~/.ssh/authorized_keys file (Raspberry Pi).