Am 20.09.22 um 22:59 schrieb andy pugh:
Is it time to split 2.9 off as a stable-ish branch with a 2.9.0~pre0 tag?
I agree.
Still at least two things to fix related to Gmoccapy, but can be
finished in a 2.9 branch as well.
But I have another question: Some time ago I extended MB2HAL and also
changed some of the existing pin names to match the structure.
So one have to change some pin names when switching to 2.9. I already
read some posts about trouble with MB2HAL when starting LinuxCNC from 2.9.
The question is: should I add these old pins for backward compatibility
and mark them as obsolete in the docs?
*Pins in 2.8* *Pins in 2.9* *Proposal*
*fnct_02_read_discrete_inputs* mb2hal.m.n (bit out) mb2hal.m.n.*bit*
(bit out) mb2hal.m.n.bit (bit out)
mb2hal.m.n.*bit-inv* (bit out) mb2hal.m.n.bit-inv (bit out)
*
* mb2hal.m.n (bit out)
*fnct_06_write_single_register* mb2hal.m.n (float in)
mb2hal.m.n.*float* (float in) mb2hal.m.n.float (float in)
mb2hal.m.n.*int* (s32 in) mb2hal.m.n.int (s32 in)
*
* mb2hal.m.n (float in)
*fnct_15_write_multiple_coils* mb2hal.m.n (bit in) mb2hal.m.n.*bit*
(bit in) mb2hal.m.n.bit (bit in)
*
* mb2hal.m.n (bit in)
*fnct_16_write_multiple_registers* mb2hal.m.n (float in)
mb2hal.m.n.*float* (float in) mb2hal.m.n.float (float in)
mb2hal.m.n.*int* (s32 in) mb2hal.m.n.int (s32 in)
mb2hal.m.n (float in)
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
