Working with LCN & SCADA Views

 

 

Control Architect requires both Point (pnt) and Hardware (hdw) data to be exported from Quick Builder for conversion to PKS standard XML Configuration files.  When exporting items from the Quick Builder application select the menu item "File-Export..." and choose the Scope option "All items relevant to file type".  Expand the "Show Options >>" section and choose the option "Export all Fields" to export all Parameter items regardless of their default value.  This will export all configured Channels, Controllers, and Points.  A single Point configuration file named [filename].pnt will be created for all the existing point configuration.  Another single Hardware configuration file named [filename].hdw will also be created for all the existing Channel and Controller configuration.  These 2 exported configuration files are then referenced in the conversion tool.

 

 

When LCN & SCADA Point types are converted to XML Configuration files their assigned to Node, Box, or Unit is used to form an equivalent PKS Control Execution Environment (CEE) assignment.  The example below shows a typical LCN that contains both Hiway, UCN and AM data types that were converted.  The data column AssignedTo shows how the LCN node types are used to form an assigned to CEE.  These nodes and their AssignedTo name are used to identify Peer nodes when viewing Peer relationships.

 

AM type entities are assigned to a node that is formatted using its assigned to LCN Unit id.  The example below shows an AM entity 2AC4086X that is assigned to the AM Unit '05' where its AssignedTo node is formed using its configured LCN UNIT id.  The format used is "AMUNIT_uu" where uu is the configured LCN Unit id for the entity.

 

 

 

 

LCN Point types use their configured UNIT id to form a ParentAsset.  The ParentAsset is formatted as "UNIT_uu" where uu is the configured LCN Unit id for the entity.

 

 

 

It is recommended that all control related nodes assigned to an LCN are converted to form a single configuration project.  Working with a full LCN assures that all connection relationships between AM and other node types are captured along with any UCN node-to-node peer common between xPM and SM node types.  Export your LCN Schematic files as debug DX text files for importing into your LCN based configuration project to provide graphic references.  If LCN Schematic screen captures are available as Bitmap or PNG file types, then these can also be imported to provide a visual view of the LCN Schematic.

 

PKS SCADA and FSC type projects should be imported into the configuration project that contains the C300 CEE entities.  This assures that any ACE-to-SCADA type OPCServer references are fully identified and navigable through ChartView hyperlink connection references.  FSC connection references to C300 CEE functions, FSC-to-FSC Controller peer, and HMIWeb references are supported when FSC data is imported into the same configuration project that contains the C300 CEE entities and HMIWeb graphic files.

 

 

LCN point types that support Control Language such as MC/PM/APM/HPM Process Module and AM Bound or Package CL types are converted as a PKS CAB equivalent.  The examples below show a CustomAM point type that is configured with a CL Package and an XPM Process Module point type that is bound by a CL Sequence application.  The Parameter references found during the CL Analysis phase are created as part of the application definition.  Process Module types have their internal parameter types such as NN, FL, TM, STR converted as "Value CDP's".