Difference between revisions of "IoTGateway/CoAP-like"
From ESS-WIKI
Line 45: | Line 45: | ||
*'''Method Not Allowed(4.05): 133''' | *'''Method Not Allowed(4.05): 133''' | ||
*'''Not Implemented(5.01): 161''' | *'''Not Implemented(5.01): 161''' | ||
+ | |||
+ | |||
=IPSO for CoAP-like= | =IPSO for CoAP-like= | ||
− | ==IPSO Smart Object ID= | + | ==IPSO Smart Object ID== |
+ | |||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- |
Revision as of 04:41, 8 March 2016
Advantech CoAP-like Packet Structure
Name | Size ( bits ) |
---|---|
Ver | 2 |
Type (T) | 2 |
TKL: Token Length | 4 |
Code | 8 |
Message ID | 16 |
Length | 32 |
Type (T) : 2-bit unsigned integer Transaction Type field. Indicates if this message is
- Confirmable (0): Some messages require an acknowledgment
- Non-Confirmable (1): Some other messages do not require an acknowledgment
- Acknowledgment (2): An Acknowledgment message acknowledges that a specific Confirmable message (identified by its Transaction ID) arrived
- Reset (3): A Reset message indicates that a specific Confirmable message was received, but some context is missing to properly process it. This condition is usually caused when
- the receiving node has rebooted and has forgotten some state that would be required to interpret the message
Code : : 8-bit unsigned integer
Request
- GET(0.01): 1
- PUT(0.03): 3
Response
- Change(2.04): 68
- Content(2.05): 69
- Bad Request(4.00): 128
- Unauthorized(4.01): 129
- Not Found(4.04): 132
- Method Not Allowed(4.05): 133
- Not Implemented(5.01): 161
IPSO for CoAP-like
IPSO Smart Object ID
Sensor | Object ID |
---|---|
Temperature | 3303 |
Humidity | 3304 |
Magnetic | 3314 |
Accelerometer | 3313 |
Light Sensor | 3301 |
Digital Output | 3201 |
Digital Input | 3200 |
CO2 | 9001 |
CO | 9002 |
Ultrasonic | 9200 |