Skip to content

Feature/jazzy devel updating odinfleet documentation - #60

Merged
ATemova merged 4 commits into
jazzy-develfrom
feature/jazzy-devel-updating_odinfleet_documentation
Apr 19, 2026
Merged

ATemova merged 4 commits into
jazzy-develfrom
feature/jazzy-devel-updating_odinfleet_documentation

Conversation

@Paveljolak

Copy link
Copy Markdown
Collaborator
  • Changed the naming from "open-rmf" to "odin_fleet", and so on (OpenRMF -> OdinFleet, etc).

  • Deleted "OdinFleet Advanced Page" until we have something decent and worth showing.

  • Added screenshots of our web dashboard and cleaned up explanations.

  • Anything that was vague and not needed was deleted.

Suggestions for improvements:

  • I would also add how to add a robot to a fleet, how to add a map to the dashboard.
    I would add this stuff only once we have something decent. For now I think we can ignore them, as everything is in a prototype phase.
  • Another page might be added to explain users how to setup OdinFleet by themselves. This should be done last, once we have a stable system.

The **Fleet Manager** acts as the bridge between OdinFleet and individual robot fleets.
It translates OdinFleet commands into vendor-specific instructions for each robot.
It collects status updates, and reports back to the system.
By doing so, it enables coordinated operation across heterogeneous fleets, ensures safe navigation, and allows multiple robots to share tasks and resources efficiently within the same environment.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The "Fleet Manager" description here actually covers the Fleet Adapter's role — it's the adapter that translates RMF commands into vendor-specific instructions, not the Fleet Manager. The Robot Adapter/Client layer is also missing entirely; the three-layer stack (Fleet Adapter → Fleet Manager → Robot Client) should be distinguished.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will be updated in the next iteration.

- **Go to Place** - Sends a robot or an entire fleet to a specified location on the map.
- **Patrol** - Commands a robot or fleet to continuously move between defined waypoints.
- **Delivery** - Directs a robot to pick up an item from a specified location and deliver it to a designated drop-off point.

@Oussama-Dallali99 Oussama-Dallali99 Apr 15, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Delivery is a custom action ,so it s better to be Custom Action (delivery,cleaning...) than mentioning one of them

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do these custom actions, come by default, or there should be work done by us to get them up in our current iteration. If they are not implemented in our current system, we are not mentioning it.
In my knowledge we got delivery up and running.

@ATemova
ATemova merged commit 3acb669 into jazzy-devel Apr 19, 2026
@ATemova

ATemova commented Apr 19, 2026

Copy link
Copy Markdown
Collaborator

I went through everything, and this version is the best one for our system so far. What I would preferably change in the near future is the section with the web application screenshots.

@Paveljolak

Copy link
Copy Markdown
Collaborator Author

@ATemova Change the web application screenshots in what way?
What would you change?

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

Successfully merging this pull request may close these issues.

3 participants