CLI Working - change end of carve behavior?

[Milner99]

Hi,

I've got the carve working from the command line - that's great, however at the end of the carve the CLI stays running in what I can assume is an idle state.

Is it possible for the CLI to exit the app after the carve GCode instructions have been executed and the (for me) TinyG has reported all actions complete.

I'm looking to do this because I'm using a Python script to launch the CLI and would need to "detect" when the carve and all GCode is complete so I can instruct the machine to move into the next process (which is a different system).

Thank you for any help/guidance.

C

[breiler]

Just to make sure, what arguments are you using when running ugs-cli?

There is an argument --daemon or -d which will run UGS with a web server which would cause this. If you are not using that argument there is something else that is wrong.

[Milner99]

Thanks for replying @breiler

I am not using -d or -daemon

I am using
--controller
--port
--baud
--print-stream
--file

I've rigged up a python script to monitor the realtime output of the UGS .jar and kill the process after the last line of the processed GCode which I am hoping will work the same way but the commandline call (in the screenshot) simply sits on a blank line at the end of the GCode instuctions - and even after all movement has been processed by the TinyG.

Happy to screen share if it will be useful for you?

Kind Regards

[breiler]

Nah, that is ok, I just wanted to make sure that you did not use that option.

This is not the intended behaviour, so this problem must have sneaked in in the last couple of releases. I don't have the time to look at it tonight though. Might take a couple of days before I can fix it.

[Milner99]

Thank you - I'll keep an eye on the repo and look for an update. Appreciate you taking the time to update.