convert β preview live β pick robot β deploy over eth/wifi β RViz
β»
Dashboard stopped
cd ~/Robotics_workspace/yslootahtech/Project/Other/pudu_map_gui ./start.sh
Robots were not touched β anything running on them keeps running.
1Convert a Pudu export
or type/paste a path: folder with map.png+map.json, a .zip, or a folder of
zips (newest wins). Result is saved into the project map library below.
Map library β recent maps
scanningβ¦
converted + edited maps are saved in
Project/Other/pudu_map_gui/maps/ (one folder per map);
robot stage dirs and ~/Downloads are scanned too. Newest first β
Load to preview/edit/stage/deploy, π deletes the set from disk.
2Robot destination
your robots β one shared list everywhere; add/remove them in the Status tab
3Connect & deploy
β not checked
4Nav stack on robot
not checked β pick a robot + IP, then Check
Install = fully-docker stack built on the robot (Go2/R1; ~10β15 min first
time, needs robot internet). Refuses while the stack is live. Progress β Logs tab.
5View in RViz
Preview = no robot needed. The two live views auto-start the robot's
nav stack over ssh if it isn't running (G1/Go2) and wait for it β bring-up alone
never moves the robot; motion still needs a goal you click.
convert a map to preview it here
π― Goal mode: off
π Set location: off
Live: off
β Cancel goal
π¦Ώ checkingβ¦
hover the map
open this tab to scan the map library
no log lines yet
LiDAR
not connected
Fleet & GUI status
Scan targets β your robots
any number of robots β name, type (g1/go2/r1), IP. Saved in this browser.