


Unfortunately, most people sprinkle a few comments here and there, which is helpful 5 years later if you have the source code. (Ask me why I developed that habit for everything I have coded for the past 30 years.) Doing so, facilitates just the exercise I am suggesting. This won't be productive unless the original programmer liberally included Serial.print() statements throughout the code, something I STRONGLY RECOMMEND as a programming habit to develop. If, in fact there is any output that you can observe, make it a task to create your own new code to emulate what the program DOES.
Way to the woods pc download serial#
That is, run the program and take careful notes of what happens (via Serial Monitor or whatever). None of the variable names are preserved, and the way the compiler optimizes code, even the structure of the code would be hard to determine.Īnother approach might be to treat the program onboard the Arduino as a black-box exercise. In the "long sketch" case - it just isn't worth it. In the "short sketch" case, you are better off just rewriting from scratch.
