|


Default firmware
features:
-
Supports Modbus/TCP
communication protocol to access I/Os that plug on slots.
-
Supports VxComm technique for
every COM port of controllers.
-
Supports 8K and 87K DI/DO/AI/AO
modules.
Please refer detail list in Modbus
Utility on-line help.
-
Automatically scan I/O modules.
You can plug I/O modules in any slot.
Don't mind the slot order, it's doesn't mater
-
Allowed a maximum of 8 host PCs
access simultaneously.
In fact, it can allow 16 host PCs
access simultaneously.
But for getting better stability, we
recommend you don't use more than 8 host PCs
to access a Modbus/TCP controller.
-
Firmware modifiable
Modbus SDK (
in C language ) :
We provide Modbus SDK to
users. You can use it to integrate several serial devices. Thus
the controller can be a Modbus/TCP slave and Modbus/RTU master.
The Modbus SDK has below features:
 |
-
Supports extra
user-defined command protocol (TCP/P)
-
Register based
programming method (easy to use)
-
Provides
user-defined registers
-
Can link to
Modbus/RTU slave devices
-
Can link to
non-Modbus/RTU serial devices
-
Xserver SDK
compatible
|
Modbus tools:
We provide Modbus tools for
Windows 98/SE/NT/2K/XP, it includes
1. Modbus Utility
-
On-line configuration via
Ethernet
-
On-line help
-
Automatically generate
register mapping tables
-
Configuration export/import
2. MBRTU
Modbus/RTU client (with source
code in VB6) to diagnostic Modbus/RTU slave devices.
3. MBTCP
Modbus/TCP client (with source
code in VB6) to diagnostic Modbus/TCP slave devices.
Typical applications
|
Basic
application 1: Modbus/TCP I/O device
Controller runs default firmware to be a Modbus/TCP slave
device. You just need to run Modbus Utility to configure I/Os
and then set connection between SCADA, HMI software and
Modbus/TCP slave devices.
|
 |
|
Basic
application 2: Modbus/TCP I/O device with VxComm technique
Compare to basic application 1,
you can also link serial devices to COM ports of controllers. To
use this function, you need 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 firmware to add extra functions and
integral serial devices to Modbus/TCP kernel. Thus an I-8000 can
be a powerful controller.
|
 |
|
Advanced
Modbus/TCP controller with VxComm technique
Compare to advanced application 1,
you can link same hardware device. The difference is on
software. If 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-8431/I-8831
Ordering
Information
|
I-8431
-MTCP
|
Modbus/TCP
Embedded Controller with 4 empty slots
|
|
I-8831
-MTCP
|
Modbus/TCP
Embedded Controller with 8 empty slots
|
|
|