You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is possible for device to not use ReleaseRequest and ReleaseResonse.
Before this was handled by customizing the client, but since we now Have the DlmsConnectionSetting-object it would be better to put it there.
Example:
@attr.s(auto_attribs=True)classDlmsConnectionSettings:
""" Class to hold values and settings to handle different quirks of different dlms server implementations and manufacturers specific irregularity. """# Indicates if the connection and the client should allow for RLRQ to be send.use_rlrq_rlre: bool=attr.ib(default=True)
# In Pietro Fiorentini local communication over HDLC the system title in GeneralGlobalCiphering is omitted.empty_system_title_in_general_glo_ciphering: bool=attr.ib(default=False)
The text was updated successfully, but these errors were encountered:
Some devices does not use the ReleaseRequest and ReleaseResponse to release an association and the lower layer can be disconnecter right away.
Implementing the new setting, how it handled in the connection and in the client.
Fixes#78
* feat(connection): Added use_rlrq_rlre on DlmsConnectionSetting
Some devices does not use the ReleaseRequest and ReleaseResponse to release an association and the lower layer can be disconnecter right away.
Implementing the new setting, how it handled in the connection and in the client.
Fixes#78
-- Smal fixes to CI.
---------
Co-authored-by: Henrik Wahlgren <henrik.wahlgren@utilitarian.io>
It is possible for device to not use ReleaseRequest and ReleaseResonse.
Before this was handled by customizing the client, but since we now Have the
DlmsConnectionSetting
-object it would be better to put it there.Example:
The text was updated successfully, but these errors were encountered: