Skip to content

GitLab

"...backbone-message-format.git" did not exist on "4ba55ad594ebb387547a2c9910ba45e3f1bf3c3c"
Switch branch/tag
History Find file
Clone
refactor(docs): add row for autonomy engine's mission plan
Trishna Saeharaseelan authored
4ba55ad5
Name Last commit Last update
docs refactor: schemas and ntoes for observation data
examples refactor: terms used and optional fields
formats refactor: schemas and ntoes for observation data
LICENSE Add MIT License
README.md refactor(docs): add row for autonomy engine's mission plan
__init__.py refactor: schemas and ntoes for observation data
autonomy_configuration.py refactor: terms used and optional fields
platform_status.py refactor: terms used and optional fields
README.md

Message Formats (DRAFT)

Consists of all messages transferred into and out of the Communications Backbone. Message type schemas will be developed once reviewing each platform's data and statuses defined by each partner.

Message Types

Type Summary of File Human-Readable
autonomy_configuration  Autonomy Engine's Configuration file (sent by each C2 if there are any changes) Yes
autonomy_mission_plan  Mission plan generated by Autonomy Engine per platform Yes
mission_plan  Encoded/serialized platform-specific mission plan (shared filepath) No
platform_status  Encoded/serialized platform-specific platform status (shared filepath) No
platform_status Decoded/de-serialized generic platform status Yes
observation  Encoded/serialized observation data from platform for Autonomy Engine (shared filepath) No
observation  Decoded/de-serialized observation data from platform for Autonomy Engine Yes

Breakdown of Message Sources & Types

1/ Autonomy Engine

Transmit

  • mission plan (sent per platform)
  • TBD:
    • Will emergency commands be sent via the autonomy engine (from the GUI) or directly to the C2s?

Receive

  • configuration file
  • emergency stop all
  • decoded ecosub status message
  • decoded reav status message
  • decoded autosub-hover status message
  • decoded ecosub observation data (from squad 1 platforms)

2/ Ecosub C2

Transmit

  • compiled ecosub mission plan
  • decoded ecosub status message
  • configuration file
  • decoded ecosub observation data

Receive

  • mission plan
  • encoded ecosub status message
  • encoded ecosub observation data

3/ Autosub C2

Transmit

  • compiled autosub-hover mission plan
  • decoded autosub-hover status message
  • configuration file

Receive

  • mission plan
  • encoded autosub-hover status message

4/ Reav C2

Transmit

  • decoded reav-60 status message?

Receive

  • mission plan
  • encoded reav-60 status message?

5/ Hermes Box/Hydrosurv Smart Router?

Transmit

  • encoded ecosub status message
  • encoded (or is this already decoded?) reav status message
  • encoded autosub status message
  • encoded ecosub observation data
  • TBD:
    • are there acknowledgment messages from platforms?
    • how are we receiving beacon messages per platform?

Receive

  • compiled ecosub mission plan
  • compiled reav mission plan
  • compiled autosub mission plan
  • compiled ecosub emergency command
  • compiled reav emergency command
  • compiled autosub emergency command