Memory bank

"Damaged, but still possibly functional. I may be able to access its memory banks, see if I can salvage any information."

―Rissa Mano, examining a downed B1-series battle droid^[7]

Memory banks, also known as memory cores or memory logs, were devices used by machines, including starships and droids, to store knowledge.

Description[]

"He says he's found something in your droid's forbidden memory bank. Words, translated from Sith."

―Zorii Bliss, speaking for Babu Frik^[6]

Much like databanks,^[8] memory banks,^[7] also known as memory cores^[9] or memory logs, were a type of device used in droids^[1] and starships^[10] to retain information. For droids, memory bank 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]

History[]

"We've broken the access codes and powered up the droid's guidance system."
"According to his memory logs, he fired the emergency thrusters on the escape pod to avoid a midair collision."

―Clones Crys and Cody, on the memory logs of a B1-series battle droid^[1]

Hacking-into-a-B1 — 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 banks were placed in B1-series battle droids,^[7] a series of cheaply produced combat droids^[11] that served as the main soldiers^[12] 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^[11] in 21 BBY,^[13] 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,^[14] 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 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]

The protocol droid C-3PO had a memory bank.^[4] On one occasion, he used it to store banking records linking the Amaxine warriors and Rinnrivin Di's cartel to a mysterious entity that threatened the New Republic.^[5]

This article is a stub about technology. You can help Wookieepedia by expanding it.

Behind the scenes[]

A memory bank was first mentioned in the current Star Wars canon in Star Wars: Episode V The Empire Strikes Back.^[4] The term "memory log" was first used in 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. The episode guide used the term "memory banks" instead, thereby confirming a memory log and memory bank were the same device.^[15]