# How to avoid error on popup when setpoint values are out of my control? **URL:** \ **Category:** Ignition\ **Tags:** vision, ignition81\ **Created:** [June 29, 2025, 1:23pm UTC](https://forum.inductiveautomation.com/t/how-to-avoid-error-on-popup-when-setpoint-values-are-out-of-my-control/107913 "2025-06-29T13:23:30Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![tiim](https://avatars.discourse-cdn.com/v4/letter/t/f9ae1b/32.png) [@tiim](https://forum.inductiveautomation.com/u/tiim)\ **Post date:** [June 29, 2025, 1:23pm UTC](https://forum.inductiveautomation.com/t/how-to-avoid-error-on-popup-when-setpoint-values-are-out-of-my-control/107913/1 "2025-06-29T13:23:30Z")
Hi again! Today, my first roadblock is I have a PLC where neither the programmer or operator has set their alarm setpoints to a reasonable value, for, say... most of the tags! Worse, there are absolutely NO BOUNDS on the PanelView setpoint ranges, a huge oversight (or sheer laziness) IMHO. Everything is happily default: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/5/c595a3d4e1a157b4c559f8a56380a05e606f323b.png) Yikes... ANYWAY, I tried setting the property of the setpoint input field in Ignition to disabled when the alarm setpoint is disabled, however, I keep getting the error: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/a/fa8973b1f8a76b44f5e3e94e69648879737ddc0d.png) Is there a script I can write, and where, to avoid this on my popup? I am using UDT, and if I can program something in there, maybe that is a better option. Thanks! ---
**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:** [June 29, 2025, 1:59pm UTC](https://forum.inductiveautomation.com/t/how-to-avoid-error-on-popup-when-setpoint-values-are-out-of-my-control/107913/2 "2025-06-29T13:59:28Z")
> [@tiim](#): > > there are absolutely NO BOUNDS on the PanelView setpoint ranges Then you cannot enforce bounds in Ignition with the built-in features. You must **check** for out-of-bounds yourself, highlight in your UI where that is true, and prevent "save" or "write" from pushing the invalid value back to the PLC. And yes, you **won't** be able to bidirectionally bind from entry field to tag. ---
**Author:** ![tiim](https://avatars.discourse-cdn.com/v4/letter/t/f9ae1b/32.png) [@tiim](https://forum.inductiveautomation.com/u/tiim)\ **Post date:** [June 29, 2025, 2:23pm UTC](https://forum.inductiveautomation.com/t/how-to-avoid-error-on-popup-when-setpoint-values-are-out-of-my-control/107913/3 "2025-06-29T14:23:17Z")
I mark the numeric entry as disabled if the alarm itself is disabled, but that doesn't stop an error from being thrown anyway. May I prevent the value from being bound using an expression, rather than an indirect tag binding? Would that even stop the error? It's a frustrating first project. I usually program the PLCs, and this would not happen under my watch. ---
**Author:** ![tiim](https://avatars.discourse-cdn.com/v4/letter/t/f9ae1b/32.png) [@tiim](https://forum.inductiveautomation.com/u/tiim)\ **Post date:** [June 29, 2025, 3:10pm UTC](https://forum.inductiveautomation.com/t/how-to-avoid-error-on-popup-when-setpoint-values-are-out-of-my-control/107913/4 "2025-06-29T15:10:10Z")
What I did to avoid errors, was to paste the insane High and Low default bounds number on my four alarm setpoint numeric fields, under Max and Min Value.. (for those following this, the number is + or - 150,000,000,274,887,790,000,000,000,000,000,000,000.0) I set each default Ignition Numeric Entry field type to Float and default value of 0.0 Now the error does not show. HOWEVER, the programmer really must fix this, it's insanity...