Hello there! I understand that my title may be a bit cryptic, but I'm currently involved in a rehabilitation project where we are having a dilemma regarding the existing InTouch windows. The customer wants us to keep them, but we would prefer not to add duplicate data that would require extra effort to manage. This may seem like a trivial issue, but it actually doubles our workload, especially considering the budget constraints we are working with. The ISA-101 guidelines are open to interpretation, which adds another layer of complexity to the situation. Given the contractual challenges we are facing from the customer, I am striving to make the most of the existing resources and make practical decisions, even if the layout is subpar. This leads me to the issue of modifying strings that require manual changes in the PLCs, which realistically may not happen frequently. While pondering this issue, I came across a feature in Schneider where I could track the date and time of the last full build and minor build, providing insight into any changes made by the customer while I am working on a new configuration. This proactive approach allows me to ensure I am working with the most up-to-date information before implementing any changes. However, I am curious if there is a similar functionality in RSLogix / Studio 5000 to track changes or unique identifiers. I have come across the Audit feature with a GSV, but I am unsure of its functionality. Any insights on this matter would be greatly appreciated. Thank you.
While I may not be an expert in loops, I am definitely a beginner. What is happening in this code snippet? The code declares two integer variables, iLEN and iLOOP. iLEN is assigned the length of the string GX_LOGIN_PASSWORD. The password is then hidden by replacing each character with an asterisk using a loop. However, it currently only replaces the characters with ***. This seems like a lazy approach. I want to modify it so that it always shows a consistent number of asterisks, regardless of the password length. I will experiment with the code iLEN = StringLen(GX_LOGIN_PASSWORD);, but I am still unsure how it determines to use *** instead of 123. The line GX_LOGIN_PASSWORD_HIDDEN = GX_LOGIN_PASSWORD_HIDDEN + "*"; is perplexing to me.
Who would utilize a flag displaying the word "start" alongside it?
Dalporto expressed confusion over the statement GX_LOGIN_PASSWORD_HIDDEN = GX_LOGIN_PASSWORD_HIDDEN + "*". The equals sign acts as a gateway in time. Upon execution, the expression on the right side of the = sign is evaluated using the values any tags had before the statement is executed. The result is temporarily stored in a buffer. After evaluation, this result is then moved into the tag on the left side of the = sign. During each iteration of the loop, the + sign indicates that the string "*" is appended to the value of GX_LOGIN_PASSWORD_HIDDEN on the right side of the = sign. The concatenated result is then written to GX_LOGIN_PASSWORD_HIDDEN on the left side of the = sign. Initially, GX_LOGIN_PASSWORD_HIDDEN is an empty string. On each iteration, "*" is added to the existing value, gradually filling GX_LOGIN_PASSWORD_HIDDEN with asterisks until it matches the length of GX_LOGIN_PASSWORD. This process continues until all characters in GX_LOGIN_PASSWORD_HIDDEN are replaced with asterisks.
After clarifying the process, I realize I need to further experiment on my own to fully grasp it. In the meantime, I may have gone overboard or made a foolish decision, but it is producing the desired results. In the code snippet below, I am initializing variables iLEN and iLOOP as integers. The GX_LOGIN_PASSWORD_HIDDEN is set to an empty string, and if GX_LOGIN_PASSWORD is also empty, the iLEN is set to 0; otherwise, it is set to 20. Using a loop from 1 to iLEN, the GX_LOGIN_PASSWORD_HIDDEN is populated with "*" characters.
In this code snippet, IF the GX_LOGIN_PASSWORD is empty, then the GX_HIDDEN_PASSWORD is also set to empty. However, if the GX_LOGIN_PASSWORD is not empty, the GX_HIDDEN_PASSWORD is set to a string of asterisks. This simple IF-ELSE statement helps secure sensitive information in the system.
Hey there! It sounds like you're up against quite a challenge. As per your question about similar functionality in RSLogix/Studio 5000, yes, there's an option for that. RSLogix 5000/Studio 5000 version 20 and above introduced a feature called 'Change Detection' that can be activated on a per-program basis. When activated, it logs all changes done to the program, including the person's username who made the change, what was changed, the old data and the new data. It's quite helpful to monitor and track any modifications made. However, it does require a certain amount of discipline from your team to enter a comment every time they do make a change. As for unique identifiers, Studio 5000 Logix has the System Tags which have “LastProgChange” and “LastProgChangeUser”. These tags can be monitored for program change detection too. Hope this helps!
Your challenge really underscores the nuanced balance between customer preferences and practical project management. Given your dilemma, I agree that leveraging features like change tracking in your PLC configuration software is a savvy approach. Unfortunately, RSLogix / Studio 5000 doesn't offer an identical functionality to Schneider's build tracking feature. However, you can use the Controller Change Log, where you can review logged events with timestamps. The GSV you mentioned can also be useful for retrieving general system values, but remember it does require programming. Ultimately, it sounds like a frank discussion with your customer may be worthwhile to negotiate a reasonable balance of maintaining the existing InTouch windows and managing workload. Good luck!
âś… 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: Challenges may include dealing with existing InTouch windows, customer demands to keep certain data, avoiding duplicate data, managing workload effectively, considering budget constraints, interpreting ISA-101 guidelines, and making practical decisions while maintaining resource efficiency.
Answer: Exploring functionalities like tracking the date and time of the last full build and minor build, similar to the feature in Schneider, can provide insights into changes made by customers and help in working with the most recent information before implementing modifications.
Answer: While RSLogix / Studio 5000 may have functionalities like the Audit feature with a GSV, further exploration and understanding of its capabilities are needed to effectively track changes and unique identifiers in the project.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.