Low Authentication for Iskra AM550 meter fails with 'Authentication failure'

By switch2_app , 17 June, 2024
Forums
DLMSDirector

Hi,
I am using your GXDLMSDirector application to communicate with a Iskra AM550 meter via the RS485 port,

Using a client address of 16 with 'Authentication - None' I can connect with the meter and read the top level objects.

When I use a client address of 17 and low authentication and using a password of '12345678' I keep getting 'Authentication failure'.

I haven't set anything in the 'Secured Connections' tab in the 'Device Properties' popup ie 'Secured Connections - Security' is set to 'None.
The AM550 user manual didn't list any defaults for these, only the OBIS codes which I can't read in 'no security' mode.

Any ideas on why my setup is failing?

Thanks,
switch2_app

switch2_app

1 year 11 months ago

Update.
After some googling I tried a password of '00000000' and Client SAP address of 17 and the connect was successful.
Though the objects are the same as for 'Authentication - None' and like in that mode, I can't read any values.

Kurumi

1 year 11 months ago

Hi,

If I remember right the Low client address for AM550 is 1, not 64.
Try to change that.

If you can't read anything one of your settings (password or client address) is different than the meter expects.

BR,
Mikko

BR,
Mikko

switch2_app

1 year 11 months ago

Hi,
Yes, you are correct, the created screen grab doesn't reflect the client address in the message text.
As it turns out after asking Iskra, a client address of 1 or 17 can be used for read/write permissions. The difference being that 17 only seems a subset of the objects that the admin client address of 1 sees and this later address sees all the objects at the end of the AM550 manual.

As for the read problem, this was finger trouble on my side. If I had clicked the 'refresh' menu item the object list would have been refreshed to the new permission view with read/write access.

Thanks,
switch2_app

Kurumi

1 year 11 months ago

Hi,

The client and server addresses might vary between meter models and the used communication interface. That is always a problem because the meter doesn't reply if they are wrong.

BR,
Mikko