2,414
edits
Changes
no edit summary
===Codec JSON===
JSON (JavaScript Object Notation) it is a light data exchange format, that due its simplicity to be written and fast interpretation and generation for machines.
JSON (JavaScript Object Notation) is a light data exchange format, that due to its simplicity to be written and fast interpretation and generation for machines.
<br><br>
<br><br>
JSON is made up of two structures:
JSON is made up of two structures:
* A collection of name/value pairs. In various languages this is known as an object, record, structure, dictionary, hash table, key list, or an associative array.<br>
* A collection of name/value pairs. In various languages, this is known as an object, record, structure, dictionary, hash table, key list, or associative array.<br>
* An ordered list of values. In most languages, this is implemented as arrays, vectors, lists, or sequences.<br><br>
* An ordered list of values. In most languages, this is implemented as arrays, vectors, lists, or sequences.<br><br>
As this Codec is based on a subset of the JavaScript Programming Language, Standard ECMA-262 3rd Edition - December 1999. JSON is a text format that is completely language independent but uses conventions that are widely known to programmers of the C family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others. These properties make JSON an ideal language for data exchange.
As this Codec is based on a subset of the JavaScript Programming Language, Standard ECMA-262 3rd Edition - December 1999. JSON is a text format that is completely language-independent but uses conventions that are widely known to programmers of the C family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others. These properties make JSON an ideal language for data exchange.
JSON is an open standard file format and data exchange format used between FMBXXX devices and AWS IoT Shadow Service:
JSON is an open standard file format and data exchange format used between FMBXXX devices and AWS IoT Shadow Service:
Its basic principles are:<br>
Its basic principles are:<br>
* AVL data will be uploaded to Amazon Web Services IOT Shadow service.<br>
* AVL data will be uploaded to Amazon Web Services IOT Shadow service.<br>
* AVL data is JSON key value based<br><br>
* AVL data is JSON key-value based<br><br>
Data sending procedure and logic is same as sending to regular servers, except data is being packed to JSON document as required in Amazon Shadow service.<br>
Data sending procedure and logic are the same as sending to regular servers, except data is being packed to JSON document as required in Amazon Shadow service.<br>
This codec is required to use in Amazon AWS console, it is important to note that AWS uses TLS encryption protocol, and it must be set up the FMBXXX device properly into the AWS IoT service.<br>
This codec is required to use in the Amazon AWS console, it is important to note that AWS uses TLS encryption protocol, and it must be set up the FMBXXX device properly into the AWS IoT service.<br>
Since the '''03.28.00. Rev.00'''''Italic text'' AWS JSON codec is supported.<br><br>
Since the '''03.28.00. Rev.00'''''Italic text'' AWS JSON codec is supported.<br><br>
'''AWS Shadow'''<br>
'''AWS Shadow'''<br>
AWS shadow allows to retain device state, this service reports only latest Shadow state data. Using this mode does not allow to send commands to device or receive responses.<br>
AWS shadow allows to retain device state, this service reports only the latest Shadow state data. Using this mode does not allow sending commands to device or receiving responses.<br>
When using this mode JSON format must be enabled, otherwise data sending will not begin.
When using this mode JSON format must be enabled, otherwise, data sending will not begin.
Using this service device uses x509 certificates to authenticate. No other method is possible. https://docs.aws.amazon.com/iot/latest/developerguide/x509-client-certs.html<br>
Using this service device uses x509 certificates to authenticate. No other method is possible. https://docs.aws.amazon.com/iot/latest/developerguide/x509-client-certs.html<br>
Doc: https://docs.aws.amazon.com/iot/latest/developerguide/iot-device-shadows.html<br><br>
Doc: https://docs.aws.amazon.com/iot/latest/developerguide/iot-device-shadows.html<br><br>
'''AWS Custom'''<br>
'''AWS Custom'''<br>
This mode allows to configure custom topic names, where data will be published and commands received.
This mode allows configuring custom topic names, where data will be published and commands received.
When using this mode all Codec protocols are supported (Codec8, Codec8ext, Codec JSON).
When using this mode all Codec protocols are supported (Codec8, Codec8ext, Codec JSON).
Authentication is same as AWS Shadow.
Authentication is the same as AWS Shadow.
[[File:Codec JSON.png|center|frameless|222x222px]]
[[File:Codec JSON.png|center|frameless|222x222px]]
[[File:MQTT Server.png|center|frameless|300x300px]]
[[File:MQTT Server.png|center|frameless|300x300px]]
Additionally, to develop the fully configuration in the Teltonika device, make sure to use the '''MQTT protocol''', this can be done in the '''''Teltonika’s configurator>>GPRS Server Settings>> and in protocol selecting MQTT.'''''
Additionally, to develop the full configuration in the Teltonika device, make sure to use the '''MQTT protocol''', this can be done in the '''''teltonika's configurator>>GPRS Server Settings>> and in protocol selecting MQTT.'''''
It is important to note that the communication to the AWS IoT Service uses a TLS certificate to authenticate, please follow this link where is explained how to obtain it:
It is important to note that the communication to the AWS IoT Service uses a TLS certificate to authenticate, please follow this link where is explained how to obtain it:
