I'm building an IDP serial discovery profile, as per the docs
- Parameter: The value to get from the device during discovery. For serial discovery actions, this contains the commands to be sent to the device, which must be in hexadecimal format.
Setting it to the correct hex value e.g. "49445030010100000100" and checking what is actually sent via WireShark, it's treating the string as ASCII and converting it to hex, is this a bug or a setting I need to change?
A small hint for the method GetUdpSingle in QAction 1, don't convert it to ASCII with 'commandData = Encoding.ASCII.GetBytes(command);', just convert it to an array.
Also the response is only converted to a string from a byte array instead of ASCII.
The whole mechanism needs to be more robust in general though, as information may need stripping off the frontend of the response, or part of a JSON response when it's an HTTP style response is wanted for use in the name, so regex options could go with being added etc.
Hi Philip,
I had a look at the IDP solution, and it does not appear to only support ASCII commands and not hex as per the documentation.
However, the example in the Docs is a valid use case, as it is very common for serial commands to not be representable in ASCII.
As such, we consider this to be a software issue on our side.
Could you please reach out and create a ticket so that you can follow the progress of the issue fix?
If needed, feel free to reach out to Tech Support or support.data-acquisition@skyline.be.