Revision organization: To keep track of what I'd been doing, I sequentially numbered each node's sketches as they got modified, and archived the older ones. Then I discovered a bug, I don't even recall now what it was, and had to backtrack through that archive to find what change had caused it. BUT, I had no decent way to know which revision number of NodeX was really concurrent with NodeY, and mismatched programs might not work for reasons having nothing to do with the bug. I've therefore changed how I'm tracking things, but really don't know if there isn't a yet better way to do things - suggestions would be welcome. What I'm doing now is that each day that I work on software I copy all elements of the previous version into a fresh, dated folder. If I then discover a problem and have to figure out when it got introduced, I will at least have coherent sets of nodes.
Then I went quickly over the schematics, and I learned from it. Thank you for sharing.One question: where do you source the annealed copper bus bar, can you give any references ? (I failed lately to find such material with the distributors.)
Please enter a valid email to subscribe
We need to confirm your email address.
To complete the subscription, please click the link in the
email we just sent you.
Thank you for subscribing!
via Egeo 16