We have observed one failure under below scenario,
Electricity Meter Load Profile data is being read block by block through Cellular Communication Module. During one of the blocks, the response from Meter got lost in Network and did not reach to Gurux Director within timeout, hence Gurux retired for the same block, but this retry request is rejected by Meter as the Invocation Counter within the meter was higher than the used by Gurux.(The counter within the meter got incremented for response packet which never reached to Gurux, hence creating the mismatch).
Hence, during retry it is required that Gurux should increment the counter even if the response for previous request has not received.
Can you please check this and confirm?
You are right. GXDLMSDirector re-sends the generated message and doesn't generate a new message. The reason is that there are meters that can't handle if the invocation counter value is increased on re-send.
I'll need to think about how to handle this. I believe that there will be another parameter for GXDLMSDirector so older meters can also be handled.
Hi Anil,
Hi Anil,
You are right. GXDLMSDirector re-sends the generated message and doesn't generate a new message. The reason is that there are meters that can't handle if the invocation counter value is increased on re-send.
I'll need to think about how to handle this. I believe that there will be another parameter for GXDLMSDirector so older meters can also be handled.
BR,
Mikko