SkiCarver wrote: ↑
Fri Jun 07, 2019 6:11 am
How can I find out how many robots are waiting for recharge? I would like to be able to check on this to determine if I need to place more robotports, but I cannot find a way to do it without coming across a robotport with a circle of robots.
Many thanks in anticipation.
As others have said, I don't believe it can be done globally. But it is possible to see exact numbers on a per roboport basis - rather than just relying on counting clouds of bots. You can get extra info through the UI, by enabling extra tooltip debug info:
EDIT to add: The info below appears to only apply to 0.17. 0.16.51 doesn't have the 'show-debug-info-in-tooltips' setting, so I don't know a way to get this info in 0.16.51 - it seems likely that it's not possible. So if you're playing on 0.16, you probably have to upgrade to see this info.
- Press F4 to open the Debug settings menu
- Enable 'show-debug-info-in-tooltips'
- Now hover over a given Roboport to get its tooltip. You will see there is some extra info in the tooltip. The new debug fields are marked with a blue dot:
The debug fields relevant to this discussion are:
- charging: will be 0-4
- waiting to charge: the number clustered around, waiting for an empty charge spot
- robots to station: how many bots are scheduled to enter this roboport, ie. they have finished their job. They need to recharge before they can do this.
- logistic and construction robots stationed: the number of idle bots in the inventory of this roboport; this is not new info, as it's also shown in the normal tooltip using item icons.
I have found this debug information to be quite interesting while I'm doing tests on optimal bot-based smelting and other designs.
When analysing this info It's important, in my view, to consider not only 'waiting to charge' but also 'robots to station'. It may seem bad if 'waiting to charge' is high, however if 'robots to station' is also high, it may well be fine. Bots recharge when they have finished their task, right before they go to the inventory of a roboport. So having lots of bots waiting to charge is not necessarily a problem, if they are only waiting to then go into the roboport inventory.
I believe that the ideal bot network configuration is to achieve a state where bots only recharge when they have finished their job. In that situation having high 'waiting to charge' numbers is usually fine. This requires that you have more bots than are being actively used for the given task, so that every new logistic job will always go to an idle bot, allowing the already-active bots to complete their task, recharge, and go to sit in a roboport. If this is achieved, bot travel times are never extended by bots charging and waiting to charge.