SCHC Network Interface
The content of Acklio FullSDK can be described in its simplistic view as an adaptation layer with the SCHC mechanisms, and a set of interfaces: the Management API, the Datagram API, the Network API and the L2A interface.
Refer to the diagram of layers and interfaces for a better understanding.
The demo examples running on the nRF 9160 board use the following AT commands in their communication sequences.
Send Raw Data
| What | Detail |
|---|---|
| Command | AT#SEND,<data> |
| Parameter | <data> - The IPv4/v6 packet to be sent, as an ASCII HEX string |
| Result codes | OK |
#SEND: <status>,<error> |
Transmissions
The OK result code or an error is returned immediately. If OK was returned, a transmission is attempted.
If the transmission succeeds,
+SEND: 0,0is returned at the end of the transmission.If the transmission fails,
+SEND: <status>,<error>, is returned at the end of the transmission.
The status that can be returned after a transmission failure the following:
| Numeric value | Error code | Comment |
|---|---|---|
| 1 | NET_ERROR | Internal error |
| 5 | NET_L2_ERR | Error from L2 layer |
| 6 | NET_SEND_ABORT_ERR | Session aborted by the sender |
| 7 | NET_RECV_ABORT_ERR | Session aborted by the receiver |
Reception of Data from a Remote Application
| What | Detail |
|---|---|
| Command | — |
| Parameters | — |
| Result codes | #RECVOK: <binary_data> |
| Result codes | #RECVFAIL: <status> |
Received data is an ASCII string containing an hexadecimal value.
The status that can be returned after a reception failure are:
| Numeric value | Error code | Comment |
|---|---|---|
| 1 | NET_ERROR | Internal error |
| 5 | NET_L2_ERR | Error from L2 layer |
| 6 | NET_SEND_ABORT_ERR | Session aborted by the sender |
| 7 | NET_RECV_ABORT_ERR | Session aborted by the receiver |
| 8 | NET_CD_ERR | Error in the CD layer |
| 9 | NET_RULES_NOT_FOUND_ERR | No CD rules found |