The header structure (ParamMsgHdrDef)
All LAN messages involved in parameter subscription management starts with a ParamMsgHdrDef structure.
typedef struct
  {
  unsigned short usCurrentMsg; // This is the current
UDP package number.
  unsigned short usTotalMsg; // This is the total number
of UDP packages.
  long lSeqNo;
  long lMsgID;
  } ParamMsgHdrDef;
lSeqNo: This is the “Value and attribute update" number. It is incremented for each UDP package. In a Server alive message this means the last used sequence from the server. In an Request retransmit message, this means the UDP package that should be re-transmitted.
lMsgID: This is the identification of the current message. The following values are defined.
•  const long lPM_SERVER_ALIVE = 3;
•  const long lPM_REQUEST_RETRANSMIT = 4;
•  const long lPM_VALUE_ATTRIBUTE_UPDATE = 6;
If the amount of data exceeds the limit of one UDP message, the data will be split into multiple UDP messages. The TotalMsg field contains the number of UDP messages for the current data. This is identified with any number larger than 1. The CurrentMsg field contains the current UDP package number out of the total number of packages.
The actual parameter notification data is organised as follows:
•  Value and attribute update messages
–  Parameter update structures
–  Attribute update structures
•  Server alive message
•  Request re-transmit message