Before commenting read Forum rules
Don't comment the topic if you have a new question.
You can create a new topic selecting correct category from Gurux Forum and then create a new topic selecting "New Topic" from the top left.
Forums
Yesterday I tested to read the MetCom MCS301 via Ethernet-Modem (HDLC) and it worked with LLS.
After some fiddling with settings and keys I managed to connect, read assoc. & values via HLS as well.
Send this to a partner, he was not able to read via HLS. Today a new version of DLMSDirector was updated (8.2.1909.2501) and now I can read the meter via LLS, but it fails via HLS ("connection rejected").
The main issue seems that reading the invocation counter (MCS301 uses 0.0.43.1.0.255) as start value, does not generate the right value to start.
In verbose mode I can see the value been read, let say "715", but to work with MCS301 it must be incremented prior to using (i.e. to "716").
If I manually set the counter (in the security settings tab) to "715" it fails with "connection rejected". If I manually set there "716", it works again as a charm: After reading different objects/attributes and then re-reading Innvocation counter, it's value shows that it's has been incremented for each packet.
Is there a way to tell DLMSDirector, that it should start reading Invocation counter and then increment by one before using like [OBIS-code]+1 ?
Is this specific by Manufacturer or described as such in the standard.?
Has something changed in the implementation in the new release ?
Can you please enlight, how to handle this case with DLMSDirector?
Thanks
Ralph
Hi Ralph,
Hi Ralph,
There are no changes on GXDLMSDirector for this. DLMS standard don't define should invocation counter increase by one. It depends on the meter. We'll check can we read existing meters if we increase value automatically by one or should we add an option to the device settings in GXDLMSDirector.
This takes couple of days.
BR,
Mikko