FB_CrankModuleDiagSource

 

FB_CrankModuleDiagSource - General Information

Overview

Type:

Function block

Available as of:

V1.0.2.0

Inherits from:

Implements:

Task

Output of the additional interface of the FB_CrankModule in a diagnostics prompt.

Description

To diagnose the template project with PacDrive Diagnostics, this POU provides the variables in the ST_ModuleInterface of a crank module as a diagnostic source. It lists modules, starting with the MainMachine. For each CrankModule the entire additional interface is output.

Interface

Input

Data type

Description

i_xEnable

BOOL

A rising edge (FALSE -> TRUE) activates the POU, a falling edge (TRUE -> FALSE) deactivates the POU.

A deactivated POU does not execute any actions.

i_xDiagQuit

BOOL

Acknowledging a pending diagnostic message.

i_xPrintCamData

BOOL

By this input, you can help prevent the detailed output of the CAM tables. For a diagnostic as good as possible, it is recommended to set the input to TRUE.

Output

Data type

Description

q_xActive

BOOL

TRUE: The POU is active and has to be executed further.

FALSE: The POU is inactive.

q_xReady

BOOL

TRUE: The POU is ready to operate and can accept user commands.

FALSE: The function block is not ready to accept user commands.

q_etDiag

GD.ET_Diag

General, library-independent statement on the diagnostic.

A value unequal to GD.ET_Diag.Ok corresponds to a diagnostic message.

q_etDiagExt

ET_DiagExt

POU-specific output on the diagnostic.

q_etDiag = GD.ET_Diag.Ok -> status message

q_etDiag <> GD.ET_Diag.Ok -> diagnostic message

q_sMsg

STRING[80]

Event-triggered message which gives more detailed information on the diagnostic state.

Input/Output

Data type

Description

iq_stComStructure

TPL.ST_DiagnosticsManagerToDiagSource

Communication with the DiagManager. This input must always be connected to "stComStructure".

iq_stMachineItf

TPL.ST_StandardModuleInterface

The interface of the MainMachine. By using this input the diagnostic source can search for all existing modules, utilizing the module tree. This input must always be connected to "SR_MainMachine.stMachineInterface".