# \[Bug - 16356\]Derived Tags for Bit usage

**URL:** <https://forum.inductiveautomation.com/t/bug-16356-derived-tags-for-bit-usage/34007>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [April 17, 2020, 1:30pm UTC](https://forum.inductiveautomation.com/t/bug-16356-derived-tags-for-bit-usage/34007 "2020-04-17T13:30:06Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [April 20, 2020, 2:25pm UTC](https://forum.inductiveautomation.com/t/bug-16356-derived-tags-for-bit-usage/34007/6 "2020-04-20T14:25:17Z")

</div>

There seems to be a bug in the UDT parameter stuff right now that causes them to resolve as float/doubles, which in the case of these Modbus tags is turning the address from something that would be for a register, e.g. `[Device]HR1` into something for a bit write, e.g. `[Device]HR1.0`.

This was supposed to be fixed in the 8.0.11 release but there’s apparently some case or cases that are still broken.

I think it’s the same thing as is happening in this post: [[BUG]8.0.11-rc1 Numeric UDT parameters now appear as floats when used in OPC\_Item\_Path](http://forum.inductiveautomation.com/t/bug-8-0-11-rc1-numeric-udt-parameters-now-appear-as-floats-when-used-in-opc-item-path/33600/5)

---

_[View the full topic](https://forum.inductiveautomation.com/t/bug-16356-derived-tags-for-bit-usage/34007)._