SET 89299, Technical Description

Page: 34 / 38

34 of 38 www.smart-e-tech.com
cRIO LVDT 9312 Module
Technical Description
Issue 05 24/05/2022
5.3 LVDT9312 D
RIVER
E
RROR
C
ODES
Error
Code
[U8]
Error Type
Error
Detection
Description
0 No Error none If no error has appeared during communication with the LVDT9312
module, the received telegram has error code „0“.
1 Unknown
Command
LVDT
Module
This error occurs when the LVDT Module receives an unknown
instruction code.
2 Communication
Error
LVDT
Module
This error occurs when the FPGA aborts a telegram transmission to
the LVDT Module or when an internal communication error of the
module occured
3 Invalid
Parameter
LVDT
Module
This error occurs when the parameter “Data” is out of range.
8 Excitation
ShortCircuit
LVDT
Module
This error occurs if the Excitation is in Short Circuit and deactivated
due to thermal limits. The Excitation will be disabled for 5 seconds and
the Error will remain 10 more seconds. Regularly driving the Excitation
in its thermal limit will degrade performance!
100 No Module FPGA
Driver-VI
This error occurs when no LVDT Module is connected to the applicable
slot.
101 Module Busy Functions-
VI
The busy signal to the FPGA indicates module readiness. When a time
consuming instruction is processed by the module, the busy signal
becomes valid for a certain amount of time. However, if a new
instruction is sent to the module while the module still processes a
previous instruction (and therefore the busy line still is active), the
FPGA driver waits for the busy line to return to the ready state. The
maximum idle time for the FPGA driver is a default value and can be
increased from the user. When the specified timeout is exceeded, the
error “Module Busy” is generated by the functions -VI.
103 Transmit
Incomplete
FPGA
Driver-VI
This error occurs when the LVDT Module aborts telegrams or exceeds
the driver timing constraints.
104 Wrong Driver
Answer
Functions-
VI
This error occurs when the replied telegram does not match with the
instruction telegram.
Note: This error may occur subsequently to a module power interrupt
while the application is still running. However, this is only a singular
error.
105 FIFO Timeout Functions-
VI
This error occurs if a FIFO fault takes place during data transfer from
the functions-VI to the applicable driver-VI.
Note: To reset this error scenario, both communication FIFOs
(SlotN_CommandIN und SlotNCommandOUT) of the applicable
mo
dule must be cleared with the „Clear“ instruction
106 Power Error Functions
VI
This Error occurs if the external Supply of the Module is not in it’s
limits.
107 Loose of
Tracking LVDT
Module
This error occurs if both signals (Ua/Ub) are below 350mVrms.
- In 4 Wire mode this error occurs only if Excitation and Ua are
below 350mVRms.
5.4 M
ODULE
I
DENTIFICATION
U
NDER
L
AB
VIEW
LabVIEW automatically detects the cRIO module type (Discover C-Series Modules),