Our FR5 read-only connection check times out on the workshop laptop, while another laptop has worked; ping is intermittent and the successful setup was not recorded, so I want to compare the destination, route and service access before the controller gets blamed by elimination.
Are both checks using the same controller address and physical connection? Start by making those details explicit. It is easy for 'the other laptop works' to leave out a different socket or saved address.
The scripts contain the same address, but the successful laptop was connected through a different bench socket; we have not yet repeated the comparison at one known connection.
That would be a useful comparison. Keep the application environment and network settings from each laptop too, so you know which differences remain after using the same connection.
Who has the working laptop now? I'd get its settings written down before it disappears back into somebody's bag and becomes a legend about a machine that once connected.
The controls technician has it available for the comparison; its address, mask and routes are now recorded alongside the interpreter and SDK used for the successful check.
At the same bench connection, the second laptop still works and the workshop laptop still times out; our network administrator is comparing the route selected for the controller address.
We have not; the administrator found a second adapter with an overlapping network on the workshop laptop, and is checking the route against the intended bench configuration.
Have the administrator document the corrected configuration for the people who use that laptop. A temporary fix at the bench can disappear when it returns to its usual network and comes back again.
And use the ordinary shortcut for that check. I've had a laptop work beautifully in the developer's terminal and fail from the icon everyone else was told to click.
The corrected route restored the read-only service check; we also tested the normal shortcut and recorded the working setup, so the result covers the launch method our technicians use.
Give that setup record an owner. Whoever manages the laptop needs to know these settings matter before the next rebuild or network change replaces them.
It has remained consistent in the checks since the correction, and the service request also succeeds; the administrator has taken ownership of the bench network configuration.