Hello @easytarget ,
I’m starting to go through a “normal” use of your fork. Here are my observations. Many of those could be flagged as a feature request depending on the amount of work required.
-
When importing my old R12 DXF sample, the layers are now tagged as their colors instead of their names. Is it something coming from the R2000 or something with the SVG?
-
When changing the background colors in
Settings / Machine
the colors aren’t updating even when clicking the button beside the color selector. If I toggle theSHOW MACHINE
selector above then it updates. It seems to be linked with the fact I’m using thePERFORMANCE DISPLAY CACHE
option. If the cache is off, then it behaves as I’d expect it. -
I’d recommend moving the color selection in the application section, not sure if this is really related to the machine, makes more sense (to me) to be along with the grid spacing selection. Maybe also consider moving the
SHOW MACHINE
selector, but maybe its best to leave it where it is for legacy reasons? -
Would it be possible to double the width of the simulator slider cursor? I’m happy with the behavior and the ability to adjust the overall width. I made it 44 EM wide. I have a dual monitor setup and LW4 takes the main one at 1920x1080 with the usual xfce toolbars and launcher.
-
I suggest the simulator slider is reset to the left after GCode generation. It looks strange to have it part-way when GCode has just been generated.
-
GCode “eye” button in the GCode generator section now works on my setup, it didn’t on the current dev-es6 branch. This is good improvement as I had to save the file, open it, then delete it because they’d pile up in the Download folder, etc.
-
The GCode magnifier / zoom control seems to work good. At first I wasn’t sure of its purpose as I always work in Doc zoom but I understand someone may have paths displayed that isn’t part of the GCode.
-
The Gcode filename generation works good.
-
The GCode Analyse button is an interesting feature, but the time estimation is missing the G4 delay codes. I’m adding delays on
LASER GCODE START
to allow my fumes extractor to spool up. The way I’m doing it is on gcode start the gas assist is toggled on and off and the system waits 5 seconds with G4 S5 as the fans spools up. After the 5 seconds is done I start the gas assist again. I also have a quarter second delay at the end to make sure the kerf is clean. However the estimate seems to ignore the G4 commands. -
The estimator also highlight something I haven’t dug yet which is the G0 speeds. Right now when I look at the GCode it looks like it uses the last G0 speed… which was when I was carefully jogging to set workpiece zero or checking boundaries. How is this supposed to be handled? I can put a G0 F8000 on the gcode start code if that is the intent.
-
I noticed the tooltip for
Settings / Gcode / LASER TOOL ON GCODE
has now a mention about $INTENSITY. Thank you for this I searched quite a bit in the forums then made a typo using %INTENSITY. This tooltip should help.
I have more stuff but they are more in the wish list bucket for now. I’m waiting for some parts for my machine and then I’ll get things cutting again.
Cheers!