Introduction 2 Introduction The TcEventLogger is Beckhoffs standard alarm and event concept. It helps to trigger and visualize warnings, errors, information or status messages from the PLC. By using the TcEventlogger for your Alarm & Event implementation you are able to realize the following requiremets: 1. Issue Alarms and Events from the PLC 2. Manage events throug the TcEventLogger 3. COM APIs for HMI development 4. Fully featured ActiveX control for display of events 5. Support for implementation of distributed systems: The HMI can easily display events of a remote PC 6. Load language specific message texts from a database The TwinCAT Message-Concept:
Messages (Events) Each message is identified by a Source- and an Event ID. The Source ID is assigned to a machine and the Event ID is assigned to a certain event of that machine. Source names and event messages are stored in a certain database file. When an event is issued, the TcEventLogger looks up the appropriate message in its database and provides it to its clients. Clients typically are applications like HMIs. For each event additional "document links" may be stored in the database. Each DocLink is identified by its name and contains a link to a file.
Processing of these links is up to the clients - the TcEventLogger only provides functionality to lookup the link itself (see ' message formatting [ } 10] ' for details). Message Triggering You can use a simple Function Block to signal an event from the PLC. As soon as an event is issued (or its state changes) the TcEventLogger notifies its clients about this event. The client is called and a TcEvent [ } 157] COM object supplied. Using this event object, the client can access the event and e.g. query a completely formatted message string in the appropriate language from the database. TcEventLogger 10 Version: 1.1