> For the complete documentation index, see [llms.txt](https://campus-rover.gitbook.io/lab-notebook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://campus-rover.gitbook.io/lab-notebook/fiiva/cr-package/demos/gen2-demo-instructions.md). # gen2-demo-instructions.md ## Intro Basically all the steps we think are needed to get the [Fall 208 Demo Script](https://github.com/campusrover/labnotebook/tree/dc56aa6edc981881eef46d234f70ff1c55b767ce/demo_script_fall/README.md) to work. This was gathered by the team and then experimented and revised further by Pito during the post-semester break. ### Onboard Laptop Steps: * SSH into the robot’s onboard laptop (turtlebot\@129.64.243.64) * Start a roscore * Do a bringup for the onboard laptop: “roslaunch cr\_ros campus\_rover.launch” * Wait until the bringup finishes. Look for “Odom received” message ### On another machine (needs to be more powerful for this than for the web app) * Run `roslaunch cr_ros offboard_launch.launch` * Wait until the bringup finishes. Look for “Odom received” message ### On a third machine * Install Flask * Clone cr\_web repo * cd into cr\_web * Make sure to bring up TB2 (with cr\_ros), or run a local roscore * export ROS\_MASTERURI=\_ * export FLASK\_APP=rover\_app * flask run --no-reload --host=0.0.0.0 --with-threads *Note: --host=0.0.0.0 and --with-threads are only needed if other client machines need to access the hosted app.* * Go to localhost:5000/, or replace localhost with the other machine’s IP if you’re accessing it from a client machine. (edited) ### Known dependencies: * aruco\_detect (for fiducial\_msgs import error) * pip install face\_recognition * Kobuki docking might be part of the general TB2 install or may need to be separate ### On offboard computer * sudo apt-get install ros-kinetic-moveit-ros-visualization * make sure that ROS\_MASTER\_URI= (or whereever roscore is runnung) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://campus-rover.gitbook.io/lab-notebook/fiiva/cr-package/demos/gen2-demo-instructions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.