Hi Jooyoung, Welcome, obviously reach out if you have any questions :)
If you're working with mspec files there's now a plugin for Intellij and vscode, which may come in handy. https://plugins.jetbrains.com/plugin/28936-toddysoft-mspec-language-support https://marketplace.visualstudio.com/items?itemName=hutcheb.mspec-dsl-support Kind Regards Ben On Sat, Jun 6, 2026 at 5:43β―AM ott.lukas.murena.io via dev <[email protected]> wrote: > > Hi Jooyoung, > > Welcome to the PLC4X Community, really happy to see a new developer on the > mailing list and awesome to see someone starting to work on a first > Mitsubishi Driver. > > π > > Cheers, > Lukas > > Am 5. Juni 2026 13:24:45 MESZ schrieb Christofer Dutz > <[email protected]>: > >Hi Jooyoung, > > > >Glad to have you here β¦ always happy about people actually willing to > >contribute π > > > >If you run into any general questions, feel free to ask here and weβll do > >your best to answer them as quickly as possible π > > > >Chris > > > > > >Von: μ μ£Όμ <[email protected]> > >Datum: Freitag, 5. Juni 2026 um 11:20 > >An: [email protected] <[email protected]> > >Betreff: Introduction + SLMP, MELSEC-Communication 3E, read-only driver > > > >Hi all, > > > >I'm Jooyoung Jung (GitHub: LivingLikeKrillin). My background is in > >industrial connectivity gateways β OPC UA and PLC protocols (S7, Modbus, > >and the Mitsubishi MELSEC / MC family, which I've implemented and run in > >production). Chris suggested I bring things over to the list, so β > >introducing myself. > > > >I'm working on a read-only SLMP (MELSEC-Communication, 3E binary frame) > >driver; PLC4X doesn't have a Mitsubishi driver yet. It's proposed in #2585 ( > >https://github.com/apache/plc4x/issues/2585). I've started mspec-first: an > >slmp.mspec for the 3E Batch Read frame from the public SH-080008 manual, > >plus a ParserSerializer suite. I'll validate it against a real 3E capture > >before calling the wire layer done. > > > >Chris flagged that the SPI rewrite changes how the root type declares > >encoding defaults, so I'll keep the mspec on current develop for now and > >build the driver logic on the new SPI once it merges. Happy to early-adopt > >the new SPI for SLMP and report back anything I hit β point me at > >whatever's useful. > > > >Separately, I've got a smaller item ready in plc4x-extras β upgrading the > >opcua-server tool from Milo 0.6.16 to 1.1.3 (#700, which Chris welcomed) β > >and will open that PR shortly. > > > >Thanks, > >Jooyoung
