# Erroneous Default Values Upon Mobile Launch

**URL:** <https://forum.inductiveautomation.com/t/erroneous-default-values-upon-mobile-launch/24759>\
**Category:** Ignition\
**Created:** [May 7, 2019, 5:42pm UTC](https://forum.inductiveautomation.com/t/erroneous-default-values-upon-mobile-launch/24759 "2019-05-07T17:42:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![cclose](https://avatars.discourse-cdn.com/v4/letter/c/278dde/32.png) [@cclose](https://forum.inductiveautomation.com/u/cclose)\
**Post date:** [May 7, 2019, 5:42pm UTC](https://forum.inductiveautomation.com/t/erroneous-default-values-upon-mobile-launch/24759/1 "2019-05-07T17:42:02Z")

</div>

On several of my projects, when the mobile client is opened, some of the components used to write values to a MODBUS device are automatically set to zero. Is there a way to prevent any components from writing a default value on startup?

---

<div class="post-metadata">

**Author:** ![cclose](https://avatars.discourse-cdn.com/v4/letter/c/278dde/32.png) [@cclose](https://forum.inductiveautomation.com/u/cclose)\
**Post date:** [May 7, 2019, 9:03pm UTC](https://forum.inductiveautomation.com/t/erroneous-default-values-upon-mobile-launch/24759/2 "2019-05-07T21:03:35Z")

</div>

After some fiddling I found the problem came from the “Property Change” event handler. After changing the process to a single button that sends all write requests at once, No erroneous values have occurred. So I’m still not sure what the original problem was, but everything is functioning as intended.

---

<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:** [May 8, 2019, 12:34pm UTC](https://forum.inductiveautomation.com/t/erroneous-default-values-upon-mobile-launch/24759/3 "2019-05-08T12:34:54Z")

</div>

> [@cclose](#):
>
> I’m still not sure what the original problem was

PropertyChange events are not like other events -- all properties for the component in question send their changes to the same handler. So the handler _ **must** _ check the propertyName to know what action to take, if any. And if you mess up the indentation, or forget to check at all, **boom** , all hell breaks loose.