spaceLynk reading 14 byte HEX, how to preserve null characters?

[olemotor]

Hello all,

A KNX device have an object with the DPT 219.001 6 byte alarminfo, which is currently not supported directly by the spaceLynk. It can be read using DPT 16.002 14 byte HEX.

Our problem is that the spaceLynk discards null characters ('\0'), which makes it difficult to decode the data properly. Having logged the object I can see the raw data in the Object data column.

We have tried string.format('%q') without success.

Is there any other way to get the raw data with all null characters read by a script for further processing?

[sesa299442]

What exactly do you need to do with this number?

[olemotor]

Hi Tomas,

The 6 bytes in DPT 219.001 alarminfo represents different error states of the equipment. Our customer would like to monitor this information via the BMS system.

My thought is to split the complete HEX string into two groups (4 and 2 byte) that can be exported to BMS for further processing and decoding. That is however difficult to achieve as long as the length of the raw HEX string varies.

Let me know if you require more details.

Many thanks for your reply.

[lfiat]

Hi Ole Morten,

May you test with this non official FW update (attached), it is for homeLYnk but it has to be possible to install in a spaceLYnk:

this update includes correction for DPT 16.002 14 byte HEX management.

Regards,

Lionel

[olemotor]

Thank you Lionel,

The update was installed and the spaceLynk rebooted.

Unfortunately, the value seems to be interpreted the same way as before the update was applied. Have I missed something?

[sesa299442]

Can you try to use ASCII data type?

[olemotor]

I have tried, the result is exactly the same as with HEX.

Null characters are discarded.

[sesa299442]

If you use ASCII, only zeros on right-hand side should be non-visible.

Actually the zeros are there, they are not just displayed in the view.

[olemotor]

Thanks again,

Using either ASCII or HEX and the script below, with a raw value 0x000300000000 the alert says: "\3"

value = grp.getvalue('4/1/1')

str = string.format("%q", value)

alert(str)

Is there another format to use to make the zeros appear?

[sesa299442]

I do not know why you have the the slash "\" in your alert.

What do you get if you just print log(value) from your script?

Where did you read the "raw value"?

Give me one example of alert you are sending from KNX device:

-expected value in hex

-homelynk object data type

-current value in homeLYnk object list

-value in log (decoded value)

-value in log (object data)

-str from you script

-value from your script

And can you tell me which device you are communicate with?

[olemotor]

Hello,

Attached is a document with the information you have reqested.

If you have time next week I can arrange so you can connect to the spaceLynk controller and have a look yourself. Let me know an appropriate time and I can email you details.

[olemotor · Accepted solution]

For instance, in an event-based script:

value = event.datahex

will retrieve the complete HEX value with all null characters.

Thanks to for pointing out the right direction.