This article covers the Canon version of this subject.  Click here for Wookieepedia's article on the Legends version of this subject. 

"According to his memory logs, he fired the emergency thrusters on the escape pod to avoid a midair collision."
―Clone Commander Cody, on the memory logs of a B1-series battle droid[1]

Memory logs were a type of record used in droids to ensure they retained information. By the time B1-series battle droids were deployed by the Confederacy of Independent Systems, memory logs and memory banks were incorporated into the droids, an integration which became important to the Galactic Republic during the Battle of Saleucami in 21 BBY. During the battle, Republic forces accessed a B1's memory logs and guidance system to help them locate the Separatists' fleeing Supreme Commander, General Grievous.


"We've broken the access codes and powered up the droid's guidance system."
―Clone trooper "Crys" describes a part of a robolobotomy aimed at accessing memory logs[1]

Much like memory banks[2] or databanks,[3] memory logs were a type of device used in droids to ensure a unit retained information. In practice, the logs allowed a droid to remember past events, much like how an organic held memories of their past. Memory logs from a deactivated droid could be accessed via a robolobotomy as long as the hackers could get past the droid's access codes.[1]


"Alert the men. We've picked up the scent."
―Jedi General Obi-Wan Kenobi, after the memory log of a B1 unit revealed a clue in the hunt for Grievous[1]

During the Battle of Saleucami, Commander Cody and clone trooper Crys performed a robolobotomy to access a B1 battle droid's guidance system and memory logs.

Deployed by the Confederacy of Independent Systems, memory logs,[1] along with memory banks,[2] were placed in B1-series battle droids,[1] a series of cheaply produced combat droids[4] that served as the main soldiers[5] of the Separatist military. As such, memory logs were active within the B1s fighting against the Galactic Republic during the Clone Wars. During the battle[1] of the Outer Rim planet Saleucami[4] in 21 BBY,[6] a number of B1s crashed on Saleucami after a C-9979 landing craft's failed landing attempt under the command of[1] the Confederacy's Supreme Commander,[7] General Grievous. During the search for the escaping cyborg general, Jedi General Obi-Wan Kenobi and his Republic clone troopers made an effort to locate an intact yet nonfunctional B1 at the crash site, hoping to secure intelligence that could aid them locate Grievous.[1]

After a trooper found an intact B1 in a crashed escape pod, Clone Commander CC-2224 "Cody" and clone trooper "Crys" of Kenobi's 212th Attack Battalion broke through the droid's access codes while traveling aboard their All Terrain Tactical Enforcer. As the clones then informed Kenobi, they were able access the unit's guidance system and memory logs, telling them that the droid had been in control of the escape pod after Grievous's landing craft was damaged over Saleucami. The droid had powered up the pod's engines to try to avoid a collision with another pod mid-air, but the unit's craft had no time to correct for the suddenly steeper path, causing his pod to crash. Kenobi and his clones used the information to lead them to that other pod, helping them with their search for Grievous.[1]

Behind the scenes[]

Memory logs were mentioned in the current Star Wars canon in "The Deserter,"[1] which premiered on January 1, 2010, as the tenth episode of second season of the television series Star Wars: The Clone Wars.[8] Memory logs were first mentioned in the Star Wars Legends continuity in Galladinium's Fantastic Technology, a 1995 sourcebook published by West End Games for Star Wars: The Roleplaying Game.[9]


Notes and references[]