My idea is actually very simple. I would leave the original mesa_modbus chapter in the documentation, but change it to clearly say that the component has been deprecated/removed and replaced by hm2_modbus, with a link to the new documentation.
Maybe Bertho remembers that I had to learn mesa_modbus myself, and just when I finally had it working, I was told that it was already an obsolete component and I had to learn hm2_modbus instead, so that I could use the standard components. I am not blaming anyone for this. Nobody is at fault. This is simply part of working with the Master branch as a tester. What I expect, however, is that quite a few users will be surprised when moving from 2.9 to 2.10 and discovering that mesa_modbus is gone. Most users don't read upgrade logs. I would therefore like those users to find out as quickly and as easily as possible that mesa_modbus has been replaced by hm2_modbus. That's all. I don't want to make a big issue out of it. We are volunteers, and we don't have the resources to build sophisticated tools for automatic migration. Good documentation and a clear migration path are probably the simplest and most practical solution. -- S pozdravem Zdeněk Zdražil ---------- Původní e‑mail ---------- Od: Bertho Stultiens <[email protected]> Komu: [email protected] Datum: 13. 8. 2026 15:14:57 Předmět: Re: [Emc-users] Deprecating the old mesa_modbus / modcompile driver "On 8/13/26 2:14 PM, Zdeněk Z wrote: > 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. That is a very true observation. The current plan is to inform the user of deprecation when modcompile is run. There are no formal guidelines how long something stays deprecated before removed. I do not know of any other channel than the mailing lists where these changes are announced. It was my understanding of the original mail that it did exactly that, announce the upcoming deprecation of the old driver. FWIW, there are many more changes coming and some are or may be breaking changes for users that have (deep) source-code integrated customizations. Progress takes its toll. > So my concern is not keeping the old driver alive. It is making the > migration path clear and visible to the existing user base. Creating new (howto) documentation and describing a migration path is important. Please, if you can find the time, you are welcome to add and fix the docs. ;-) Always appreciated to include better docs. -- 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
