photo of a kuka kr200 robot, the krc1 controller that drives it and a monitor showing the controller software.

Notices where this attachment appears

1. elia (elia@fedi.quiescent.nexus)'s status on Friday, 02-Feb-2024 09:58:54 JST elia
   picking up where we left off in the previous thread: https://fedi.quiescent.nexus/notice/AeRV7KpDmnSI2Ewg4G
   
   the hardware part o this story seems to be mostly done. it powers up and works. I have yet to test the actual servo drive, robot is not even connected at this point, but I'd say we're most of the way there.
   
   let's look at the boot sequence: https://www.youtube.com/watch?v=LWHW8WK4cDk
   
   00:03 - powerup.
   00:07 - low voltage supply status led check.
   00:14 - computer starts post sequence.
   00:26 - windows 95 starts booting.
   00:34 - wait what? yes, wxwrt.vxd. wxworks.
   00:40 - at about this point the external monitor starts getting output, as the kvga driver is loaded and enables the vga port, which is normally disabled.
   00:50 - windows boots, autostart kicks off kuka software.
   01:16 - the control software proper starts up and begins hardware initialization.
   01:39 - "download" begins - the digital signal processors on the mfc card are "downloading" firmware.
   02:00 - dsps boot, last stage of startup begins.
   02:20 - startup complete.
   
   now, this is actually not the correct software for the krc1 control encosure. it's the volkswagen software that was configured for the vkrc1 hardware (see the linked thread). this is why it immediately throws a ton of errors.
   
   next step: reinstall proper software.
   
   more posts in this thread incoming soon.