Homologation Commands Definition
Operation Code
Given that the Homologation is a special firmware, all the homologation commands have the Operational Code 0x03.
| Asset => Module | Module => Asset | ||||
|---|---|---|---|---|---|
| Request | Answer | ||||
| ID | Name | Description | ID | Name | Description |
| 0x03 | HOM_R | Homologation request command | 0x83 | HOM_A | Homologation answer |
Sub-Operation Code List
Homologation commands are then identified with their Sub-Operational Codes.
The table below provides a list of Sub-Operational Codes as Request Sub-IDs and corresponding Answer Sub-IDs. The IDs are used in the protocol. The names are just for referring to the operations in this document.
| Asset => Module | Module => Asset | ||||
|---|---|---|---|---|---|
| Request | Answer | ||||
| Sub-ID | Name | Description | Sub-ID | Name | Description |
| 0x01 | TCO_R | Start Tx continuous | 0x81 | TCO_A | Answer Tx continuous |
| 0x02 | TDC_R | Start Tx Duty Cycle | 0x82 | TDC_A | Answer Tx Duty Cycle |
| 0x03 | TFH_R | Start Tx Frequency Hopping | 0x83 | TFH_A | Answer Tx Frequency Hopping |
| 0x04 | TLI_R | Start Tx Link | 0x84 | TLI_A | Answer Tx Link |
| 0x05 | RLI_R | Start Rx Link | 0x85 | RLI_A | Answer Rx Link |
| 0x08 | MOO_R | Monitor Operations | 0x88 | MOO_A | Answer Monitor Operations |
| 0x09 | STO_R | Stop Operations | 0x89 | STO_A | Answer Stop Operations |
The following sections discuss the usage of these requests/answers.
Result Code
The answers to the commands listed bellow include a dedicated byte to indicate if the action requested as been executed correctly.
| Result Code | Status |
|---|---|
| 0x00 | Success |
| 0x01 | Busy |
| 0x02 | Fail |
Tx Operations
TCO Start Tx Continuous
TCO_R Request
Start a continuous Tx session.
User can select between the lowest, middle and highest frequency of the L-Band frequencies. More information about frequencies can be found in chapter 4 of the application note Product homologation with embedded Astronode.
User can select between modulated and unmodulated data.
| Sub-ID | Parameters |
|---|---|
| TCO_R=0x01 | 2 bytes |
| Byte offset | Format | Name | Description |
|---|---|---|---|
| 0 | UInt8 | Select Tx frequency | 0 = Lowest frequency 1 = Mid frequency 2 = Highest frequency |
| 1 | UInt8 | Modulation | 0 = Continuous wave 1 = Modulated |
TCO_A Answer
| ID | Parameters |
|---|---|
| TCO_A=0x81 | 1 byte |
| Byte offset | Format | Name | Description |
|---|---|---|---|
| 0 | UInt8 | Result Code | See Homologation Result Code table |
TDC Start Tx Duty Cycle
TDC_R Request
Start a Tx session with a fixed duty cycle (6x frames ON and 5x frames OFF).
| Sub-ID | Parameters |
|---|---|
| TDC_R=0x02 | 0 bytes |
TDC_A Answer
| ID | Parameters |
|---|---|
| TDC_A=0x82 | 1 byte |
| Byte offset | Format | Name | Description |
|---|---|---|---|
| 0 | UInt8 | Result Code | See Homologation Result Code table |
TFH Start Tx Frequency Hopping
TFH_R Request
Start a Tx session alternating between different Tx frequencies within a channel.
User can select between the lowest, middle and highest channel of the L-Band frequencies. More information about the channels can be found in chapter 4 of the application note Product homologation with embedded Astronode.
User can select between “low and high” or “low, mid and high" frequencies hopping pattern.
The hopping order is from low to high frequency and then repeats.
| Sub-ID | Parameters |
|---|---|
| TDC_R=0x03 | 1 byte |
| Byte offset | Format | Name | Description |
|---|---|---|---|
| 0 | UInt8 | Select Tx channel | 0 = Lowest channel 1 = Mid channel 2 = Highest channel |
| 1 | UInt8 | Hopping pattern | 0 = Lowest and highest frequencies 1 = Lowest, mid and highest frequencies |
TFH_A Answer
| ID | Parameters |
|---|---|
| TFH_A=0x83 | 1 byte |
| Byte offset | Format | Name | Description |
|---|---|---|---|
| 0 | UInt8 | Result Code | See Homologation Result Code table |
TLI Start Tx Link
TLI_R Request
Start a continuous Tx end to end session with a frame counter included in the payload content. Feedback (success or failure) can be read via the satellite emulator.
Mid frequency is used for Tx link.
| Sub-ID | Parameters |
|---|---|
| TLI_R=0x04 | 0 bytes |
TLI_A Answer
| ID | Parameters |
|---|---|
| TLI_A=0x84 | 1 byte |
| Byte offset | Format | Name | Description |
|---|---|---|---|
| 0 | UInt8 | Result Code | See Homologation Result Code table |
Rx Operations
RLI Start Rx Link
RLI_R Request
Start a continuous Rx end to end session. Feedback (success or failure) can be read via the Monitor Operations command described below.
Mid frequency is used for Rx link.
User can select between Rx Gain reduced or set to the calibration value.
| Sub-ID | Parameters |
|---|---|
| RLI_R=0x05 | 1 byte |
| Byte offset | Format | Name | Description |
|---|---|---|---|
| 0 | UInt8 | Reduced Rx Gain | 0 = Rx Gain is set to the calibration value 1 = Rx Gain is reduced |
RLI_A Answer
| ID | Parameters |
|---|---|
| RLI_A=0x85 | 1 byte |
| Byte offset | Format | Name | Description |
|---|---|---|---|
| 0 | UInt8 | Result Code | See Homologation Result Code table |
Monitor Operations
MOO Monitor Operations
MOO_R Request
Monitor a Tx or Rx session.
This command returns only the current homologation mode during a Tx session (Tx continuous, Tx duty cycle, Tx frequency hopping or Tx link) and returns all the TLV listed below for a Rx session.
| Sub-ID | Parameters |
|---|---|
| MOO_R=0x08 | 0 byte |
MOO_A Answer
Answer to this command is returned as multiple Type, Length, Value (TLV) combinations. This is for flexibility, fields might be added or removed in future.
| ID | Parameters |
|---|---|
| MOO_A=0x88 | N bytes |
Parameters
| Byte offset | Format | Name | Description |
|---|---|---|---|
| 0 | UInt8 | 1st Module State Detail Type (T) | Describes the type - see below |
| 1 | UInt8 | Length of the 1st detail (L) | Number of bytes |
| 2 | L Byte Value | Value of the 1st detail (V) | Value. If Length > 1: little endian format |
| 3 + (Lprev) | ... | TLV value scheme repeats |
| MOO Type ID | Expected Length | Data Type | Value | Description |
|---|---|---|---|---|
| 0x79 | 1 | UInt8 | Current Homologation mode | 0 = HH_MODE_TX_CONTINUOUS 1 = HH_MODE_TX_DUTY_CYCLE 2 = HH_MODE_TX_FREQ_HOPPING 3 = HH_MODE_TX_LINK 4 = HH_MODE_RX_LINK 5 = HH_MODE_OFF |
| 0x63 | 4 | UInt32 | Time since last satellite search (sec) | This is a relative time (seconds since) because the absolute time may not be known by the module. |
| 0x62 | 1 | UInt8 | Last satellite search peak RSSI | The maximum RSSI seen during last satellite search at the Rx Channel frequency. Expected range 0-30 for most environments, with 0-5 meaning no signal and 25+ saturation. |
| 0x61 | 1 | UInt8 | Last MAC Result | Values are described in the table below. |
| 0x73 | 4 | UInt32 | Rx operations attempt count | How many Rx operations have been attempted since latest RX mode started. |
| 0x72 | 4 | UInt32 | Rx operations success count | How many Rx operations have succeeded since latest RX mode started. |
| 0x71 | 1 | UInt8 | Rx operations success moving average | Percentage of successful Rx operations during the past 1min. |
| MAC Result | Description |
|---|---|
| 0 | None |
| 1 | Success |
| 2 | Satellite not detected |
| 3 | Sync demodulation fail |
| 4 | Signalling demodulation fail |
| 7 | Error |
Stop Operations
STO Stop Operations
STO_R Request
Stop a Tx or Rx session. This command has to be sent before changing from one mode to another.
After a successful answer, it might take up to 6s before successfully entering the next mode.
This command reset the different counters used in the MOO_R Monitor Operation command.
| Sub-ID | Parameters |
|---|---|
| STO_R=0x09 | 0 byte |
STO_A Answer
| ID | Parameters |
|---|---|
| STO_A=0x89 | 1 byte |
| Byte offset | Format | Name | Description |
|---|---|---|---|
| 0 | UInt8 | Result Code | See Homologation Result Code table |