二次系统
一、二次系统基础 | Secondary System Fundamentals
二、保护装置 | Protection Devices
三、控制系统 | Control Systems
四、通信协议 | Communication Protocols
五、二次系统施工与调试 | Secondary Construction & Commissioning
Characters: Protection Engineer (保护工程师 PE) / Commissioning Lead (调试主管 CL) · Characters: SCADA Engineer (SCADA工程师 SE) / System Integrator (系统集成商 SI)
I've loaded the protection settings into all 24 relays across 6 bays. Each relay has been configured with the settings file exported from the protection coordination study. Now we need to do the secondary injection testing to verify each protection function operates at the correct threshold values. We'll use the Omicron test set.
保护定值已下装到6个间隔共24台继电器。每台按保护配合研究导出的定值文件配置。 现在做二次通流验证每个保护功能在正确阈值动作。用Omicron测试仪。
Good. Let's start with Bay 1 — the incoming line protection. Key functions to test: distance protection Zones 1 through 4, directional overcurrent, auto-reclosing scheme, and breaker failure initiation. For the distance zones, inject the calculated fault impedance at the zone boundary and verify the trip time — Zone 1 must trip within 25 ms, Zone 2 within 350 ms. Also, test the communication-aided schemes — permissive overreach and direct underreach — with the carrier signal simulated. Log every test point.
好。从第1间隔进线保护开始。主要功能测试：距离保护1到4段、方向过流、自动 重合闸逻辑、断路器失灵启动。距离段在边界点注入计算故障阻抗验证跳闸时间—— 1段须25ms内跳、2段350ms内。还要测通讯辅助方案——允许式超范围、直跳式欠范围 ——模拟载波信号。每点都记录。
Zone 1 trip time: 22 ms — pass. Zone 2: 328 ms — pass. Zone 3: 680 ms at 80% reach — pass. Zone 4 reverse: 1200 ms — pass. Now testing the auto-reclosing scheme: single-phase trip and reclose delay at 1 second, three-phase trip and reclose after 5 seconds, and the drive-to-lockout sequence after a permanent fault. All logic sequences match the approved settings. One issue: the breaker failure timer is set to 150 ms but the specification calls for 200 ms. I need to check this discrepancy.
1段跳闸：22ms——通过。2段：328ms——通过。3段80%范围：680ms——通过。4段反向： 1200ms——通过。现在测自动重合闸：单相跳闸1秒重合、三相跳闸5秒重合、永久故障 后的闭锁序列。所有逻辑序列与批准定值一致。一个问题：断路器失灵计时设了150ms 但规范要求200ms。这个差异需要核实。
Good catch. Check the protection coordination report — sometimes the final approved setting differs from the original specification after coordination with upstream and downstream protections. If 150 ms is the approved value from the coordination study, document it. If it's an error, correct it and retest. Never assume.
发现得好。查保护配合报告——有时配合上下游保护后最终批准定值会和原始规范不同。 如果150ms是配合研究批准的值，文件记录即可。如果是错误，纠正后复测。绝不臆断。
We've configured the IEC 61850 station bus for the new digital substation. All IEDs are communicating on the process bus via GOOSE — circuit breaker status, interlocking signals, and trip commands. But I'm seeing intermittent GOOSE message loss on VLAN 102. The network switch counters show occasional CRC errors. This is a problem because GOOSE is a publish-subscribe protocol with no retransmission — a lost message means a potential missed trip.
新数字化变电站IEC 61850站控总线已配置。所有IED通过GOOSE在过程总线通信—— 断路器状态、联锁信号、跳闸命令。但VLAN 102出现间歇性GOOSE报文丢失。网络 交换机计数器显示偶尔CRC错误。这是问题因为GOOSE是发布-订阅协议无重传—— 丢报文就是可能没收到跳闸。
CRC errors on a process bus are critical. Let's isolate. Is the issue on a specific fiber link? Check the SFP (Small Form-factor Pluggable) module signal levels on the affected port — if the optical power is marginal, replace the SFP or clean the fiber connectors. Also verify that the network switches are configured with QoS (Quality of Service) prioritizing GOOSE and SV traffic over MMS. GOOSE should be in the highest priority queue with strict priority scheduling. I also want to check the network topology — the process bus should be a ring with RSTP (Rapid Spanning Tree Protocol) for redundancy. A single point of failure can cause message storms.
过程总线CRC错误是致命的。先定位。是特定光纤链路吗？查一下受影响端口SFP 模块的光信号水平——如果光功率临界则换SFP或清洁光纤接头。还要确认网络交换机 配置了QoS让GOOSE和SV优先于MMS。GOOSE应放在最高优先队列用严格优先级调度。 还要查网络拓扑——过程总线应该是环网配RSTP冗余。单点故障会引起报文风暴。