The URSim boot sequence is much faster than that of a real robot: it transitions from Power-off to Idle in 1s or less, and similarly from Idle to Running, where a real bot can take ~8-15s for these transitions. This speed-up is usually helpful (saves time), but is it possible to slow it down so that I can test my program that connects over the network to a bot? I want to make sure my program gets to see the intermediate modes (Power-on, Booting) and something representing a “real” sequence timing.
Hi @lxop
do you have reaction / workflow connected to the status change?
As far as I know, it is not possible to delay this procedure.
/Stefan
I just want to make sure I’m correctly handling those statuses if the program sees them. That’s a shame, any chance it could be added to the URSim in a future version? Just having it exposed in a config file would be perfectly adequate.
Hello @lxop
let me check for that, but I would not get my hopes too high atm
Sorry for that.
In case you just want to test it once, getting access to a real robot may be the most direct workaround.
/Stefan