The motorcycle was done sooner than she thought. It only took a few readjustments to get rid of the odd noises it was making. It seemed the owner had hit something or the bike had been jostled, causing a few things to become misaligned, thus causing rattling and weird exhaust patterns. Oh well, just means that her customer didn't need new parts and that would keep cost down for them. She was sure they would be happy with the result.

Kala cleaned up her arms before starting her next item on her list. She began to run diagnostics on her suit. She checked the OS first. It was having no problems and she had fixed the bug from last time causing it to randomly restart. Next, she looked at the installed modules. Again, no problems. Cables showed up as ready. Claws appeared as retracted. Her damage module showed no damage. So far, so good. Live testing came next. She enabled the testing mode in the suit and began by testing the damage sensor. She took a wrench and gave each piece a good whack, only enough to register as force applied. Each area hit lit up in her HUD properly, registering as a non-damaging hit. A quick test of her claws showed that they extended and retracted properly as well as properly changing status in the HUD. Everything was going well thus far. That was a good sign. The final test came along as a sort of dry fire. She ran a program that sent the signal that the cables had been fired and then retracted. Both fired successfully, but her left one did not register in the HUD properly. It threw an error. She shut down the suit and frowned before jumping into the work. She had to find the error and reprogram it to properly show the firing in the HUD. At least the problem could have been worse. Hardware problems are more dangerous than small software bugs.