I don't think I explained my point clearly enough. I am not asking for the old driver to be supported indefinitely. I was only describing the current state of my small application and my experience as an integrator.
I am actually in favour of removing duplication, so I have no objection to deprecating and eventually removing mesa_modbus. My point was rather about the users of the old driver. I suspect there will be quite a large number of existing configurations using mesa_modbus, especially because the old approach is still presented in tutorials and documentation without making it obvious that it is now obsolete. Users who want to keep using the old driver can of course stay with LinuxCNC 2.9 indefinitely. But for users moving to a newer LinuxCNC version, I think it is important to clearly communicate that mesa_modbus has reached the end of its life and that hm2_modbus is its replacement. So my concern is not keeping the old driver alive. It is making the migration path clear and visible to the existing user base. -- S pozdravem Zdeněk Zdražil ---------- Původní e‑mail ---------- Od: Bertho Stultiens <[email protected]> Komu: [email protected] Datum: 13. 8. 2026 13:43:45 Předmět: Re: [Emc-users] Deprecating the old mesa_modbus / modcompile driver "On 8/13/26 1:22 PM, Luca Toniolo wrote: > I can send PR to make `hm2_modbus` more portable There is a PR in the pipeline that does away with the absolute path message. The old mesa_modbus driver is very rigid and completely inflexible. It cannot have multiple devices on the same bus. It does not support endian swaps or different sized types, nor can it perform modbus device initialization or have different speed devices on the same bus. All these problems, and a lot more, have been solved with the hm2_modbus driver. The old driver has been superseded for (more than) 12 months now. >> However, from my point of view I don't really see a benefit of `hm2_ modbus` >> over the old solution yet. It works for me, but I don't see a feature >> that would make me prefer it over the old driver. Does that mean we need to support the old driver ad infinitum because your use case has no advantage? For the developers, the old driver is presenting structural problems in code organization and exposure. Removing it is the only real option. We have a proper replacement, hm2_modbus, that can do it all and better. >> There is also one thing I don't like about the new version: the >> `mbccbs` parameter requires an absolute path to the MBCCB file. The >> current documentation explicitly says: Will be fixed shortly. -- Greetings Bertho (disclaimers are disclaimed) _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users " _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
