I just upgraded to version 1.5 and now my lser is slowing down when the laser is on. It was working fine prior to this upgrade. Yes $32=1. I have a home build machine wirh a DLC32 GRBL controller. I’m going to try and go back to the previous version and see if that works. ANyone else having similar issue?
I reloaded 1.4 FW but same issue. So probably nat a FW bug Issue. I did recently change machine settings for max speed and it was all working. then when I restarted a day later i get this weird behavior where the image etch speed slow down when the laser fires. Anyone got ideas? Thanks
Perhaps the new speeds setting interact with the Fast Whitespace Scan speed in peculiar ways?
Fast white space is not enabled.
I just re downloaded FW to the DLC32controller and it still does the same thing. there has to be some setting that changes how the stepper motor speed changes. It makes no sense to me that the speed slows down only when the laser fires instead of being a constant speed. any other settings other than $32 = 1? It was working fine a day or two ago and when I restarted this morning it does this. I also resent all of my machine settings froma saved file. didn’t help.
Check your power supply, I’m wondering if you’re getting a voltage drop when the laser is firing.
I think I figured it out. I changed some layer settings while doing some cuts the other day. When I reassigned the image to a layer I had never used it worked perfectly. So I think I just need to restet to defaults and then apply to all layers and that will fix it permenently. Thanks for all your comments!!!
Wouldn’t the settings still be apparent even if you had changed them?
Next update. When reset defaults and assigned to all layer it went back to slowing down again. I uninstalled lightburn removed all of the Pref files and reinstalled. Same thing. I have a second computer I will try this morning to eliminate that variable. Maybe i just don’t know what setting I need to change back.
SO I finally figured this out. I processed the image in ImageR and that was the problem. When I ran another image it was fine. I reprocessed the image in ImageR but didn’t use the norton material settings. The unstead of pass thru I used Jarvis. Problem solved.
You typically would not use both ImageR and non-passthrough concurrently. In other words, there’s no value in processing through both and actually this can make the output quality worse. If you do process in ImageR then you certainly would want to use passthrough.
If your DPI setting in ImageR was excessively high it could cause the slowdown that you’re experiencing. Or if you were doing grayscale. Basically, any operation that would entail a large number of instructions to the machine.
You are correct. When I fully processed the image in imager I used pass thru and that’s when I had the problem. When I did not fully process the image in in ImageR I used Jarvis and it worked without slowing down. I had it set for 300 DPI in both cases.
How did you process the image? Was it dithered or grayscale?
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.