MergenHub Envest Live demo
Home/Protocols/Fatek FBs
Protocol · Fatek FBs

Fatek FBs — direct access with the native protocol

Connect to Fatek PLCs with the PLC's own addresses, without setting up a Modbus map. X, Y, M, R and D areas become tags directly; consecutive addresses are read in one request.

← All protocols & modules
MergenHub — Fatek FBsConnected
Project
▾Connectivity
▾Fatek
▪Pump_Station2
Pump_Station2 · 192.168.10.40 : 500
DriverFatek FBs
ConnectionEthernet (TCP)
ModelFBs
Station no1
Timeout1000 ms
TagAddressValueQuality
Pump1_RunY01Good
LevelR100412Good
PressureDF104.18Good
Total_FlowDD200184206Good
Fault_BitR120.30Good

The MergenHub interface — a Fatek FBs PLC: output bit, register, 32-bit float and a bit inside a register.

The Fatek protocol

Fatek FBs family PLCs give access to every bit and register area with their own communication protocol, through an Ethernet module or a serial port. MergenHub speaks this protocol directly.

Where is it used?

Common, economical PLCs in pumping stations, irrigation, small treatment plants, machine building and building services. Fatek PLCs in the field are monitored in the same SCADA as other brands.

Driver capabilities

Feature coverage

Fatek FBs / FBe / B1 / HB1 series; Ethernet (TCP / UDP, default port 500) or serial port.

Bits

Bit areas

X, Y, M, S, T, C bits are read; writable areas are written.

Registers

16-bit registers

R, D, F, WX…WC, RT, RC; a bit inside a register (R100.3).

32-bit

Native 32-bit

DR, DD, DF, DWM, DRC; Float / Long from two consecutive registers (low word first).

Efficiency

Block reads

Consecutive addresses in one request (128 bits / 64 registers).

Resilience

Per-block errors

An address the PLC rejects only makes that block Bad; the connection stays up and the other tags keep reading.

Connection

Ethernet or serial

TCP, UDP or serial port; the same driver, the same address syntax.

Address areas
X / YM / ST / CR / DFWX…WCRT / RCDR / DD / DFDWM / DRCR100.3TCP / UDPSerial port