> On 23 Mar 2020, at 6:52 pm, Chris Morley <[email protected]> wrote:
>
> I have been delving deeper into linuxcnc to see if I could correct the status
> of F code.
> For those who don't know the Fcode status report in AXIS (or any gui) is
> actually the status of the interpreter rather then the current Fcode. If you
> have a long program that changes the fcode lat in the program you will see
> that f code before you should.
>
> I have code that works; it reports through status the current F code, and it
> outputs a HAL pin of current F code.
> I'm not sure I've done it right of course.
>
> It does this by sending a new NML message to motion each time the F code
> changes.
> When that message gets to Motion, it updates status and the HAL pin.
> Since it's read from the interpreted list, it is in sync with the actual F
> code.
>
> Currently the message is called feedrate or base_feedrate which needs to be
> changed probably to F_code.
> Then I was thinking S code should probably be updated in sync too.
> Rather then having a message per code I could call the message sync_code and
> add other codes to it.
>
> Opinions ? is this the wrong way to go?
> Does my code look wrong? (most of it is boiler code actually)
>
> You can see the commits here (top 6):
> https://github.com/LinuxCNC/linuxcnc/commits/feedcode_message
>
> Chris
>
>
> _______________________________________________
> Emc-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/emc-developers
Great work Chris, it is a bit above my pay grade but plasma users will
appreciate this.
Cheers, Phill.
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
