Simplified explanation of Mach4 and Coroutines

https://youtu.be/t2xQYvAXT8o


DazTheGas

Hi Daz,
superb work, I've really struggled with coroutines, not so much the concept but the implementation, this will help BIGTIME. Thanks.

Craig

What Craig said, exactly!!!

Thanks!!!

Any difference running one from a module or macro script?

RT



RT

Can't seem to get coroutine working with a macro.  Anything special that needs to be done, or is that not even a thing?

There are 2 instances/states of wxLua, one is for the Gui and this is where the PLC/Timer Event is that makes coroutines possible. Macros run in a different wxLua state with no PLC/Timer Event available. neither of these 2 states can comunicate with eachother directly.

DazTheGas

Hi Daz,
still struggling with coroutines.

Is it possible to switch back and forth between the Gcode interpreter and the GUI?

The reason I ask is because there is a thread on the forum where the OP wishes when an M6 is encountered in
a Gcode job, ie Gcode interpreter is in control, he wishes to manually jog and/or MDI ,ie GUI in control then
revert back to the interpreter to continue the job.

Naturally would require some coding so that on resumption of the job that the machine coordinates remain in sync.

Can a coroutine work across the two instances of Lua?

Craig

Simple answer is no, the only way you can share data across 2 instances of lua is to use registers.

DazTheGas

Hold that last "simple no" whilst I try something Chaoticone has suggested.

DazTheGas

Hi Daz,
yes I could easily use registers to communicate data between the two.

More importantly can say the Gcode interpreter be suspended while control is assumed by the GUI?
The interpreter would need to be 'massaged' before it was resumed.

Craig