DNP3 Communication on PowerLogic P5 Protection Relays
Issue:
How to configure and use DNP3 protocol for PowerLogic P5 relays, including supported features, security considerations, and integration requirements.
Product:
PowerLogic P5 Protection Relay
Environment:
SCADA systems using DNP3 over Ethernet (TCP/IP) or serial (RS-485/fiber)
Industrial networks with multi-protocol support
Configuration tools: eSetup Easergy Pro, Web HMI
Cause:
DNP3 is widely used for event-driven communication in utility automation. Incorrect configuration of addressing, deadbands, or security settings can lead to communication
failures, missing events, or control issues.
Resolution:
- Protocol Support:
- Available on Ethernet (TCP/IP, port 20000) and serial RS-485/fiber
- Selectable in COMMUNICATION menu or via eSetup Easergy Pro/Web HMI
- Multi-Protocol:
- Can run with IEC 61850, Modbus TCP, EtherNet/IP on separate IP ports
- Supports up to 8 TCP clients and 3 IP addresses simultaneously
- Data Exchange:
- Real-time measurements, alarms/status, controls, time-stamped events
- Disturbance records, SOE files, setting group changes
- Supports unsolicited/event reporting and class 0–3 polling
- Data Model:
- 64 Binary Inputs, 32 Double-Bit Inputs, 32 Analog Inputs, 32 Counters, 32 Binary Outputs
- Extensive mapping for protection, measurement, control, and configuration
- Function Codes:
- Read (1), Write (2), Select (3), Operate (4), Direct Operate (5), Restart (13/14), File operations (25/26/28/30)
- Time Sync:
- UTC-based, DNP3 time sync (group 50), NEED_TIME bit handling
- Security:
- No native encryption; use VLANs, firewalls, TLS tunnels, and IP whitelisting (up to 8 CIDR ranges)
- Configuration Parameters:
- Bit rate: 1200–115200 bps, parity, 2/4 wire, slave address (1–65519)
- Deadband, unsolicited response, SBO timeout (60s), multi-fragment support
- Integration:
- Fully documented mapping tables for SCADA integration, including scaling and enumerations