“MOB…Mobility
Obstruction Barrier”
In this post, I want to examine a device and
technique that nanotroopers use to exercise position and mobility control over
moving objects, like enemy soldiers or prisoners.
It’s called MOB.
And it is a part of the normal kit for any ANAD Detachment. Every nanotrooper carries a MOB canister. Let’s take a closer look at this essential
piece of mission gear.
Physical
Description:
A Mobility Obstruction Barrier is a dense swarm of
specially configured nano-robotic elements designed to link into a tight,
programmable, semi-autonomous mesh-like barrier. MOB systems can be used to enclose almost any
desired area or volume, from fractions of an inch to kilometers in
diameter. There are practical limits to
how well extremely large MOB nets can be deployed and controlled. But, as an example, in one of The Tales of the Quantum Corps, an
effort is made to design a MOB net for an entire island, to quarantine one of
the bad guys.
MOB nets are stored and deployed from
canisters. Un-deployed, MOB is just a
few bots hiding out in some kind of containment vessel inside the
canister. The canister contains the containment
capsule and all communications elements needed to command and control the MOB
bots. It also contains a baseline amount
of atom feedstock, so that when MOB is deployed, it has something to work
with.
The canister has controls on a small thumbpad at the
top for initializing, priming and discharging the bots. Configuration templates are preloaded and
because the MOB master bot does not normally have a huge processor, it’s
limited in how many different configs it can store. Here’s one depiction of an individual MOB bot
configured to link up with its brothers.
Capabilities:
MOB systems have some unique capabilities. As the name suggests, the primary purposes of
MOB are to immobilize recalcitrant personnel and to enclose and/or protect
specified areas and volumes.
One of the more interesting capabilities of a MOB
system comes from the nature of what it is...a big swarm of nanobots. Like any ANAD-style nanobot, MOB bots can
assume many different configurations, though (as mentioned), their processors
don’t match that of a true combat-capable ANAD.
MOB nets are programmable, meaning they can be changed in config on the
fly, while in use. Their immobilizing
effects are likewise programmable. MOB
systems can form any kind of barrier from a loose netting to a tightly
constricting cocoon-like enclosure. They
can be programmed to literally squeeze the life out of a contained target, or
to apply pressure in graded steps, depending on selected parameters…like how
hard the target tries to escape. In
other words, the degree of immobilization can be programmed.
MOB systems are also semi-autonomous. This means that once discharged, the MOB
master bots can travel stealthily on propulsors with a small force of
obstruction bots, reach its intended target, then replicate at maximum rate and
envelope the target in a matter of a few minutes. The MOB system can be designed to stun, or
detain its target in a programmable fashion while the mesh is forming, even up
to rendering the target unconscious (though this is rare and requires specially
configured MOB masters).
A special MOB configuration called Clampdown is used when absolute
immobility or restraint is required.
When this configuration is selected, the MOB master executes the command
and envelopes the target in a highly restrictive, tightly compressed mesh,
making it difficult for the poor souls affected even to breathe. The Clampdown can actually kill if the
pressure isn’t reduced after a period of time.
Tactical
Employment:
All nanotroopers carry MOB canisters and all are
trained in the use, deployment and release of MOB nets in tactical
situations.
A typical use of MOB systems would be to restrain
and immobilize enemy combatants who have either been defeated in battle and
surrendered or who cannot be assaulted in any other way. The stealthy and autonomous nature of MOB
allows it to be used for surprise effect, even for deception operations, to
distract an enemy force from the main line of engagement.
MOB systems are sometimes used against enemy bot
swarms, but remember that MOB bots normally have limited processor, limited
maneuvering, and very limited effector complements. Thus they are typically used to engage
non-nanobotic targets, like human beings, dangerous animals, runaway vehicles,
etc, that can’t fight back at the atomic level.
Using a MOB system to try and engage a fully-capable ANAD combat nanobot
is like trying to stop a charging tiger with a spoon. It doesn’t work.
One tactic that Quantum Corps has developed is the
ability to gang multiple MOB discharges into one larger restraining mesh. This takes some preliminary programming, for
one MOB swarm to accept and interlink with another, but it can be done. Gang MOB can be used to secure especially
large targets, or enclose larger than normal areas or volumes.
Because MOB systems are barebones yet
semi-autonomous ANAD swarms, they can also be configured and programmed to
discharge at a set time interval, even multiple time intervals. Let’s say you’re a commander of an ANAD
platoon. You suspect a house you’re
reconnoitering contains some very bad people but you don’t have time or manpower
to stake out the place and catch any baddies trying to escape. Deploy one of more MOB masters into position
and program them to deploy on sensing a human-size mass and heat load. When the baddies open the door and try to
escape, or even leave quietly, blam! MOB drops on top of them and they’re
caught. In this case, MOB was deployed,
but replication and containment were set to execute on a given sensor input(s).
Neat, huh?
Your own autonomous, semi-intelligent jail cell. And it fits inside a canister too.
The next blog post for QC Times will come on August 1, 2016. This post will cover another piece of mission
gear that nanotroopers always carry…camou-fog….programmable
swarms that scoop and manipulate photons in such a way as to make you and your
buddies invisible or at least blend you into the background.
See you in August.
Phil B.
No comments:
Post a Comment