Protocol specification · version 5.5.11
Inter Module Communication (IMC)
Every message, field and constant of IMC 5.5.11: how packets are laid out on the wire, what each field means, its unit and valid range, and which messages carry which.
Categories
About IMC
This document describes the Inter Module Communication (IMC) protocol (originally developed by LSTS: https://github.com/lsts/imc) as adopted and extended by OceanScan-MST (OMST) for seamless integration across its maritime robotic systems. IMC defines a structured messaging framework for exchanging self-contained data fields among system components.
Given OMST's diverse operational environments, the protocol is agnostic to the communication channel and includes CRC checks for reliable data transfer for effective coordination across hardware and software components.
OMST leverages IMC for mission planning, vehicle command and control, real-time monitoring and log analysis. For instance, a Command and Control Unit (CCU) may take on planning tasks, supervise operations, and interface with other IMC-compliant systems - including those developed by third parties - through a standardized set of messages. By following IMC specifications, integrators can extend system functionality, exchange sensor data, and command multiple types of vehicles and sensors with minimal adjustments.
IMC Versioning and Message ID Allocation
OMST latest systems follow IMC version 5.5.x, ensuring compatibility with LSTS-developed systems. Each IMC message has a unique identification number (ID) that dictates its interpretation:
- IDs [0,999]: Reserved by LSTS.
- IDs [2000,2999]: Reserved for OMST-developed messages, shared with LSTS.
- IDs 3000+: Available for further protocol extensions.
- ID 65535: Reserved and cannot be used for extensions.
Open-Source Development and Community Contributions
The OMST IMC protocol is open-source and actively maintained at OMST's GitHub repository (https://github.com/oceanscan/imc). OMST is committed to sharing its extensions with the community by synchronizing the feature/unify branches of the OMST and LSTS IMC repositories. Contributions are encouraged through pull requests to help improve and evolve the protocol.