EnOcean Link
1.14.0.0
Middleware to Connect EnOcean easily to other Projects
|
The maintenance message class, these messages represent an EnOcean maintenance message. More...
#include <eoMaintenanceMessage.h>
Public Member Functions | |
eoMaintenanceMessage (const eoReManMessage &msg) | |
eoMaintenanceMessage (uint16_t u16Size) | |
eoReturn | copyTo (eoReManMessage &msg) const |
Copies the maintenance message to a reman message if the maintenance message is of the sys_ex type. | |
eoReturn | copyTo (eoMaintenanceMessage &msg) const |
Copies to another maintenance message. | |
Public Attributes | |
eoMaintenanceKey | usedKey |
The maintenance key which shall be used, starts by 1 and can be max 15. | |
eoMaintenanceMessageType | type |
The type of the maintenance message. | |
eoMaintenancSecurityState | securityStatus |
State of the security. | |
uint16_t | fnCode |
Remote Management Function Code of the Remote Management Message. | |
uint16_t | manufacturerID |
Manufacturer ID of the Remote Management Message. | |
Additional Inherited Members |
The maintenance message class, these messages represent an EnOcean maintenance message.
This class describes a maintenance message, which represents unchained maintenance telegrams. Maintenance messages are always transmitted secure and normally the eoGateway class tries to encrypt/decrypt it. A decrypted message can than be used for maintenance or configuration tasks, e.g. reman over a secure channels. The user needs to decide which "key" he wants to use for decryption/encryption and if the key has the right access levels for the intended user action. If the automatically decryption failed the user can try to decrypt the message with providing, the key and if needed the SLF,RLC. For more information about maintenance messages and telegrams read the security and reman specification
It contains the payload data, the Source ID and the RORG information.