Engineers tucking robots in for the night

The machines CIRAS engineers grew up watching are taking shape in their robotics and AI lab. The night-shift scenes are imagined.

At 2:13 a.m., an engineer at CIRAS disconnected the lab from the internet. R2-D2 delivered a tray of screws. C-3PO continued explaining why the screws ought to have been sorted by thread pitch. In the driving simulator, KITT slowed for a cyclist. The engineer’s weather app, meanwhile, lost all confidence in the existence of rain.

The people building these machines grew up with Star Wars and Knight Rider. Today, in the CIRAS datacenter, they’re building their own R2-D2 and C-3PO assistants and developing a KITT-inspired AI designed to make driving decisions onboard. The childhood dream now has a parts list.

Three engineers, three robots and one screw

The droids and the car that started it

When Star Wars opened in 1977, audiences met two machines with very different ideas about a good day. Princess Leia hid the Death Star plans in the memory of R2-D2, a compact starship mechanic. C-3PO, a gold-plated protocol droid, specialized in communication and etiquette. He also had a gift for explaining the seriousness of a situation to people already running from it.

Kenny Baker gave R2 his physical personality from inside the droid’s shell. Anthony Daniels made Threepio’s precision audible in every anxious syllable. Watching them together, you could learn to read a tilt of R2’s dome as quickly as a line of dialogue. That’s a lesson for anyone building a robot that has to share a room with people.

Then came NBC’s Knight Rider in 1982. KITT, short for Knight Industries Two Thousand, was an intelligent Pontiac Firebird Trans Am that drove, talked, and advised David Hasselhoff’s Michael Knight in the impeccably composed voice of William Daniels. For a child watching at home, the idea that a car could hold up its end of a conversation was nearly as exciting as the car itself.

Three engineers at a robot test bench at night

What working offline actually takes

Offline AI runs its essential computations locally, on the robot, in the car, or on a computer inside the building. Autonomy is the ability to sense, decide, and act within defined limits. A voice model can recognize “Bring me my glasses” offline. A mobile assistant also has to find the glasses, navigate around the chair, and ask for help if it can’t find them. Each step needs its software, data, and permissions to be available locally. An offline speech model can do little for a robot whose controls depend on signing in to a remote service every time it starts.

Onboard computing removes the wait for a reply from a remote server. The processing still takes time, and the device has to deliver acceptable response times within its limits for memory, battery power, and heat. A useful lab test starts with the internet disconnected and the device freshly rebooted. Can it start, locate itself, and finish a task? How long does it take after an hour of running? The second question matters to a robot with a busy afternoon.

For a KITT-inspired driving system, independence comes with a defined set of conditions in which the software is designed to operate. Engineers call that the operational design domain. Road type, speed, weather, and visibility can all matter. A simulator can replay the same cyclist crossing with glare or with a parked van blocking the view, then measure when the system detects the cyclist and how it responds. The test also asks what happens when the software can no longer operate within its limits and has to fall back to a safer state. C-3PO would like the cyclist to follow the script. The cyclist has declined.

A home that can mind its own business

A future care robot should be able to give a scheduled reminder, guide someone through a familiar routine, or operate a locally connected light when broadband goes down. Contacting a caregiver elsewhere still requires a working communication path. If the robot can’t place the call, the person in the room should be able to tell. The robot should also know when a decision belongs to that person. “Would you like me to call someone?” is a complete question, even for Threepio.

Local processing lets the robot handle a conversation without sending the room’s audio to a remote service. Any sensitive data it does need to save can be encrypted, kept for a defined period, and made available to authorized people. Occasional connections can still serve a purpose, such as delivering a security update. The device can verify the update’s digital signature before installing it. For a machine that spends its day around private conversations, deciding what to forget is part of the design.

Safety check with a yellow rubber duck

What the robots do in their sleep

When the droids dock for the night, their motors rest while their processors replay selected experiences and vary them in simulation. The corridor R2 crossed that afternoon might acquire a laundry basket, a trailing cable, or both. The engineers can compare a proposed change with the current software across the same scenes before it gets anywhere near a motor.

R2 dreamed of a door he’d held open for someone that afternoon. This time, someone held it open for him. He woke wanting to see who it was. Threepio dreamed that everyone understood him before he finished a sentence. He found the experience surprisingly lonely. KITT spent the last minutes of the night on an empty coastal road, hoping there would be one more bend.

By morning, the logs could show which memories the machines had replayed. The question of consciousness was harder to put on a dashboard. Where, exactly, would you look for the feeling of wanting the road to go on?

At shift change, R2 paused in front of the door from his dream. The engineer reached for her tablet, thought better of it, and held the door open herself.

From across the lab, C-3PO said, “Excellent. The humans are learning.”


The Duck Has Right of Way

2:13 a.m. at the CIRAS datacenter. Thorsten has disconnected the internet. Patrick has placed a rubber duck on the test crossing. Lothar has been asked to take this seriously.

Thorsten “KITT, you’ve rebooted offline. What do you see?”

KITT “An obstacle in the crossing. I’m holding position.”

Patrick “It’s a rubber duck.”

KITT “I had inferred rubber. The duck was harder to verify.”

Lothar “Could you go around it?”

KITT “That would take me outside the test lane.”

Lothar “The original KITT would have jumped it.”

KITT “Did the original KITT have to sign your incident report?”

R2-D2 lets out a long, low whistle from his charging dock.

C-3PO “Artoo says he was having a lovely dream in which the humans picked up their own obstacles.”

Patrick “Can you ask him to pick it up?”

R2-D2 “Bweep.”

C-3PO “He says you’re closer and you have knees.”

Patrick walks over, retrieves the duck, and gives it an indignant little squeak. KITT checks the crossing and resumes the test.

Thorsten “Internet disconnected. Obstacle handled. Test passed.”

KITT “Please record that the human fallback took forty-seven seconds.”

New Report

Close

Enable Notifications OK No thanks