How to get the number of active construction bots of a certain quality?

[mooklepticon]

I know I can get the total number of bots available from a roboport. Signals W, X, Y, and Z.

How do I get how many rare construction bots I have? For example, let's say I want to recycle any bots over 100. I tried having the roboport ask for bots to station there and that worked. I can withdraw them with an inserter, but I want to logic that inserter. I want to leave a reserve of 100 bots, and then recycle the rest. I can't get how many bots I have active, only how many bots are passive in storage. Connecting via circuit doesn't give active bot stats.

[mmmPI]

I think this won't be possible ingame without seriously over-engineering the solution. The roboport signals you get from "reading" the available robots don't distinguish quality. You would need to remove them "all" and sort in the chest, and re-add 100 rare.

[teatime11]

How about something like this:

0eNrNVVFunDAQvct8m2iBZatFak/RnypaIQOziSWwydimXa04QO/Rk/UkHUMCSkKTVbYf1f6A7Xlv3nse9gxl47EjpR3kZ1CV0Rby2zNYdadlE9a0bBFyIFOazpCDQYDSNf6APB4OAlA75RROVePLqdC+LZH4gHiqPkrrIqUtkuMNAZ2xXGV0IAhIWXqTCThBHsXJTcYUtSKsphNxIoD7cmSaosR72StDoa5SVHnlCtSybLCG3JFHMS9zST1zHBVZVyyi3KkLbfWKnOeVuc/pRPQtqAxeOBmMiTeb8Np2kqQL5PAFBj5xVA3LmaQ/eTJDNeZOWaeqKDjnmOKBmdid4KUkhBeIv3/+guCnt1jMuEHRIF75mswknbRW9Rh1ZHpVI0XVPVq3ZvD2mcEroKl4FfUKTPwIEg/roRDKuhgVF2yemzXwxoPn1hZtfMemhF/691FXtaF2zPKZr5/HBT/FGGQ/Qi4ejjmTH3u5Gja9pFOvGatlVy8E3V7a62XAB/6tXICFxbLgJmpk2709qpv1m5R9ZOzj/2Dsv/6DsX8noWtHfzcTtVgr30bYsGHE16wzDb49+H+J69NVX5OQW2j+OycXLLmNRSJSkRzE+JTxE+8qhy0TLH82AnqWOUJmu2S/3e+zLMl2aRIPwx8Ymzcj

Copy blueprint

[mooklepticon]

How about something like this:

Almost! It's not exactly what I'm after, but it's damn close. This will withdraw bots, qual < rare, if there are >100 bots in the network. I'd really like to be able to withdraw if there are >100 of a specific quality. Say there are 99 normal and 102 uncommon. I want to grab those 2 uncommons and recycle them (to possibly get rare materials). I want to leave the 100 normals alone until there's 100 of them.

This may not be the most ideal setup, but essentially it'll keep that reserve of each quality, upcycling any extras >100 of each quality in the system.

[robot256]

It's an interesting experiment, but what use does it have? If you have extra epic robots, why do you need a reserve of rare robots *in the network*? You can always keep them in storage if you want something to kickstart quality production again.

But your original post was correct, the information you want is simply not available in the circuit network and never will be. It could be extracted via a mod script and sent to a combinator that way.

[teatime11]

In that case, how about manually set up requested specific quality of bots in Robotport(Leave Normal Quality). And set for example Uncommoned and Rare Logictis bot on inserter to pull into box.

Personally I'll keep requesting lesser quality bot until it got 600 or so and put them onto upscaling Build. Then put desire quality bot into Roboport.
viewtopic.php?t=124099

[mooklepticon]

But your original post was correct, the information you want is simply not available in the circuit network and never will be.

Wait,how do you know it never will be?

[robot256]

But your original post was correct, the information you want is simply not available in the circuit network and never will be.

Wait,how do you know it never will be?

