FC_CanContinueWriting

FC_CanContinueWriting - General Information

Overview

Type:	Function
Available as of:	1.1.2.0
Inherits from:	-
Implemented:	-
Access restriction:	PUBLIC

Task

The approval to process is queried in the routines using FC_CanContinueWriting to ensure that Diagnostic does nor require system resources in critical routines.

Description

Processing blockage of FC_CanContinueWriting is kept until FB_DiagnosticsManager resets the state (to the next cycle start).

The method checks the system state for cycle timeouts and overfilled ramdisk. Further configuration details are described in the ST_CanContinueWriting structure.

Interface

Output	Data type	Description
q_etDiag	GD.ET_Diag	General, library-independent statement on the diagnostic. A value unequal to GD.ET_Diag.Ok corresponds to an error 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 -> error message
q_sMsg	STRING(80)	Event-triggered message which gives more detailed information on the diagnostic state.

Output

Data type

Description

q_etDiag

GD.ET_Diag

General, library-independent statement on the diagnostic.

A value unequal to GD.ET_Diag.Ok corresponds to an error 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 -> error message

q_sMsg

STRING(80)

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

Input/Output	Data type	Description
iq_stCanContinueWriting	ST_CanContinueWriting	Communication structure that contains all data for FC_CanContinueWriting and return values

Return Value

Data type	Description
BOOL	Returns TRUE if successful, FALSE in the case of errors