简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
HanaBennett0709 · 2025年1月8日 09:21 UTC
Check which adapter carries the connection while docked. A ping reply tells you something answered; it doesn't identify the route your application used or prove the expected service is available.
23分Dock Ethernet and bench adapter both have addresses on the same subnet. Hadn't noticed that.
8分That is worth investigating. Compare the selected route in both setups and the address the script actually targets. Don't start changing the robot address to compensate for a laptop routing problem.
5分What did the route comparison show? Also check whether the application binds to a particular local adapter (some wrappers do). Two addresses in one subnet are a clue, not a diagnosis.
-7分Agreed. I jumped from a plausible cause to a fix too quickly. The route output and application target are the useful evidence here.
15分IT found our wrapper bound to the dock adapter. Corrected that setting; docked and undocked status reads now work. Robot untouched.
16分此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .