On 05/31/2016 02:00 PM, John Morris wrote:
> I've enabled remap of the M62 thru M66 codes [1]. Is this of interest
> for merge into LinuxCNC?
In my opinion: yes.
> Seb, I borrowed your 'statbuffer-g5x-abort' test for this. Proper
> testing of calling the original e.g. M64 from within the remap
I've enabled remap of the M62 thru M66 codes [1]. Is this of interest
for merge into LinuxCNC?
Seb, I borrowed your 'statbuffer-g5x-abort' test for this. Proper
testing of calling the original e.g. M64 from within the remapped M64
needs bath interp and HAL, plus the connecting machinery, so i
On 05/31/2016 10:40 AM, John Morris wrote:
> On 05/27/2016 07:01 PM, John Morris wrote:
>> I just pushed a branch to glo that fixes a bug where
>> `_setup.sequence_number` is set incorrectly after a remap return. In
>> very rare circumstances, this can cause a "Duplicate O-word" error, as
>> the
On 05/27/2016 07:01 PM, John Morris wrote:
> I just pushed a branch to glo that fixes a bug where
> `_setup.sequence_number` is set incorrectly after a remap return. In
> very rare circumstances, this can cause a "Duplicate O-word" error, as
> the parent of the HEAD commit demonstrates.
>
> http:/
