Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Laser Mode Enabled after every Draw Frame action #19

Closed
AlligatorFate opened this issue Dec 18, 2019 · 5 comments
Closed

Laser Mode Enabled after every Draw Frame action #19

AlligatorFate opened this issue Dec 18, 2019 · 5 comments
Assignees
Labels
bug Something isn't working cannot reproduce good first issue Good for newcomers help wanted Extra attention is needed question Further information is requested
Milestone

Comments

@AlligatorFate
Copy link

It appears to me that laser mode ($32=1) is enabled whenever I draw the frame by pressing the "Draw Frame" button. Draw Frame functionality is useful to visualize the boundaries, but I'm using CNC, not Laser. I never want laser mode enabled.

The problem with laser mode while using CNC is that the "spindle" won't turn on until the cutting move (G1 as opposed to G0) is acted on. But a real spindle needs time to spin up and can't cut immediately. So, this causes problems. If I set $32=0 in grbl settings, I'd like it to stay that way.

It looks to me like drawing a frame is trying to make sure laser mode is off and then turning it back on when it's done. However, I believe it should only do this if laser mode was on to begin with. Otherwise, it'll turn laser mode on when it was initially off, which can be very hard to troubleshoot if you don't know where it's coming from. Who would expect that "draw frame" would turn laser mode on when it was off before?

(And thanks again for your work, synman.)

@synman
Copy link
Owner

synman commented Dec 19, 2019

Remember, I only have a laser :)

Will take a look at this and see about cleaning up.

Shell

@synman synman added the bug Something isn't working label Dec 19, 2019
@AlligatorFate
Copy link
Author

I think my tone was wrong... sorry. I meant to be persuasive, not critical. It's all about continuous improvement, right?

@synman synman added good first issue Good for newcomers help wanted Extra attention is needed labels Jan 21, 2021
@synman synman added cannot reproduce question Further information is requested labels Dec 13, 2021
@synman
Copy link
Owner

synman commented Dec 14, 2021

I'm working on factoring out system ($) command interactions as much as possible right now, focusing initially on removal of all $32 commands within the plugin (except for when you want to change them via Grbl Settings).

synman added a commit that referenced this issue Dec 15, 2021
no longer rely on $32 for framing #19
framing now uses grbl 1.1 jogging
@synman
Copy link
Owner

synman commented Dec 16, 2021

Tying this together with #35 and #4

This is turning into an extensive, but very necessary, exercise. I've brought a lot of stuff into scope here including laser detection based on $32 value, usage of Grbl 1.1 jogging for framing operations, and backwards compatibility for older devices.

I'd rather just drop support for pre 1.1 firmwares but recognize there are probably a bunch of people stuck on .9.

I'm also revisiting all embedded gcode and refactoring many of the commands used by the plugin today for various operations.

Lastly, I've finally, just moments ago, pulled trigger on a budget CNC machine. I went with this bad boy: https://www.foxalien.com/collections/cnc-router/products/cnc-router-machine-masuter-with-300w-spindle-bundle-kit

So yeah, anticipate some major improvements over the next month or so as I adapt the plugin to cover all my own CNC needs.

Shell

@synman synman added this to the v1.7.6 milestone Dec 17, 2021
@synman synman self-assigned this Dec 17, 2021
@synman
Copy link
Owner

synman commented Dec 19, 2021

this should be fixed. please comment if you observe otherwise

@synman synman closed this as completed Dec 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working cannot reproduce good first issue Good for newcomers help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants