Opto Software Suite
PAC Control.........................................................page 25
PAC Display (includes FAC2PAC)......................................page 71
- Display Configurator
- Display Runtime
PAC Manager.........................................................page 147
PAC Project Tools...................................................page 172 (Includes OptoVersion, OptoDisplay Converter, PAC Message Viewer, PAC Sim, PAC Terminal. Also includes changes to PAC Project Installer)
PAC Redundancy Manager..............................................page 180
OptoDataLink........................................................page 182
OptoOPCServer.......................................................page 190
SoftPAC.............................................................page 202- PAC Control.........................................................page 25
PAC Display (includes FAC2PAC)......................................page 71
PAC Manager.........................................................page 147
PAC Project Tools...................................................page 172 (Includes OptoVersion, OptoDisplay Converter, PAC Message Viewer, PAC Sim, PAC Terminal. Also includes changes to PAC Project Installer)
PAC Redundancy Manager..............................................page 180
OptoDataLink........................................................page 182
OptoOPCServer.......................................................page 190
SoftPAC.............................................................page 202
Pac Control generates IDB file. It is also where you create a control engine that will be used in other processes. Sets active control engine. You can create multiple control engines in one idb file or in multiple files.
Pac Display Configurator connects to multiple control engines you create in Pac Control and opens the idb files associated with the engines.
Pac Display Configurator generates IIU file.
Pac Display Runtime opens IIU file.
Pac Manager Burns IP addresses into the Hardware.
Opto Browser Configurator can open multiple IDB files. In Browser Configurator you can add items you want to be in your "Database" bdb file and update the server with the current browser database this is what makes the data available in the OptoOPCServer.
Opto Data link talks from the OPCServer to the SQL Database. It is also a service and is used to communicate between the projects(I think.)
OptoOPCServer This has both a front end that you can get to (This is where you look at the browser tabs) and is run like a headless process but it is not a service. The process is brought up all the time.
Input and Output files IDB file is the control strategy file.
Architecture Diagram
Brief Description
Control file ends in .idb. This is used as an input for several projects in the Opto Software Suite.
Browser Configurator 10.5: Imports control strategy file and inputs the tags into the OptoOPCServer 10.5 OptoOPCServer: Sends Messages from the hardware to the Software Suite? Opto Data Link: Sends the Scada Data to the MySql for historical data storage. (This is a one way connection at this point.)
We currently are not using the following:
I need to work on the UI. Use Stream 1 as my base case for the streams.
Write up notes on how to Transfer the System over from R2 and Brains to R1s.
- Note where we can find IP address in Pac Control. There is a location to modify the infomation here as well.
- Make a note of the disscussion that Sudhir and I had with Julio about converting brains and R2 into an R1 Gen 2.
Go through and add documentation.
- Flash the Strategy needs to be noted.
- Which Pac Project burns IP addresses
- Pac Manager
- Explain the Control Screens I saw this in chapter 15 of Camile User Manual.
- Add notes from Opto OPC Server and Opto Data link.
I need to register for the conference on the 18th.
Ethernet dongle assign Static IP 10.60.1.41? It may have to be 42. Use IP manager with R1 after we get the rack.
Document where everything fits together what creates the input and output files what reads them what modifies them.
File types need to be documented.
Make sure we put stickers on the boxes with the IP addresses so we don't fuck them up.
Ask the question How do we flash a control strategy to an IO unit do we have to use debug before running?
Take a look at the Pac Control tutorials.
What is the process of flashing the control strategy to the hardware.
Ok so we make a change to the type of IO units from R2 to R1 in the Pac Control Pro. Then in order to bring the changed control strategy into the OPC Server to Open Browser configurator remove current control strategy from the server modify the control strategy and then Update the bdb file? Even through it does not appear that the type is the changing factor. For each and every change to the Control strategy I will need to update the bdb?
[X] Ask the question How do we flash a control strategy to an IO unit do we have to use debug before running? [X] Ok so we make a change to the type of IO units from R2 to R1 in the Pac Control Pro. Then in order to bring the changed control strategy into the OPC Server to Open Browser configurator remove current control strategy from the server modify the control strategy and then Update the bdb file? Even through it does not appear that the type is the changing factor. For each and every change to the Control strategy I will need to update the bdb?