Elster a1800 clock reset to year 2000 with one tariff billing

By zakaria.b , 10 August, 2026
Forums
Gurux.DLMS

Hi to all,
We are managing an AMI project and we designed with our provider an external modem than can connect to different existing meters, including elster A1800. The modem is powered with external 220v source and connected to the elster meter through the rs485 port. The meter has been configured to enable the connection with the modem and the dlms protocol has been activated also to support data collection from our HES.
We observed an issue with the elster a1800 meters with FW3.2 produced in 2011. After days of good data collection, the date and time of meter has been reset to the first day of the year 2000 and the meter is measuring only using T1 tariff instead if the three TOU. Some of the meter has shown full segments screen and no communication was possible through metercat software.
It is important to notice that No time synchronisation has been triggered from the HES nor from the field. This phenomena has been observed only with the meter connected to the modem and the other meters waiting for their roll our are still with the right time.
Can you help please to explain the origine of this problem and the solution to avoid it.
Thanks

Kurumi

1 day 2 hours ago

Hi,

Can you read the meter with GXDLMSDirector and check what year it shows?
Can you also add the hex trace from the meter reply so I can verify this from the bytes?

BR,
Mikko

zakaria.b

22 hours 41 min ago

Hi Mikko.
Thanks for your interest.
We made remote on demand read of the clock of some meters that are still connected to our HES (the other meters disconnected already).
The package send is the following : Send[21]: 00 01 00 01 00 11 00 0D C0 01 4C 00 08 00 00 01 00 00 FF 02 00\n
The received package is the following : Recv[26]: 00 01 00 11 00 01 00 12 C4 01 4C 00 09 0C 07 D0 01 0B 02 16 0F 04 FF 00 00 01\n
Under xml, it give this:
<GetResponse>
<GetResponseNormal>
<!-- Priority: Normal, ServiceClass: Confirmed, Invoke ID: 12 -->
<InvokeIdAndPriority Value="4C" />
<Result>
<Data>
<!-- 11/01/2000 22:15:04+00:00Z -->
<OctetString Value="07D0010B02160F04FF000001" />
</Data>
</Result>
</GetResponseNormal>
</GetResponse>

Let me know if you need any other information.

Thanks
Best regards