Monitoring the Safety Application in Logic Builder

Online Object Editors

You can use the object editors of the devices involved to display online values of device objects while Logic Builder is connected to the running Logic/Motion Controller.

Displaying the Object Status in Logic Builder:

Step	Action
1	Select Online > Login or click the Login command on the main toolbar or press Alt + F8.
2	If the application is not running, start the application execution by selecting the Debug > Start command or pressing F5.
3	Double-click the Safety_PLC node in the Devices tree.
4	Click the Schneider Electric Sercos III parameters tab to display the online values of the SLC objects in the Current Value column.
5	Expand the desired parameter group in the grid, for example, SlcProjectInformation or SlcProjectStatus, and so on.
6	Perform the steps 1 to 4 appropriately for the safety-related and standard TM5/TM7 I/O modules to display their object values.

SLC-related information can also be displayed in the SafePLC Info dialog. You can open this dialog from the SafePLC control dialog in Machine Expert - Safety.

NOTE: The ProjectTime displayed in Logic Builder may differ from the time shown in the SafePLC Info dialog in Machine Expert - Safety. Refer to section System-specific Notes for details.

Online Mapping Editors Display Variable Values

You can use the mapping editors of the SLC and the I/O modules involved to display online values of variables and signals while Logic Builder is connected to the running Logic/Motion Controller.

Displaying the Variable/Signal Status in Logic Builder:

Step	Action
1	Select Online > Login or click the Login command on the main toolbar or press Alt + F8.
2	If the application is not running, start the application execution by selecting the Debug > Start command or pressing F5.
3	Double-click the Safety_PLC node in the Devices tree.
4	Click the Schneider Electric Sercos III I/O Mapping tab to display the online values of signals in the Current Values column.
5	Expand the desired parameter group in the grid, for example, SLC2LMC_BOOL.
6	Perform the steps 1 to 4 appropriately for the safety-related and standard TM5/TM7 I/O modules to display their variable/signal values.

SafeLogger

The SafeLogger in EcoStruxure Machine Expert collects messages which are generated by the safety-related system objects (openSafety messages) and transfers them over the Sercos bus. These messages provide diagnostic information which can be used for troubleshooting purposes. In the SafeLogger, the messages are shown with a time stamp. Corresponding managing functions for handling the messages are provided.

Refer to the section System-specific Notes for details regarding the SafeLogger entries.

The messages are classified according to three message types:

Information messages, for example, status information
Alert messages (yellow)
Error messages (red)

For detailed information on the SafeLogger, its configuration and the handling of messages, refer to the SafeLogger User Guide.

Opening the SafeLogger in EcoStruxure Machine Expert:

Step	Action
1	Double-click the Logic/Motion Controller in the Devices tree.
2	Click the SafeLogger tab in the editor area.

SafeLogger Entries Merged to GlobalLogger

Entries shown in the SafeLogger can be merged into the GlobalLogger. If no GlobalLogger is available, proceed as follows:

Procedure in EcoStruxure Machine Expert while logged off from the Logic/Motion Controller:

Step	Action
1	In the Devices tree, right-click the MyController node and select Add Object > GlobalLogger from the context menu.
2	Enter a name for the new GlobalLogger and click Add. Result: The new logger is inserted under the MyController node and opened in the editor area.
3	In the GlobalLogger window, click the Get messages from Logger command and select the Safe Logger check box to include its entries into the GlobalLogger.

Step

Action

In the Devices tree, right-click the MyController node and select Add Object > GlobalLogger from the context menu.

Enter a name for the new GlobalLogger and click Add.

Result: The new logger is inserted under the MyController node and opened in the editor area.

In the GlobalLogger window, click the Get messages from Logger command and select the Safe Logger check box to include its entries into the GlobalLogger.

System-specific Notes

Observe the following notes regarding the entries in the SafeLogger when used in the specific architecture of a Logic/Motion Controller with Embedded Safety:

Differring time stamps: The time stamps displayed in Logic Builder (for example, in the SafeLogger or for the ProjectTime parameter in the SLC Schneider Electric Sercos III Parameters) may differ from the time stamps shown in Machine Expert - Safety (for example, in the SafePLC Info or Project Info dialog).

The reason is that the tools may use different time bases. Machine Expert - Safety always converts time stamps to local time while the SafeLogger uses the setting in the Services editor for the Logic/Motion Controller. (The time setting is written to the slaves during Sercos phase-up.) Refer to the chapter Services (M262 Logic/Motion Controller Programming Guide) for details. In the object editors, always UTC-based time stamps are shown.
Differing project CRC: The ProjectCRC parameter is shown as decimal value in the object editor of the SLC (Logic Builder) and possibly as hexadecimal value in Machine Expert - Safety. The format used in Logic Builder can be set via the Display Mode context menu of the VIS_SlcRemotController visualization page (while in online mode).
Topological Station ID: In SafeLogger, the station ID is displayed as topological path. TopoAdr: 1 identifies the first slave node under the Sercos Master. The node itself, for example, the SLC or a bus coupler, has StructureInstance: 0. TM5/TM7 I/O modules under the bus coupler follow with a StructureInstance > 0.