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? And that ambiguity means that there is not enough information to decide what the new pin name will be? That does seem to be a difficult one to fix automatically unless you were also to run off and parse the mb2hal definition file. > - 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? -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1912 _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
