It seems to be the only problem left I think everything else is good although it did seem to have a more powerful laser on my easel file than the test file in pic sender let me fix the speed issue and see how it burns then. I am also going to make another in easel and generate gcode then modify and run in pic sender
Ok so Iām an idiot I changed the rate saved the tool path without regenerating one so I saved the same path at the high rate thinking I had changed itā¦ Iām still learning vcarve too lol. I think im good to go and it should just be trial and error from here on finding the speeds needed
Experiment with the grbl X&Y accel settings $120= & $121= also.
I use the 3.8W laser and I get good result in wood at 90 to 100 IPM feedrate. On bamboo, to get nice dark/deep lines I go at 50 IPM.
I seem to get a decent line in cardboard at 30 IPM with my $120 $121 at 8000. I will have to try 90 because I feel like 30 is too slow but itās such a fine line I donāt think 90 will do enough burning. I also have the 3.8w. I will have to make some test files and play with it now that I have it figured out but I am calling it a night in the garage I have other things to get done tonight. Thanks again for all the help guys
Try 2000. Vector engraving does not need as high accels as Raster engraving does.
Thanks, using Larryās pp for Ryan got the laser to turn on and run the code.
Trying to get the power up enough to burn. Also speed is much too high and Havenāt been able to slow it down. Another issue is that pic sender wonāt copy $32. I add it to the grbl file hit send and it is missing from the file copied to pic sender. Iāll have more time to work on it and tomorrow, not sure that Iāll make much progress without help!
Thanks Robert, I will do that but first need to figure out why I canāt get enough power to the laser. Also canāt get the speed down low enough to stop the machine from shaking from the rapid direction changes.
In the GRBL menu, did you select the GRBL Settings button when in Laser Mode and change $32=0 to $32=1 in the Edit Settings window before selecting Send? Did you Save the grbl settings change to the Laser.txt file?
I also thought I was having power issues but it seems the speed is just too high so the laser canāt leave a burn. I turned down the feed rate on my laser tool in vcarve and seemed to solve that issue
Ryan, what is the speed that you finally decided to use?
I left the laser file at 8000 and the tool feed rate at 30 havenāt had time to experiment further yet
Yes $32=1, I have copied it to the laser file. When I load that file in pic sender $32=1is in the file . When I send the file ā¦there is no $32. Line in the file
Saving it the file has no effect. What is the function of $32 =1? What does it do?
Appreciate the help
Enabling or disabling Grblās laser mode is easy. Just alter the $32 Grbl setting.
To Enable: Send Grbl a $32=1 command.
To Disable: Send Grbl a $32=0 command.
WARNING: If you switch back from laser mode to a spindle for milling, you MUST disable laser mode by sending Grbl a $32=0 command. Milling operations require the spindle to get up to the right rpm to cut correctly and to be safe, helping to prevent a tool from breaking and flinging metal shards everywhere. With laser mode disabled, Grbl will briefly pause upon any spindle speed or state change to give the spindle a chance to get up to speed before continuing.
Donāt forget that in my version the laser mode also requires a spindle speed range of 0 - 255.
If the spindle speed for laser work is change outside of that range - grbl will issue an error message and change $32 to 0. I donāt know if the error message gets passed to the user by the sender programs.
Sonnyās 1.1f does not have this requirement.
[Edit] UGCS 1.0.9 does report the error if you change the rpm range.
PicSender 2.7.4 reports the error if you change the rpm range via the Do CMD, but does not report the error if you change the rpm range outside of 0 - 255 in Grbl editing mode when you do the āSendā command. Also does not report an error if the Laser.txt has an rpm range that exceeds 0 - 255 when the Laser.txt file is loaded into the Arduino. @JohnChamplain
I think at this point it is Ryan and Frank.
I think Iām good trying to help Frank now
Thanks. Seems as if the $32=1 could be one of my issues. Iāll have some time to work on it tomorrow.
Some senders may have their own internal error handling routines, but PicSender only reports errors detected by Grbl. So, if PicSender does not display an error during sending, Grbl did not detect and report it to PicSenderā¦
My version of Grbl does detect this error and sends a message to the serial port.
Try it with the Do CMD.
Have your system set up with laser mode ($30=255. $31=0. $32=1) and in Do CMD change $30=256.