# Ignition Tags Not Matching S7-400 Output Addresses **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [December 1, 2022, 10:06pm UTC](https://forum.inductiveautomation.com/t/ignition-tags-not-matching-s7-400-output-addresses/67165 "2022-12-01T22:06:54Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![mbturner94](https://avatars.discourse-cdn.com/v4/letter/m/d78d45/32.png) [@mbturner94](https://forum.inductiveautomation.com/u/mbturner94)\ **Post date:** [December 1, 2022, 10:06pm UTC](https://forum.inductiveautomation.com/t/ignition-tags-not-matching-s7-400-output-addresses/67165/1 "2022-12-01T22:06:54Z")
Hi, The IO I am reading is Q216.6 and Q216.7. Addressed like so using Ignitions driver, [Device Name]QX216.6 Tag diagnostics and gateway logs are not showing any issues, yet the tags are intermittently turning off and back on yet the outputs do not change state in the PLC. ![2022-12-02 07_59_15](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/d/8d413eb6eedb516d373caddac62a3758571cecff.jpeg) ![2022-12-02 07_58_49](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/0/a0f1f091351808c4bc409a72230604cd83caa31f.jpeg) This is also happening with other output addresses in the 210.x and 211.x ranges. The tags are read only in ignition and nothing is attempting to write to them. Cheers Matt ---
**Author:** ![Kfoldesi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kfoldesi/32/11327_2.png) [@Kfoldesi](https://forum.inductiveautomation.com/u/Kfoldesi)\ **Post date:** [December 5, 2022, 2:30pm UTC](https://forum.inductiveautomation.com/t/ignition-tags-not-matching-s7-400-output-addresses/67165/2 "2022-12-05T14:30:05Z")
It may be that the PLC bit is off for 1 scan, and you can't see it flicker in the VAT table. Add a line of code that sets an M bit when Q216.6 is off. The Ignition Tag updates less frequently and if it catches the bit off every once in a while it will display that off for the 'update time' probably 1 second... ---
**Author:** ![mbturner94](https://avatars.discourse-cdn.com/v4/letter/m/d78d45/32.png) [@mbturner94](https://forum.inductiveautomation.com/u/mbturner94)\ **Post date:** [December 5, 2022, 9:41pm UTC](https://forum.inductiveautomation.com/t/ignition-tags-not-matching-s7-400-output-addresses/67165/3 "2022-12-05T21:41:57Z")
I have just test this with the below logic and confident the output is on continuously. Observed the output flicker in Ignition while the latch is not being set. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/4/b4d7c263bc52298d6b6b8596072c8bfaafa94b2c.png) ---
**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:** [December 6, 2022, 1:01am UTC](https://forum.inductiveautomation.com/t/ignition-tags-not-matching-s7-400-output-addresses/67165/4 "2022-12-06T01:01:27Z")
Looks like a bug. You should create a support ticket. (This forum is **not** support.) ---
**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:** [December 6, 2022, 1:04am UTC](https://forum.inductiveautomation.com/t/ignition-tags-not-matching-s7-400-output-addresses/67165/5 "2022-12-06T01:04:37Z")
> [@mbturner94](#): > > Observed the output flicker in Ignition while the latch is not being set. Can you get a Wireshark capture of the comms between Ignition and the PLC while one of these "flickers" occur? Support can help you with this if you're not comfortable doing it on your own. ---
**Author:** ![mbturner94](https://avatars.discourse-cdn.com/v4/letter/m/d78d45/32.png) [@mbturner94](https://forum.inductiveautomation.com/u/mbturner94)\ **Post date:** [December 6, 2022, 3:12am UTC](https://forum.inductiveautomation.com/t/ignition-tags-not-matching-s7-400-output-addresses/67165/6 "2022-12-06T03:12:39Z")
I contacted iControls Brisbane, they walked me through the Wireshark capture and will be creating the support ticket. ---
**Author:** ![mbturner94](https://avatars.discourse-cdn.com/v4/letter/m/d78d45/32.png) [@mbturner94](https://forum.inductiveautomation.com/u/mbturner94)\ **Post date:** [December 14, 2022, 12:07am UTC](https://forum.inductiveautomation.com/t/ignition-tags-not-matching-s7-400-output-addresses/67165/7 "2022-12-14T00:07:12Z")
Resolved the issue. The addresses are profibus coupler addresses. Another area of the program moves data block bits to these output addresses. This block move does not show in a cross reference making it appear like the outputs were only being written once. Quick patch up of the program and everything works ok. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/7/b7d5b5baadba3df539d9cde088f31f2f3cfa3f77.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/9/f93e07c0e0b8e2abf9a2ebc9568ed13a20cede5a.png)