Why does DataMiner prefer even number of bytes?

Solved250 viewsprotocol QAction SetParameter
3
0 Comments

Hi,

I have a parameter

that I set from QAction

If I set value with odd number of bytes, for example "0x02 0x31 0x12", and then fetch that same parameter value with SLProtocol.GetData, I get "0x02 0x31 0x12 0x00".

However if I set even number of bytes, for example "0x02 0x31 0x12 0x03", and then get the same parameter value, I get the expected "0x02 0x31 0x12 0x03".

Is there a reason why DataMiner seems to prefer even number of bytes and if so, how might I disable this behaviour?

Thanks,
Cheers

Edib Šupić [SLC] [DevOps Catalyst] Selected answer as best 22nd April 2025

1 Answer

5
8.89K 1 Comment

Hi Edib,

This is probably because the parameter is internally being converted to a string in a unicode connector. Can you please try setting the parameter with SetParameterBinary instead of SetParameter, and see if it still happens?

If the parameter is being used in a serial command, this option might also be needed: ascii.

Hopefully this helps solving the issue.

Edib Šupić [SLC] [DevOps Catalyst] Posted new comment 22nd April 2025
Edib Šupić [SLC] [DevOps Catalyst] commented

Hi Tom,
Using SetParameterBinary did the trick.
Thanks
You are viewing 1 out of 1 answers, click here to view all answers.