Documentation / help

[n3roGit]

Hello, I find your plugin simply ingenious. I have also found no other alternative :)

Unfortunately, there is currently little documentation for the plugin and for many things I have to guess.

Therefore, I write here times my smaller problems with my laser down. Maybe you can help here and then include this for the next in the doku.

1. after I have made PAUSE, the laser continues to run, but the power remains at 0%.
2. partly the job stops during lasering without any message in the log. The laser simply stops at X percent.
3. it would be a list of possible GCodes to use your plugin really helpful. For 3D printing you can find some. In this case, rather not.
4. sometimes Octoprint does not connect to my laser or it takes quite a long time (30 seconds) after connecting before I can send control commands to the laser.

Best regards and thank you!

[synman]

There's a bit happening here. Let me try to break it down a little.

after I have made PAUSE, the laser continues to run, but the power remains at 0%.

I'll need to translate your screenshots to rule out any custom gcode you may have added to these events interfering with the plugin's built-in pause code. I'll come back to this after doing some comparisons in a follow up comment.

partly the job stops during lasering without any message in the log. The laser simply stops at X percent.

This may be a communication problem between your Octoprint host and your machine. Is there a specific command it always pauses on? I will need to see output from your terminal window to help further here but I suspect you may be have a bad connection or something of that nature causing the stream session to be interrupted.

it would be a list of possible GCodes to use your plugin really helpful. For 3D printing you can find some. In this case, rather not.

I think this is a question more so about GRBL, than the plugin. There are quite a few guides available on the internet about "GBRL GCODE". I use the official GRBL GitHub repo as an authoritative source for my own stuff: https://github.com/gnea/grbl/tree/master/doc/markdown

If this is the heart of the question, do a google search for the above quoted text. You're going to get a lot of decent results.

sometimes Octoprint does not connect to my laser or it takes quite a long time (30 seconds) after connecting before I can send control commands to the laser.

Share your terminal window when this happens with me. It could be tied to the issue you reported above regarding a job "stalling". It could also be something specific to your machine I have not accounted for.

[synman]

Do you mind sharing what your custom gcode commands "OCT01" and OCTO02" are doing?

I initially thought I would find something custom in your pause / resume gcode scripts to interfere with the pause / resume operations but it looks like you've got these two sections empty (this is a good thing).

I have been experiencing some issues of my own related to pause / resume. Octoprint inserts some of its own gcode here (that the plugin translates to dwell) that I think may be interfering with this operation. I think we can call this a bug that I just need to figure out and fix.

There is already code in the plugin to explicitly disable the spindle / laser on pause, and reset it on resume. I would very much appreciate seeing your terminal window output when you experience this problem to help identify (and address) root cause.

[n3roGit]

Thanks for the quick and detailed answer! I use the OctoX command only to shut down the PI after work is done. This seemed like the easiest way to do it.

The GRBL codes I will also take a look.

I will provide the logs as soon as possible!

I also have another question. Can it be that I do not get the laser to 100% power under Octoprint? I felt I had more power when I controlled the laser directly via Lieghtburn.

[synman]

I have some similar custom commands... I do not believe yours are causing any issues either.

[n3roGit]

