Is there any way to speed up macro execution?

Here is where you can request new features or special features.

Re: Is there any way to speed up macro execution?

Postby cncdrive » Tue Dec 06, 2016 9:07 am

I've checked how complicated is to add a Codelong function which could interpret multi-lines of g-codes with look-ahead.
It basicly requires a rewritting of the whole macro executer, not from the grounds up, but about 3000 lines of codes needs to be changed.
And this is because we did not think about this, so the whole thing was prepared to be able to execute single lines of g-codes only using the look-ahead with motion buffer.
So, it will probably take some time for us to make this and to test all through.
cncdrive
Site Admin
 
Posts: 4887
Joined: Tue Aug 12, 2014 11:17 pm

Re: Is there any way to speed up macro execution?

Postby Robertspark » Tue Dec 06, 2016 2:58 pm

6000 lines of revised code :shock:

I'd also like the "sub" ("O" code) for gcode please.

could we also think of a way to call a gcode line number maybe from the code directly.

Thanks,
Robertspark
 
Posts: 1892
Joined: Sat Sep 03, 2016 4:27 pm

Re: Is there any way to speed up macro execution?

Postby cncdrive » Tue Dec 06, 2016 11:58 pm

Terry,

Changing the #var writting to the Status instead of a popup window is far the most easy of the things you asked about.
All the other things you mentioned requires drastic codes changes.
The expression next to g-codes needs lots of code changes, because now only a variable number and a boolean value about if it is a number or a variable is stored when the # is used with a word and this is done in all codes in the whole interpreter and g-code executer, so if we want to change this then we have to change what we store, we have to store the whole expression string and compile it on runtime which is programmatically not a problem, but it probably takes a few thousands of code lines to be changed both in the interpreter and in the g-code executer.

I think I will make the ?#var first to Status bar, because that one is simple and can be done fast, and will try to implement the .codelong directive and when done will come back to discuss what to do next.
It seems it is better to do the .codelong first, because sooner or later, but I will like to implement that and we already talked about it a long time now with Terry and it seems to be the most complicated and longest code change of all, so I think it would be better to make it asap to let you guys test it and to give it time to mature.
cncdrive
Site Admin
 
Posts: 4887
Joined: Tue Aug 12, 2014 11:17 pm

Previous

Return to Feature Request

Who is online

Users browsing this forum: No registered users and 8 guests