|
DeviceXPlorer 2007 is middleware that communicates with control devices and measuring instruments and then passes product information to each application. OPC interface enables exchanging data with each application. We used to develop each OPC Server for each PLCs. But from this version, you can access domestic 10 main PLCs such as Mitsubishi MELSEC, OMRON SYSMAC by only single product. We met customer's demand that occurred in various PLCs intermingle and multivender-ization is evolved. In addition, DeviceXPlorer 2007 has been enhanced with various functions substantially such as "RAS Function" that diagnoses connection number of OPC Client and status of accessing tag and, "Watch Function" that watches tag value.
|
| Feature of DeviceXPlorer OPC Server |
| |
Multi PLC connection |
When there were some kinds of PLC, it used to require using each kinds of OPC Server. DeviceXPlorer 2007 integrated all existing products and can communicate with multiple PLCs. OPC client only access single name space and then it can access all PLCs.
|
| |
Add support models |
DeviceXPlorer 2007 can communicate with Fuji Electric MICREX-SX series, SHARP SATELLITE JW series and KEYENCE KV series those last OPC Server couldn't communicate with. We are going to increase the lineup.
|
| |
Support MELSEC-QnU and TOYOPUC-PC10 |
DeviceXPlorer 2007 supports Mitsubishi MELSEC-QnU series and JTEKT TOYOPUC-PC10 series. We are going to keep up news models.
|
| |
Support Wonderware SuiteLink/DDE |
DeviceXPlorer 2007 supports SuiteLink/DDE. This makes it possible to access from InTouch directly. Throughput increases because this does not go through FSGateway.
|
| |
Support Windows Vista |
DeviceXPlorer 2007 supports UAC (User Account Control), which makes it possible to work DeviceXPlorer 2007 with restricted user without promoting to Administrator privileges.
|
| |
Improve the operability with the latest GUI style |
Dockingpane of Visual Studio.NET style allows you to operate application in free style. And auto hide function is provided in each window. It make it possible to use application work space to the full.
|
| |
Various RAS Functions |
By the OPC Access Log function, it becomes easy to debug the OPC client development because it can dump the call situation in the OPC interface.
Moreover, by the Communication Log function, because the message to send and receive the PLC can be dumped, the sending and receiving packet can be optimized, and the trouble of the communication error occurrence be analyzed.
And the output message is listed in real time, and it is also possible to preserve the message in the file automatically.
The communication status with PLC and the value and quality information of the tag can be monitored from the screen. And it is possible to monitor connecting client information, OPC group information (the number of Active tags, Deactive tag and Error tags and update interval) and accessing tag information by client diagnosis function. So, this makes it easier to trace the source of trouble such as type mistake of tag name and error PLC.
|
| |
Watch Function |
Tags made by separate devices can be registered and monitored freely. And tags can be registered easily by drag and drop operation from tag view.
|
| |
System Tag |
You can change update interval and can monitor the status of total number of accessing tags and status of communication load. And also you can acquire or change system time and timing clock from outside application easily.
|
| |
Tag generator |
Tag generator can create tags that have specific form in batch. The number of created tags and numbering way of tag name and PLC device can be specified freely. So even if tag form is complex, it is easy to make them in batch.
|
|
OPCDA3.0 |
Our OPC Server corresponds to latest specification OPCDA3.0 of opening to the public in 2003. Therefore, even if latest SCADA etc. are used, it operates without the trouble.
And even if the client is developed with VC, and so on, the function added with OPCDA3.0, like the MaxAge function and the KeepAlive function, can be used full. (The sample program is attached to the product.)
|
|
.NET Framework |
OPC Server works as COM object. so when accessing from .NET environment, you should convert between COM and .NET. The OPC Foundation supply .NET Wapper called RCW and we supply the sample code of Visual Basic.NET using RCW.
Moreover, latest version V2.02 of the OPC automation trumpet also does the bundle. Therefore, the source code of past VB6.0 can be recycled without correcting it greatly, and it is possible to develop at ease even in the NET environment.
|
|
OPC Compliance Test |
Our OPC Server is confirmed to connect with all OPC client products by the OPC Interoperability Workshop, and it is published on the site of OPC-J.
http://www.opcjapan.org/iw/index.asp
In addition, it is confirmed to fill the specification by the OPC Compliance Test, and it is published on the site of OPC Foundation.
http://www.opcfoundation.org/Products/
|
|
Redundant Communication |
When the trouble occurs in the communication route, it switches immediately to the other communication route.
The duplex system can be constructed with two Ethernet segments, and automatically switching from Ethernet to MELSECNET becomes possible.
It is possible to use it at ease even with the system for which tedium is necessary.
|
|
Simulation Mode |
The simulation facilit to which the client development is advanced is installed in the situation without the PLC. Therefore, the client system can be debugged even at time for the trouble after an initial stage and the system are delivered of not becoming complete PLC.
The value returned to the client can set random and the increment etc. of each tag.
|
|
Shared Memory |
The tag in the OPC Server can be used as a shared memory by applying the simulation mode. Virtual tag is generated in the OPC Server to share the value between two or more VB client and SCADA client and it read/writes it from each client.
|
|
SCADA Ready |
We testified that these following products are compatible with each HMI/SCADA every year. So our OPC Server can be used at ease with all SCADA systems. Please see here about the SCADA list that has been verified.
|
|
Correspond MELSEC Completely |
To say nothing of the access to the MELSEC-Q / QnA / A / FX series, it corresponds to all functions of MELSEC like Ethernet, Serial, CC-Link, MELSECNET, Multi CPU system, Redundant CPU, and Process CPU, etc.
|
|
Top Page
Feature
Sample
Manual/Demo
