# Access to BACnet Property

**URL:** <https://forum.inductiveautomation.com/t/access-to-bacnet-property/43719>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [February 23, 2021, 12:20pm UTC](https://forum.inductiveautomation.com/t/access-to-bacnet-property/43719 "2021-02-23T12:20:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![s.imhof](https://avatars.discourse-cdn.com/v4/letter/s/439d5e/32.png) [@s.imhof](https://forum.inductiveautomation.com/u/s.imhof)\
**Post date:** [February 23, 2021, 12:20pm UTC](https://forum.inductiveautomation.com/t/access-to-bacnet-property/43719/1 "2021-02-23T12:20:25Z")

</div>

Hello together

I am having difficulty accessing individual BACnet properties in the Ignition Designer.  
In the concrete case it is about accessing the property of a binary input. The binary input is found in the OPC Tag Browser, but not all properties are displayed.

I have now tried to access the desired property with a manually created OPC Tag and a customized Tag Path which unfortunately did not work.

My manually created OPC tag with customized path for “Elapsed\_Active\_Time”.

 ![BACnet manual OPC Path](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/c/8c1d33ebab59b3114ec4bc3f26f12a8bc1a03512.png)

Has anyone had similar difficulties or have an idea how I could go further?

Well, I was able to access another property, Present Value, via a manually created OPC tag. What has confused me a bit now.

Thank you for your support!

---

<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:** [February 23, 2021, 1:32pm UTC](https://forum.inductiveautomation.com/t/access-to-bacnet-property/43719/2 "2021-02-23T13:32:00Z")

</div>

Many (most? all?) of the optional properties on the Objects supported by the driver are not supported. Support for this property would need to be added to the driver before it would attempt to access it.

---

<div class="post-metadata">

**Author:** ![s.imhof](https://avatars.discourse-cdn.com/v4/letter/s/439d5e/32.png) [@s.imhof](https://forum.inductiveautomation.com/u/s.imhof)\
**Post date:** [February 23, 2021, 1:44pm UTC](https://forum.inductiveautomation.com/t/access-to-bacnet-property/43719/3 "2021-02-23T13:44:21Z")

</div>

Thanks for the quick reply Kevin.  
I almost thought so, only I hoped that this only affects the BACnet objects.

By chance, are there any plans to expand the driver in the near future or is there already no demand for it?

Greetings Sven

---

<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:** [February 23, 2021, 1:51pm UTC](https://forum.inductiveautomation.com/t/access-to-bacnet-property/43719/4 "2021-02-23T13:51:39Z")

</div>

Extra properties can be added if there is demand, especially if they’re easier to support types like this one.

Eventually we are going to add some kind of broadcast discovery UI and, unrelated, explore making initialization of a device not require the who-Is / i-Am “handshake” and maybe not require the reading of segmentation / supported services. It’s a little tricky.