# The opc points change quickly in the tag browser, but some take a long time to change？ **URL:** \ **Category:** Ignition\ **Tags:** ignition80\ **Created:** [July 5, 2021, 3:42am UTC](https://forum.inductiveautomation.com/t/the-opc-points-change-quickly-in-the-tag-browser-but-some-take-a-long-time-to-change/48490 "2021-07-05T03:42:53Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![616958939](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/616958939/32/16900_2.png) [@616958939](https://forum.inductiveautomation.com/u/616958939)\ **Post date:** [July 5, 2021, 3:42am UTC](https://forum.inductiveautomation.com/t/the-opc-points-change-quickly-in-the-tag-browser-but-some-take-a-long-time-to-change/48490/1 "2021-07-05T03:42:53Z")
Hi, These points include the opc, expressions and the tag editor have set a 30-second acquisition frequency, but far away in the time from the last published value : ![pro](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/0/f01c35a3ed54d849fa62236a9f3f5a67c930d893.jpeg) ![prj](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/2/82cbdc0ce714a124a9e9644924884417b5a0f4f4.jpeg) I want all types of points to change quickly rather than a fixed value. The last published value should be time before 30s. Thank you ! ---
**Author:** ![jespinmartin1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jespinmartin1/32/57175_2.png) [@jespinmartin1](https://forum.inductiveautomation.com/u/jespinmartin1)\ **Post date:** [July 5, 2021, 5:25am UTC](https://forum.inductiveautomation.com/t/the-opc-points-change-quickly-in-the-tag-browser-but-some-take-a-long-time-to-change/48490/2 "2021-07-05T05:25:01Z")
The last published time should be 30s only if it actually changed its value within/after the scan. If value haven’t change after the scan time, then, the last published value won’t change. The scan happened but nothing was published. ---
**Author:** ![jespinmartin1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jespinmartin1/32/57175_2.png) [@jespinmartin1](https://forum.inductiveautomation.com/u/jespinmartin1)\ **Post date:** [July 5, 2021, 5:35am UTC](https://forum.inductiveautomation.com/t/the-opc-points-change-quickly-in-the-tag-browser-but-some-take-a-long-time-to-change/48490/3 "2021-07-05T05:35:26Z")
I just noticed something, you should not execute a runScript() in tags. Instead, create some gateway timer script, put your code there and write it to a memory tag. But with that big time scan, I think it’ll be ok, I’ll let someone else to give some option about this. ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [July 5, 2021, 9:05am UTC](https://forum.inductiveautomation.com/t/the-opc-points-change-quickly-in-the-tag-browser-but-some-take-a-long-time-to-change/48490/4 "2021-07-05T09:05:45Z")
Actually, runScript inside a tag is fine if the tag group is not used by other non-run-script tags. If you run it with other tags, then you risk your other tag update rates being affected ---
**Author:** ![616958939](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/616958939/32/16900_2.png) [@616958939](https://forum.inductiveautomation.com/u/616958939)\ **Post date:** [July 5, 2021, 9:34am UTC](https://forum.inductiveautomation.com/t/the-opc-points-change-quickly-in-the-tag-browser-but-some-take-a-long-time-to-change/48490/5 "2021-07-05T09:34:45Z")
The point(expression type) is calculated from the opc point with runScript(), either the opc point or the expression point changes slowly. I found that the opc point has changed but the expression point occurred earlier. Code: ```auto runScript("system.opc.readValue('ES', 'ns=2;s=MODBUSTCP1_1.DB_3P01_1.IC').getValue()") * pow(10, (runScript("system.opc.readValue('ES', 'ns=2;s=MODBUSTCP1_1.DB_3P01_1.UPT_IPT').getValue()") & 255) - 4) ``` ![pro1](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/9/893b1f59e95e32ba625922521de99b00b6e43183.jpeg) ![pro2](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/1/61a5c854e5aad5d4f5bb73e85a7e8c575b5f2992.jpeg) How can I do it to make these points look like real-time? ---
**Author:** ![616958939](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/616958939/32/16900_2.png) [@616958939](https://forum.inductiveautomation.com/u/616958939)\ **Post date:** [July 5, 2021, 10:32am UTC](https://forum.inductiveautomation.com/t/the-opc-points-change-quickly-in-the-tag-browser-but-some-take-a-long-time-to-change/48490/6 "2021-07-05T10:32:46Z")
I still don’t quite understand it Can it be in detail? ---
**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:** [July 5, 2021, 2:42pm UTC](https://forum.inductiveautomation.com/t/the-opc-points-change-quickly-in-the-tag-browser-but-some-take-a-long-time-to-change/48490/7 "2021-07-05T14:42:51Z")
Why are you using system.opc.read() instead of creating OPC tags to monitor these OPC items?