// Categories
Communication I/O Control
Remote I/O controllers that act as a Modbus RTU or LS ELECTRIC Cnet slave over RS-485, RS-232 or UART.
4 controllers
MNET-8A8T
MNET-8A8T Communication I/O Controller
MNET-16A16R
MNET-16A16R Communication I/O Controller
MNET-32A32R
MNET-32A32R Communication I/O Controller
Communication I/O Control
When field devices must be driven straight from a PC, SCADA system, HMI or PLC, ILOGICS communication I/O controllers give you remote I/O with RS-232, RS-485 and TTL UART terminals plus I²C. They run no user program: each unit operates as a Modbus RTU slave or an LS ELECTRIC Cnet slave, and the protocol is chosen at order time. Baud rate and slave address are set with dip switches, and the master reads and writes the isolated digital inputs and relay outputs at fixed register addresses. DIN-rail 35 mm mountable, with analog input, PT100 temperature, analog output and pulse output available as expansion-module options.
Frequently asked questions
Do I write a program for an MNET controller?▾
No. MNET runs no user program and there is no firmware to write. It is controlled entirely over the bus: a master you already own — a PC application, an HMI or a PLC — reads and writes its I/O points directly. There is no development toolchain to install and no sketch to upload.
Which protocol does an MNET controller speak?▾
One of two, chosen when you order: Modbus RTU slave or LS ELECTRIC Cnet slave. A unit is built for one protocol — the two do not ship together on the same board — and it is always the slave, never the master. The serial link is RS-232, RS-485 or UART depending on the model.
When should I choose MPINO or MPAINO instead?▾
Choose MNET when the logic already lives in a master and you only need isolated I/O on the far end of a serial link. Choose an industrial Arduino (MPINO / MPAINO) when the board itself has to run the logic — interlocks that must hold with the network down, timing that cannot wait for a poll, or any behaviour you want to write yourself.