I want to do the probe_config_set callback against a robot that has an invalid IP but the nimbus.request seems to require the UIM address which will use the broken IP. Is there a way to specify the IP like in a PU?
pu -u <admin_account> -p <password> -H <ip_address_of_robot> -P 48000 probe_config_set controller controller robotip <ip_address_of_robot> "" ""
There was an enhancement request for just this sort of functionality the other day.
I think though the short answer would be no because IP address is far from a unique address - consider how many robots there might be out there with the legitimate address of 192.168.1.1.
It does seem to happen pretty frequently that the robot binds to 127.0.0.1 or 169.254.x.x when it shouldn't.
Maybe more to the point of the ask, it would be really nice to be able to prevent the controller from ever binding to one of these unusable addresses unless configured to do so specifically.