-
Converters Modbus/TCP to Modbus/RTU
An I-7188E -MTCP is a Modbus/TCP
gateway. It can easily upgrade Modbus/RTU devices to have Ethernet
communication
ability.
-
Supports VxComm technique for
every COM port of controllers
If serial
devices don't support Modbus/RTU, you can still access these devices. But need
to install VxComm driver on host PCs and assign a COM port number to link to
the remote COM port (of I-7188E -MTCP). After that, serial clients can
access these remote serial devices via standard RS-232 functions.
-
Allowed multi-client (or called
master) access simultaneously
Different I-7188E -MTCP controller
supports diffent client numbers connect to. Please refer to our FAQ on web
for more detail.
http://www.icpdas.com/faq/7188e/ech003.htm
-
Firmware modifiable
We provide Modbus
SDK to let users modify Modbus firmware.
-
Supports extra user-defined
command protocol (TCP/IP)
Modbus/TCP protocol supports
2 basic data format (bit and 2-byte integer). It means if clients (or called
masters) don't support Modbus/TCP or you need other format data (for example:
string of floating value), I-7188Es (with default firmware) cannot communicate
with them. Using this feature, you can develop your special command protocol
to transfer any format of data.
-
Register based programming
method (easy to use)
Modbus library supports 4 internal
register tables (iMemory_AI, iMemory_AO, iMemory_DI, iMemory_DO), you can
use these to store specific information. When Modbus/TCP clients request
to I-7188E, Modbus kernel will response information from these 4 tables.
-
Provides user-defined registers
The 4 internal register tables
are all open to users. You need to assign these tables by yourself.
-
Can link to Modbus/RTU slave
devices
By using function ModbusMaster2Slave
(declared in MBTCP_7E.h), Modbus/RTU devices can be easily
integrated to internal registers of I-7188Es. An I-7188E polling every Modbus/RTU
devices and put every necessary information to internal registers. Clients
only ask the I-7188E to get all information of Modbus/RTU devices. That
reduces loading of Clients.
-
Can link to non-Modbus/RTU
serial devices
Some serial devices don't support
Modbus/RTU. We provide functions to let I-7188E -MTCP access serial devices.
You can put information to internal registers of it. Thus, the non-Modbus
serial devices can also support Modbus/TCP.
-
Supports X boards
You can choose one suitable
Xboard to add on an I-7188EX to be on board I/Os.
-
Xserver SDK compatible
Modbus SDK is based on Xserver
SDK. To lear more programming skills, you can refer demos of Xserver.
To get information of demos of Xserver, please refer to CD:_Napdso_7188e_TCP_Xserver_Xserver.htm
|
►Basic application
1: protocol converter
An I-7188E -MTCP runs default firmware
to be a Modbus/TCP to Modbus/RTU converter. You just need to run Modbus Utility
to configure it and then set connection between SCADA, HMI software and the
I-7188E.
|
 |
|
►Basic
application 2: protocol converter with VxComm technique
Compare to basic application 1,
an I-7188E -MTCP can also link to serial devices that don't support Modbus/RTU.
To use this function, you need to install VxComm driver on host PCs. After
installing it, you can access these remote COM ports by using standard serial
driver.
|
 |
|
►Advanced
application 1: Modbus/TCP
controller
Using Modbus SDK, users can develop
their special Modbus firmware to add extra functions and integrate serial
devices and a Xboard to Modbus/TCP kernel. Thus an I-7188E can be a powerful
controller.
|
 |
|
►Advanced
application 2: Modbus/TCP
controller with VxComm technique
Compare to advanced application
1, I-7188E -MTCP can link same hardware devices. The difference is on software.
If some devices connectd to some COM ports are not integrated into your special
firmware, you can still access these COM ports via standard serial driver,
but you must install VxComm driver on host PC.
►Software
and Documents:
ftp://ftp.icpdas.com/pub/cd/8000cd/napdos/modbus
►Hardware:
Same as I-7188E series embedded
controllers
|
