#Beckhoff plc software#
Obviously the TwinCAT (and even PLC) community is considerably smaller than for the “standard” software fields, but I can’t help but feel that the field of automation is much more closed in terms of sharing knowledge. If you try to find information on forums, Stack Overflow, tutorials, open source projects or blogs, you will have limited success compared to for example doing C++ development. What I am missing however is more resources than the Beckhoff infosys. When I started TwinCAT s/w development, the Beckhoff documentation had lots to wish for, but this has vastly improved over the last years. The list is in order from good to best, and from bad to worst (respectively). To be fully clear, this list is 100% my personal opinion and is 100% subjective and might not represent the average TwinCAT developers opinions. What I would want to share with you is a list of five things that I think Beckhoff have done right, and five things that they could improve. It has given me opportunities to work with insanely fun projects that I would never have worked with if I didn’t start with PLC software development. Overall, I would say that I can do tremendously more things (in a reasonable amount of time) with TwinCAT by myself, than I could do before when I was developing software in the “standard” programming languages. I have recently philosophized about how my life as a software developer has changed compared prior to doing automation software. This includes the programming language, development environment, software development processes, hardware, communication protocols and much more. I have been using TwinCAT for quite some time now, and since I started developing software with TwinCAT it has changed almost everything for me as a software engineer, both as a profession and as a hobby.
0 kommentar(er)