Sorry, that was an assumption on my part based on how the current behavior (number of bots + requesting certain qualities to a roboport for extraction) covers all the reasonable use cases. And the performance cost of counting up how many bots of each quality, and adding another option on the already crowded roboport GUI would seem to discourage its addition.

[mooklepticon]

It's an interesting experiment, but what use does it have? If you have extra epic robots, why do you need a reserve of rare robots *in the network*?

Thinking more on this, you're probably right. I was thinking that I needed to keep x of each type. Idk why I'm stuck on that. Why can't I recycle anything under leggo, as long as I have enough bots?

[Tertius]

You probably want to gradually phase out old bots and replace them with higher quality bots as they become available.
I would do it like this:
- request 10 of the old quality bots into some roboport
- read robot statistics from that roboport. We're interested in Y and T.
- if Y >= 1000 (or whatever robot count you want), extract 1 logistics bot of the old quality from the roboport with a filtered inserter. (inserter activation condition: Y>=1000). This brings the number down to 999.
- request 10 of the new quality logistics bots into a requester chest
- move 1 bot from the requester chest into the roboport if Y < 1000 (inserter activation condition Y < 1000).

The same with T and construction bots.

This way 1 old bot is extracted, then immediately replaced with a new bot. The process pauses while a new bot is not yet available.

[mooklepticon]

You probably want to gradually phase out old bots and replace them with higher quality bots as they become available.
I would do it like this:
- request 10 of the old quality bots into some roboport
- read robot statistics from that roboport. We're interested in Y and T.
- if Y >= 1000 (or whatever robot count you want), extract 1 logistics bot of the old quality from the roboport with a filtered inserter. (inserter activation condition: Y>=1000). This brings the number down to 999.
- request 10 of the new quality logistics bots into a requester chest
- move 1 bot from the requester chest into the roboport if Y < 1000 (inserter activation condition Y < 1000).

The same with T and construction bots.

This way 1 old bot is extracted, then immediately replaced with a new bot. The process pauses while a new bot is not yet available.

I did something similar to this.

1. I have a port that stocks 10 of each bot, Epic and below.
2. I pull out bots, if there are more than 500 available, on to a belt.
3. Generally, because of belt mechanics, the lowest quality ones are prioritized in ascending order. (The normals are at the beginning of the belt and the epic at the end, so the epic has a tough time placing them.)
4. I put them in a chest.
5. Inserter A waits until there are 20 bots in the chest.
6. Once >20, it grabs the lowest quality one (calculated by a series of decider combinators and set filters) into another chest, for manual review.
7. Inserter B *also* waits until there are 20 bots in the chest.
8. Once >20, it grabs the highest quality one and puts it back into the system.
9. Once there are more than 200 bots in the manual review chest, an alarm flashes telling me to review.
10. I manually put the normals into a recycler and the uncommon and above back into the system.

I think I can further optimize the setup so I don't have the manual recycling, but I want to make sure.

That limit of 20 for evaluation is still under consideration. I used to do 10, but it was getting a lot of uncommons in the review chest. I'm trying 20. The larger the pool, the less errors I'll have, but the more inventory I'll stock.

I created 2 of these systems, one for each type of bot.

[Lighthouse]

it grabs the lowest quality one (calculated by a series of decider combinators and set filters) into another chest,

This can be done with a single Selector Combinator (Quality Transfer) + connect 1 Constant Combinator (set with Signal of bot in scope, Q1, strengh 1).

[mooklepticon]

This can be done with a single Selector Combinator (Quality Transfer) + connect 1 Constant Combinator (set with Signal of bot in scope, Q1, strengh 1).

How does that prioritize taking the lowest quality items first?

[Lighthouse]

This can be done with a single Selector Combinator (Quality Transfer) + connect 1 Constant Combinator (set with Signal of bot in scope, Q1, strengh 1).

How does that prioritize taking the lowest quality items first?

Aww, should have tested before posting - sry, that one only gives the highest available quality, not the lowest. I stand corrected and proclaim the opposite.