Allow TPL to emit arbitrary G-code about camotics HOT 5 CLOSED

There is already the print() command. However, running such code in the simulator may not have the desired effect. Any GCode which is emitted by print() will be missed by the simulator. You could preprocess with TPL, then run the resulting GCode in the simulator.

from camotics.

It should be writing to the same stream. CAMotics::CommandLineApp::stream is also passed to TPLContext in TPLangApp::run() in tplang.cpp. This is what cb::StdModule::print() writes to. Are you saying that print() still ends up in stdout when you set --out <filename>? What build are you using?

from camotics.

I just tested this in my local build and the streams are the same. I in believe v1.2 print() always prints to stdout but that has been fixed. I've been trying to make a new CAMotics release for a long time now but haven't been able to find the time. You can always build from source.

from camotics.

That was a quick reply. Thank you!

We are not talking about the simulator. Just TPL. The simulator cannot understand arbitrary g-code. That's obvious.

I tried what you suggested using the tplang program as preprocessor. But, when executing

tplang test.tpl --out "test.nc"

Where the file test.tpl is

print("G0 X0 Y0");
print("G1 X10"); 

The resulting file test.nc is

G21
M2 

The command line console does show

G0 X0 Y0G1 X10

in the standard output, and we could use --out - but then we are conflating two different streams. One with the g-code and the standard output.

I have tried to understand how the print command works following the source code. The only appearance of "print" is in GCodeInterpreter::specialComment() which uses LOG_INFO. However, both message() and comment() call the same-named methods in GCode::GCodeMachine and these methods use GCode::GCodeMachine::stream which is the output file of CommandLineApp::build() initialized in CommandLineApp::init().

As far as I can understand the source code, there is no command to emit g-code from TPL. I mean, a command that has a semantics that says "write to the g-code file/stream". We can use print (to standard output) and make the g-code file be the standard ouput to get around that, but... is this it? By design?

from camotics.

tplang --version says 1.2

from camotics.