I would say that, If your robot was outputting a plain text log and not just running on compiled code. the log might look something like.
Running Cake Search Routine...
Running Cake Search Routine...
Running Cake Search Routine.. Cake Found!
Run Cake Aquisition v1.0...
Navigating to cake: Running Navigational Waypointer... Initiating Rayscan...
Rayscan took 3.4seconds
Path found..
Initiating move command
WARNING IMPEDIMENT DETECTED: Class 1 Human Interaction
Initiating Asimov Saftey System
Cake Aquisition: Run Deterrance Protocol
Voice Response: "I am just browsing"
Cake Aquisition: Run Deception Protocol
Voice Response: "Sir I am detecting a fire in the building you should leave while I secure the premises and call the fire brigade"
Cake Aquisition: Run Aquire cake
Cake Aquisition: Cake Aquired! Mission Successful!
Cake Aquisition: Return to base Initiating Return Home Protocol
Robot returns to base.
thats how I might do a log
If we assume the robot is running some kind of ROBO OS, a dumb AI that essentially chooses what is the best instruction or command to run based on its current set of user inputted instructions.
You can simply output what commands it might be running in a similar way to how DOS display's user commands.
so it runs various commands and they output various results to the console, all the nitty gritty coding is hidden just the important parts are written down.
Its understandable by your standard reader because its the same kind of text that scrolls up alot of computers on boot.