Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ROS2] Startup Sequence #117

Open
amalnanavati opened this issue Oct 3, 2023 · 0 comments
Open

[ROS2] Startup Sequence #117

amalnanavati opened this issue Oct 3, 2023 · 0 comments

Comments

@amalnanavati
Copy link
Contributor

The user needs a way to start the entire robot software from the app. This will be relevant for two scenarios:

  1. when the user is starting a meal
  2. if the e-stop is flipped, but either the system recovers (e.g., the F/T sensor resumes a stable connection) or the user deems it is safe (e.g., the user presses the hardware e-stop but at a later point wants to continue.)

To enable this, we should do the following:

  1. Write an Ubuntu startup script that launches the web app and a flask server.
  2. The web app should make one or more HTML calls to the flask server to launch all the required ROS components. The flask server should kill any previously running processes and start new ones.
  3. In addition to displaying the watchdog status, the web app should display system diagnostic status from the flask server that monitors which nodes are running.

In this way, as long as the web app is running the user can start the whole system, and if the web app is not running (which is easy to detect) or the Flask server is not running (which we need to display to the user on the web app), the user has someone restart LoveLace and then it should be running.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant