# Setpoint - Decimal places and Error out of bounds

**URL:** <https://forum.inductiveautomation.com/t/setpoint-decimal-places-and-error-out-of-bounds/117746>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [November 4, 2026, 8:53pm UTC](https://forum.inductiveautomation.com/t/setpoint-decimal-places-and-error-out-of-bounds/117746 "2026-11-04T20:53:03Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**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:** [November 4, 2026, 9:11pm UTC](https://forum.inductiveautomation.com/t/setpoint-decimal-places-and-error-out-of-bounds/117746/2 "2026-11-04T21:11:14Z")

</div>

This is almost certainly due to floating point fraction behaviors, since 0.9 doesn't have a precise binary representation. (Repeats in binary, much like ⅓ repeats as a decimal.)

Possibly exacerbated by this related phenomenon:

> [@Numeric Text Field - Float vs Double Issue](https://forum.inductiveautomation.com/t/numeric-text-field-float-vs-double-issue/117737/6):
>
> This is a known/accepted issue in Vision's numeric text field component; if you want to talk to support you can reference our internal ticket number IGN-11528. We're delegating the internal string -\> number type to an external library, and that external library goes from smallest -\> largest possible presentation, and 13.3 happens to be a value that can be (acceptably to the library, at least) represented in a 32-bit float, and therefore that's what is returned. Changing that logic in the numer…

---

_[View the full topic](https://forum.inductiveautomation.com/t/setpoint-decimal-places-and-error-out-of-bounds/117746)._