You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 18, 2024. It is now read-only.
The current Botlab code relies on LCM to communicate with various systems/subsystems. As we move to the Pico, we want to remove Docker and the notions of Flask/Webserver/etc. in favor of a self-contained app that runs in students browsers. Towards that end, we would like that webapp to simply communicate via JSON requests to the robot and receive all of its information that way. Step 1 to making that happen is to update the image on the bots to allow for ROSBridge to run there - the webapp would then become a basic webpage that students would point to in their browser, that then opens a TCP socket to the robot for info exchange.
The text was updated successfully, but these errors were encountered:
I have the full lcm_to_ros + rosbridge -> mbot_app working. I am able to run a lcm log on the pi and update odom values in the browser. It runs slower than realtime over WiFi, but locally is realtime. This may be an issue since we want to cut out NoMachine from the course.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The current Botlab code relies on LCM to communicate with various systems/subsystems. As we move to the Pico, we want to remove Docker and the notions of Flask/Webserver/etc. in favor of a self-contained app that runs in students browsers. Towards that end, we would like that webapp to simply communicate via JSON requests to the robot and receive all of its information that way. Step 1 to making that happen is to update the image on the bots to allow for ROSBridge to run there - the webapp would then become a basic webpage that students would point to in their browser, that then opens a TCP socket to the robot for info exchange.
The text was updated successfully, but these errors were encountered: