Ok, It finally cooled off enough for me to work on the K40 w/ ramps again. I have it working awesome with the inkscape plugin but one or two problems are plaguing me with LW3 code generation:
-
The first few moves from home are really jerky (will try to get video) This isn’t the case with the inkscape plugin.
-
The laser doesn’t turn off - even with the M5 (could be firmware) - my guess is the last move needs an S0 after the last move to set the PWM down to zero. The display says 0% on laser power after the M5 = so definitely firmware problem.
-
Gcode output has a lot of “precision” in it - is there a setting that can say truncate the coordinates out to say 4-5 decimal places to make the G-code more legible for debugging stuff like this?
Does anyone have a K40+RAMPS config file they’d care to share?
@Michael_Audette Marlin ( firmware on ramps) is not fully supported on LW at this time. We have working setups on Smoothie and GRBL
Yes aware of that - but g-code is g-code 
I’m not looking to send it over serial…I know that’s broken. But the export to code for simple vectors should work. MARLIN’/RAMPS was supported “back in the day” - although it never did quite work right. FWIW the RAMPS does work fairly well for vector - which is what I want…and for $25 it works better than the crap that came in the machine…and there’s really no reason why it shouldn’t work in LW without proper settings…I think I’m just missing something basic or have something misconfiged.
Yeah that’s what I used to cut/engrave the hops in the image above…but it doesn’t offer the control that LW does. It appears to increase the beam intensity on the outline for no reason (and there doesn’t appear to be a control for that)…and I’d rather not use inkscape and a plugin.
So if you have set up LW properly with on / off commands plus the power range the the gcode should be fine, but then tyranny which is supposed to be an optimized laser firmware is not producing the expected results?
The Gcode looks more or less fine (technically)…just can’t figure out why LW’s code isn’t turning off the laser at the end. I really don’t think it’s LW fault - event display says it’s off (firing at 0%) but in reality the laser is still firing at the previous power level - but I think perhaps I need something more in the GCODE or the buffer is messed up (also highly likely). Setting the S value back to zero at the end of the last move might work too. I copied in my end code from the Turnkey plugin…but maybe I have to mash in a couple extra M5 to make sure it’s off. I figured I’m not the only one with a RAMPS still
I think I found the issue in the firmware config - will try that - if that works it may be my only barrier to moving to LW!
On my first issue…I think I have that one figured out - the GCODE getting generated from the SVG does not honor the travel moves rate. Instead it’s outputting (coords truncated for convieninece):
G0 F90000 X53.747 Y43.529
Shouldn’t this honor my Settings “Travel Moves (mm/s) (Required)” setting , which I have set to 1500?
LW receives mm/s but translates to mm/min. So 1500 mms imjust to much.
LW receives mm/s but translates to mm/min. So 1500 mms imjust to much.
Ahhh…damn. OK that makes sense - I transcribed my setting from the other program and that was in mm/min. Thanks for this. Complete brain fart. Is it beer thirty yet?
