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.
| Tag | Address | Value | Quality |
|---|---|---|---|
| Pump1_Run | Y0 | 1 | |
| Level | R100 | 412 | |
| Pressure | DF10 | 4.18 | |
| Total_Flow | DD200 | 184206 | |
| Fault_Bit | R120.3 | 0 |
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.
Feature coverage
Fatek FBs / FBe / B1 / HB1 series; Ethernet (TCP / UDP, default port 500) or serial port.
Bit areas
X, Y, M, S, T, C bits are read; writable areas are written.
16-bit registers
R, D, F, WX…WC, RT, RC; a bit inside a register (R100.3).
Native 32-bit
DR, DD, DF, DWM, DRC; Float / Long from two consecutive registers (low word first).
Block reads
Consecutive addresses in one request (128 bits / 64 registers).
Per-block errors
An address the PLC rejects only makes that block Bad; the connection stays up and the other tags keep reading.
Ethernet or serial
TCP, UDP or serial port; the same driver, the same address syntax.
MergenHub