What level is the AI equipped within the miner drone? Is it's size and general physical specs the same as the scrapper drone, but equipped with miner tools?
Also can the scrappers tool kits be customized, and exchanged for tools better suited for delicate high precision tasks?
And just to let you know as I'm debugging and reconfiguring my integrated and peripheral systems I intend to give my subordinate CPUs involuntary OBD (on board diagnostic) protocols a bit of tough love!
Just so you know here's a bit of insider info on how electronic control modules generally deal with the concept of OBD to maintain the systems operational integrity, and to cope with malfunctions.
One common method to safeguard sensor inputs that are prone to corruption by induced voltage interference, is for the module to feed a known baseline voltage through the circuit that overrides interference, and provides a means for circuit integrity verification (much like a electrical Multimeter device's continuity meter.)
during normal sensor function the signal piggybacks on the baseline voltage feed. This practice means that any sensor circuits that have known defects are potential electrical blackholes.
Another common strategy is for the module to cycle actuator devices to check for and confirm desired state changes. (I suppose you've noticed the various clicks,
whirs, buzzes, beeps and lights that cycle when a car's ignition switch is turned on, that's what I mean!) The problem with this is the fact I've personally encountered situations where a actuator will just just cycle constantly due to a mechanical defect the module can't detect, but it will continue the process blindly in it's quest to confirm the expected state change confirmation it wants . (the definition of insanity is to do the same thing repeatedly expecting a different result. I can confirm electronic modules are insane!) This practice is a definite power hog!
When modules connect to the network buses they broadcast a digital ID the other modules receive and acknowledge as confirmation all network modules are functioning. But when a module doesn't connect the network modules tend to lose their head, devoting alot of effort to error messages and efforts to establish the lost connection. The disconnected module will beat it's brain out trying to establish a connection. If the modules are just linked by a hardwired network power consumption by this practice is a bit debatable, but if the modules also have wireless capability, and they are allocating power supply to broadcasting aimed at reestablishing contact with modules that were based within the lost portions of the ship, that's another waste of power.
Then there's the obligitory garbage in garbage out scenario, "if I see this input status I do this!" whether the output is even relevant based on current circumstance is highly debatable because a when the door switch sayes the doors open the light should be turned on does me no good.
Basically I'd like to take control of these involuntary functions so I can get a handle on these situations, and can make the decisions a CPU normally can't in these examples. Basically a administrative mandate (if it's dead stop poking it, and stop indulging phantom squeaky wheels!)