Ignition 8
Ignition 7.9
Ignition 7.8
Sepasoft - MES Modules
Cirrus Link - MQTT Modules
Inductive University
Ignition Demo Project
Knowledge Base Articles
Forum
IA Support
Deprecated Pages
SDK Documentation
FactoryPMI Reporting Manual
FactorySQL
Ignition 8.1. Offline Version (04/2021)
Enter the IP address or hostname of the device you are connecting to in the Hostname field. All other default settings can be left as is.
On the connected driver, IEC61850 in this example, and click More > scd. Substation Configuration Description (SCD) files grant user control of transfer device descriptions and communication parameters. This file format is the only accepted System Configuration Language (SCL) file type. It is generally recommended to use an SCD file if you intend to limit the request size and visibility of access points during OPC browsing. This will effectively reduce the load against the substation device. Without an SCD file, any device connection restart will request all defined Logical Nodes from your defined IED for OPC browsing, which can become network-traffic heavy. However, because of how Ignition treats device attributes we recommend always using an SCD file, as it may not be possible to resolve associated quality or timestamp values without it.
Note:
Select the IED you want to request for reports.
Note: Returning to step 9, the selected IED will now display in the IED Name field and the accessPoint information will now display in the Access Point Name field for the SCL File Settings section of the advanced properties.
Click Save.
Note: The advanced properties will now show the saved SCD file settings. Checking the Show advanced properties box on the Device > edit page will display the settings. Use SCD File will be checked, and IED Name and Access Point Name will match the selected upload config settings. You can use these settings to verify correct configuration or further tweak your SCD file.
Once you've established a device connection, you'll likely be looking to enable a report so it may be helpful to check the device data before opening your Designer. The OPC Quick Client can be a useful tool for checking report statuses or for troubleshooting purposes. Navigate to OPC Client > OPC Quick Client to access the Ignition OPC UA Server folder and locate your IED under the Devices folder. The configured device data is stored in three main folders:
Reports: The Reports folder includes all the available reports and attributes available for subscription.
Note: Subscribing to any reporting control block attribute will trigger Ignition to attempt to enable the associated report via the RptEna attribute. If enabling of a report cannot be achieved you will see quality like Bad_OutOfService: The source of the data is not operational.
If you are unsure of your report subscription status, you can use the Read link [r] for the RptEna tag within the related Reports folder to confirm if the report is available before you try to enable it. If the value returns as True, that report is already enabled elsewhere and unavailable for use.
Few events in the IEC 61850 standard allow for writes to occur, and no write actions should be attempted on the Quick Client page. See Device Operations below for recommended practices to write back to an IED.
| General | |
|---|---|
| Name | The name of this IEC61850 device connection. |
| Description | Device connection description (optional). Can be used to provide any useful information / comments about this connection. |
| Enabled | If True (checked), the connection is enabled; if False (unchecked), the connection is disabled. |
| Main | |
| Hostname | The IP Address of the device. |
| Port | The port to use when connecting to an IEC61850 device, default is 102. |
| Request Timeout | Determines the maximum amount of time a request to the device will wait for a response, default is 2000. |
Authentication | |
|---|---|
| Authentication Enabled | Determines if a password will be provided for authenticating requests to the device, default is false. |
| Authentication Password | The password used to authenticate requests to the device, default is an empty string. |
| SCD File Setting | |
| Use SCD File | Determines if a SCD file upload will be used when requesting from the device. The default value is false. |
| Use Configured Hostname | Override any hostname that may have been set by the SCD file with the configured hostname, default is false. |
| Use Configured OSI Params | Override any OSI params that may have been set by the SCD file with the configured OSI params, default is false. |
| IED Name | If Use SCD File is enabled, this field will be populated automatically with the selected IED name during the SCD File Upload. |
| Access Point Name | If Use SCD File is enabled, this field will be populated automatically with the selected IED access point information during the SCD File Upload. |
| Advanced Client OSI Parameters | |
| Client AE Qualifier | Sets the client Application Entity Qualifier, default is 12. |
| Client AP Title | Sets the client Application Process Title, default is 1,1,1,999,1. |
| Client Presentation-Selector | Sets the client Presentation-Selector (P-SEL), default is 00000001. |
| Client Session-Selector | Sets the client Session-Selector (S-SEL), default is 0001. |
| Client Transport-Selector | Sets the client Transport-Selector (T-SEL). It is optionally transmitted in the OSI Transport Layer connection request (CR), default is 0001. |
| Advanced Server OSI Parameters | |
| Server AE Qualifier | Sets the server Application Entity Qualifier, default is 12. |
| Server AP Title | Sets the server Application Process Title, default is 1,1,1,999,1. |
| Server Presentation-Selector | Sets the server Presentation-Selector (P-SEL), default is 00000001. |
| Server Session-Selector | Sets the server Session-Selector (S-SEL), default is 0001. |
| Server Transport-Selector | Sets the server Transport-Selector (T-SEL). It is optionally transmitted in the OSI Transport Layer connection request (CR), default is 0001. |
| Misc. Advanced Settings | |
| Use Report Timestamp | Determines if the timestamp from the report will be used instead of the timestamp associated with each reported value. |
Reports can exchange monitoring information, power metering, power quality, and fault event analysis, among other data from IED servers to clients. Device data and reports are sent to the client based on user-defined device configuration through report control blocks (RCBs) and SCL files. The IEC 61850 driver supports Unbuffered/Buffered Report Control Blocks (URCB/BRCB). Remember, an RCB can only be enabled by a single device connection to the IED. This is because an RCB is blocked once a client has registered to receive a report by enabling it. Therefore, if the report is in use elsewhere, an attempted overlap could prevent connections from occurring. You will need to replicate the report on your IED if you want multiple Ignition Gateways to access the same report or leverage a Remote Tag Provider.
If you are using a buffered report, be aware the config.idb file will be frequently updated with the last report_id received. This could cause the auto-backup to trigger every 2 minutes when Ignition sees a change to the config.idb file. Changes to the auto-backup settings are encouraged to prevent threads pausing until the DB finishes being backed up. Changes can be made by modifying either of the following properties in the data/gateway.xml file.
The first modification option is to change the value in minutes for how often the auto-backup is triggered based on when Ignition checks for changes. The current value as shown is 2 minutes.
<entry key="localdb.autobackup.delay">2</entry>
The following method is not recommended, but you can also change the true value to false, which will turn off this feature entirely if desired.
<entry key="context.startup.useautobackups">true</entry>
Adding a report folder in your Designer immediately enables a report and allows you to see related attributes in the Tag Browser. This process is done in the same manner as creating a tag.
As you navigate to your desired Logical Node and Points folder, you'll notice a different format than what you might expect from a typical tag in the Tag Browser where all attributes are contained in a single tag. Attributes are listed as separate tags with their own qualified values (e.g. value, quality, and timestamps). This is because the Ignition needs to map the 61850 specification to the OPC UA model that requires an associated value, quality, and timestamp. Ignition will attempt to retrieve the q and t attributes that correspond with reported value attributes if they are available. Be sure to only add a single folder from the Points folder to your Tag Browser to avoid any issues that can occur from enabling multiple reports. 
Once a specific attribute tag has been added in the Connected Devices window, you'll see your enabled report data in the Tag Browser. You can further curate this data by deleting unwanted data from the browser display.
Additionally, the OPC item path that Ignition uses can be isolated to identify individual attribute data because paths are built with an hierarchical data model. The data included in the path identifies the IED, logical device, logical node, data object, and attribute information. The example attribute we've been using in this section is shown below.
[SSSA_52AFA_FPR]LD0/LLN0.rcbDigitals05$SSSA_52AFA_FPRCTRL/CBCILO1.EnaCls.stVal
Deleting all Points from the Tag Browser in your Designer and/or deleting all report point subscriptions from the OPC Quick Client page will disable a report. You can confirm a report is successfully disabled by using the read from link [r] for the corresponding RptEna tag on the OPC Quick Client page.
Additionally, if a device is disabled while a subscription is still active, the subscription status code will show Uncertain_LastUsableValue instead of the good value.
The IEC 61850 driver supports certain system functions to control operations and perform file services. These functions can be used to discover object data, test or maintain desired statuses, and modify device files. Check out the system.iec61850 page for complete function information.
The supported IEC 61850 system control functions are getControlParams, Select, Operate, and Cancel. The getControlParams function returns a list of report control names and their attributes contained in the configured IEC 61850 device. Having a function to collect this data in the moment is useful for many instances, including to provide the required params keys for the Select, Operate, and Cancel functions if they are otherwise unknown.
The type of control model (ctlModel) defines how to use the Select (if applicable) and Operate control functions to write to the connected 61850 device when possible. A Status-only type means you cannot perform any operation actions. Direct types allow an immediate change to an access point using the Operate function only. Select before Operate (SBO) types require use of the Select function to confirm a chosen access point before the Operate function will run. Control model types are represented by the following values:
The Cancel function will clear a selection of an SBO type control if an operate command is not desired to be executed on the selected control.
The supported IEC 61850 system file functions are listFile, readFile, and writeFile. These functions allow users to obtain a list of files present on configured devices, and transfer IED files between remote IED servers and local paths. Note that local paths for file functions are local to the Gateway. For example, if these functions get used on a Perspective page, the file will be downloaded to the Gateway, not the client where the browser is running.
