KepserverEX for IEC 61850 data read

​

Greetings ​ ​@JA_14571452 ,


You may use the IEC 61850 device driver to connect it with the kepware.

Phase 1: Ingesting IEC 61850 Data into KEPServerEX

The KEPServerEX IEC 61850 MMS Client Driver translates standard Manufacturing Message Specification (MMS) packets into internal channel/device tags.

1. Driver and Channel Configuration

1. Open the KEPServerEX Configuration utility.
2. Select Click to add a channel and set the type to IEC 61850 MMS Client. Follow the wizard defaults.
3. Select Click to add a device, assign a unique name (e.g., Feeder_Relay_1), and enter the target physical IED’s IP Address.

2. Automated Tag Generation

Avoid manual tag mapping by leveraging the driver's structural auto-generation:

• Method A (SCL File - Recommended): Navigate to Device Properties > Automatic Configuration. Set the source to SCL File and browse to your relay configuration file (.icd, .cid, or .scd). Select the designated IED and Access Point.
• Method B (Online Discovery): If live on-site with network access to the IED, set the source to Device.
• Execution: Right-click the Device in the tree view and select Automatic Configuration > Create Tags. The system will automatically build the hierarchical structural tree (Logical Devices $\rightarrow$ Logical Nodes $\rightarrow$ Data Objects $\rightarrow$ Data Attributes).

Phase 2: Exposing KEPServerEX via OPC UA

Once tags are populated, the internal database must be hosted on an active, secure OPC UA endpoint.

1. Endpoint Provisioning

1. Right-click the KEPServerEX Administration icon in the Windows System Tray and launch OPC UA Configuration.
2. Under the Server Endpoints tab, click Add...
3. Select the appropriate network adapter interface and configure the service port (Default: 49320).
   • Endpoint URL Example: opc.tcp://[Server_IP]:49320
4. Security Policies: Select security profiles matching your client capabilities.

⚠️ Security Note: Enable None only for initial sandbox troubleshooting. For production environments, strictly enforce Sign or Sign & Encrypt policies (e.g., Basic256Sha256).

2. Trust and Certificate Exchange

1. Navigate to the Instance Certificate tab to confirm or generate the KEPServerEX self-signed certificate.
2. When an upstream client (e.g., FactoryTalk View SE) attempts its initial connection, it will be rejected.
3. Open the Trusted Clients tab within this utility, locate the rejected client certificate from your HMI host, and click Trust to finalize the bidirectional security handshake.

Verification Checklist

• [ ] Verify that the KEPServerEX OPC UA runtime service is restarted/reinitialized after applying endpoint modifications.
• [ ] Launch the QC (Quick Client) inside Kepware to validate that live, changing values are populating from the physical IED into the IEC 61850 driver registers before attempting HMI binding.

​