Am 01.10.22 um 18:01 schrieb andy pugh:
On Sat, 1 Oct 2022 at 16:29, Hans Unzner <hansunz...@gmail.com> wrote:
Unfortunately this would not work because:
- From the pin name you can't draw a conclusion on the function.
For example "mb2hal.00.01" could be fnct_06_write_single_register or
fnct_02_read_discrete_inputs. So should be either converted to
"mb2hal.00.01.int" or "mb2hal.00.01.bit".
So, previously the pin names were ambiguous as to type, and you have
removed the ambiguity?
Yes
And that ambiguity means that there is not enough information to
decide what the new pin name will be?
Exactly
That does seem to be a difficult one to fix automatically unless you
were also to run off and parse the mb2hal definition file.
Yes so I think it will be easier to introduce a mb2hal version number
and force the user to insert the new version number to use the new
features. And then he should know that the pin names have changed.
- The component name could be modified and the transaction names as well.
So "mb2hal.00.01" could be "my_modbus_vfd.read_status.01"
But would that change _purely_ as a result of the update to mb2hal
with no changes in the HAL or INI files?
Yes that's the point.
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
