GE 8624-FT-IS Intrinsically Safe Field terminal with loop-disconnect

Program development process 

A resource contains several programming units called Program Organization Units (POUs). 

POUs can be programs, functions or function blocks. Programs can be described in any of the five IEC 61131-3 languages plus Flow Chart.

The Build 

To validate the project, the project code must be built. This step is also very useful for syntax checking; 

all detected errors can be easily located with a simple mouse-click. The generated code is fully publicly documented and supported. 

The code generator produces the code for each resource.

GENERAL SPECIFICATIONS

Common mode rejection (using 50/60Hz filter)

• > 120 dB @ 50/60 Hz

Series mode rejection (using 50/60Hz filter)

• > 65 dB @ 50/60 Hz

Maximum input voltage (except current I/P)

• ± 25V

Common mode voltage between channels

• 250 V ac rms

Isolation

• Channel to channel – 250 V ac rms

• Any channel to Railbus – 250 V ac rms

• Any channel to Bussd Field Power – 250 V ac rms

• Railbus to Bussed Field Power – 150 V ac rms

Input filter response

• Time constant 4 ms

Input impedance

• > 1 M ohm

Data Format

• 0 to 65535 corresponds to selected span

RESPONSE TIME

Signal change on any channel to availability

on Railbus

• Dependent on user-selectable filter/sample rates

Note: For those inputs requiring multiple measurements, i.e. resis

tance and RTD, the minimum response time is 55 ms. See also on this

page Tradeoff of Resolution for module throughput.

Open circuit detection

• < 1 sec (with < 0.5μF cable capacitance)

SAFETY

FM non-incendive field wiring parameters

(each channel)

• V

oc

= 20 V; Isc = 75mA; Ca = 0.61μF; La = 11.3mH

POWER SUPPLIES

Railbus (12V) current

• 60 mA (typ.)

• 100 mA (max.)

Bussed Field Power

• @ 24 V dc ± 10%

• All configurations (except 4/20mA with excitation) –

125 mA (max.)

• 4/20mA with excitation – 300 mA (max.)

• Enable / Disable

Linking variables to I/O channels 

Before defining the project code, the I/O is defined in the Workbench in the form of a tag database, 

which identifies the I/O channels and their respective field devices. Once a device is selected, a simple mouse-click 'connects' a variable to a channel.