MITSUBISHI MELSEC Performance
MELSEC-Q seiries Ethernet communication
Add array OPCItems as Advise from a OPC Client.
It is measured reading time from added OPCItems. Communication performance is defined as average time of ten times measurement.
This time means to read the value of a continuous area of the device.
PC specification
OS:
    Windows 7 Professional  32bit OS
CPU:
    Intel(R) Core(TM) i7 CPU 860 @2.80GHz
Memory:3.00GB
OPC Server:
    DeviceXPlorer OPC Server Ver4.2.0.2
OPC Client:
    OPCClient sample VcSampleOpc(C++)
Cable:
    100BASE-TX cross cable connecting directly
OPC Server setting
Protocol Timer Tick:10msec
Timer Tick for Async Update Mode:10msec
Multi Access Mode:Enable
Multi Access for Snyc Asnyc:Disabled
Async Update Mode:Disabled
PLC setting
CPU:Q06UDEHCPU
Register:D0-D8191
Max scan time:0.06msec
Communication Performance
≪Built-in Ethernet port≫
(sec)
|
| 1024
| 2048
| 4096
| 8192
| 16K
| 32K
| 64K
| 128K
|
| Average
| 0.031 |
0.047 |
0.078 |
0.141 |
0.307 |
0.611 |
1.235 |
2.487 |
| Max
| 0.031 |
0.047 |
0.078 |
0.141 |
0.312 |
0.624 |
1.248 |
2.496 |
| Min
| 0.031 |
0.047 |
0.078 |
0.140 |
0.296 |
0.608 |
1.232 |
2.480 |
≪QJ71E71-100≫
(sec)
|
| 1024
| 2048
| 4096
| 8192
| 16K
| 32K
| 64K
| 128K
|
| Average
| 0.031 |
0.047 |
0.078 |
0.141 |
0.304 |
0.624 |
1.262 |
2.481 |
| Max
| 0.031 |
0.047 |
0.078 |
0.141 |
0.312 |
0.624 |
1.388 |
2.481 |
| Min
| 0.031 |
0.047 |
0.078 |
0.141 |
0.296 |
0.624 |
1.248 |
2.480 |
Results
There is little change between Ethenet unit and Built-in Ethernet port, it is possible to get max 48,000 points per sec.
Comment
*Graph displays average time of ten times measurement.(1point = 1word)
*In case of 32K points access , Read 32K points by using 2 devices.( 16K point per 1 device).
*The result only means our examination, it doesn't guarantee performance.
[Jun 2010]
MELSEC-FX seiries Ethernet communication
Add array OPCItems as Advise from a OPC Client.
It is measured reading time from added OPCItems. Communication performance is defined as average time of ten times measurement.
This time means to read the value of a continuous area of the device.
PC specification
OS:
    Windows 7 Professional  32bit OS
CPU:
    Intel(R) Core(TM) i7 CPU 860 @2.80GHz
Memory:3.00GB
OPC Server:
    DeviceXPlorer OPC Server Ver4.2.0.2
OPC Client:
    OPCClient sample VcSampleOpc(C++)
Cable:
    100BASE-TX cross cable connecting directly
OPC Server setting
Protocol Timer Tick:10msec
Timer Tick for Async Update Mode:10msec
Multi Access Mode:Enable
Multi Access for Snyc Asnyc:Disabled
Async Update Mode:Disabled
PLC setting
CPU:FX3U-16M
Communication unit:FX3U-ENET-L
Register:D0-D8191
Max scan time:42msec
Communication Performance
(sec)
|
| 1024
| 2048
| 4096
| 8192
| 16K
| 32K
| 64K
| 128K
|
| Average
| 0.612 |
1.204 |
2.398 |
4.925 |
9.420 |
18.536 |
38.027 |
74.852 |
| Max
| 0.690 |
1.361 |
2.731 |
5.381 |
10.381 |
19.415 |
39.121 |
76.929 |
| Min
| 0.510 |
0.990 |
2.000 |
4.112 |
8.092 |
17.891 |
35.950 |
72.239 |
Results
In case of continuous data memory(D), it is possible to get max 1,500 points per sec.
Comment
*Graph displays average time of ten times measurement.(1point = 1word)
*In case of 32K points access , Read 32K points by using 2 devices.( 16K point per 1 device).
*The result only means our examination, it doesn't guarantee performance.
[Jun 2010]
Interface performance
Results of measurement of each interface(eg.sync /async /datachange event etc).
(detail)