Title:
Snags of an Aircable industrial interfacing via Modbus protocols with an energy meter
ISSUE DEFINED: <excerpt>
the current version of
Aircable basic uses the null char {defined as \x00} to flag the end of a string! </excerpt>.
PRIOR SUPPORT RESPONSE: <excerpt>
the next version of the OS will have a
function that will be able to dump to the ports the content from a file
in a binary way. ... The new function will solve this problem.</excerpt>
I'm looking to incorporate AIRCable into a MODBUS environment. Will the \x00 issue still persist, or is there a workaround that has been accepted as a tested and working solution?