# New DNP3 Module Read After Operate Not Working? **URL:** \ **Category:** Ignition\ **Created:** [March 11, 2024, 8:31pm UTC](https://forum.inductiveautomation.com/t/new-dnp3-module-read-after-operate-not-working/87157 "2024-03-11T20:31:08Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![edward.fowler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/edward.fowler/32/24179_2.png) [@edward.fowler](https://forum.inductiveautomation.com/u/edward.fowler)\ **Post date:** [March 11, 2024, 8:31pm UTC](https://forum.inductiveautomation.com/t/new-dnp3-module-read-after-operate-not-working/87157/1 "2024-03-11T20:31:08Z")
I'm not saying this setting isn't working, but I thought it would fix the issue. The issue is the value of my DNP3 analog output tag is always _one behind_. I have a test tag (memory) with a value changed script that writes the value to a DNP3 analog output (OPC item path) tag each time the test tag value changes. The value of the DNP3 analog output tag always shows the previous value. I know the output is working because I'm monitoring the address in the RTAC, it shows the same value as the test tag (so I know the output is working). Here's a little sequence if my previous explanation is poor. ```auto test tag value: 1, 2, 3, 4, 5, 6, 7, 8 DNP analog output tag: 1, 2, 3, 4, 5, 6, 7 RTAC tag: 1, 2, 3, 4, 5, 6, 7, 8 ``` The device configuration includes: Command Mode - DIRECT\_OPERATE Read After Operation - TRUE Is there something I'm missing in my configuration? Side note - this doesn't happen with the Legacy DNP3 driver and the same RTAC. Ignition v8.1.37 New DNP3 Module v1.1.38.2024030513 ---
**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:** [March 11, 2024, 8:33pm UTC](https://forum.inductiveautomation.com/t/new-dnp3-module-read-after-operate-not-working/87157/2 "2024-03-11T20:33:16Z")
Wireshark capture? Maybe the RTU takes a little too long to execute and the read-after-operate ends up reading the old value. 8.1.39 has a new setting to insert a configurable delay before the read-after-operate is issued. ---
**Author:** ![edward.fowler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/edward.fowler/32/24179_2.png) [@edward.fowler](https://forum.inductiveautomation.com/u/edward.fowler)\ **Post date:** [March 11, 2024, 9:11pm UTC](https://forum.inductiveautomation.com/t/new-dnp3-module-read-after-operate-not-working/87157/3 "2024-03-11T21:11:09Z")
I can't share the packet capture (need to keep the IPs hidden), but here are some screen shots. Apologies if its hard to follow. @Kevin.Herron It looks like you nailed it. What delay does the legacy driver use? When will 8.1.39 be released? The RTAC is an SEL-3505. Not an expert on this but I'll look for some settings. Thanks Kevin. * * * ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/0/4022c4a19df7d7c408bcee39265f3b5af535a96d.png) * * * ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/5/257056e616848ef0016b482609173ee2ca2fa4ab.png) * * * ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/e/fe784f67d78a1492eb511d5e99802850d8276a18.png) * * * ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/f/7f3ce056803c2fcada54a95bd4bfc93562278912.png) * * * ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/a/eaad8de98700310491693eb0ca1e0e0661483a93.png) * * * ---
**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:** [March 11, 2024, 9:22pm UTC](https://forum.inductiveautomation.com/t/new-dnp3-module-read-after-operate-not-working/87157/4 "2024-03-11T21:22:26Z")
The legacy driver doesn't issue an explicit read-after-operate, but it was probably explicitly polling that point as a consequence of how the legacy driver operated, so you eventually saw the update. The new driver is using class-based polling by default, and read-after-operate is a hack for outstations that don't generate an analog output event with the new value after the operation completes. ---
**Author:** ![Mark\_Phillips](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@Mark\_Phillips](https://forum.inductiveautomation.com/u/Mark_Phillips)\ **Post date:** [April 2, 2024, 10:14pm UTC](https://forum.inductiveautomation.com/t/new-dnp3-module-read-after-operate-not-working/87157/5 "2024-04-02T22:14:44Z")
Kevin, when is 8.1.39 scheduled to be released? I am having the same issue. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [April 2, 2024, 10:35pm UTC](https://forum.inductiveautomation.com/t/new-dnp3-module-read-after-operate-not-working/87157/6 "2024-04-02T22:35:31Z")
As soon as April 9th, though no sooner. ---
**Author:** ![Mark\_Phillips](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@Mark\_Phillips](https://forum.inductiveautomation.com/u/Mark_Phillips)\ **Post date:** [April 9, 2024, 9:00pm UTC](https://forum.inductiveautomation.com/t/new-dnp3-module-read-after-operate-not-working/87157/7 "2024-04-09T21:00:22Z")
Thanks! I am excited to test it out. ---
**Author:** ![Mark\_Phillips](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@Mark\_Phillips](https://forum.inductiveautomation.com/u/Mark_Phillips)\ **Post date:** [April 12, 2024, 4:47pm UTC](https://forum.inductiveautomation.com/t/new-dnp3-module-read-after-operate-not-working/87157/8 "2024-04-12T16:47:14Z")
Thanks! I set the "Read After Operate Delay (ms)" to 1000 ms for the analog output point and it's working well.