Scilab-DAQ
Exchange data between Scilab and Hardwares
Zhe.Peng, Longhua.Ma
State Key Lab of Industrial Control Technology
Zhejiang Unvi. P.R.China
Ver. 1.0, 1 Sep 2006
Please cotact me if any questions: pengzhe1113@gmail.com
About Scilab-DAQ Project
Scilab DAQ (Data Acquisition) Toolbox enables Scilab exchange data with other hardware and software through Serail, Ethernet using OPC, Modbus RTU/ASCII/ETHERNET protocol.
Now we only provide Windows version of DAQ Toolbox, we will release Linux version soon.
About OPC protocol
The OPC Foundation has established a set of standard OLE/COM interface protocols intended to foster greater interoperability between automation/control applications, field systems/devices, and business/office applications in the process control industry .
This specification describes the OPC COM Objects and their interfaces implemented by OPC Servers. An OPC Client can connect to OPC Servers provided by one or more vendors.
Different vendors may provide OPC Servers. Vendor supplied code determines the devices and data to which each server has access, the data names, and the details about how the server physically accesses that data. Specifics on naming conventions are supplied in a subsequent section.
Although OPC is primarily designed for accessing data from a networked server, OPC interfaces can be used in many places within an application. At the lowest level they can get raw data from the physical devices into a SCADA or DCS, or from the SCADA or DCS system into the application.. The architecture and design makes it possible to construct an OPC Server which allows a client application to access data from many OPC Servers provided by many different OPC vendors running on different nodes via a single object.
You can download it in OPC Toolbox V1.2 .
OPC Functions the DAQ Toolbox provided:
=================================================
Version 1.2
2007.1
Add two function:
opc_item_browse
opc_server_browse
Rewrite TCL/TK GUI
----------------------------------------------------------------
----------------------------------------------------------------
Version 1.1
2006.11
Enable float r/w
Fixed some bugs
----------------------------------------------------------------
----------------------------------------------------------------
Version 1.0
2006.8
Main function:
opc_add_group
opc_add_item
opc_connect
opc_disconnect
opc_item_read
opc_item_write
==================================================
About Modbus protocol
Controllers supporting Modbus protocol can communicate with each other and with other devices over a variety of networks. Supported networks include the Modbus and Modbus Plus industrial networks, and standard networks such as MAP and Ethernet. Networks are accessed by built¨Cin ports in the controllers or by network adapters, option modules, and gateways .
During communications on a Modbus network, the protocol determines how each controller will know its device address, recognize a message addressed to it, determine the kind of action to be taken, and extract any data or other information contained in the message. If a reply is required, the controller will construct the reply message and send it using Modbus protocol.
MODBUS/TCP is a variant of the MODBUS family of simple, vendor-neutral communication protocols intended for supervision and control of automation equipment. Specifically, it covers the use of MODBUS messaging in an ¡®Intranet¡¯ or ¡®Internet¡¯ environment using the TCP/IP protocols. The most common use of the protocols at this time are for Ethernet attachment of PLC¡¯s, I/O modules, and ¡®gateways¡¯ to other simple field buses or I/O networks.
You can download it in Modbus-RTU toolbox V1.0; Modbus-TCP toolbox V1.0
Modbus Functions the DAQ Toolbox provided:
The Industry Application
See as follow screenshot:
Screenshot1, Screenshot2, Screenshot3, Screenshot4, Screenshot5
