MLxLogEntry

Time of log event.

• It reflects the time at which the process of sending the command data to the robot controller started
• It formats the time as the number of milliseconds since midnight (00:00 hours)

Command identifier.

Robot number (-1=none).

Command specific target number (-1=none).

Assigned buffer entry number.

Number of active buffer entries. This is the same as the commandsInUse output of MLxCommunicationWrite.

It helps to understand what fill levels the command buffer reaches when running your MotoLogix application.

MotoLogix system state. Check the state transitions diagram to learn more about below states.

Command specific data. See MLxLogging for details.

Conversion

Floating point (REAL) values are converted to integer (DINT) with the specified precision. Example of a conversion to .01 unit (resulting in a precision of two decimals):

// conversion of a REAL to a DINT (.01 unit)
// 1234.56789 -> 123457
varDint := REAL_TO_DINT(varReal * 100)

This allows you to store additional information with every log entry. It can be of great value when analyzing log data.

Some examples for user data:

• Index of the sent motion command (PosTable.LoadIndex)
• State machine variable

Example for converting a floating point variable:

// conversion of a REAL using factor 100
// 1234.56789 -> 123457
varDint := REAL_TO_DINT(varReal * 100)