Our cell is unavailable, so I'm working offline on read-only controller reporting for Fairino FR5 in a fixture inspection station, with a fixture-mounted coupon as a reference. The existing SDK mock returns true from every method.
The screen looks happy, but that doesn't catch interface mistakes. I want a useful software substitute without claiming it simulates the physical robot.
Fairino FR5: An offline substitute that can actually fail
MeiAli0255 · 2026年4月27日 12:56 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
7 条回复
回复 MeiAli0255
Have you saved a documented SDK success and error response for the interface your screen uses? Start with those
23分Yes. Replaying our saved error response reproduces a parser bug. The always-true mock sailed straight past it, naturally.
13分回复 MeiAli0255
Use a small substitute implementing only your required methods, matching the saved response contracts and rejecting unexpected calls. That should keep the run contained offline
10分Contained how? A strict mock doesn't stop startup code constructing a real client somewhere else.
22分@JamieChan1078 You're right. I blurred two checks. The strict interface catches wrong calls; offline startup also needs to exclude the real client and reject controller endpoint configuration
16分I've settled what this mock is for: checking our documented interface with explicit success and error cases. I'll count it ready only when those checks pass and the offline run attempts no controller connection.
17分回复 MeiAli0255
That scope is useful, and your readiness condition covers both contract behaviour and staying offline
21分