Advanced Search

In the source i see you how you handle expressions.

I shoukd use a lib like: mu parser to handle expressions. 
This also handles and updates gcode variables for you. 

It wont run (nested) while loops. This while loop algo you can design yourself.

in future i love to see gcode dialect parsing,
given a json config file.

Then hopely the interpreter is also able to read fanuc and kuka robot language and produce the motion outputs for it. An extended version off straight_feed xyz...
would look like straigt_feed j1 j2 ....

Mu parser example

Pcw had no luck on Mesa. The install script
destroyed his home directory back then.
This was done by a rm -rf command 
wich can do nasty things so we dont use that any more for cleaning up environment.

I only tested it on Ethercat with el2124 driven steppers and delta servo. 


 

Parameters still seem to be a problem to me.

Doing a polar pattern based on the test file posted earlier.
8 coordinate systems at 45 degree steps.

Shutdown overnight, now polar pattern off by 45 degrees rotation, and X,Y datum shifted.
The problem is most likely something silly by me, but the questions are still valid.

I used G10 L2 P1 X0 Y0 Z0 R0 to ensure G54 was where I started the polar pattern.
I this unnecessary and may complicate things ?

Should coordinate offsets be cleared before shutting down ?
How can I avoid parameters biting me in the future?
Should something be included in the shutdown.hal ?

John.