I have inquired about this issue previously, but I still have not been able to find a solution. It is challenging for me to visualize a resolution. The local RTU has a screen where a few setpoints can be adjusted. In the past, all modifications were made locally using the OI. Now, the Main Plant also wishes to have control over these setpoints via telemetry. How can this be accomplished? The challenge arises when the Telemetry package contains outdated setpoints, which will automatically overwrite the local ones during each poll. Additionally, the Main Plant will not be aware of any changes to the setpoints unless they are manually read back. One possible approach involves implementing a complex readback method that involves multiple reads and writes to each location. Another option could be to allocate one set of setpoints to a specific array location and store the local setpoints elsewhere, utilizing a selector at the local site to determine which setpoint to utilize. However, these options may introduce unnecessary complications. I am hopeful that there is a simpler technique that I have not yet considered. It is likely that I am not the only one facing this dilemma.
In order to clearly identify the owner of the setpoint, it is essential to have a designated tag for this purpose. The Operational Interface (OI) is responsible for determining whether the setpoint is set to local or remote ownership. Additionally, distinct tags such as localSetpoint and remoteSetpoint are required. The OI controls the local setpoint while the Distributed Control System (DCS) manages the remote setpoint. The system's logic determines which value is written into the actualSetpoint based on the ownership status of the setpoint.
Yes, that's precisely what I'm trying to prevent - consistently being in the incorrect setting. I aim to reach each specific setpoint from both ends. Will I need to retrieve these values at the facility in order to successfully achieve this?
Have you thought about implementing a system that logs the time whenever a setpoint is adjusted on the local Operator Interface? This timestamp can then be included in a telemetry change request when sent, ensuring that the request is processed in a timely manner. The local SCADA or PLC can verify the request timestamp against the current timestamp, updating the setpoint only if the request is at least 10 seconds newer. You may also choose to send a confirmation message to the remote operators, advising them to retry the update if no change is seen after 20 seconds. This protocol can improve efficiency and accuracy in your control system operations.
It seems like you might have a promising idea there. I never considered utilizing timestamps before.
Dealing with timestamps can be a challenge when working with integer registers.
It sounds like your main concern is ensuring the two locations—Main Plant and local RTU—are constantly updated with the correct setpoints. From your description, it seems you're on the right track with considering different storage options for each setpoint. However, you might want to explore leveraging a networked solution that updates both setpoints in real-time, minimizing any discrepancies. This requires a robust network infrastructure but can streamline your process significantly. You could also look into utilizing a master-slave or producer-consumer architecture, where the Main Plant acts as the master/producer, controlling the data transfer. This way, the control could remain at the Main Plant but still allow for local adjustments as needed—essentially combining your two methods. Remember, the best solution often lies in balancing control, practicality, and cost-effectiveness.
âś… 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: Answer: One possible solution could involve implementing a readback method that involves multiple reads and writes to each location, or allocating setpoints to specific array locations and utilizing a selector at the local site to determine which setpoint to use.
Answer: Answer: The challenge arises when the Telemetry package contains outdated setpoints, which can automatically overwrite the local setpoints during each poll. Additionally, the Main Plant may not be aware of any changes to the setpoints unless they are manually read back.
Answer: Answer: While complex readback methods and using array locations for setpoints are options, there may be simpler techniques that have not been considered yet. It is worth exploring alternative approaches to find a more straightforward solution to this dilemma.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.