# \[Feature-13738\] offset with more operation in opc address

**URL:** <https://forum.inductiveautomation.com/t/feature-13738-offset-with-more-operation-in-opc-address/23101>\
**Category:** Ignition Early Access\
**Created:** [March 6, 2019, 7:04pm UTC](https://forum.inductiveautomation.com/t/feature-13738-offset-with-more-operation-in-opc-address/23101 "2019-03-06T19:04:11Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\
**Post date:** [March 6, 2019, 7:04pm UTC](https://forum.inductiveautomation.com/t/feature-13738-offset-with-more-operation-in-opc-address/23101/1 "2019-03-06T19:04:11Z")

</div>

In Ignition 7.9, when can use offset for computing address,  
We encounter many case where the offset is not +X but something like  
**DataPoint{BaseAddress + ( {ParamNum} \* X)}**

**Ignition 7.9 doc :**

OPC Item Path: `DataPoint{BaseAddress}`

##### Offset

Imagine that our data type had three fields, and these were laid out sequentially in the device.  
Instead of specifying each address for each Tag, we can simply offset from the base address:  
Member 1: `DataPoint{BaseAddress+0}`  
Member 2: `DataPoint{BaseAddress+1}`  
Member 3: `DataPoint{BaseAddress+2}`

---

<div class="post-metadata">

**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\
**Post date:** [April 4, 2019, 5:28pm UTC](https://forum.inductiveautomation.com/t/feature-13738-offset-with-more-operation-in-opc-address/23101/2 "2019-04-04T17:28:57Z")

</div>

Hi,

This has been requested many times over the years. Really we should support all mathematical operators in that syntax, and sub grouping with parentheses. I’ll see what we can do.

---

<div class="post-metadata">

**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\
**Post date:** [April 4, 2019, 7:24pm UTC](https://forum.inductiveautomation.com/t/feature-13738-offset-with-more-operation-in-opc-address/23101/3 "2019-04-04T19:24:11Z")

</div>

Thanks @Colby.Clegg, I hope this ticket will have a good seat in one of the first train-car of the new release train 🚂🚆🚆🚆

---

<div class="post-metadata">

**Author:** ![Paul.Scott](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul.scott/32/4578_2.png) [@Paul.Scott](https://forum.inductiveautomation.com/u/Paul.Scott)\
**Post date:** [June 28, 2019, 5:45pm UTC](https://forum.inductiveautomation.com/t/feature-13738-offset-with-more-operation-in-opc-address/23101/4 "2019-06-28T17:45:57Z")

</div>

In the interest of posterity, the 8.0.3 nightly build uploaded on the 27th added support for these missing operators.

---

<div class="post-metadata">

**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\
**Post date:** [June 28, 2019, 6:02pm UTC](https://forum.inductiveautomation.com/t/feature-13738-offset-with-more-operation-in-opc-address/23101/5 "2019-06-28T18:02:44Z")

</div>

👏👏👏Thanks a lot !
