|
|
|
|
| |
|
| |
|
| |
| |
 |
| Model:I-8831-MTCP |
|
|
I-8431-MTCP/I-8831-MTCP
I-8431-80-MTCP/
I-8831-80-MTCP
Modbus/TCP Embedded Controller(Ethernet
enables Modbus commands to run over TCP/IP)
|
|
|
|
 |
|
|
| |
| Introduction |
I-800E-MTCP are Modbus/TCP I/O units with Modbus communication protocol. They support most of 8K and 87K series I/O modules, such as DI, DO, DIO, AI, AO, etc.. Most SCADA software support Modbus communication protocol, thus users can easily and quickly integrate remote I/Os to the SCADA software as data acquisition and monitor to apply to environment monitoring, power management, factory automation, etc. |
|
| |
| Default
firmware features: |
| |
| Supports Modbus/RTU to Modbus/TCP converter. |
I-8000E -MTCP's COM Port can be setted as gateway mode, and connect to Modbus/RTU device. Host PC can link
the Modbus/RTU device by Modbus/TCP protocol with enthernet. |
| |
| Supports VxComm technique for every COM port of controllers.
|
When the serial device does not support Ethernet, user still can use virtual COM Port to access the device by
Ethernet . Just set I-8000E -MTCP's COM Port as VxComm mode, and install VxComm driver on PC, then mapping
a virtual COM Port to I-8000E -MTCP's COM Port. After all, user's program can communicate with serial COM Port of
remote device by standard RS-232 process. |
| |
| Supports 8K and 87K DI/DO/AI/AO modules. |
| Refer to Modbus Utility on line help |
| |
| Automatically scan I/O modules and range I/O registers address to continuous. |
You can plug I/O modules in any slot. The Modbus firmware can automatically scan all slots and range I/Os to
registers in continuous.You can use Modbus Utility to see the I/O address mapping. |
| |
| Support power on value and safe value for analog/digital output module |
| Refer to Modbus Utility on line help |
| |
| Allowed several host PCs( client ) access simultaneously. |
It depends on how many serial ports on the 7188E/8000E and how many serial ports of 7188E/8000E that each PC
connected on it. See FAQ for detail, http://www.icpdas.com/faq/7188e/hardware/003.htm |
| |
| Firmware modifiable |
| We provide the Modbus SDK allowing users to develop their custom Modbus firmware. |
|
|
| |
|
|
|
|
|
| |
back |
|
| |
| 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) |
Modbus/TCP support 2 basic data format (bit and 2-byte integer). If the client did not spport Modbus protocol or if
the client use other format of data(such like character, float...), user still can define his own particular protocol for
any format of data. |
| |
| Register based programming method (easy to use) |
Modbus function supports 4 register able (iMemory_AI, iMemory_AO, iMemory_DI, iMemory_DO)，you can use
them to save user defind data(such like expanded I/O data). When Modbus/TCP client query I-8000E -MTCP main
control unit, Modbus main function will return the data of the 4 register table to client. |
| |
| Provides
user-defined registers |
I/O on slot will use the register at begining of these 4 register table. Each register table has most 300 register
memories for I/O on slot. User can define other registers that not used. |
| |
| Communicate with Modbus/RTU device |
By using ModbusMaster2Slave function (define in MBTCP_8E.h), Modbus/RTU device can be integrated to I-8000E
-MTCP register easily. I-8000E -MTCP requires the Modbus/RTU device I/O data，put then into its registers. The
hoat PC can get all I/O data by reading the registers of I-8000E -MTCP. |
| |
| Communicate with other device |
For serial device which did not support Modbus/RTU protocol, we defined functions to link them and put the I/O
data to registers. User can modify the device to support Modbus/TCP. |
| |
| Firmware programmable |
Modbus firmware is based on Xserver SDK. For fireware development, refer Xserver demo. Download Xserver
demo on CD:\Napdso\8000\843x883x\TCP\Xserver\Xserver.htm |
|
|
| |
|
|
|
|
|
| |
back |
|
| |
| Modbus
Utility: |
|
|
| The Modbus Utility package is for Windows 98/SE/2K/XP. It includes |
| |
|
| Modbus Utility on line setting |
| 1. On-line configuration via Ethernet |
| 2. TO memorize the I/O setting in EEPROM |
| 3. Automatically generate register mapping tables |
| 4. Configuration export/import |
| 5. COM Port setting(Modbus/RTU gateway, VxComm, UpLink, Programming, Debug) |
| 6. Show I/O value by 3 modes(Value, Dec, Hex) |
| 7. Analog output, digital output control |
| 8. Plot trend line |
| 9. I/O value datalog (.txt file) |
| 10.Power on value, safe value, WDT setting |
|
|
| |
| MBRTU |
| Modbus/RTU client (with source code in VB6) to diagnostic Modbus/RTU slave devices. |
| |
| MBTCP |
| Modbus/TCP client (with source code in VB6) to diagnostic Modbus/TCP slave devices. |
|
|
| |
|
|
|
|
|
| |
back |
|
| |
Typical applications |
|
| |
| Basic application 1: Modbus/TCP I/O device |
An I-8000E -MTCP runs a default firmware to be a Modbus/TCP slave I/O device. You can simply use the Modbus Utility to configure the device and then set connection between SCADA, HMI software and the I-8000E -MTCP. |
|
|
|
| |
| Basic application 2: Modbus/RTU to Modbus/TCP converter |
After setting COM Port as gateway mode by Modbus Utility, User can link Modbus/RTU device by Modbus/TCP protocol with linking I-8000-MTCP. Thus user can configure SCADA or HMI to upgrade Modbus/RTU device to Modbus/TCP device. |
|
|
|
| |
Basic application 3: Modbus/TCP I/O device with VxComm technique |
|
| An I-8000E -MTCP is also be able to link serial devices that connect to COM ports of the I-8000E -MTCP. To use this function, you will need to install VxComm driver on host PCs. After installation, you will be able to access the remote COM ports via the standard serial driver. |
| |
|
|
| |
| Advanced application 1: User define Modbus/TCP controller |
Using the Modbus SDK, users can develop their own custom firmware, allowing extra functions, integration serial devices to Modbus/TCP kernel. Thus an I-8000 can be a powerful controller. |
|
|
|
| |
| Advanced application 2: Modbus/TCP controller with VxComm technique |
When an I-8000E -MTCP links same hardware devices as Advanced application 1 link to, if any devices connected to certain COM ports are not integrated into your custom firmware, you are still able to access the COM ports via standard serial driver. In order to do this, you must install VxComm driver on host PCs |
|
|
| |
|
|
|
|
|
| |
back |
|
| |
|
|
| |
|
|
|
|
|
| |
back |
|
| |
|
|
| |
| CPU
module |
| CPU |
80188 or compatible (8-bit and 40MHz) / I-8431-MTCP/I-8831-MTCP
80186 or compatible (16-bit and 80MHz) / I-8431-80-MTCP/I-8831-80-MTCP |
| SRAM |
512KBytes |
| Flash |
512KBytes |
| EEPROM |
2KBytes |
| NVRAM |
31Bytes |
| RTC (real time clock) |
Yes |
| Hardware Serial Number |
Yes |
| Built-in Watchdog Timer |
Yes |
|
COM
0 |
Internal
communication with the 87K modules |
| COM 1 |
RS-232 (to
update firmware) |
COM
2 |
- |
COM
3 |
RS-232/RS-485 |
| COM 4 |
RS-232 |
| Ethernet Port |
10BaseT
NE2000 compatible |
| 5 - Digit LED Display |
Yes |
| 3 - Programmable LED Indicators |
Yes |
| 4 - Push Buttons |
Yes |
| I/O
expansion slots |
| 8431-MTCP |
4
Slots |
| 8831-MTCP |
8
Slots |
| 8431-80-MTCP |
4
Slots |
| 8831-80-MTCP |
8
Slots |
| Dimensions |
| 8431-MTCP/8431-80-MTCP |
230
x 110 x 75.5 mm |
| 8831-MTCP/8831-80-MTCP |
354
x 110 x 75.5 mm |
| Operating
Environment |
| Operating Temperature |
-25°C
to +75°C |
| Storage Temperature |
-30°C
to +85°C |
| Humidity |
5
~ 95%,non-condensing |
| Power |
| Protection |
Power reverse
polarity protection |
| 3KV power isolation |
Yes |
| Power requirement |
10 ~ 30
V/DC |
| Power supply |
20W |
| Power consumption |
I-8431-MTCP
: 3.9 W |
| I-8831-MTCP
: 5.1 w |
|
|
| |
|
|
|
|
|
| |
back |
|
| |
|
|
| |
| I-8431-MTCP |
Modbus/TCP Embedded Controller with 4 empty
slots |
| I-8831-MTCP |
Modbus/TCP Embedded Controller with 8 empty slots |
| I-8430-MTCP |
Modbus/TCP
Embedded Controller with 4 empty slots |
| I-8830-MTCP |
Modbus/TCP
Embedded Controller with 8 empty slots |
| I-8431-80-MTCP |
I-8431-MTCP (80M CPU) |
| I-8831-80-MTCP |
I-8831-MTCP (80M CPU) |
Note:To use the Modbus SDK to develop custom firmware, the controller must be equipped with 512K SRAM (I-8431-MTCP, I-8834-MTCP) . |
|
|
|
|
| |
back |
|
| |
|
|
| |
| KA-52F |
AC100~250V input, DC 24V/1A output, flat
type power supply |
| DIN-KA52F |
KA-52F
with DIN-Rail mount |
| DP-665 |
AC
85 ~ 270 V input, DC 24V/1.7A and 5V/0.5A output power supply |
| DP-660 |
24V/1.7A
5V/0.5A Power Supply |
| DP-1200 |
24V/5A
Power Supply |
|
|
| |
|
|
