Events/Messages

Use this dialog to configure operator messages.

Events/Messages dialog

param

Enable events/messages

Check this field to enable operator messages.

param

Reserved program name

Use this field to specify on or more reserved names. To trigger a message, the received program must match one of the reserved program names. If no reserved names are specified, you must specify a trigger below.

To specify multiple reserved names separate them with comma.

Example: 8001, 8002

param

Trigger

Use this field to specify a trigger.

If no trigger is specified, any program matching the specified reserved name will trigger this message.

param

Message tag

Use this field to specify a 'tag' for this message. Tags can be used to group messages in the log.

param

Log Text

Use this field to specify the text that should be stored in the log, and/or send as an e-mail message.

param

Must be inside first comment

Check this field if the specified trigger must be inside the first comment.

If this field is not checked, the trigger can be located anywhere within the first 20 'lines' of the program.

param

Add to port log

Check this field to add the selected message to the normal port log.

param

Only use with DPRNT messages

Check this field if this message should only be used when receiving DPRNT style messages.

If you have not specified a reserved name and you are using DPRNT messages then you should probably check this option.

If no reserved program is specified then any program containing the trigger string will be processed as a message unless this option is checked.

param

Save received file

Check this field if the received program should also be save.

param

Message type

Use this field to specify the type of message.

The type of message can be used to redirect messages to either the log, or send them as e-mail pager messages.

param

Extract value ($MSGTEXT)

Use this field to specify how the $MSGTEXT should be extracted.

param

Operator trigger

Use this field to specify a trigger to get the operator name from the message.

When using a string trigger, the operator name must follow the trigger until the first space, newline or end of message.

When using an advanced trigger the <> operator must be used to extract the operator name.

param

Re-map message

Use this field to remap the message tag depending on the operator logged in.

Example to map the message to GOODPART when an operator in the NC-Base user group 'QA' is logged in, specify QA:GOODPART

To remap for multiple operator groups, separate remap statements by commas.

Example: QA:GOODPART, SETTER:SETUPDONE

param

Sum

Use this field to specify how many messages should be received before the messages is logged.

This is useful when monitoring a machine that generates many messages.

Example: If a machine generates a message every 1.5s and you specify 100 in this field, then the message is only logged every 150s and the MSGTEXT column contains the number of messages summarized in this entry (i.e. 100).

This only works as long as no other messages are received. As soon as a different message is received, this message is logged and the MSGTEXT field contains info about how many message were received.

param

Timeout (s)

Use this field to specify a timeout value when summarizing many messages.

If you have set the machine to summarize of every 100 messages, but no messages has been received within the timeout value, then the current message is logged and the MSGTEXT field contains info about how many message were received.

param

Interval (s)

Use this field to the maximum time between logging a summarized message.

Example if the system receives a message every 1 to 5 seconds, and the summary count is set to 100, then it can take as long as 500 seconds between each message is logged. If you specify 300 in this field, then a message is logged at least every 5 minutes and the MSGTEXT column contains the number of messages summarized in this entry.

This only works as long as no other messages are received. As soon as a different message is received, this message is logged and the MSGTEXT field contains info about how many message were received.