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.
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
@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
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.