# Mitsubishi Q-Series PLC **URL:** \ **Category:** Ignition\ **Created:** [June 14, 2022, 6:50pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-q-series-plc/60758 "2022-06-14T18:50:11Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![JohnIrving](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/johnirving/32/37638_2.png) [@JohnIrving](https://forum.inductiveautomation.com/u/JohnIrving)\ **Post date:** [June 14, 2022, 6:50pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-q-series-plc/60758/1 "2022-06-14T18:50:11Z")
I would like to connect 2x Q-Series Q03UDECPU PLCs to an Ignition implementation. Neither of the racks have an Ethernet module, only the port on the CPU itself. I've found a few threads with various options, I'd like to confirm a few things: - [Ignition Driver](https://inductiveautomation.canny.io/ignition-features-and-ideas/p/mitsubishi-q-series-drivers) - in development but not available yet. Last update in 2019 - [Kepware Mitsubishi Ethernet Driver](https://www.kepware.com/en-us/products/kepserverex/drivers/mitsubishi-ethernet/) - Says in the description that it is for use with the Ethernet module cards, however several forum posters seem to have it working using the CPU on board ethernet, as well as [this Kepware KB article](https://www.kepware.com/en-us/support/knowledge-base/2010/connecting-to-the-ethernet-port-on-a-mitsubishi-q/) says its possible. The [manual](https://www.kepware.com/getattachment/3daf1ac3-5c76-49ce-bbfe-f0fb1015f6cc/mitsubishi-ethernet-manual.pdf) (p4) also states the onboard port can be used without much further explanation. - [MX-OPC](https://emea.mitsubishielectric.com/fa/products/cnt/plc/plceng/support_tools/mx-opc/mx-opc-server-da-v0700-1l0c-e.html#) - Mitsubishi OPC-DA Server. Not clear if this can communicate over onboard Ethernet port or if an additional module is required. May have benefit of not requiring additional PLC cards? So look like Kepware (or Matrikon has a similar mitsubishi driver) is going to be the way to go unless there is some change in status on the an Ignition device driver? May have answered my own question here but welcome any input in case I've missed something. Thanks. Some other threads where I gathered info from: > [@Ignition Mitsubishi Driver](https://forum.inductiveautomation.com/t/ignition-mitsubishi-driver/52740): > > Hello, I was wondering if anyone knew where IA was with development of a Mitsubishi driver? I have an upcoming project using a Mitsubishi PLC. Is there any release date posted yet? Thanks, Frank > [@Connecting to Mitsubishi](https://forum.inductiveautomation.com/t/connecting-to-mitsubishi/9306/12): > > Mitsubishi Q series aren’t too difficult to add to Kepware. If you have the QJ71E71-100 Ethernet module you’ll have to open up a port on that through the settings. In Kepware This is what you’ll have to put in for the ID: example: 192.168.0.10:N1:20 in the format of IPAddress:Network Number:Station Number Under Communication Parameters you’ll match the port number to what you used when you open the port in the QJ71 card: [image] QJ71E71-100 Settings: [image] [image] The second … > [@Ignition Communications with Mitsubishi PLC](https://forum.inductiveautomation.com/t/ignition-communications-with-mitsubishi-plc/51752): > > Hello All, Wondering what others have used with success to communicate to Mitsubishi PLCs. Here is some equipment below I will need to communicate with. R08CPU RD81OPC96 Regards, Frank ---
**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:** [June 14, 2022, 8:10pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-q-series-plc/60758/2 "2022-06-14T20:10:10Z")
> [@JohnIrving](#): > > So look like Kepware (or Matrikon has a similar mitsubishi driver) is going to be the way to go unless there is some change in status on the an Ignition device driver? May have answered my own question here but welcome any input in case I’ve missed something. Thanks. I'd go with Kepware right now. Our driver got sidelined while we finish the 61850 driver and if you can avoid dealing with OPC Classic (COM/DCOM/DA) you absolutely should. ---
**Author:** ![nathan.boeger](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nathan.boeger/32/87646_2.png) [@nathan.boeger](https://forum.inductiveautomation.com/u/nathan.boeger)\ **Post date:** [April 4, 2023, 3:54pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-q-series-plc/60758/3 "2023-04-04T15:54:25Z")
The Mitsubishi Driver is in Public Beta (using the 8.1.27 nightly) through April. The plan is for production release in 8.1.28 on May 30th, 2023. This is a "core driver", meaning it will be included for free as a part of the Ignition platform. > [@Mitsubishi Driver Beta Test Open Now! Test through April](https://forum.inductiveautomation.com/t/mitsubishi-driver-beta-test-open-now-test-through-april/71913): > > Beta Testing Context Thank you for helping test the native Ignition Mitsubishi drivers. This is a tight window (April) as we are aiming for production release in 8.1.28 (May 30th). Please provide feedback here as soon as you have it. Non-bug feature requests will be most actionable in the first few weeks of April. April 3rd. Beta Release. Set up your Mitsubishi hardware now! April - ~May 1st Beta Test Window. May 12th Code freeze for final QA/release (8.1.28). Changes must be complete. May 3…