While I was still an industrial electrician I learned to program with BASIC ( which I later learned to hate ), 'C' ( which I love ), and PLC Ladder Logic. All mostly self taught. I think this was a big part of why I later got a much better job in process automation. Our processes were controlled by a hybrid system, a DCS ( distributive control system ) did all of the analog stuff ( flows, temperatures, etc ) and a PLC ( programmable logic controller ) handled the digital logic ( motors, bindicators, interlocks, etc ). In addition the DCS handled the operator consoles, originally using DEC PDP-11-73s running RSX, later with DEC Alphas running VMS. and finally ( much to my disgust ) a PC running Windoze. When I was assigned to do the automation programing in a plant, I did the all the programming on both systems, and also drew the operator console graphics with ACAD At first, I found my job fascinating, but some years before I retired, I was sick of the whole thing. When you've written code that people use every day, you don't own the program - it owns you! All of those of 3:00 am phone calls, where 99.999 percent of the time it's either operator error or a hardware problem. Very rarely is it what we called in the department a "logic bomb". IOW where code that's run perfectly for years encounters a unique set of circumstances that makes it blow up. Hey, I just realized that my Hughes data usage problems may have turned ME into to one of those 3:00 am callers! :>)> "Enough about me, let's talk about you for a a minute" Alanis Morissette
... View more