5 ms·

In my experience, good logging is the first step to good debugging. Having good logs lets you find a lot of problems without even debugging "properly" (using a

• MarkSweep 13y ago
  Good logs have been especially useful while integrating new motion controls in our wafer handling robot. We have a vendor who's product sometimes does not respond correctly to motion commands. Before logging each movement command, debugging a weird movement error would involve repeatedly moving the robot until the error happened again. Now I just pull the last N commands out of the log file, reproduce the issue, and send a script to the vendor so they can fix it.