Craig Pearce

Programmers will spend three hours writing code that saves them three seconds. "We can't add those details to the HMI, budget won't allow time to do it" Yesterday, I shared an example of a discrete input object designed to improve troubleshooting and operation, without modifying PLC code. One key element was a descriptive label for the input device. Budget concerns came up in the comments, as they often do when discussing these solutions, especially for one-off applications. But when working in an environment optimized for code reuse, this becomes a "buy once, cry once" scenario. I’ve manually typed in these descriptions before. It’s manageable on a system with 20 I/O points, but with hundreds or thousands? That quickly becomes tedious, time-consuming, and error-prone. Being a bit lazy myself, I set out to automate it. Since the objects follow a hierarchical structure, the description almost writes itself. Here’s the approach I took in CODESYS: 🔹 Extract the full path name during a cold start using pragmas. This includes everything, so time to clean it up… 🔹 Trim to just after the program name by finding the first five dots and removing all preceding text. 🔹 Remove remaining dots using a similar function. 🔹 Format for readability by parsing ASCII values, inserting spaces before uppercase letters and numbers (I tend to use PascalCase). Arrays will need special handling, and instances ending in zero don’t play nicely. 🔹 Consolidate the functions initially separate, but I merged them into one. Future me will probably regret this decision. After three hours of trial and error, documentation diving, debugging, and refactoring, I ended up with a function that automatically generates clean, structured descriptions. All to save 3-5 seconds per instance. Was it worth it? Absolutely. There’s probably some cliché about not seeing the forest for the trees here. But the takeaway? If your environment supports code reuse, USE IT. Worth noting, this is one implementation with many caveats. It should probably be put into an init method of some sort, account for other use cases, errors, etc. How would you improve it? Drop a comment below! ⬇️ #codesys #twincat #plcprogramming #structuredtext #ladderlogic #alanbamly #agtech #agautomation

622

30 Comments

SCADA didn’t stand still — and neither did we. From DOS-based PCs in the 80s to .NET-powered Edge deployments today, industrial software has changed more in 40 years than most plants realize. Generation 4 SCADA is here: context-driven, edge-to-cloud ready, built for Unified Namespace and real-time collaboration. If your system still feels like Gen 2 with new paint, maybe it’s time to see what’s really possible. Read my take on four decades of SCADA → https://lnkd.in/dZD5D6PP #SCADA #Industry40 #IIoT #FrameworX #EdgeComputing #IndustrialAutomation 

45

4 Comments

Stop pitching automation as a cost cutter. Start proving it’s a profit engine. When calculating ROI for your next automation project, be sure to calculate increased capacity into the return calculation. Assuming you can sell the product on your increased capacity, you can use the gross profit generated from the new revenue in your ROI calculation. This new profit will add up surprisingly quickly and show you how valuable new equipment can be for your organization. Increased capacity can be generated from less downtime (less maintenance or running more frequently through automation), faster cycle time, improved yield. Also be sure to… > Identify all costs associated with the automation project  > Get the exact benefit in cost from your integrator > Make a plan to track costs after installation What gets measured gets managed. So if you can prove that you can achieve a great ROI (<2 years like we provide our customers) through real numbers, your next project has better odds of getting approved.

326

30 Comments

Once again, Keith Gamble 👏 has demonstrated that there are no limitations when it comes to leveraging #Ignition -- whether in the world of industrial automation or DevOps. He introduced the Tag CI/CD Module, a powerful tool that brings version control and continuous integration/continuous deployment (CI/CD) practices to Ignition tags. Module provide Comprehensive REST API through a REST API for CI/CD pipeline integration Learn more here: https://lnkd.in/dQYZupie #Ignition #Ignition83 #DreamItDoIt

58

2 Comments

Have you ever wondered why the industrial community doesn't share PLC code like software developers do with open source code? Sharing PLC code could greatly benefit the community by allowing for collaboration, faster problem solving, and the sharing of best practices. “That’s our IP!” is the thing I always hear, but does that out weigh the benefits? Have we moved on from closed systems? There are several benefits that engineers can gain from open sourcing their PLC code: 1. Collaboration: By sharing their PLC code, engineers can collaborate with others in the industry to improve upon it, leading to better and more efficient solutions. 2. Faster problem solving: With access to a wide range of PLC code, engineers can quickly find solutions to problems they may be facing by searching for similar code. 3. Best practices: Open sourcing PLC code allows engineers to share best practices and learn from others in the industry. 4. Reusability: Making PLC code open source allows other engineers to use and build upon it, increasing the overall efficiency of the development process. 5. Cost savings: Open sourcing PLC code can save companies money by allowing them to use existing code rather than starting from scratch. 6. Innovation: Open sourcing encourages experimentation and innovation, leading to new and better solutions. 7. Transparency: Open sourcing PLC code allows for greater transparency in the industry, making it easier for engineers to identify and rectify any issues. Git with the Program!! Let's start a conversation about the potential benefits of open sourcing PLC code and how we can make it a reality, or does it already exist? #opensource #plc #scada #industrialautomation #automation #community #innovation #development #share #collaboration #engineers #sourcing

142

62 Comments

Industrial Protocol Series! We’ve wrapped up our series on Industrial Communication Protocols, covering: • Field Level: Modbus RTU/TCP • Control Level: EtherNet/IP & Profinet • Enterprise Level: OPC UA Our final session featured a live demo of OPC UA using Prosys OPC UA Simulation Server and OPC UA Browser—giving participants a practical view of real-time data integration from plant floor to enterprise systems. The series was well-attended, interactive, and packed with insights. Thanks to everyone who joined us on this journey! Missed a session? All sessions were recorded and are now available—feel free to reach out for the links. A new series is already in the works. Stay tuned—we’re just getting started! #IndustrialAutomation #OPCUA #IIoT #SmartManufacturing #ControlSystems #DigitalTransformation #CorsSystems #ProsysOPCUA

44

1 Comment

Effortlessly integrate water utility operations data from any source to rapidly enable better business decisions while increasing production, profits and sustainability with DeltaV SaaS SCADA for water utilities. Learn More > https://ow.ly/nXQa30sNxIN #utilities #wastewater #water #iiot #saas

19

🌟 Practical Learning is Key! The PLC trainer empowers learners with practical skills that go beyond theoretical knowledge. It allows you to simulate real industrial processes, troubleshoot live issues, and program PLCs—all in a safe, controlled environment. 🔧 Check out the demo: https://lnkd.in/gHUP24Qx #PracticalLearning #HandsOnTraining #PLC #Automation

57

6 Comments

The SITRANS LT500 MultiRanger is now available with 3 new communication protocols. Ethernet IP (EIP), ProfiNet and Modbus TCP-IP. EIP is available with a Class Leading EDS-AOP for easy integration into Rockwell Studio, ProfiNet is certified V4 with available GSDML file and Modbus TCP-IP has access to the Modbus map. #SITRANSLT500 #level #makessense #siemens

56

4 Comments