The Viper probe droid, commonly referred to as the probot or Imperial probe droid, was a deep-space exploration and reconnaissance probe droid produced by Arakyd Industries. The Viper model was based on the success of Galalloy Industries' early probe droids. The design of the probot also relied heavily on the work of Viper Sensor Intelligence Systems, a corporation acquired by Arakyd during the Clone Wars. Though they were used almost exclusively by the military, they were considered class two exploration droids.
- "'Fraid there's not much left."
"What was it?"
"A droid of some kind. I didn't hit it that hard. It must've had a self-destruct."
- ―Han Solo and Princess Leia
The lightly-armored Viper droid measured 1.6 meters in height with six manipulator arms extending from a central pod and several retractable sensor arms for gathering samples. High resolution receivers and sensors covered the domed head—including motion, acoustic, sonic, and seismic sensors, a radiation meter, magnetic imager, and holocamera. It had an atmosphere sensor capable of determining a planet's atmosphere class within one half-hour. It moved on a repulsorlift generator which was equipped to operate over any terrain. One of the arms was high-torque, and the droid was equipped with a floodlight on its head. In addition, when making transmissions, the probe droid emitted a audio encrypted imperial computer code set of an unknown serial number.
Information was relayed back to its superiors via a high-frequency HoloNet transceiver. Its repulsorlift engines carried the droid across terrain at up to 40 km/h, while the arms gathered samples. Vipers were delivered to their targets through single-use custom built hyperspace pods. They were commonly deployed along the perimeters of key strategic star systems and hyperlanes to act as automated guardians.
- "Go and report. You have much to see. Burn brightly."
- ―IG-88, to the last Viper probe droid constructed on Mechis III
Arakyd probe droids were originally designed for use by the Galactic Republic in survey and exploration duty, but when the Republic was transformed into the Galactic Empire, Arakyd modified their probots with military-level sensors and equipment, and marketed them as Viper probe droids. This was not the first time Arakyd probots had been upgraded for warfare, however, as the Confederacy of Independent Systems had employed a number of upgraded probots during the invasion of Kashyyyk during the Clone Wars. Viper probots in service with the Empire were upgraded under the direct supervision of Darth Vader, and featured a blaster cannon, a self-destruct mechanism, and, in some cases, deflector shields.
Many thousands of the Imperial Viper probe droids were manufactured on Mechis III, and were in production when the rogue assassin droid IG-88 took control of the planet's automated factories. IG-88 included a secondary set of programming into the Viper droids to relay any obtained intelligence back to Mechis III, as well as to the Empire. Thus, they simultaneously served as the eyes and ears of the Droid Revolution. The Imperial Intelligence's Analysis Bureau also used them as remote surveillance droids posted largely in the Outer Rim Territories. In conflict zones, probots often worked alongside the Imperial Navy to monitor traffic and provide early warnings of attack. They could also be programmed to engage pursuit mode, whereupon the Viper would track an enemy vessel and report back on its location and destination.[source?]
Arakyd's success with the military model of the Viper yielded the C-Viper probe droid variant designed for planetary law enforcement organizations, the Infiltrator probe droid for sabotage missions, and the Hunter-Killer probot.[source?]
Six months after the Battle of Yavin, the Galactic Empire sent a detachment of probe droids to root out Rebel Commander Luke Skywalker. They were destroyed by Skywalker and Rogue Squadron. Probe droids were also used to scout ahead for Imperial strike forces, including during the Reytha campaign and the battle at Corellia, or were sent on search missions like at Chorax.
Locating Echo BaseEdit
Following the Battle of Yavin, the Empire committed thousands of these modified probe droids to scour the galaxy for hidden Alliance to Restore the Republic bases, specifically the Alliance High Command headquarters. They even went as far as to provide bounty hunters with remote request devices to search out targets moving from planet to planet.[source?]
It was an Arakyd Viper, launched from the Imperial II-class Star Destroyer Stalker, that landed on the ice planet Hoth and discovered the Rebellion's Echo Base. Upon landing on the frozen world, the probe droid appeared to the casual onlooker, and even the base's sensor readings, as one of many meteorites streaking to Hoth's surface. During a routine patrol of the Hoth wastes, Luke Skywalker intended to inspect the crash site, but was attacked by a wampa ice creature, and never learned what had really crashed to the ground. Thus, the Hoth probe droid was free to continue on its programmed mission.
Immediately upon emerging from its hyperspace pod, the probe detected a faint comm signal on non-Imperial bandwidths. This indicated to the droid the presence of an unregistered, and possibly Rebel, settlement. Since it had not yet gathered enough conclusive evidence to report, the droid moved away from the nearby signal in order that it might avoid contact until such time as self-preservation no longer became necessary.
Soon after moving away from its first contact, the probe droid vectored in on the detected signal's probable destination point, triangulating from its last known position. A long time passed where the droid made no contact with the signal whatsoever, so it continued to search. During the night blizzard that threatened the lives of Skywalker and Han Solo, the probe detected and destroyed a wampa with its powerful blaster cannon. Only with the most advanced Imperial sensor technology was the probe able to detect a wampa in a blizzard whiteout. As the blizzard raged into the night, the probe activated its modified power-intensive particle shield to protect it from the thick snow hazard.
In the early hours of the next morning, the probe ceased operation entirely, shunting its energy to its shield. The droid reappeared when the sun rose, cresting the rise of a snow bank in Echo Base's Zone 12. There, it detected the presence of a large deflector shield generator. It immediately began audio-visual recording of the contact. Following its programming, the droid then beamed, on omnisignal unicode, a transmission via its HoloNet transceiver concerning its find to Vader's personal flagship, the Star Dreadnought Executor. This information was privately received simultaneously by IG-88 back on Mechis III. Vader decided from this information that the Hoth system was indeed the location of the Rebel base, and he ordered his Death Squadron there in preparation of a full-scale ground assault.
With the initial contact reported, the probe continued on its mission. It proceeded to meticulously map out the Echo Base defenses, including the surrounding trenches, artillery emplacements, and even the size, model, and location of the v-150 anti-orbital ion cannon, as well as observing troop movements and positions. This information was received by General Maximilian Veers. He and his commanders used this invaluable tactical information to plan the attack, a testament to the Empire's incredible preparedness during the Battle of Hoth.
Before the probe had a chance to implement its "sabotage and disruption" programming, the Echo Base command center received a transmission from Echo Station 3-8. The scout outpost had detected a metal object skimming through the icy wastes. The probe droid was discovered. The probe then proceeded to completely destroy the outpost and the scout within it with its blaster, turning it into a smoldering ruin. Solo and the Wookiee Chewbacca were dispatched to deal with the spy machine. The probe detected the approach of its two enemy assailants, but it was no match for them. The probe was soon trapped despite its evasive maneuvers. After a quick game of "decoy," Solo blasted the confused probe. Solo's shots were only meant to disable the probe's motor functions, intending to take the droid intact, but its override programming kicked in and the probe immediately self-destructed.
Although the probe attempted to destroy itself, its self-destruct programming had apparently been at least marginally affected by either the frigid Hoth temperatures or the damage that was inflicted on it upon entering the Hoth system. The probe was almost destroyed entirely, though enough of it was left for Solo to retrieve and bring back to the base for memory scan. The base technicians and Alliance historian Voren Na'al were able to piece together some of the probe's memory circuits and learn many details concerning its particular mission experiences. Na'al used much of this data to help compile his subsequent reports on the history of the Rebellion during this period. Other probe droids were used during the actual Battle to locate Rebel installations.
Behind the scenesEdit
One of artist Jean "Moebius" Giraud's designs was used for the probe droid in The Empire Strikes Back. Later Star Wars films also share many visual characteristics with Giraud's work, particularly the depiction of Coruscant.
The film THX 1138 features numerous radio voices that sound strikingly similar to and likely influenced the strange electronic voice of the probe droid in Empire.
Star Wars: Rebellion: Prima's Official Strategy Guide explains that Imperial probe droids are equipped with small hyperdrives, enabling them to scout the galaxy without needing to be deployed by capital ships, for use in the video game Star Wars: Rebellion. This serves as the game-mechanics explanation for the absence of the Predator I Probe-Mate jump pod in Star Wars: Rebellion, which is the Viper probe droid's mode of hyperspace transportation.
Probe droids also appear in the 2006 video game LEGO Star Wars II: The Original Trilogy, a humorous take on the original trilogy in LEGO form. The game is also included in its 2007 compilation re-release.
It should be noted that the main image used on this article is a picture of the damaged model from the Lucasfilm Archives, with its right antenna bent slightly to the left.
- LEGO Star Wars: The Complete Saga
- LEGO Star Wars II: The Original Trilogy
- The Return of Tag & Bink: Special Edition
Notes and referencesEdit
- ↑ 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 1.13 1.14 1.15 1.16 1.17 1.18 1.19 1.20 1.21 1.22 1.23 1.24 1.25 1.26 1.27 1.28 Galaxy Guide 3: The Empire Strikes Back
- ↑ 2.0 2.1 2.2 2.3 Therefore I Am: The Tale of IG-88
- ↑ 3.0 3.1 Star Wars: Jedi Knight: Jedi Academy
- ↑ Star Wars: Rogue Squadron II: Rogue Leader: The Official Nintendo Player's Guide
- ↑ 5.0 5.1 5.2 Star Wars: Galactic Battlegrounds
- ↑ Deep Forest
- ↑ 7.0 7.1 Star Wars: Rogue Squadron
- ↑ Star Wars: Behind the Magic
- ↑ 9.0 9.1 Star Wars Episode V: The Empire Strikes Back novelization