# DNP3 integration 32767 Value **URL:** \ **Category:** Ignition\ **Created:** [November 3, 2025, 2:15am UTC](https://forum.inductiveautomation.com/t/dnp3-integration-32767-value/111883 "2025-11-03T02:15:32Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![LCC](https://avatars.discourse-cdn.com/v4/letter/l/ccd318/32.png) [@LCC](https://forum.inductiveautomation.com/u/LCC)\ **Post date:** [November 3, 2025, 2:15am UTC](https://forum.inductiveautomation.com/t/dnp3-integration-32767-value/111883/1 "2025-11-03T02:15:32Z")
Hi All, I’m sure this an easy one for the right person! I’m integrating SEL protection relays via DNP3 into ignition and then passing to another SCADA system via OPC. The accumulative energy value has stalled at 32767, even though in the originating device it has continued to increase. Its currently reading as a Datatype: Double and OPC Item Path is ns=1;s=[{Device}]AnalogInput16 Any suggestions? thanks! ---
**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:** [November 3, 2025, 2:18am UTC](https://forum.inductiveautomation.com/t/dnp3-integration-32767-value/111883/2 "2025-11-03T02:18:07Z")
Signed integers in a 16-value can only hold values from -32768 to +32767. If the intervalue can go higher, then it must not be a 16-bit register. Seems like a design error to connect it through an AnalogInput16. ---
**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:** [November 3, 2025, 2:20am UTC](https://forum.inductiveautomation.com/t/dnp3-integration-32767-value/111883/3 "2025-11-03T02:20:42Z")
This probably means the point is configured in your outstation as variation 2 or 4 (16-bit). > [@pturmel](#): > > to connect it through an AnalogInput16. Pretty sure the 16 is just a coincidence here; it’s point/index 16. ---
**Author:** ![LCC](https://avatars.discourse-cdn.com/v4/letter/l/ccd318/32.png) [@LCC](https://forum.inductiveautomation.com/u/LCC)\ **Post date:** [November 3, 2025, 2:39am UTC](https://forum.inductiveautomation.com/t/dnp3-integration-32767-value/111883/4 "2025-11-03T02:39:19Z")
> [@Kevin.Herron](#): > > it’s point/index 16 Thanks gents, I’ve experienced this with Modbus, but I’m new to DNP3. I don’t think I have a lot of configuration options in the originating device as its not mine unfortunately! ---
**Author:** ![LCC](https://avatars.discourse-cdn.com/v4/letter/l/ccd318/32.png) [@LCC](https://forum.inductiveautomation.com/u/LCC)\ **Post date:** [November 3, 2025, 2:42am UTC](https://forum.inductiveautomation.com/t/dnp3-integration-32767-value/111883/5 "2025-11-03T02:42:06Z")
yes 16 is just a coincidence! register 16 on the Analog list... ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [November 3, 2025, 8:36am UTC](https://forum.inductiveautomation.com/t/dnp3-integration-32767-value/111883/6 "2025-11-03T08:36:25Z")
The sel guy we worked with had to divide the sel value by 10 in the dnp3 mapping for values that go above 32767 ---
**Author:** ![msteele](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/msteele/32/77889_2.png) [@msteele](https://forum.inductiveautomation.com/u/msteele)\ **Post date:** [November 3, 2025, 2:27pm UTC](https://forum.inductiveautomation.com/t/dnp3-integration-32767-value/111883/7 "2025-11-03T14:27:32Z")
If you have access to the relay, I’d suggest downloading SEL AcSELerator QuickSet (free with a [selinc.com](http://selinc.com) account) and see if you can read the settings file from the meter, and look at the configuration for your DNP3 connection(s).