Choose the right tool!
Article#: 00007
Date: 2020-04-11
Author: Radim
Choose the right tool that will help you on the way to the target.
Make sure that the tool is well supported by the manufacturer.
This can be, for example, a project management tool, a software development environment with a programming language, a documentation tool, etc.
Get to know the possibilities of the tool well.
Check out the demo to see what can be done with the tool.
Get inspired by the possibilities of the tool and be ready to change your familiar processes (possibly those that you used with another tool) and learn new processes.
Get familiar with the tool.
Find out how to use it efficiently.
Learn the important keyboard shortcuts to work fast and surely with the tool.
© Radim-Automation, 2020–2025. All rights reserved.
Sharing of this article is permitted with proper attribution (link to the original page).
Related next articles:
- Sharpen your axe before you start felling!
- Focus on target!
- Have an expert on hand!
- Do you really want to start with this?
- Is the way really the goal?
- Prepare a good project plan and keep it up to date!
- HMI and PLC applications should grow together
- Write down your best practices and processes!
- Functional and intuitive HMI
- Why do automation projects fail?
- Project leader
- Learn from your journey!
- Think critically!
- Are there also any disadvantages?
- A good concept = Complete set of suitable solutions
- Hardware concept
- Modular software architecture
- Abbreviations
- Choice of programming language
- Visual modeling
- Documentation issues
- Safety relays versus safety PLC
- Software update
- Event logger as the very first function implemented in the program
- Diagnostic tools
- My boss was a hero
- Version control system
- Keep the documentation up to date throughout the project
- Dream of a platform-independent PLC program
- Keep everything you need together
- High Performance HMI
- HMI - Have a consistent style
- HMI - Don't overdo it with complex design
- Hidden dangers during commissioning
- The false illusion of rapid progress
- HMI layout design
- HMI navigation
- HMI - back and forward navigation buttons
- HMI – Don’t hide anything
- HMI - annoying pop-up windows
Comment#: 00001
Date: 2021-01-30
User: Radim
The possibility of changing all occurrences of a variable name in the program at the same time must be available in the development environment!
The need to change a variable name during development is often required. If the tool doesn't make it available, it's not easy to develop in such development environment.
Comment#: 00002
Date: 2021-02-05
User: Radim
If you can, choose editors with color-coded syntax. The code is much more convenient to read when keywords, comments, variables, and other elements are color-coded.
Comment#: 00003
Date: 2021-06-07
User: Radim
[Winkey + Shift + S] = screenshot a portion of the screen in Windows 10
- https://www.winhelponline.com/blog/screenshot-portion-screen-windows-10-winkey-shift-s/
Comment#: 00004
Date: 2021-06-07
User: Radim
[Alt + Click + Drag] = select a box of text in Visual Studio
- https://code.visualstudio.com/docs/editor/codebasics
Comment#: 00005
Date: 2021-10-20
User: Radim
Can "everything" be put together in the development environment simply by drag-and-drop? Well, that's great when you just have to drag and drop a few things together.
When it comes to developing a larger application, it is better (faster and more convenient) to have coding / scripting available and using it.
Comment#: 00006
Date: 2022-10-25
User: Radim
A mouse right-click on a variable in the program must offer the useful jumps, such as:
Go to Declaration of ...
Go to Datatype of ...
Go to Implementation of ...
Comment#: 00007
Date: 2023-04-11
User: Radim
"There is so much you can do in this single development environment. Want to write software that reads temperature, pressure, flow and humidity sensors and at the same time do some monitoring and at the same time have a safety feature that powers a system off based on some criteria? While you're at it, maybe you want to control 25 motors, all synchronized together like a group of birds in the sky together below 50µs with each other? Why not add some fancy HTML5 capable front-end that will feel modern and look good? Want to have quality control on the fly? Add a GigE capable camera and some smart vision algorithms. Further down the chain, there might be people that want to look at the data you've gathered to increase the quality or productivity, then you might publish the data to a cloud provider or a local database. There is simply so much I can do, I have so many possibilities on my finger tips when I start an instance of Visual Studio and the TwinCAT XAE. I simply don't see myself getting bored with TwinCAT software development any time soon.
When I started with TwinCAT I thought I would be able to catch up with all the new stuff that was released and that I would be able to learn everything. Since then I've given up on that idea. That was very naive of me, as the flow of functionality that Beckhoff releases with every new release is overwhelming. Nowadays I only focus to learn the new stuff that I find fun, preferably in combination with solving an employer's problem."
- https://www.linkedin.com/pulse/five-best-worst-things-twincat-jakob-sagatowski/
Comment#: 00009
Date: 2024-02-08
User: Radim
"AI is not going to replace humans, but humans with AI are going to replace humans without AI."
Comment#: 00010
Date: 2024-02-14
User: Radim
Benefits and risks of software updates via remote access to customer machines
In today's agile world, quick and easy software updates are essential for maintaining technologies and systems. However, the transition from manual installation of updates to remote access raises an important discussion about the risks and benefits of this approach.
Technical feasibility and tools:
The technical aspect is not an obstacle. With today's concepts and tools, the application software can be updated on remote machines at the customer's premises.
Risks:
However, the main concerns relate to the risks associated with this procedure. There is a possibility that the installation of the new software version may cause unexpected problems that can have serious consequences. The machine may no longer be able to be started and may even no longer be accessible remotely. A specialist then has to travel to the customer. This can take up to several days and leads to expensive production downtime for the customer.
Benefits:
Conversely, remote software updates have many advantages. Customers do not have to wait for a technician to be present, which saves time and travel costs. In addition, the rapid availability of updates can improve overall customer satisfaction and increase efficiency.
Solution:
To minimize the risks associated with remote updates, clear rules and procedures must be established. These include thorough testing of updates prior to deployment, detailed data backup and recovery plans and adequate training of customer personnel.
Comment#: 00011
Date: 2024-02-22
User: Radim
Is your native language not English and do you work in an international team? Have you agreed on English as the project language within the team? Then please:
1. Install and use all project tools in English.
2. Use English help files for the tools.
3. Write English variable names and comments in the code.
These rules make collaboration between team members, documentation and support tasks easier. Because people will use the same terms.
Do you agree with these rules?
Would you add anything else?
Comment#: 00012
Date: 2024-07-04
User: Radim
How easy and how well prepared is it to install a new computer for further work on an ongoing project?
When we get a new computer or when a new colleague starts working on an ongoing project, it is important that the steps are described to get a working environment for the project and that all necessary files and installations are available!
Comment#: 00013
Date: 2024-07-04
User: Radim
Use the same program/application versions for all members of the team. And keep the installation files in case someone starts working on the project later.
Comment#: 00014
Date: 2025-02-14
User: Radim
The 3 eras of programming: How we learn to code has evolved
1. Before the internet
In the pre-internet era, programmers relied on books, printed manuals, and personal experience. If they encountered a problem, they had to solve it through trial and error or by consulting colleagues. Debugging was slow, and every line of code was the result of hard-earned knowledge.
2. The internet era (pre-AI)
With the rise of the internet, everything changed. Documentation became instantly accessible, forums like Stack Overflow emerged, and learning to code became easier than ever. Programmers stopped memorizing everything and started searching for solutions instead — chances were, someone had already solved the same problem before.
3. The age of AI
And today? Programmers don’t just search for solutions — they have them generated. AI assists with writing code, debugging, and suggesting optimal approaches. Learning now involves experimenting with AI tools that don’t just provide answers but also explain them. More than knowing syntax, it’s about knowing how to ask the right questions.
How will the role of programmers evolve next?
What are your experiences with these changes?