If a parsing error occurs during decode of an AK response, then the remaining parameters are not decoded and 0's are returned for their values

[labviewmantc]

For the AK protocol, the add-on expects numbers (represented as strings) for each returned parameter, but, if there is an error converting the string to a number, all further processing of the response is stopped and 0's are returned for their values.

Suggestion: continue processing/parsing the remaining parameters. The final overall error code would be bit-mapped to indicate which parameter(s) has an error and use a base error-code of 0x80000 with bits 0 thru 15 to indicate which parameter(s) had the decode error. And the value for the parameter(s) that had the conversation error would return a globally user-defined value (for the driver) such as -999.999 so data being collected or displayed in Veristand can show the data is not available or in an error state).

[bogdanp-ni]

Hello @labviewmantc,

Sorry for the delayed response, we'll take a look at this issue.