# BACnet/IP positive-integer-value data type (Ignition Edge IIoT 8.3.6)

**URL:** <https://forum.inductiveautomation.com/t/bacnet-ip-positive-integer-value-data-type-ignition-edge-iiot-8-3-6/117480>\
**Category:** Ignition\
**Created:** [October 14, 2026, 2:39pm UTC](https://forum.inductiveautomation.com/t/bacnet-ip-positive-integer-value-data-type-ignition-edge-iiot-8-3-6/117480 "2026-10-14T14:39:57Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ehenigin](https://avatars.discourse-cdn.com/v4/letter/e/49beb7/32.png) [@ehenigin](https://forum.inductiveautomation.com/u/ehenigin)\
**Post date:** [October 14, 2026, 2:39pm UTC](https://forum.inductiveautomation.com/t/bacnet-ip-positive-integer-value-data-type-ignition-edge-iiot-8-3-6/117480/1 "2026-10-14T14:39:57Z")

</div>

In Ignition Designer when I try to poll a "positive-integer-value" point I get error `Bad_NodeIdUnknown`. For example OPC Item Path `ns=1;s=[{DeviceName}]PositiveIntegerValue371.Present_Value`

Is it as simple as Ignition Designer or Ignition Edge IIoT just doesn't support that data type? Or is there a way to make it work? I did some googling and came up empty handed. Claude says:

> The “primitive value” objects added in BACnet 135-2008 are newer. That group includes IntegerValue (45), LargeAnalogValue (46), PositiveIntegerValue (48) and CharacterStringValue (40). Ignition hasn’t supported them consistently: they often don’t appear when you browse a device, even when the controller lists them in its Object\_List. Edge IIoT uses the same driver as full Ignition, so it behaves the same way.

I don't know if Claude's right or where I might find official documentation on that topic...

---

<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:** [October 14, 2026, 2:55pm UTC](https://forum.inductiveautomation.com/t/bacnet-ip-positive-integer-value-data-type-ignition-edge-iiot-8-3-6/117480/2 "2026-10-14T14:55:05Z")

</div>

That point type isn't supported, but you might be able to read a value using [system.bacnet.readRaw | Ignition User Manual](https://docs.inductiveautomation.com/docs/8.3/appendix/scripting-functions/system-bacnet/system-bacnet-readRaw)

Maybe something like (untested):

```python
value = system.bacnet.readRaw(
    "DeviceName",
    system.bacnet.enumerated.ObjectType.positiveIntegerValue,
    371,
    system.bacnet.enumerated.PropertyIdentifier.presentValue
)

```

---

<div class="post-metadata">

**Author:** ![ehenigin](https://avatars.discourse-cdn.com/v4/letter/e/49beb7/32.png) [@ehenigin](https://forum.inductiveautomation.com/u/ehenigin)\
**Post date:** [October 14, 2026, 3:00pm UTC](https://forum.inductiveautomation.com/t/bacnet-ip-positive-integer-value-data-type-ignition-edge-iiot-8-3-6/117480/3 "2026-10-14T15:00:32Z")

</div>

Thanks, I'll check out the readRaw approach.

Any plans to add support for it?

---

<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:** [October 14, 2026, 3:05pm UTC](https://forum.inductiveautomation.com/t/bacnet-ip-positive-integer-value-data-type-ignition-edge-iiot-8-3-6/117480/4 "2026-10-14T15:05:38Z")

</div>

I'll let the PM know, we can probably include this in the upcoming BACnet work we're doing. Support for objects like this (as opposed to complex objects like a schedule) should be pretty trivial...

---

<div class="post-metadata">

**Author:** ![ehenigin](https://avatars.discourse-cdn.com/v4/letter/e/49beb7/32.png) [@ehenigin](https://forum.inductiveautomation.com/u/ehenigin)\
**Post date:** [October 14, 2026, 3:10pm UTC](https://forum.inductiveautomation.com/t/bacnet-ip-positive-integer-value-data-type-ignition-edge-iiot-8-3-6/117480/5 "2026-10-14T15:10:44Z")

</div>

That would be great, I've run into a handful of these points lately that I'd love to be reading without jumping through hoops