There is Some improvement required in GDLMSdirector in Password change
mechanism.
Association LN Object has two options for SECRET change :
1. LLS secret is changed by writing attribute 7
2. HLS secret is changed by method 2
GDLMSDirector provided only one feature at a single time i.e If current
association is HLS association it uses Method 2 and if Current Association is
LLS then it Writes Attribute 7 when Button "Update" is used.
My question is what if My meter has two Associations one HLS and One LLS and
Access of Password change is provided only to HLS Association. (As In Indian
Standards)
Now as LLS Association has no access and when i change password from HLS
association it uses Method 2 which can not be use to change the LLS secret.
I suggest two different windows should be available for both HLS and LLS
secret change.
Yes, I understand the problem. The password is changed usually for the current authentication level. I'll add this to the work list. We'll think something to support Indian standard better.
It is not only for Indian Association. It is Applicable for DLMS standard and SEC standard Also.
E.g. in SEC standard, Only One OBIS code is defined for both LLS and HLS authentication and HLS authentication can change password for both LLS and HLS.
so How would it change the LLS password Even using Current association.
So Attribute 7 and Method 2 shall be differently accessible.
Password Change
Hi,
Yes, I understand the problem. The password is changed usually for the current authentication level. I'll add this to the work list. We'll think something to support Indian standard better.
BR,
Mikko
Password change
Hi,
It is not only for Indian Association. It is Applicable for DLMS standard and SEC standard Also.
E.g. in SEC standard, Only One OBIS code is defined for both LLS and HLS authentication and HLS authentication can change password for both LLS and HLS.
so How would it change the LLS password Even using Current association.
So Attribute 7 and Method 2 shall be differently accessible.