Features & Limitations

A look into what the 1NCE Translation Service can and cannot do.

Features

The 1NCE Data Broker offers Binary Conversion support based on the AllThings Talk Binary Conversion Language (ABCL). More details on the general conversion language available at https://docs.allthingstalk.com/dl/AllThingsTalk_Binary_Conversion_Language_1_0_0.pdf

The Binary Conversion allows customers to simply format Binary payloads and build also more complex logic into the conversion templates. Templates are provided via the 1NCE Rules Engine and applied to the desired Devices.
Let's take the following example for a simple IoT Device with 2 Sensors one Input. A UDP Payload would look like this: 00 1A 00 37 00

As this is not readable let's apply the following Conversion Template to the message:

{
    "sense": [
        {
            "asset": "Temperature",
            "value": {
                "byte": 0,
                "bytelength": 2,
                "type": "int",
                "signed": true
            }
        },
        {
            "asset": "Humidity",
            "value": {
                "byte": 2,
                "bytelength": 2,
                "type": "int"
            }
        },
        {
            "asset": "Switch",
            "value": {
                "byte": 4,
                "type": "boolean"
            }
        }
    ]
}

This will result in a nicely formatted JSON-message that is also human-readable:

{
    "Temperature": 26,
    "Humidity": 55,
    "Switch": false
}

Limitations

  • Only values between -9999999999999999 and 9999999999999999 are guaranteed to have the correct precision. Values smaller than -9999999999999999 and larger than 9999999999999999 could be affected by rounding precision.