BLUF- Despite which machine type is selected in pulldown, “SEND CONFIG DATA” always sends the X/Y limits for the XXL.
Background- New Machine and no problems cutting thus far using Create/Motion together. While configuring machine settings within Fusion 360, I wanted to confirm movement limits, step rates, etc… After opening the GRBL log I noticed $131=850.000 and $130=845.000 and figured I had selected the wrong machine. I then switched the selection from standard to XL/XXL and all GRBL commands sent were identical.
Workaround- I’m assuming manually setting $131=430 would do the trick.
For all the smart folks here…
–Are there additional GRBL settings that are unique between machines?
–Do manually configured settings stay loaded on the controller or does Motion push out updates at some interval or pre/post running?
Ranting Conjecture-
I don’t know if this is a big deal, perhaps I’ve avoided problems since Carbide Create constrains the Gcode limits by its settings. Unless I’m missing something though, there are several potential instances where this could lead to driving into the rail limits. As I jump into 360, I certainly look to Motion at least to prevent me from colliding with the rails if I jack up some axis orientation setting while I’m learning. I’m now realizing the difference/importance between homing and limit switches, with the latter, this wouldn’t really mater.
Yes, but those values don’t serve a purpose unless you set $20 (soft limits) to one.
I don’t use Motion, but I’d hope it doesn’t change your grbl settings without your input/knowledge. Also, any idea why your $10 = 255?
The limits don’t really mean much with CM 4. It uses it’s internal values instead of the grbl settings. grbl will use the ones you set here if the “soft limits” setting is enabled.
These are just the default settings that Motion sends to the controller. I assumed that the configurations sent would be different based upon which machine type you select, however that doesn’t seem to be working. What are you using for software with your machine?
Thanks for the info, Mike. I’m a complete newb to Motion and CAM in general, but after reading the GRBL 1.1 wiki, I understand what you’re saying about the soft limits not being enabled. It does sound like something that should be enabled, and Motion should also be sending the correct limit values. Seems like a glitch that needs to be cleaned up in the next release.
Oh sweet, it’s open source too! AND supports using a Pi as a host, preventing me from staying tethered via USB in the garage like I am right now. I completely get why Carbide built their toolkit they way they did, you can draw a rectangle and pocket it out in basically 10 min without any prior knowledge. I’m a tinkerer though, I want to see under the hood and adjust an obviously dumb tool path or deepen a cut while cutting. Appreciate the info, I’m going to give it a try.