It depends on the meter. DLMS standard doesn't set the max length.
In general speaking, there is a max length. Example week profile table it might be sometimes very small, only a few bytes.
in object ActivityCalendar attribute calendar_name is type string and this time field week_profile_name is type bytearray, however in DLMS its both has types an octet string
It's nicer to see "Summertime" than "53 75 6D 6D 65 72 74 69 6D 65". For this reason, values are shown as a string if possible. Some people want to use names like 0x1 and 0x2. In that case, values as shown as a hex string "01".
Hi,
Hi,
It depends on the meter. DLMS standard doesn't set the max length.
In general speaking, there is a max length. Example week profile table it might be sometimes very small, only a few bytes.
BR,
Mikko
thank's. Why does the Python
thank's. Why does the Python version sometimes use the ByteArray object as an octet string and sometimes use str?
Hi,
Hi,
There are few reasons for this. Can you give an example so I'm sure that I'm answering your question?
BR,
Mikko
in object ActivityCalendar
in object ActivityCalendar attribute calendar_name is type string and this time field week_profile_name is type bytearray, however in DLMS its both has types an octet string
Hi,
Hi,
They are converted to an octet string when communicating with the device. Is your week_profile or calendar name non ASCII string?
BR,
Mikko
all right. both attributes
all right. both attributes are ASCII, which is convenient. simple i want understand struct of python objects in gurux.
Hi,
Hi,
It's nicer to see "Summertime" than "53 75 6D 6D 65 72 74 69 6D 65". For this reason, values are shown as a string if possible. Some people want to use names like 0x1 and 0x2. In that case, values as shown as a hex string "01".
BR,
Mikko