How to set G-code line highlighting?

More
14 Mar 2022 00:53 #237175 by chen1234
Hi guys, I'm running into a problem that I can't escape.
How do I set G-code line highlighting? When I use my own interface or other configuration interface, the running highlight of G-code lines cannot be controlled. Especially my custom M codes (M100-M199) and remapping codes, these are not highlighted, where should I go to see this? Or how to control the highlighting of G code lines?
Thank you, I hope you can give me some advice.
Attachments:

Please Log in or Create an account to join the conversation.

More
14 Mar 2022 02:31 #237179 by cmorley
I bet there is not much you can do without a lot of internal work.
The screens use a linuxcnc status message to tell them what line linuxcnc is on.
Internally linuxcnc doesn't always create a motion message for each line of Gcode.
It will combine some.

I am not sure how remap and custom code is handled internally, but I would not be surprised if they don't keep track of gcode line.
There are also a 'state Tag' mechanism for keeping track of current state.
I must admit my understanding of this process is hazy.
The following user(s) said Thank You: chen1234

Please Log in or Create an account to join the conversation.

More
14 Mar 2022 05:03 #237187 by chen1234
OK, thanks cmorley
I'll try new ways, what is this "state  tag " mechanism? I may not quite understand. . .

Please Log in or Create an account to join the conversation.

More
14 Mar 2022 05:11 #237189 by cmorley
State tags were introduced to fix the problem for say M code being reported out of sync with the current state, This was because the reported state was the 'interpreted' state not the current state. The interpreter often runs ahead of the current motion.
The following user(s) said Thank You: chen1234

Please Log in or Create an account to join the conversation.

More
14 Mar 2022 09:20 #237196 by rodw
my take is that gcode is read and tokenised into a buffer and then the gcode is thrown away. State tags attaches the interpreter state to that tokenised motion segment at the time of reading so it can be checked in real time when it is eventually executed. But the state tags structure is not easilly exposed. I would like to see the data  published on motion pins.
The following user(s) said Thank You: chen1234

Please Log in or Create an account to join the conversation.

Time to create page: 0.134 seconds
Powered by Kunena Forum