Hello everyone, I am seeking advice on integrating the Touch Tester primitive into my CR1000-04000 system in Crimson 3.1. While not essential, I believe having this feature on the Maintenance page could serve as a useful troubleshooting tool. Unlike Touch Calibration, the Touch Tester primitive does not have configurable properties, making it difficult to exit after testing. I have devised a workaround using ladder logic in the PLC, but I believe this functionality could be implemented within the HMI. As I primarily use boolean ladder logic, I assume utilizing structured text programming would be the appropriate approach, but I am unable to find suitable examples. Any guidance on this matter would be greatly appreciated. From the Maintenance Page, I have set up a (Push Button: Turn On) flag tag for Touch_Tester with a B3:2/14 address, utilizing the "GotoPage()" function and a 10-second timer in the PLC.
If you're unsure about your next steps, consider bypassing the PLC and focus on achieving your goal. Are you looking to showcase the Touch Tester page briefly before automatically redirecting to the Maintenance page after a short delay? One option is to set up an internal tag, like 'timer', to monitor the time the page is active. By creating a standard button for accessing the Touch Tester page and adjusting the Page Properties accordingly, you can reset the timer upon page load and have it count up every second until reaching the designated 10-second mark.
I am grateful, John, for showing me a simpler solution that I overlooked. I realized that I was unnecessarily complicating things. By simply using Timeout on the page properties, I was able to make it full-page without any issues. I appreciate your help in my learning process. Thank you once again for your guidance.
When designing my touch calibration page, I always include a "Back" button (Navigate to: Previous Page) at the top. It's important to place it strategically so that it doesn't obstruct any of the calibration test points. This ensures a smooth user experience and easy navigation.
I have been utilizing "On Sucess" and "On Failure" GotoPage(xxx) for Touch Calibration. This method requires the operator to interact with the red boxes, but it has been effective for me without any issues. I recently discovered the Touch Tester and now realize the importance of features like "Page Timeout". Currently, I am working on setting up an Event Log for troubleshooting purposes. I am looking for a way to remove old events without deleting the entire log and also want the ability to view the last 20 events. To test for potential memory issues, I set up an event every 2 seconds and noticed some instability after 6 hours, but clearing the event log resolved the issue. Any suggestions for improvement? UPDATE: I have created a Midnight_Reset Flag Tag to clear events, which appears to be effective.
Hi there, your approach using structured text programming in Crimson 3.1 seems pretty reasonable. I've had a similar issue with integrating Touch Tester into a system and managed to resolve it by creating a temporary exit button that only appears during testing. For the exit button, you could use a Push Button with a VB tag and temporary visibility based on a boolean condition. The issue you may face is if the touch calibration is completely off, finding and pressing the exit button could be tricky. However, I found it to be a cleaner solution than using a timed transition. Hope this helps with your setup, and I'm interested to see how other folks are solving this problem.
Hi there, it sounds like you're on the right track with your work around using structured text and the GotoPage() function. Although, you're right that the Touch Tester doesn't have configurable properties. But you can create an exit button on the same page using a simple Boolean with 'change page' operation. In your case, as you primarily use boolean ladder logic, associate this Boolean with a visibility tag in the HMI for the exit button. This way, the button only appears during touch testing, allowing you a clean exit once you've finished. It's a simple yet effective workaround that my team often implements in our systems. Hope this helps!
Hey there! It sounds like a great idea to add the Touch Tester to your Maintenance page for easier troubleshooting. Since you’re already using ladder logic with the flag tag for your button, have you considered implementing a simple structured text snippet that listens for a condition to reset the tester after the 10-second timer? You could use an IF statement to check if the timer has elapsed, and then trigger a GotoPage() back to your main screen. If you haven't found many examples in the documentation, the forums often have some creative solutions shared by others who faced similar challenges. Good luck with it; I’m sure you’ll nail it!
Hey! It sounds like you're doing some interesting integration work with the Touch Tester. I totally get your frustration with its lack of exit functionality. Since you're already using a combination of ladder logic and a timer, have you thought about using a conditional logic approach to automatically return to the Maintenance page after the 10 seconds is up? This could simplify things a bit. Also, for structured text examples, the CODESYS community has some great resources—maybe browsing there could spark some ideas. Good luck, and I hope you find the perfect solution!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: - To integrate the Touch Tester primitive, you can set up a flag tag for Touch_Tester with a specific address, utilize the "GotoPage()" function, and implement a timer in the PLC for functionality.
Answer: - Unlike Touch Calibration, the Touch Tester primitive does not have configurable properties, which can make it challenging to exit after testing.
Answer: - Yes, you can implement the Touch Tester functionality within the HMI by setting up flag tags, using functions like "GotoPage()", and incorporating timers directly in the HMI interface.
Answer: - If you primarily use boolean ladder logic, incorporating structured text programming may be the appropriate approach for implementing the Touch Tester functionality within the HMI.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.