I would like the invoke method 1, update_amount (data) in one of my credit objects. I can't figure out how to do this.
Do you support that service, and if no, do you intend to add support?
Thanks in advance, Martin
I just checked and update_amount, set_amount_to_value, and invoke_credit are not implemented to GXDLMSDirector. We'll add them to the next release. It's released at the end of this week.
BR,
Mikko
Hi,
with GXDLMSDirector, writing attribute execution_time of an Single action schedule objects returns an error. I assume the reason for this is, that the 'hundredths' part of time is set to 0xFF.
GB Part2, page 49 states: "For hour, minute, second and hundredths: 0xFF = not specified."
See file for transmission.
Thanks in advance
"not specified" works with most of the meters and it basically means that it's ignored: I know that some meters expect that hundreds are set to zero. Is this the case with your meter?
Hi Mikko,
we would like to be as close to the specification as possible. This helps us in the In case if/when the DLMS conformance test gets more strict and would fail with this violation (even though it is small)
Then you need to handle this on the meter and if it's oxFF you need to skip it.
You can find more information from this in the Blue Book 4.1.6.1 Date and time formats.
Hi Martin,
Hi Martin,
I just checked and update_amount, set_amount_to_value, and invoke_credit are not implemented to GXDLMSDirector. We'll add them to the next release. It's released at the end of this week.
BR,
Mikko
Sounds great, thank you
Sounds great, thank you
Hi,
Hi,
A new version is released where this is fixed.
BR,
Mikko
Hi,
Hi,
with GXDLMSDirector, writing attribute execution_time of an Single action schedule objects returns an error. I assume the reason for this is, that the 'hundredths' part of time is set to 0xFF.
GB Part2, page 49 states: "For hour, minute, second and hundredths: 0xFF = not specified."
See file for transmission.
Thanks in advance
Hi Martin,
Hi Martin,
"not specified" works with most of the meters and it basically means that it's ignored: I know that some meters expect that hundreds are set to zero. Is this the case with your meter?
BR,
Mikko
Hi Mikko,
Hi Mikko,
we would like to be as close to the specification as possible. This helps us in the In case if/when the DLMS conformance test gets more strict and would fail with this violation (even though it is small)
Hi,
Hi,
Then you need to handle this on the meter and if it's oxFF you need to skip it.
You can find more information from this in the Blue Book 4.1.6.1 Date and time formats.
BR,
Mikko
Hi,
Hi,
I miss read the information in Blue Book 4.1.6.1.
I'll implement as you suggest. Thanks a lot for your help.
BR, Martin