Line 6: |
Line 6: |
| ====Format==== | | ====Format==== |
| T <NODE_NB> <CMD>,<PARAMS> | | T <NODE_NB> <CMD>,<PARAMS> |
− | * '''<NODE_NB>''' Node sending message | + | * '''NODE_NB''' Node sending message |
− | * '''<CMD>''' Telemetry command ALLCAPS | + | * '''CMD''' Telemetry command ALLCAPS |
− | * '''<PARAMS>''' Optional comma separated list of command specific parameters | + | * '''PARAMS''' Optional comma separated list of command specific parameters |
| | | |
| === Complete === | | === Complete === |
Line 16: |
Line 16: |
| | | |
| === Status === | | === Status === |
| + | Report connection status for the node. Sent in response to *70 status DTMF command. |
| + | |
| + | ==== Format ==== |
| + | T <NODE_NB> STATUS,<NODE_1>,0,<NODE_LIST> |
| + | * '''NODE_NB''' Node sending message |
| + | * '''NODE_1''' Node reporting status |
| + | * '''0''' Unknown |
| + | * '''NODE_LIST''' List of nodes connected to NODE_1. Each node number is prefixed by a connection mode as follow: |
| + | ** '''T''' Transceive mode, send and receive audio |
| + | ** '''R''' Receive audio only |
| + | ** '''C''' Connection is pending |
| | | |
| ==== Example ==== | | ==== Example ==== |
Line 21: |
Line 32: |
| | | |
| === Connected === | | === Connected === |
| + | Node connection succeeded |
| | | |
| ==== Format ==== | | ==== Format ==== |
| T <NODE_NB> CONNECTED,<NODE_1>,<NODE_2> | | T <NODE_NB> CONNECTED,<NODE_1>,<NODE_2> |
− | * '''<NODE_NB>''' Node sending message | + | * '''NODE_NB''' Node sending message |
− | * '''<NODE_1>''' Node initiating connection | + | * '''NODE_1''' Node initiating connection |
− | * '''<NODE_2>''' Other node connected to | + | * '''NODE_2''' Other node connected to |
| | | |
| ==== Example ==== | | ==== Example ==== |
Line 32: |
Line 44: |
| | | |
| === Disconnected === | | === Disconnected === |
| + | Remote node disconnected |
| | | |
| ==== Example ==== | | ==== Example ==== |
Line 37: |
Line 50: |
| | | |
| === Removed Already Connected === | | === Removed Already Connected === |
| + | Remote node is already part of the network. Note that it could be a direct connection or it could be the node is connected via other nodes. |
| | | |
| ==== Example ==== | | ==== Example ==== |
Line 42: |
Line 56: |
| | | |
| === Connection Failed === | | === Connection Failed === |
| + | Remote node can't be connected to. |
| | | |
| ==== Example ==== | | ==== Example ==== |
Line 47: |
Line 62: |
| | | |
| === Version === | | === Version === |
| + | app_rpt module version. |
| | | |
| ==== Example ==== | | ==== Example ==== |
Line 55: |
Line 71: |
| | | |
| == L: Linked == | | == L: Linked == |
| + | Sent periodically by a node to broadcast all node linked to it. |
| + | |
| + | ==== Format ==== |
| + | L <MODE><NODE_NB>,<MODE><NODE_NB>,... |
| + | * '''MODE''' Each node number is prefixed by a connection mode as follow: |
| + | ** '''T''' Transceive mode, send and receive audio |
| + | ** '''R''' Receive audio only |
| + | ** '''C''' Connection is pending |
| + | * '''NODE_NB''' Linked node |
| + | If no other nodes are connected, the list is empty and only L is sent. |
| | | |
| == K: Key == | | == K: Key == |
− | === Key Query === | + | Sent by a node to update its keyed status |
| + | |
| + | ==== Format ==== |
| + | K <TO> <NODE_NB> <KEYED> <LAST_KEYED_X_SEC_AGO> |
| + | * '''TO''' Destination to broadcast this message to. Usually * seems to indicate all connected nodes. |
| + | * '''NODE_NB''' Node reporting its keyed status |
| + | * '''KEYED''' 1 = node is keyed, 0 = node is not keyed |
| + | * '''LAST_KEYED_X_SEC_AGO''' Number of second since node was last keyed |
| + | |
| + | ==== Example ==== |
| + | K * 51696 1 2 |
| + | |
| + | === Key Query === |
| + | Message to request other nodes to report their keyed state. Initiating this command results in all connected nodes replying with their keyed status. |
| + | |
| + | ==== Format ==== |
| + | K? <TO> <NODE_NB> 0 0 |
| + | * '''TO''' Destination to broadcast this message to. Usually * seems to indicate all connected nodes. |
| + | * '''NODE_NB''' Node requesting status? Could be * here as well |
| + | |
| + | ==== Example ==== |
| + | K? * 51696 0 0 |
| + | |
| == M: Message == | | == M: Message == |
| + | Text message. Can be sent as node to node or broadcast to all nodes. |
| + | |
| + | ==== Format ==== |
| + | M <TO> <FROM> <BODY> |
| + | * '''TO''' Destination node number. 0 indicates all connected nodes |
| + | * '''FROM''' Source node number |
| + | * '''BODY''' Message content |
| + | Example |
| + | M 0 51696 Reminder net starts at 10:00 pm PST tonight. |
| + | |
| + | == J: ? == |
| + | Status message reporting repeater frequencies. Seems to be only used in the context of the WebTransceiver client. |
| + | |
| + | ==== Format ==== |
| + | J Remote Frequency \n<FREQ> FM\n<OFFSET> Offset\n<POWER> Power\nTX PL <TXPL>\nRX PL <RXPL>\n |
| + | |
| + | == Miscellaneous signaling == |
| + | There are several messages being exchanged that alter the behavior of the app_rpt application. It's unclear as to their purpose. |
| + | |
| + | === New Key === |
| + | Seems that this is meant to be some sort of handshake. When a party receives this command it should send it back. |
| + | !NEWKEY! |
| + | |
| + | === New Key1 === |
| + | Seems that this is meant to be some sort of handshake. When a party receives this command it should send it back. |
| + | !NEWKEY1! |
| + | |
| + | === IaxKey === |
| + | Seems that this is meant to be some sort of handshake. When a party receives this command |
| + | !IAXKEY! |
| + | it should reply with |
| + | !IAXKEY! 1 1 0 0 |
| + | |
| + | === Disconnect === |
| + | !!DISCONNECT!! |