This page documents some of the key applications available in the Hovergroup svn.
iAcommsDriver
iAcommsDriver provides our standard interface between MOOS and the WHOI uModem. It implements the GOBY uModem driver class and allows other MOOS applications to make use of the modem through several MOOS variables.
Simple Interface
Great for simple applications or human use.
...
- ACOMMS_RECEIVED_DATA - binary string type - contains all the received data. Data from multiple frames is concatenated together, even if frames in the middle are missing.
- ACOMMS_BAD_FRAMES - string type - comma delimited list of bad frame indices
- ACOMMS_SOURCE_ID - double type - integer ID of the transmitting modem
- ACOMMS_DEST_ID - double type - integer ID of the destination modem (0 = broadcast)
- ACOMMS_RATE - double type - integer rate of the transmission
Unified Interface
Sometimes the simple interface is cumbersome because applications have to subscribe to many variable to get enough information about incoming acomms transmissions. With the unified interface, only one variable is required to send or receive data.
...
With each receipt an object of the AcommsReception class defined in the HoverAcomms libary is posted to the binary string ACOMMS_RECEIVED. This posting is still available if "enable_legacy" is turned on.
Logging
Several postings are made specifically for logging purposes, but applications may use them as well. These postings are always enabled.
...
- ACOMMS_RECEIVED_ALL - string - a loggable serialization of the reception protobuf
- ACOMMS_RECEIVED_DATA_HEX - string - a hex translation of the received data
- ACOMMS_IMPULSE_RESPONSE - string - self explanatory
Additional Options and Special Rates
Mini Packets - Rate 100
Just a 13-bit packet. If only one byte is provided, it will be packed with a leading 0x00. If two or more bytes are provided, only the first two bytes will be taken and a bitwise and with 0x1f will be performed on the first byte. Examples:
...