Recv: ok Send: G1 X0.557Y-0.208 Recv: ok Send: G1 X0.6Y-0.165 Recv: ok Send: G1 X-0.293Y-0.049 Recv: ok Send: G1 X-0.311Y-0.028 Recv: ok Send: G1 X-0.327 Recv: ok Send: G1 X-0.34Y0.014 Recv: ok Send: G1 X-0.35Y0.042 Recv: ok Send: G1 X-0.358Y0.065 Recv: ok Send: G1 X-0.363Y0.091 Recv: ok Send: G1 X-0.365Y0.115 Recv: ok Send: G1 X-0.364Y0.141 Recv: ok Send: G1 X-0.361Y0.167 Recv: ok Send: G1 X-0.356Y0.194 Recv: ok Send: G1 X-0.347Y0.22 Recv: ok Send: G1 X-0.336Y0.249 Recv: ok Send: G1 X-0.322Y0.276 Recv: ok Send: G1 X-0.305Y0.305 Recv: ok Send: G1 X-0.286Y0.333 Recv: ok Send: G1 X-0.26Y0.357 Recv: ok Send: G1 X-0.23Y0.375 Recv: ok Send: G1 X-0.2Y0.392 Recv: ok Send: G1 X-0.171Y0.406 Recv: ok Send: G1 X-0.141Y0.418 Recv: ok Send: G1 X-0.112Y0.427 Recv: ok Send: G1 X-0.081Y0.434 Recv: ok Send: G1 X-0.051Y0.437 Recv: ok Send: G1 X-0.021Y0.439 Recv: ok Send: G1 X0.009Y0.438 Recv: ok Send: G1 X0.04Y0.434 Recv: ok Send: G1 X0.07Y0.429 Recv: ok Send: G1 X0.101Y0.419 Recv: ok Send: G1 X0.133Y0.409 Recv: ok Send: G1 X0.163Y0.394 Recv: ok Send: G1 X0.194Y0.379 Recv: ok Send: G1 X0.266Y0.427 Recv: ok Send: G1 X0.292Y0.394 Recv: ok Send: G1 X0.316Y0.362 Recv: ok Send: G1 X0.336Y0.329 Recv: ok Send: G1 X0.355Y0.297 Recv: ok Send: G1 X0.371Y0.264 Recv: ok Send: G1 X0.385Y0.234 Recv: ok Send: G1 X0.395Y0.201 Recv: ok Send: G1 X0.404Y0.17 Recv: ok Send: G1 X0.41Y0.138 Recv: ok Send: G1 X0.414Y0.108 Recv: ok Send: G1 X0.414Y0.076 Recv: ok Send: G1 X0.413Y0.046 Recv: ok Send: G1 X0.409Y0.015 Recv: ok Send: G1 X0.403Y-0.015 Recv: ok Send: G1 X0.393Y-0.045 Recv: ok Send: G1 X-0.618Y-0.174 Recv: ok Send: G1 X-0.575Y-0.221 Recv: ok Send: G1 X-0.532Y-0.263 Recv: ok Send: G1 X-0.488Y-0.302 Recv: ok Send: G1 X-0.446Y-0.337 Recv: ok Send: G1 X-0.404Y-0.367 Recv: ok Send: G1 X-0.362Y-0.394 Recv: ok Send: G1 X-0.319Y-0.416 Recv: ok Send: G1 X-0.279Y-0.435 Recv: ok Send: G1 X-0.238Y-0.449 Recv: ok Send: G1 X-0.197Y-0.46 Recv: ok Send: G1 X-0.156Y-0.466 Recv: ok Send: G1 X-0.117Y-0.468 Recv: ok Send: G1 X-0.077Y-0.467 Recv: ok Send: G1 X-0.038Y-0.462 Changing monitoring state from "Printing" to "Pausing" Recv: ok Send: G4 P0.01 Recv: ok Send: ? Recv: <Idle|MPos:111.125,41.300,0.000|Bf:35,1024|FS:0,0|Pn:PS|CL:0,100|PS:2,1|VA:23782,7|A:S|H:1,7> Send: S0 Send: ! Send: ? Changing monitoring state from "Pausing" to "Paused" Recv: ok Recv: ok Recv: <Hold:0|MPos:111.125,41.300,0.000|Bf:35,1023|FS:0,0|Pn:PS|CL:0,100|PS:2,1|VA:23837,0|A:S> Send: ? Recv: <Hold:0|MPos:111.125,41.300,0.000|Bf:35,1022|FS:0,0|Pn:PS|CL:0,100|PS:2,1|VA:23824,4> Send: ? Recv: <Hold:0|MPos:111.125,41.300,0.000|Bf:35,1021|FS:0,0|Pn:PS|CL:0,100|PS:2,1|VA:23869,76>

This is the Log after Pause/Resume

[synman]

Well it's nice to see the code doing exactly what it is supposed to do

M4 for dwell Wait for idle S0 for no power ! for feed hold

You could send a ~ here to come out of feed hold, do stuff, and go back into feed hold with another !

Resume should send:

~ S### with ### being your last power level

And then the stream would resume.

And you're not observing your laser powering off here?

[n3roGit]

Hey, unfortunately I do not understand what to do now :(

Where do I have to put something?

[synman]

I don't see anything for you to put anywhere.

Not seeing the actual pause visually, but by extrapolating what i would see, it looks like it is doing exactly what it is supposed to do.