|
|
Post by coolnamesalltaken on Jul 30, 2018 6:22:13 GMT
I just finished building my M3, and didn't know that the arduino uno came with a modified version of GRBL with pin assignments changed around for the endstop switches. I updated the uno to GRBL 1.1, and after some head-scratching figured out that I needed to reverse the Y-axis homing direction ($23=2) and move the Z-endstop pin to Spindle Enable (as opposed to Z+). Now everything homes in the correct direction, but my Y-axis hits the endstop and keeps going. Are there other pin swaps that I need to do for the board to work with GRBL 1.1?
I'm also happy to go back to Millright's own version of GRBL. A few questions about that: what is the difference between the stock Millright GRBL firmware and GRBL 1.1, and where can I find the hex file? Do I just make the grbl-master files from the Millright Resources page?
Thanks!
-John
|
|
|
|
Post by Derek the Admin on Jul 30, 2018 14:16:27 GMT
I can't discuss all of the differences between stock grbl and our grbl because it's been a while since I redid it. The compile time configuration and run-time configurable settings are tailored to each machine in the versions of grbl that we load onto the boards prior to shipping, so you won't need to make any config changes. I have attached the hex for for the M3 that should be used: One problem I think you might run into now is that the settings in EEPROM (all the run time configurable settings are in EEPROM) are not always overwritten what a flash. Anything you've changed from the default will need to be changed back. Setting 23 should equal 0. |
|
|
|
Post by coolnamesalltaken on Jul 31, 2018 14:25:01 GMT
Fantastic, thanks! I downloaded it and ran it--Y-axis homing was still reversed, but after I set $23=2 everything worked like a charm.
|
|
|
|
Post by Derek the Admin on Jul 31, 2018 19:59:58 GMT
Sounds good! Congrats on the build.
|
|
|
|
Post by polylawman on Aug 8, 2018 14:56:38 GMT
Can I plug a limit switch into -X and one into -Y on the CNC Shield to limit X and Y's travel in those directions?
|
|
|
|
Post by fyddler on Aug 8, 2018 15:47:40 GMT
Can I plug a limit switch into -X and one into -Y on the CNC Shield to limit X and Y's travel in those directions? I was wondering the same thing last night. |
|
|
|
Post by Mototech on Aug 8, 2018 16:06:57 GMT
Can I plug a limit switch into -X and one into -Y on the CNC Shield to limit X and Y's travel in those directions? I was wondering the same thing last night. Yes you can. But they aren't really necessary if you set the max travel limits in your boards firmware. I'll get a screenshot and steps you need to take when I get home from work. |
|
|
|
Post by polylawman on Aug 8, 2018 18:32:58 GMT
I was wondering the same thing last night. Yes you can. But they aren't really necessary if you set the max travel limits in your boards firmware. I'll get a screenshot and steps you need to take when I get home from work. Thank you for your help. |
|
|
|
Post by Mototech on Aug 8, 2018 23:37:42 GMT
Here's a screen shot of my settings. $130, $131, and $132 are your max travel limits. I homed the machine then manually jogged carefully to about 3 to 5mm from where the v wheels would collide with the ends of travel. I rounded off the locations shown by UGS, then entered them in for each respective axis. Check out the link below. For example, I manually entered $130=430 in the command field and hit the enter key. UGS should report back with OK. These are "soft limits" and using switches at the travel limits would be "hard limits". The advantage of setting the soft limits/ max travel distances is that UGS will throw an error when it reads a command that exceeds the limits set. That way you are warned ahead of time, the end switches pretty much just protect the machine from going too far, but you have no warning till it happens. And if you do hit the end limit switches, UGS will most likely lose the machines position. Possibly causing the piece to be ruined.
Switches to protect the machine from maximum is great, but not really necessary IMO. Setting the soft travel limits is the way to go IMO for you will most likely be warned ahead of time. Edit in: my settings shown in the picture are in metric.
github.com/gnea/grbl/wiki/Grbl-v1.1-Configuration
 |
|
|
|
Post by fyddler on Aug 9, 2018 0:05:20 GMT
Here's a screen shot of my settings. $130, $131, and $132 are your max travel limits. I homed the machine then manually jogged carefully to about 3 to 5mm from where the v wheels would collide with the ends of travel. I rounded off the locations shown by UGS, then entered them in for each respective axis. Check out the link below. For example, I manually entered $130=430 in the command field and hit the enter key. UGS should report back with OK. These are "soft limits" and using switches at the travel limits would be "hard limits". The advantage of setting the soft limits/ max travel distances is that UGS will throw an error when it reads a command that exceeds the limits set. That way you are warned ahead of time, the end switches pretty much just protect the machine from going too far, but you have no warning till it happens. And if you do hit the end limit switches, UGS will most likely lose the machines position. Possibly causing the piece to be ruined.
Switches to protect the machine from maximum is great, but not really necessary IMO. Setting the soft travel limits is the way to go IMO for you will most likely be warned ahead of time. Edit in: my settings shown in the picture are in metric.
github.com/gnea/grbl/wiki/Grbl-v1.1-Configuration
Thanks! |
|
|
|
Post by polylawman on Aug 9, 2018 2:33:38 GMT
Here's a screen shot of my settings. $130, $131, and $132 are your max travel limits. I homed the machine then manually jogged carefully to about 3 to 5mm from where the v wheels would collide with the ends of travel. I rounded off the locations shown by UGS, then entered them in for each respective axis. Check out the link below. For example, I manually entered $130=430 in the command field and hit the enter key. UGS should report back with OK. These are "soft limits" and using switches at the travel limits would be "hard limits". The advantage of setting the soft limits/ max travel distances is that UGS will throw an error when it reads a command that exceeds the limits set. That way you are warned ahead of time, the end switches pretty much just protect the machine from going too far, but you have no warning till it happens. And if you do hit the end limit switches, UGS will most likely lose the machines position. Possibly causing the piece to be ruined.
Switches to protect the machine from maximum is great, but not really necessary IMO. Setting the soft travel limits is the way to go IMO for you will most likely be warned ahead of time. Edit in: my settings shown in the picture are in metric.
github.com/gnea/grbl/wiki/Grbl-v1.1-Configuration
Thank you Mototech. After your initial reply to me, I started researching and saw that I could set the limits with $130, $131, $132 in Grbl, but having no experience what so ever I felt I should wait on you to respond. Thank you so much for your help and the pic of your settings. |
|
|
|
Post by coolnamesalltaken on Aug 14, 2018 16:21:57 GMT
For the record I had my y axis reversed. Fixed that and $23=0 works fine  |
|
|
|
Post by Derek the Admin on Aug 14, 2018 17:06:37 GMT
Thanks for reporting on the fix.
Derek
|
|
|
|
Post by Bruce on Aug 15, 2018 19:22:14 GMT
I found doing my last project it hit my X axis limit while running a project G-Code and it automatically moved the whole work coordinates down the X axis to make it all fit. No alarms. I saw the LED light on my proximity switch for my X axis limit, is the only reason I knew what happened.
|
|
