Overview

The history logs published by the Hex Repeater protocol can include common EFM-related logs such as Audit (hourly) logs and Change (event) logs, as well as non-EFM related logs such as ProductionCycle and Control logs. To help identify each log type during publishing, the Hex Repeater protocol assigns publishing tokens as follows:

• $$Archive.TypeName$$ - This token is filled with the Action Sequence Group subtopic name. If the name ends with an underscore and number, such as “_1” or “_2”, it is removed before assigning the text to the token.
• $$Archive.SubtypeName$$ - This token is filled with the name of the template object. 
• $$Meter.RunNumber$$ - This token is filled with the one-based meter number associated with a log (if the log is associated with an EFM meter); or the equivalent of the number at the end of an Action Sequence Group subtopic name (such as “_1” or “_2”); or the one-based index of the instance number position for manual retrieval logs.
• $$Record.Period$$ - This token is filled with the time period (in minutes) which represents the interval at which the record was archived in the device. Audit logs have a period value of 60. Daily Production Cycle logs have a period value of 1440. All other logs have a period value of 0.

 The following table contains the types of logs defined in the known templates at the time of the first release of the Hex Repeater protocol.