# Mitsubishi addressing **URL:** \ **Category:** Ignition\ **Created:** [July 24, 2024, 8:30pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-addressing/93705 "2024-07-24T20:30:30Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Ethan8558](https://avatars.discourse-cdn.com/v4/letter/e/f07891/32.png) [@Ethan8558](https://forum.inductiveautomation.com/u/Ethan8558)\ **Post date:** [July 24, 2024, 8:30pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-addressing/93705/1 "2024-07-24T20:30:30Z")
Hello, Sorry if I'm not understanding the documentation correctly but I'm having an issue addressing ZR registers. I have a Mitsubishi Q ethernet module connected to Ignition using the native Mitsubishi TCP driver. When creating tags in Ignition I'm unable to address the ZR register. In the Ignition documentation it seems to state that this register is inaccessible for a Q series device. Is this correct? Or am I misunderstanding? Thanks in advance! ---
**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:** [July 24, 2024, 8:52pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-addressing/93705/2 "2024-07-24T20:52:03Z")
Yes, what the documentation is implying and driver implementation is enforcing. I'm trying to find some more information about why that is. There's something in the MELSEC spec: > The file register specified to "Use File Register of Each Program" in "CPU Parameter" or "PLC parameter" of the CPU module > cannot be accessed from external devices. But I'm not quite sure what this means or if this is why we didn't allow that address. ---
**Author:** ![ktran](https://avatars.discourse-cdn.com/v4/letter/k/ecae2f/32.png) [@ktran](https://forum.inductiveautomation.com/u/ktran)\ **Post date:** [July 25, 2024, 10:39pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-addressing/93705/3 "2024-07-25T22:39:20Z")
I looked more into this and confirmed the ZR register can indeed be accessed. Currently the driver disallows the ZR keyword when parsing addresses for Q and L series devices due to oversight. I'll create an internal bug ticket for this. ---
**Author:** ![Ethan8558](https://avatars.discourse-cdn.com/v4/letter/e/f07891/32.png) [@Ethan8558](https://forum.inductiveautomation.com/u/Ethan8558)\ **Post date:** [August 12, 2024, 9:53pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-addressing/93705/4 "2024-08-12T21:53:37Z")
Sorry for the delayed response. If this was fixed, I'm guessing we wouldn't know until the next version update. At that point it'd be mentioned in the release notes, correct? This fix would help our team a ton, so it'd be nice to know if/when it gets resolved. ---
**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:** [August 12, 2024, 9:55pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-addressing/93705/5 "2024-08-12T21:55:40Z")
Yes it will be in the release notes. You can also open a ticket with support and ask to be notified when this is fixed. Internally it's referred to as IGN-10455, support will need that information. ---
**Author:** ![Ethan8558](https://avatars.discourse-cdn.com/v4/letter/e/f07891/32.png) [@Ethan8558](https://forum.inductiveautomation.com/u/Ethan8558)\ **Post date:** [August 12, 2024, 9:57pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-addressing/93705/6 "2024-08-12T21:57:30Z")
Thank you so much! ---
**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:** [August 12, 2024, 9:59pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-addressing/93705/7 "2024-08-12T21:59:43Z")
It was too late to make it into the upcoming 8.1.43 release, but it looks like a quick/easy fix that can be done for 8.1.44.