# Is it possible to set an OPC tag to "manual" or "off scan" temporarily so that an operator could overwrite the value? **URL:** \ **Category:** Ignition\ **Created:** [February 16, 2023, 10:42pm UTC](https://forum.inductiveautomation.com/t/is-it-possible-to-set-an-opc-tag-to-manual-or-off-scan-temporarily-so-that-an-operator-could-overwrite-the-value/69980 "2023-02-16T22:42:04Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![tgish](https://avatars.discourse-cdn.com/v4/letter/t/34f0e0/32.png) [@tgish](https://forum.inductiveautomation.com/u/tgish)\ **Post date:** [February 16, 2023, 10:42pm UTC](https://forum.inductiveautomation.com/t/is-it-possible-to-set-an-opc-tag-to-manual-or-off-scan-temporarily-so-that-an-operator-could-overwrite-the-value/69980/1 "2023-02-16T22:42:04Z")
In our current system, the operators can set a tag to Manual, then force a value. The tag won't update from the PLC and holds the manual value until they set it back to automatic. We use this when they are calibrating analyzers so that the false values won't get sent to the historian and mess up the monthly reports. Trying to figure out a way to replicate this in Ignition and can't find it. The "enable" is no good as that sets a null value. Any ideas? ---
**Author:** ![franklepkowski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/franklepkowski/32/4808_2.png) [@franklepkowski](https://forum.inductiveautomation.com/u/franklepkowski)\ **Post date:** [February 17, 2023, 1:16am UTC](https://forum.inductiveautomation.com/t/is-it-possible-to-set-an-opc-tag-to-manual-or-off-scan-temporarily-so-that-an-operator-could-overwrite-the-value/69980/2 "2023-02-17T01:16:13Z")
Can you further explain the use case? Doing this makes little sense to me. So in manual they type in a value that does not go anywhere? Then they go back to auto and the value reverts to the tag Value in the Plc? You also mentioned values won’t go to the historian. If it is an Ignition system using Ignition historian the tag value will still go to historian in auto or manual, it doesn’t care if the tag is an opc tag or memory tag. If tag is set to be historized it will be logged either way. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [February 17, 2023, 1:46am UTC](https://forum.inductiveautomation.com/t/is-it-possible-to-set-an-opc-tag-to-manual-or-off-scan-temporarily-so-that-an-operator-could-overwrite-the-value/69980/3 "2023-02-17T01:46:15Z")
Technically, you could change the value source to memory with `system.tag.configure()`. The OPC props would still be there, so when you then use `system.tag.configure()` to change the value source back to "opc", it will pick right back up again. That said, it isn't really recommended, as it can disturb other tags in the group as the group's OPC subscription is re-optimized. ---
**Author:** ![bschroeder](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bschroeder/32/13260_2.png) [@bschroeder](https://forum.inductiveautomation.com/u/bschroeder)\ **Post date:** [February 17, 2023, 12:28pm UTC](https://forum.inductiveautomation.com/t/is-it-possible-to-set-an-opc-tag-to-manual-or-off-scan-temporarily-so-that-an-operator-could-overwrite-the-value/69980/4 "2023-02-17T12:28:07Z")
You may want to do this in the PLC rather than the SCADA side. We have that option for our AIn and DIn blocks, but it is PLC concentric rather than SCADA. ---
**Author:** ![tgish](https://avatars.discourse-cdn.com/v4/letter/t/34f0e0/32.png) [@tgish](https://forum.inductiveautomation.com/u/tgish)\ **Post date:** [February 21, 2023, 3:01pm UTC](https://forum.inductiveautomation.com/t/is-it-possible-to-set-an-opc-tag-to-manual-or-off-scan-temporarily-so-that-an-operator-could-overwrite-the-value/69980/5 "2023-02-21T15:01:24Z")
> [@franklepkowski](#): > > So in manual they type in a value that does not go anywhere? Sorry, I worded that poorly. It goes to the Historian. So the historian records the flatlined value (or manually inputted value) instead of recording the false spike caused by calibration. Otherwise, they would have to spend a lot of time manually correcting the reports to weed out the calibration spikes. ---
**Author:** ![tgish](https://avatars.discourse-cdn.com/v4/letter/t/34f0e0/32.png) [@tgish](https://forum.inductiveautomation.com/u/tgish)\ **Post date:** [February 21, 2023, 3:05pm UTC](https://forum.inductiveautomation.com/t/is-it-possible-to-set-an-opc-tag-to-manual-or-off-scan-temporarily-so-that-an-operator-could-overwrite-the-value/69980/6 "2023-02-21T15:05:02Z")
Hmm, this is a good point. Looks like we will have to go this route. Our project scope doesn't include PLC programming, so we'll be over budget, but looks like there is no way around it. If the PLC is "holding" a value, presumably based on a bit called "analyzer in manual", Can the operator still overwrite that value somehow even if it is an OPC tag? or do you use a separate OPC address for the "manual value" versus the analog I/O value and then have the PLC select between them? ---
**Author:** ![tgish](https://avatars.discourse-cdn.com/v4/letter/t/34f0e0/32.png) [@tgish](https://forum.inductiveautomation.com/u/tgish)\ **Post date:** [February 21, 2023, 3:06pm UTC](https://forum.inductiveautomation.com/t/is-it-possible-to-set-an-opc-tag-to-manual-or-off-scan-temporarily-so-that-an-operator-could-overwrite-the-value/69980/7 "2023-02-21T15:06:18Z")
Ok, Thanks. We'll keep this as a last resort. ---
**Author:** ![bschroeder](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bschroeder/32/13260_2.png) [@bschroeder](https://forum.inductiveautomation.com/u/bschroeder)\ **Post date:** [February 21, 2023, 5:06pm UTC](https://forum.inductiveautomation.com/t/is-it-possible-to-set-an-opc-tag-to-manual-or-off-scan-temporarily-so-that-an-operator-could-overwrite-the-value/69980/8 "2023-02-21T17:06:42Z")
We have a couple of different levels. Our digital block and analog block though both have 3 different levels of data in this order of hierarchy: Raw Value Raw Simulated Value EU Substitute Value Each analog and digital block has an option if that value can be substituted or not. That way values that are critical to safety, ie E-Stop, Disconnects etc... cannot be overridden by the operator. In regards to OPC, the Operator writes to a substitute value tag, and then the PLC will either use that or discard that based on whether substitute is enabled and available for that device. Then the value actually shows on the screen is the final value that comes out of the block. Also, the value that is used int the PLC is also this final value, which makes it nice if a downstream process depends on that value to operate properly. IE a tank level, temperature, etc...