Alarm summary
Common alarms
Parameters are defaulted or corrupt in some way. Sub code is
from paramStatusT
Messages from a module on the same physical CAN bus are no
longer being received but the module can be seen via a different
CAN bus. This suggests that a cable has come off or a CAN segment
has become faulty. Sub code is the CAN port that is affected
No hellos have been seen from a module
A hello message came from the wrong hardware ID suggesting
duplicate CAN addresses
Something is wrong with the hardware in this module
A directly attached module either shouldn't be there or is on the
wrong port
Subcodes:
0 - Transfer button
1 - Mouseboat hold button
2 - Mouseboat RPM+ button
3 - Mouseboat RPM- button
4 - Mouseboat thrust hold button
5 - Mouseboat station-keeping button
6 - Mouseboat virtual anchor button
The station or side of this module is unknown.
Subcodes:
This module is looking for JIMs but can't see any
This module wants a SCP but can't see any
An error occurred while writing or reading other data from flash or
EEPROM
conflict
The configuration of this module is incompatible with another.
Subcodes:
0 - Gearbox
An internal error occurred and has been logged. Appears in
development builds only
Ship parameters are defaulted or corrupt in some way. Sub code is
from paramStatusT
The calibration data for the inputs and outputs of this module is
invalid
This module is running a un-released development build of the
software
incompatible
INCOM
This module's hardware is incompatible with the software that has
been loaded or the configuration the system is in. Most
incompatibilities are detected in the boot block. Few will fire this
alarm.
Subcodes:
0 - Single jet: The system is configured as a single jet, but the
JIM hardware is too old to support it