Machine FG_02

FG_02 in TwinCAT

This page is generated from the machine handoff and the TwinCAT solution. Published from _docs/context/fg-02.md — edit it there, not here. Changes made in the wiki are overwritten on the next sync.

The control side only. What FG_02 is - its scene hierarchy, its devices and everything a human authored about it - is in the main repo: FG_02.

Twin PLC path	MAIN.FG_02
Control PLC path	MAIN.Machine.FG_02
Module	FG_02 EXTENDS FB_PackML_BaseModule
Served by	Index02 (FG_Transport)
Devices	1
Behaviour	fg-02-behaviour.md

Components

Symbol	Device type	Twin FB	Control PLC path	I/O	Linked
P_Camera	DataReader	FB_Camera	MAIN.Machine.FG_02.P_Camera	2	2

The twin path is not the control path. Only the control PLC path works in an HMI binding or a TcLinkTo pragma, and the twin's spelling fails silently in both.

SIM_1

POU	TwinCAT_1/PLC/SIM_1/FG_02/FG_02.TcPOU
In .plcproj	yes
Mapping targets	GVL_EtherCAT_1_SIM
Mapping lines	8

Only the Mapping action is ours. The {region generated code} block belongs to OC Assistant and is overwritten on the next twin regeneration.

PLC_1

POU	TwinCAT_1/PLC/PLC_1/Modules/12 FG_02/FG_02.TcPOU
In .plcproj	yes
PackML states	Execute, Aborting, Clearing, Stopping, Resetting
Fault codes	1, 2, 3
HMI struct	ST_HMI_FG_02

Fault codes are read from _FaultCode := in the ST. What each one means is behaviour and lives in the reference page named in the header.

Mapping

Process image member	Dir	Terminal	Via
P_Camera.InputData	IN	FG_02_EL1859_1 channel 8	Mapping_PLC.xml
P_Camera.OutputData	OUT	FG_02_EL1859_1 channel 16	Mapping_PLC.xml

2 members, 2 linked, 0 unlinked. A declared but unlinked signal compiles and is silently dead - see plc-io.md for the channel map and plc-io-exceptions.md for the ones that are unlinked on purpose.