<< Click to Display Table of Contents >> Navigation:  »No topics above this level« Description

mapp Services V5.16

This function block can be used to log all events to a buffer that are also entered in the mapp Services Logger in order to prepare them for the VC4-based HMI application.

All mapp components forward various events to the Logger. Some of the events forwarded to the Logger are errors. This function block stores these events in an internal buffer in order to prepare them for the VC4-based HMI application.

Selecting events

Inputs "Scope", "MpLink" and "EntryFilter" are used to select the events that should be logged.

All events

If input "MpLink" is not connected, then all events are selected. Input "Scope" is not taken into account in this case.

Events from a certain mapp component

The mapp component from which events should be logged is specified via the "MpLink" on the input (e.g. the events of a conveyor belt with gConveyorLink as MpLink). Element mpCOM_CONFIG_SCOPE_COMPONENT is also specified on input "Scope".

Events from a machine group

A machine group can be part of a machine or a robot with all of the axes under its control. Information about setting up a machine group (hierarchy) can be found in section Creating modular applications. The "MpLink" of the group must be selected in order to select all events from a machine group.

Filtering events via "EntryFilter"

Input "EntryFilter" can also be used to further filter which events should make it to the buffer and which should not. Events filtered out by this filter are discarded. This filter makes it possible to filter according to mapp component, level, area or even error numbers, for example. The input format of the filter looks like this:

•FilterType=FilterArea

•FilterType1=FilterRange1,FilterType2=FilterRange2

•FilterType1=FilterRange1,FilterType2=FilterRange2-FilterRange3,FilterType4=FilterRange4

As can be seen here, it is also possible to define several filters one after the other. The following table lists the available filter types and filter areas:

Filter types can be combined as needed:

•Component=gAxisConveyorLink,Severity=ERROR

•Component=gAxisConveyorLink,ErrorNumber=4007

•Component=gAxisConveyorLink,Component=gAxisCutterLink,Severity=ERROR

Buffer size

The function block buffer can generally hold up to 100 entries. If a different amount is necessary, the optional input "BufferSize" can be used to define how many entries should be able to fit in the buffer. The buffer can be cleared on a positive edge of input "Clear". This deletes all logged entries. Command "Clear" can be used in the application, e.g. in combination with command "ErrorReset" of an axis to acknowledge the most recent axis errors and to simultaneously clear the buffer that was used to display the errors in the HMI application.

MpComLoggerUIConnectType

Structure "UIConnect" is divided into the following areas:

•List: Shows the events with all associated details

•Clear: Deletes all events from the buffer.

•SearchFilter: An additional string filter mechanism that can be used via the HMI application. Filters the events according to the component entered. If the filter is deleted, then all events are displayed again.

Command "Clear" in the UIConnect structure corresponds to command "Clear" command on the function block input. This command is only intended for use on the HMI, however, not in the application. "SearchFilter" does not delete any events from the buffer. It only filters them temporarily until the filter string is reset. A component can be selected via MpLink using "SearchFilter":

•gAxis01Link

•gConveyorLink

•gAxis*

* can be used to filter multiple components. If specific combinations are needed, then the same filter types and ranges as with "EntryFilter" can be used.

MpComLoggerUISetupType

"LoggerListSize" defines in this structure how many events should be displayed on one page of the HMI application. "LoggerListScrollWindow" determines how many events are displayed in advance when scrolling up and down.