GetSpecificDeviceError (FB)ΒΆ
FUNCTION_BLOCK GetSpecificDeviceError EXTENDS CBM.ETrigA
Note
The interpretation of pData is fieldbus dependent and will be specified by the associated fieldbus driver.
Note
This feature may not be supported by all fieldbus drivers.
eError will return ERROR.NOT_SUPPORTED if not supported.
- InOut:
- Scope - Name - Type - Comment - Inherited from - Input - xExecute- BOOLRising edge: Action startsFalling edge: Resets outputsIf a falling edge occurs before the function block has completed its action, the outputs operate in the usual manner and are only reset if either the action is completed or in the event of an error. In this case, the corresponding output values (- xDone,- xError,- iError) are present at the outputs for exactly one cycle.- ETrigA - xAbort- BOOL- TRUE: Action is stopped immediately and all outputs are reset to their initial values.- ETrigA - Output - xDone- BOOL- TRUE: Action successfully completed- ETrigA - xBusy- BOOL- TRUE: Function block active- ETrigA - xError- BOOL- TRUE: Error occurred, function block aborts action- FALSE: No error- ETrigA - xAborted- BOOL- TRUE: Action aborted by user- ETrigA - Input - itfNode- device node - pData- CAA.PVOID- Pointer to memory where specific device error information should be copied to. - Inout - szSize- CAA.SIZE- IN: Size of memory pData points to. Out: Size of data copied to pData - Output - eError- operation error code 
