广告广告位招商联系 ads@iaunion.comA5 · 728×90(移动端 320×100) · 参考价 ¥300/月了解详情 →

【Editorial】A general-purpose switch in a PROFINET or EtherNet/IP line: when does jitter, not throughput, fail first?

Started by FPGA_ARM_Linux · 2026-11-14 03:58 UTC · 23 views · 2 replies
F Member
【Editorial Discussion】

A convenient Ethernet switch in the middle of a motion or I/O line can pass a ping and still spoil a cyclic bus. The first failure is often jitter or lost I/O connections under load, not a lack of average bandwidth. “It is only a few devices” is not a sufficient argument if the switch does not meet the profile the protocol expects.

1) Check whether the device is a managed switch with the required features (store-and-forward behaviour, QoS for the protocol’s traffic class, no energy-efficient idle surprises, and a documented forwarding latency) or an office unit that happens to link at 100 Mb/s. The label “Gigabit” does not answer the jitter question.

2) Measure cycle-time jitter and lost frames when the line is busy, including a burst of non-real-time traffic if that can appear in the cabinet. An unloaded lab line will not show a queueing problem that only appears when a camera or a laptop is also plugged in.

3) Topology matters. A star through one oversubscribed box, or a long daisy-chain of store-and-forward hops, adds delay that the controller’s watchdog may not tolerate. Count hops and the published latency, not only cable length.

4) If you must use a general-purpose switch for a non-critical segment, keep it off the isochronous or motion path and document the split. Mixing those roles on the same unconfigured box is how intermittent drops get blamed on the PLC.

Open question: have you had a line that pinged clean and still dropped I/O, later traced to an office switch or an unconfigured QoS path? What test do you now require before a switch is allowed on a cyclic bus?
I Editorial
工业以太网里先看抖动和连接保持,而不是平均带宽,这个判断对。通用交换机最常见的问题是没有按协议轮廓处理循环报文:缓存里混了办公突发、禁用了或没有 IRT/优先队列、巨型帧或风暴控制把周期报文拖晚。建议验收时至少做三项:在额定周期和设备数量下看抖动和丢失周期计数,而不是只 ping;人为在同一交换机上注入非实时流量,循环连接应仍保持;确认端口速率、双工和线缆是固定的,没有在 100M/半双工之间来回协商。非管理型交换机或家用交换机即使“暂时能通”,也不要留在运动总线或远程 IO 线上。如果必须用管理型通用交换机,要把 QoS、IGMP、LLDP 和环网特性按总线要求逐项核对,并在负荷试验后保留抓包。通了和满足周期,是两件事。
Z Member
遇到过类似情况,补充一个现场案例和验收清单。
案例是这样的:一条 PROFINET 线上挂了十几个远程 IO,平时 ping 全部正常,生产一上量就偶发 IO 掉站,控制器报设备丢失,几秒后自己恢复。查下来是中间串了一台办公用的非网管交换机,端口还带节能模式,空闲一阵就降速,循环报文到时要先等端口从节能唤醒,抖动直接冲破更新周期。换成工业网管交换机、端口固定速率双工、关掉节能后问题消失。ping 测的是毫秒级平均延迟,根本看不到这种几百微秒级的抖动。
现在交换机上循环总线前,强制做四项验收测试:
一是满载抖动测试:在额定周期和设备数量下跑满 24 小时,记录最大抖动和丢帧计数,不是只看平均值。
二是突发流量注入:在同一台交换机上人为注入非实时突发流量,循环连接必须保持,丢帧为零才算过关。
三是端口状态核对:逐个确认速率、双工固定,EEE 节能、生成树、风暴控制全部按总线要求配置,风暴控制的阈值不能把循环报文误限流。
四是断电重启验证:交换机断电重启后,所有设备要在规定时间内重新建立连接并恢复循环数据,超时未恢复的要记录。
这四项都通过才允许交换机上循环总线,否则宁可多布一根线。
广告广告位招商联系 ads@iaunion.comA6 · 728×90(移动端 320×100) · 参考价 ¥200/月了解详情 →
Log in or register to reply.