Dynamic Data Acquisition

Main.DataAcquisition History

Hide minor edits - Show changes to output

February 07, 2020, at 03:45 PM by 12.45.189.171 -
Changed lines 53-54 from:
           result  = client.write_registers(int(reg), payload, skip_encode=True, unit=int(slave_address))
to:
           result  = client.write_registers(int(reg), payload,\
                     
skip_encode=True, unit=int(slave_address))
July 17, 2019, at 12:22 PM by 136.36.211.159 -
Changed lines 142-149 from:
The Arduino is a popular micro-controller that allows data acquisition, limited on-board processing, and output capabilities. With a large developer community and supported sensors, this platform is a popular choice for data acquisition and automation applications.
to:
The Arduino is a popular micro-controller that allows data acquisition, limited on-board processing, and output capabilities. With a large developer community and supported sensors, this platform is a popular choice for data acquisition and automation applications. The [[http://apmonitor.com/do/index.php/Main/AdvancedTemperatureControl|Temperature Control Lab (TCLab)]] connects to a computer with a serial USB connection with MATLAB or Python. The serial USB connection sends commands (heater level, LED level) and receives data (temperature) to enable real-time control.

(:html:)
<video width="550" controls autoplay loop>
  <source src="/do/uploads/Main/tclab_linear_mpc.mp4" type="video/mp4">
  Your browser does not support the video tag.
</video>
(:htmlend:)
July 17, 2019, at 12:18 PM by 136.36.211.159 -
Changed lines 19-20 from:
This example code **Show Modbus Example Code** shows how to connect to a Modbus Server (Slave) with a Modbus Client (Master) using **pymodbus**. The code writes a table of 16 values to 16 individual registers (2 each for a floating point number). The registers start at 40001.
to:
This example code '''Show Modbus Example Code''' connects to a Modbus Server (Slave) with a Modbus Client (Master) using [[https://pypi.org/project/pymodbus/|pymodbus]]. The code writes a table of 16 values to 16 individual registers (2 each for a floating point number). The registers start at 40001.
Changed line 69 from:
This example code **Show OPC Example Code** shows how to write to an OPC Server with an OPC Client (OpenOPC). The code writes 16 values to 16 individual OPC tags on a Kepware OPC Server.
to:
This example code '''Show OPC Example Code''' writes to an OPC Server with an OPC Client with [[https://pypi.org/project/OpenOPC/|OpenOPC]]. The code writes 16 values to 16 individual OPC tags on a [[https://www.kepware.com/en-us/products/kepserverex/|Kepware Server]].
July 17, 2019, at 12:14 PM by 136.36.211.159 -
Changed lines 19-20 from:
This example shows how to connect to a Modbus Server with a Modbus Client. The code writes a table of 16 values to 16 individual registers (2 each for a floating point number). The registers start at 40001.
to:
This example code **Show Modbus Example Code** shows how to connect to a Modbus Server (Slave) with a Modbus Client (Master) using **pymodbus**. The code writes a table of 16 values to 16 individual registers (2 each for a floating point number). The registers start at 40001.
Added lines 68-69:

This example code **Show OPC Example Code** shows how to write to an OPC Server with an OPC Client (OpenOPC). The code writes 16 values to 16 individual OPC tags on a Kepware OPC Server.
July 17, 2019, at 12:11 PM by 136.36.211.159 -
Changed line 22 from:
(:div id=gekko:)
to:
(:div id=modbus:)
Added lines 68-121:

(:toggle hide opc button show="Show OPC Example Code":)
(:div id=opc:)
(:source lang=python:)
# #######################################
# OPC write
# #######################################
try:
    # OPC connection
    import OpenOPC
    opc=OpenOPC.client()
    b=opc.connect('Kepware.KEPServerEX.V5')
    #opc.connect('Kepware.KEPServerEX.V5','localhost')

    Load1_avg  = opcm[0][0]
    Load2_avg  = opcm[0][1]
    Load3_avg  = opcm[0][2]
    Load4_avg  = opcm[0][3]
    Load1_max  = opcm[1][0]
    Load2_max  = opcm[1][1]
    Load3_max  = opcm[1][2]
    Load4_max  = opcm[1][3]
    Load1_min  = opcm[2][0]
    Load2_min  = opcm[2][1]
    Load3_min  = opcm[2][2]
    Load4_min  = opcm[2][3]
    Load_T12  = opcm[3][0]
    Load_T21  = opcm[3][1]
    Load_T32  = opcm[3][2]
    Load_T41  = opcm[3][3]

    opc.write( ('Channel2.Device1.T_12_Load_AVG',Load1_avg) )
    opc.write( ('Channel2.Device1.T_21_Load_AVG',Load2_avg) )
    opc.write( ('Channel2.Device1.T_32_Load_AVG',Load3_avg) )
    opc.write( ('Channel2.Device1.T_41_Load_AVG',Load4_avg) )
    opc.write( ('Channel2.Device1.T_12_Load_MAX',Load1_max) )
    opc.write( ('Channel2.Device1.T_21_Load_MAX',Load2_max) )
    opc.write( ('Channel2.Device1.T_32_Load_MAX',Load3_max) )
    opc.write( ('Channel2.Device1.T_41_Load_MAX',Load4_max) )
    opc.write( ('Channel2.Device1.T_12_Load_MIN',Load1_min) )
    opc.write( ('Channel2.Device1.T_21_Load_MIN',Load2_min) )
    opc.write( ('Channel2.Device1.T_32_Load_MIN',Load3_min) )
    opc.write( ('Channel2.Device1.T_41_Load_MIN',Load4_min) )
    opc.write( ('Channel2.Device1.T_12_Load_INST',Load_T12) )
    opc.write( ('Channel2.Device1.T_21_Load_INST',Load_T21) )
    opc.write( ('Channel2.Device1.T_32_Load_INST',Load_T32) )
    opc.write( ('Channel2.Device1.T_41_Load_INST',Load_T41) )

    opc.close()
except:
    print 'OPC communication failed'
    pass
(:sourceend:)
(:divend:)
July 17, 2019, at 12:09 PM by 136.36.211.159 -
Added lines 18-61:

This example shows how to connect to a Modbus Server with a Modbus Client. The code writes a table of 16 values to 16 individual registers (2 each for a floating point number). The registers start at 40001.

(:toggle hide modbus button show="Show Modbus Example Code":)
(:div id=gekko:)
(:source lang=python:)
# #######################################
# Modbus write
# #######################################
try:
    # import the various server implementations
    from pymodbus.client.sync import ModbusTcpClient as ModbusClient
    from pymodbus.constants import Endian
    from pymodbus.payload import BinaryPayloadBuilder
    from pymodbus.client.sync import ModbusTcpClient as ModbusClient
    from pymodbus.payload import BinaryPayloadDecoder

    # initiate client
    ##client = ModbusClient('192.168.0.1')
    client = ModbusClient(host='localhost', port=502)
    slave_address = 0

    # AVG Registers Modbus 40001,3,5,7
    # MAX Registers Modbus 40009,11,13,15
    # MIN Registers Modbus 40017,19,21,23
    # INST Registers Modbus 40025,27,29,31
    # registers
    reg = 0
    # AVG, MAX, MIN, INST
    for i in range(0,4):
        # Channels
        for j in range(0,4):
            builder = BinaryPayloadBuilder(endian=Endian.Little)
            builder.add_32bit_float(opcm[j][i])
            payload = builder.build()
            result  = client.write_registers(int(reg), payload, skip_encode=True, unit=int(slave_address))
            # two registers for floating point numbers
            reg = reg + 2
    client.close()
except:
    print 'Modbus communication failed'
    pass
(:sourceend:)
(:divend:)
May 02, 2015, at 04:35 AM by 45.56.3.184 -
Changed lines 5-6 from:
There are many methods to acquire and send data for industrial systems with a range of proprietary and community-based standards that facilitate exchange of information between instruments, a programmable logic controller (PLC), a distributed control system (DCS), and other systems that measure, analyze, or optimize the system. Exchange of information is increasingly important, particularly for optimization solutions, as availability of information is the foundation for many automation and optimization methods. Of particular interest to this course are the methods to retrieve data, run parameter estimation or optimization algorithms, and then either display advisory results or implement a solution back into the process. Common communication standards include:
to:
There are many methods to acquire and send data for industrial systems with a range of proprietary and community-based standards that facilitate exchange of information between instruments, a programmable logic controller (PLC), a distributed control system (DCS), and other systems that measure, analyze, or optimize the system. Exchange of information is increasingly important, particularly for optimization solutions, as availability of information is the foundation for many automation and optimization methods. Of particular interest to this course are the methods to retrieve data, run parameter estimation or optimization algorithms, and then either display advisory results or implement a solution back into the process.

!!Common Communication Standards

Added lines 30-42:

!!Data Acquisition and Communication

There are several hardware platforms that allow data acquisition and software platforms that facilitate communication.

!!!!Robot Operating System (ROS)
ROS is a C++ or Python library that allows inter-process communication. It can be run on anything from a desktop computer to an Arduino (at least in part). Its strength comes from the many different types of ROS packages that already exist and allow for sensors and actuators to communicate.

!!!!Micro-processors
Several micro-processors, such as the Raspberry PI and the Beagle Bone Black, have been developed to allow on-board data acquisition and processing. These credit-card sized platforms run a full version of Linux with ARM processors several digital and analog inputs and outputs.

!!!!Micro-controllers
The Arduino is a popular micro-controller that allows data acquisition, limited on-board processing, and output capabilities. With a large developer community and supported sensors, this platform is a popular choice for data acquisition and automation applications.
April 30, 2015, at 11:59 PM by 45.56.3.184 -
Changed lines 7-9 from:
* ([[https://en.wikipedia.org/wiki/Modbus|MODBUS]])
* ([[https://en.wikipedia.org/wiki/OLE_for_Process_Control|OPC-DA / OPC-UA]])
* ([[https://en.wikipedia.org/wiki/SQL|SQL Server / Client]])
to:
* [[https://en.wikipedia.org/wiki/Modbus|MODBUS]]
* [[https://en.wikipedia.org/wiki/OLE_for_Process_Control|OPC-DA / OPC-UA]]
* [[https://en.wikipedia.org/wiki/SQL|SQL Server / Client]]
April 30, 2015, at 11:59 PM by 45.56.3.184 -
Changed lines 7-11 from:
* MODBUS
* OPC-DA
/ OPC-UA
* SQL Server
/ Client

!!!! MODBUS
([[https://en.wikipedia.org/wiki/Modbus|Wikipedia Article]])
to:
* ([[https://en.wikipedia.org/wiki/Modbus|MODBUS]])
*
([[https://en.wikipedia.org/wiki/OLE_for_Process_Control|OPC-DA / OPC-UA]])
* ([[https://en.wikipedia.org/wiki/SQL|SQL Server / Client]])

!!!! MODBUS
Changed line 17 from:
!!!! OPC ([[https://en.wikipedia.org/wiki/OLE_for_Process_Control|Wikipedia Article]])
to:
!!!! OPC
Changed line 23 from:
!!!!SQL Client/Server ([[https://en.wikipedia.org/wiki/SQL|Wikipedia Article]])
to:
!!!!SQL Client/Server
April 30, 2015, at 11:57 PM by 45.56.3.184 -
Deleted lines 10-12:
!!!! OPC ([[https://en.wikipedia.org/wiki/OLE_for_Process_Control|Wikipedia Article]])
OLE (Object Linking and Embedding) for Process Control (OPC), was developed in 1996 by an industrial automation group based on the need for a common platform for exchanging data. The OPC standard details the communication of real-time or historical plant data between control devices and computers. OPC is sometimes referred to as "Oh, Please Connect" with frequent difficulty in connecting to various computers with incorrect DCOM settings. A recent effort termed OPC-UA or Unified Architecture, is a new implementation of the software that allows communication to devices other than the Windows OS platform. In November 2011, the OPC Foundation (body primarily responsible for the OPC standard) officially renamed OPC to mean "Open Platform Communications".

Added lines 14-22:
* [[https://www.mathworks.com/matlabcentral/fileexchange/27815-modbus-rs232-ascii-communication-functions|MODBUS Toolbox for Matlab]]
* [[https://github.com/bashwork/pymodbus|MODBUS Package for Python]]

!!!! OPC ([[https://en.wikipedia.org/wiki/OLE_for_Process_Control|Wikipedia Article]])
OLE (Object Linking and Embedding) for Process Control (OPC), was developed in 1996 by an industrial automation group based on the need for a common platform for exchanging data. The OPC standard details the communication of real-time or historical plant data between control devices and computers. OPC is sometimes referred to as "Oh, Please Connect" with frequent difficulty in connecting to various computers with incorrect DCOM settings. A recent effort termed OPC-UA or Unified Architecture, is a new implementation of the software that allows communication to devices other than the Windows OS platform. In November 2011, the OPC Foundation (body primarily responsible for the OPC standard) officially renamed OPC to mean "Open Platform Communications".

* [[https://www.mathworks.com/products/opc/|OPC Toolbox for MATLAB]]
* [[https://openopc.sourceforge.net/|OPC Client for Python (OpenOPC)]]

Added lines 24-27:
SQL (Structured Query Language) is a programming language popular with enterprise and web applications that requirement storage and access to historical or real-time data. It is not commonly used for process control or automation like MODBUS or OPC but the large user base of SQL programmers and requirements for big-data suggests that SQL may become a more popular platform in the future.

* [[https://www.mathworks.com/help/database/run-sql-query.html|SQL Queries from MATLAB]]
* [[https://pypi.python.org/pypi/python-sql|SQL Queries from Python]]
April 30, 2015, at 11:43 PM by 45.56.3.184 -
Changed line 2 from:
(:keywords data acquisition, OLE for process control, OPC, DAQ, dynamic data, simulation, validation, differential, algebraic, tutorial:)
to:
(:keywords data acquisition, OLE for process control, OPC, Modbus, DAQ, dynamic data, simulation, validation, differential, algebraic, tutorial:)
Added lines 4-17:

There are many methods to acquire and send data for industrial systems with a range of proprietary and community-based standards that facilitate exchange of information between instruments, a programmable logic controller (PLC), a distributed control system (DCS), and other systems that measure, analyze, or optimize the system. Exchange of information is increasingly important, particularly for optimization solutions, as availability of information is the foundation for many automation and optimization methods. Of particular interest to this course are the methods to retrieve data, run parameter estimation or optimization algorithms, and then either display advisory results or implement a solution back into the process. Common communication standards include:

* MODBUS
* OPC-DA / OPC-UA
* SQL Server / Client

!!!! OPC ([[https://en.wikipedia.org/wiki/OLE_for_Process_Control|Wikipedia Article]])
OLE (Object Linking and Embedding) for Process Control (OPC), was developed in 1996 by an industrial automation group based on the need for a common platform for exchanging data. The OPC standard details the communication of real-time or historical plant data between control devices and computers. OPC is sometimes referred to as "Oh, Please Connect" with frequent difficulty in connecting to various computers with incorrect DCOM settings. A recent effort termed OPC-UA or Unified Architecture, is a new implementation of the software that allows communication to devices other than the Windows OS platform. In November 2011, the OPC Foundation (body primarily responsible for the OPC standard) officially renamed OPC to mean "Open Platform Communications".

!!!! MODBUS ([[https://en.wikipedia.org/wiki/Modbus|Wikipedia Article]])
ASCII or RTU MODBUS is an older standard than OPC and has several limitations that motivated the creation of OPC. Although it is an old standard, several legacy pieces of equipment still support this protocol. There are several serial or network connection possibilities including RS232, RS422, RS485 (serial) or TCP/IP (network).

!!!!SQL Client/Server ([[https://en.wikipedia.org/wiki/SQL|Wikipedia Article]])
Added lines 1-3:
(:title Dynamic Data Acquisition:)
(:keywords data acquisition, OLE for process control, OPC, DAQ, dynamic data, simulation, validation, differential, algebraic, tutorial:)
(:description Python tutorial for collecting data for dynamic simulation, estimation, and control:)