Command logging

From version V3.4.19: The Planar mover can log all incoming commands.

Starting with version V3.4.60: The Planar track, Planar group, and Planar environment can all log incoming commands.

All commands generate a log line with the "Info" priority level. If the commands contain many options, these are displayed in a second log line with the "Verbose" priority level. If the priority level set for the Planar mover (or another Planar object) is, for example, “Warning” (the default value), then no command information is written to the output.

The specific second part of the first protocol line (after timestamp, object name, etc.) is structured as follows: first comes the command name (this is identical to the name of the corresponding method in the PLC that sends the command). This is followed by a colon. The command parameters or options are then listed (separated by commas). Each command parameter is specified with its name and value. The name corresponds to the name of the parameter in the method of the command in the PLC. The protocol line is terminated by a dot.

Example:

…: MoveOnTrack: targetTrack ? (0x00000000), targetPosition 100.000, limitVADJ (100.0, 200.0, 200.0, 1000.0)

The optional second log line begins with "Options:" if it lists all elements of the last option parameter of the method in full. Here too, all elements are separated by commas. This is the case for the "MoveOnTrack" command, for example. Otherwise, the list of method parameters (or option elements) is continued in this line (e.g. "GearInPosOnTrack" command).

Example:

…: Options: gap 200.000, direction NonModulo, turns 0, modTol 0.000, dynMode None, gapMode Standard1D.

The "constraint" parameter for motion commands, which specifies the dynamic limits for the movement, is currently not logged or only logged to a limited extent (for "OnTrack" commands).

If a command is rejected immediately, this is logged.

Example:
…: Command rejected (error ID: 0x98118151).

Starting with version V4.0.6: For all commands that are rejected immediately, an (additional) log entry with the severity level “Warning” is generated, specifying the exact reason for the rejection.

The specific second part of this log line (following the timestamp, object name, etc.) is structured as follows: It begins with “Rejected command”. This is followed by a colon. The specific reason for the rejection will then be provided.

Example:

…: Rejected command: The mover's state is Disabled instead of Enabled.

In this case, a motion command was rejected because the mover is not turned on.

For all commands that are rejected due to potential collisions, the severity level is set to “Verbose” instead of “Warning,” since these rejections often occur during normal operation.