Changing parsing parameters!
The parameter #user.data.value, which is currently registered under tags 0xE2 ... 0xE9, has a signed type, which does not comply with the protocol. The registration of the parameter will be changed on December 14, 2023 at 12:00 UTC+0. The parameter value will be changed to unsigned.
This information is confirmed by the hardware manufacturer.
If you need more time to adapt, please let us know via chat.
After the changes have been applied, you can also return the signed value of these parameters using the PVM plugin:
{
"id": 1043089,
"required": true,
"enabled": true,
"validate_message": "",
"item_type": 11,
"name": "pvm-plugin-tester",
"configuration": {
"code": "// define new optional parameter: event.id\n\nrepeat[8, counter=$i, from=1]:\t// cycle for 8 parameters. tag's range 0xE2-0xE9\n\tformat[\"user.data.value.%d\", $i] ==> $name\t// format name to check index of parameter\n\toptional {$name} ==> binary %uint8 ==> input:\t// check if exists parameter with formated name with current index\n\t\t%int8 ==> #user.data.value.signed[index=$i]\t// register signed value"
},
"priority": 0,
"type_id": 1,
"timezone": "UTC",
"metadata": {}
}
JSON plugin configuration can be inserted using the corresponding option in the interface as in the screenshot.
