(step 1 of 2)
Write your email address in the white field and then click the "Confirm" button.
(step 2 of 2)
Write your password in the white field and then click the "Confirm" button.
Or click the "Request password" button to request forgotten password.
Email address has not been found!
Click the "Previous step" button to to enter your email address again.
Or click the "Register user" button to register your email address.
Pasword does't match!
Click the "Previous step" button to enter the password again.
Or click the "Request password" button to request forgotten password.
(step 1 of 2)
Write your email address in the white field and then click the "Confirm" button.
(step 2 of 2)
Your password has been sent to your email.
Please also check your spam folder.
Email address has not been found!
Click the "Previous step" button to enter your email address again.
Or click the "Register user" button to register your email address.
(step 1 of 5)
Write your email address in the white field and then click the "Confirm" button.
(step 2 of 5)
Registration code has been sent to your email.
Please also check your spam folder.
Copy the registration code from your email in the white field and then click the "Confirm" button.
Or click the "Previous step" button to request the registration code again.
Email address already exists!
Click the "Previous step" button to enter the email address again.
Or click the "Log in user" button to log in with your email address and password.
Or click the "Request password" button to request forgotten password.
(step 3 of 5)
Set your user name in the white field and then click the "Confirm" button.
Registration code does't match!
Click the "Previous step" button to enter the registration code again.
(step 4 of 5)
Set your password in the white field and then click the "Confirm" button.
User name already exists!
Click the "Previous step" button to set another user name.
(step 5 of 5)
User has been successfully registered.
Click the "Log in user" button to log in.
Please log in to be able to open user settings.
Click the "Log in user" button to log in with your email address.
Or click the "Register user" button to register your email address.
Your subscription has been successfully canceled.
Your subscription has been successfully established.
Write your comment in the white field and then click the "Add comment" button.
Article#: 00032
Date: 2020-09-25
Author: Radim
"If you don't listen to your customers you will fail. But if you only listen to your customers you will also fail." – Amazon
"A lot of time, people don't know what they want until you show it to them." - Steve Jobs
Listen to your customers.
Try to understand their needs.
Study new technologies, keep an eye on the new products and features from suppliers (producers of PLCs, sensors, drives, actuators, software solutions, etc.).
Try to imagine how the new technologies can help your product make it more useful and interesting to the customers.
Show the new possibilities to stakeholders, including customers, users, maintenance, tech support and others, and ask about their interest.
Take the inputs into account and improve your product.
Train the customers on the product.
Request customers feedback.
Take into account every feedback from the customers and improve your product.
Remember that alongside all the new trends, reliability and transparency of the entire system are of the greatest importance.
© Radim-Automation, 2020–2025. All rights reserved.
Sharing of this article is permitted with proper attribution (link to the original page).
Related previous articles:
Related next articles:
Comment#: 00001
Date: 2020-09-25
User: Radim
...
"And do you have Industry 4.0?"
"Yes, we do."
"And do you have IoT?"
"Yes, we do."
"And do you have artificial intelligence?"
"Yes, we do."
"So where's the problem?"
"Machine does not work :("
=> Remember that alongside all the new trends, reliability and transparency of the entire system are of the greatest importance.
Comment#: 00002
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#: 00003
Date: 2023-07-21
User: Radim
"The essential function of the PLC is to receive data from sensors or other field devices; make a decision on what to do with that information based on its programming instructions, for example, to open or close a valve based on fluid levels or direct a robot to pick up an object based on its presence in the work cell; and send the correct signal to the actuator (such as a valve or robot gripper) to perform the task."
- David Greenfield. AutomationWorld (2023). Peer-to-Peer FAQ: Controllers.
- https://www.automationworld.com/control/article/22724233/industrial-controller-technologies
Comment#: 00004
Date: 2023-08-10
User: Radim
"The information that should be available on a graphical user interface (GUI) of a machine depends heavily on the type of machine and its application. However, here are some basic pieces of information that are often displayed on a GUI:
1. Status Information: The GUI should display important status information about the machine, such as whether it's powered on or operational, whether it has issues or error messages, and whether all systems are functioning properly.
2. Operational Parameters: Display the current operational parameters of the machine, such as speed, temperature, pressure, voltage, etc. This allows the user to monitor the machine's current state and make adjustments if needed.
3. Process Overview: If the machine is involved in an ongoing process (e.g., manufacturing, processing, analysis), relevant process data and steps should be displayed on the GUI. This helps the operator monitor the progress of the process and identify potential deviations.
4. Warnings and Error Messages: Display warnings or error messages if problems or critical situations arise. This enables the operator to react quickly and take appropriate actions.
5. User Interaction: Provide interfaces for user interaction, such as adjusting settings, changing parameters, or issuing commands. This includes buttons, dropdown menus, text fields, and other elements.
6. Historical Data: A history or log of past events and activities can be helpful for identifying trends, diagnosing errors, or making performance improvements.
7. Documentation and Help Material: Provide user manuals, help tutorials, or links to further information so that users can learn about operation, maintenance, and potential issue resolutions.
8. Visualizations: Depending on the application, charts, graphs, or visual representations of relevant data can be useful for recognizing relationships and trends more easily.
9. User Profiles and Settings: Allow users to create individual profiles and configure specific settings to match their workflow.
10. Safety Information: If the machine could potentially be hazardous, the GUI should display safety instructions, emergency stop buttons, or other safety mechanisms.
11. Contact Information and Support: Provide contact information for technical support or customer service in case users need assistance or support.
It's important to carefully design the GUI based on user needs and the type of machine to ensure a user-friendly and efficient experience."
- https://chat.openai.com (What information should be available in the machine's graphical user interface?)
Comment#: 00007
Date: 2023-09-11
User: Radim
Does it make sense to think about digitalization if we don't see any use case?
"If you don't see any practical use case or clear benefit for digitalization in your specific situation, it may not make sense to pursue it blindly. Digitalization should always align with your organization's goals and needs. Here are some considerations:
1. Assess Business Objectives: Start by identifying your organization's objectives and challenges. Digitalization should align with your strategic goals, whether it's improving efficiency, reaching new markets, enhancing customer experiences, or reducing costs.
2. Customer Demands: Consider whether your customers or clients expect or would benefit from digital solutions. If there's no demand for digital services, investing in them may not provide a return on investment.
3. Competitive Landscape: Analyze your competition. If your competitors are effectively utilizing digital technologies to gain a competitive advantage, it might be necessary to explore digitalization to stay relevant.
4. Cost-Benefit Analysis: Conduct a thorough cost-benefit analysis to determine if the potential benefits of digitalization outweigh the costs. If the investment doesn't offer a reasonable return, it might not be justified.
5. Resource Availability: Evaluate whether you have the necessary resources, including financial resources, technical expertise, and staff training, to implement and sustain digital solutions effectively.
6. Future Growth: Consider the scalability of your organization. Even if you don't currently see a clear use case for digitalization, it's essential to think about your organization's future growth and whether digital technologies could play a role in that growth.
7. Technology Trends: Stay informed about industry trends and emerging technologies. While there may not be an immediate use case, technological advancements could create new opportunities down the line.
8. Customer Feedback: Engage with your customers or stakeholders to gather feedback on their needs and preferences. They may provide insights that could uncover potential use cases for digitalization.
9. Pilot Projects: Instead of a full-scale digital transformation, consider starting with smaller pilot projects to test the waters and assess the feasibility and impact of digital solutions in a controlled environment.
10. Consult Experts: Seek advice from digital transformation consultants or experts in your industry. They can provide insights into potential use cases and help you determine if digitalization is appropriate for your organization.
In some cases, it may indeed be the case that digitalization doesn't make sense for your organization at a given time. However, it's essential to regularly revisit this assessment as technology and business landscapes evolve. What might not be relevant today could become essential in the future. Ultimately, the decision to pursue digitalization should be guided by a thorough understanding of your organization's unique needs and circumstances."
- https://chat.openai.com (Does it make sense to think about digitalization if we don't see any use case?)
Comment#: 00008
Date: 2023-09-13
User: Radim
Often the person who knows the answer or the right way is closer than you think. All you have to do is ask.
Comment#: 00009
Date: 2023-09-15
User: Radim
Complaints and identified problems are good sources of innovation.
Comment#: 00010
Date: 2023-09-27
User: Radim
"By continuously improving the design of code, we make it easier and easier to work with.
This is in sharp contrast to what typically happens: little refactoring and a great deal of attention paid to expediently add new features.
If you get into the hygienic habit of refactoring continuously, you'll find that it is easier to extend and maintain code."
- Joshua Kerievsky. Addison-Wesley (2004). Refactoring to Patterns.
Comment#: 00011
Date: 2023-10-02
User: Radim
How to get the right intuition?
"Developing and honing your intuition can be a valuable skill, but it's important to remember that intuition is inherently subjective and can't always be "right" in an objective sense. However, you can work on improving the accuracy and reliability of your intuition by following these tips:
1. Increase Your Knowledge and Experience: The more you know about a particular subject or domain, the better your intuition is likely to be within that area. Gain expertise and experience through study, practice, and exposure.
2. Trust Your Gut: Pay attention to your gut feelings or initial impressions. Sometimes, your subconscious mind processes information faster than your conscious mind, leading to intuitive insights. Don't dismiss these feelings outright; give them consideration.
3. Practice Mindfulness: Mindfulness meditation can help you become more aware of your thoughts and feelings. This self-awareness can improve your ability to recognize and trust your intuition.
4. Keep a Journal: Maintain a journal where you record your intuitive hunches and the outcomes. Over time, this can help you assess the accuracy of your intuition and learn from your experiences.
5. Seek Feedback: Discuss your intuitive insights with trusted friends, mentors, or colleagues. They can provide valuable perspectives and help you refine your intuition by offering feedback on your decisions.
6. Validate with Data: When possible, seek out data or information that can confirm or refute your intuitive impressions. This can help you develop a more evidence-based form of intuition.
7. Relax and Clear Your Mind: High-stress levels or a cluttered mind can cloud your intuition. Engage in relaxation techniques like deep breathing, meditation, or progressive muscle relaxation to clear your mind and enhance your intuitive abilities.
8. Ask Open-Ended Questions: When facing a problem or decision, ask yourself open-ended questions and let your mind wander. This can stimulate creative and intuitive thinking.
9. Learn from Mistakes: Embrace your intuition's imperfections. When your intuition leads you astray, use those experiences as learning opportunities. Analyze what went wrong and adjust your intuition accordingly.
10. Practice Patience: Sometimes, intuition needs time to develop. Don't rush your decision-making process if you're unsure. Give yourself the space to allow your intuition to emerge.
11. Combine with Analysis: Balance your intuition with analytical thinking. For important decisions, use your intuition as an initial guide but then follow up with critical analysis and data-driven assessment.
12. Cultivate Emotional Intelligence: Understand and manage your emotions effectively. Emotional intelligence can enhance your ability to perceive and interpret your own and others' emotional signals, which can inform your intuition.
Remember that intuition can vary from person to person, and it's not always infallible. It's a skill that you can refine over time, but it's also important to recognize its limitations and use it as a complementary tool alongside rational thinking and evidence-based decision-making when appropriate."
- https://chat.openai.com (How to get the right intuition?)
Comment#: 00013
Date: 2024-01-05
User: Radim
I have found the solution !!!
But unfortunately the problem did not match my solution.
:-)
Comment#: 00015
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#: 00016
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#: 00017
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?