Hi Mikko,
I am reading IS 15959-2 METER Using Gurux for Generic events read
Profile Generic_Voltage Events and current events Read-Count based issue throwing error as "Memory Insufficient" when reading count based for the following below cases
1-With Authentication+Encryption,Our maximum Buffer entry=40, when I am trying to read from 1 to 27
Its throwing error as "Memory Insufficient".
trying with read from: 1 to 26 or below or 1 to 28 above its working fine. Only the Particular read from
1 to 27 only throw the error.
2-Without Authentication+Encryption,Our maximum Buffer entry=40, when I am trying to read from 1 to
27 ,Its reading records up to 26 but the error message not generated
Similar case happens for Billing Profile Generic: here
1-With Authentication+Encryption,Our maximum Buffer entry=12, when I am trying to read from 1 to 5
or 1 to 9 Its throwing error as "Memory Insufficient".
when trying with read from: 1 to 4 or below or 1 to 10 and above or 1 to 6 and above except 1 to 9
above its working fine. Only the Particular read from 1 to 5
or 1 to 9 Its throwing error
I'm sorry. I have missed this. Can you send the trace to me by email? I believe that there is an issue with the meter, but I will verify it from the bytes.
Meter says that there are five rows, but there are only four. Meter is not sending the last row for some reason. Ask the meter manufacturer to check this.
It's easy to verify from the log that you sent me. Lat bytes are 0000A8C0 and it's the 4th row.
Hi Mikko,
Hi Mikko,
Any update on the above issue? Please support
Hi,
Hi,
I'm sorry. I have missed this. Can you send the trace to me by email? I believe that there is an issue with the meter, but I will verify it from the bytes.
BR,
Mikko
Hi,Mikko
Hi,Mikko
thanks for your reply
I Have forwarded a mail with the Log file attached for your verification.Please check it.
Hi,
Hi,
Meter says that there are five rows, but there are only four. Meter is not sending the last row for some reason. Ask the meter manufacturer to check this.
It's easy to verify from the log that you sent me. Lat bytes are 0000A8C0 and it's the 4th row.
BR,
Mikko