Doug,
No, I had bricked my JL1 board when trying to do the UPGRADE.exe program.
I bought an SL-Link V2, then using Sal’s JL1V2.bin file I was able to get the board operational again. I’m currently reinstalling it to the KL1 hardware and will begin to test it with Lightburn this morning.
Progress at last.
Thanks again for the support from both you and Sal,
Mike
Let us know how that goes as I had tried it last week and for some reason could not get my laser to wake up.
Can you post the full process you used to flash with the ST-Link V2? I have also bricked my JL1 board by not hitting the button before running UPGRADE.EXE…
All,
Lightburn can see the laser and communicate via the console. I got the following from the $$ command:
$$
$0=6
$1=255
$2=0
$3=2
$4=1
$5=1
$6=0
$10=1
$11=0.010
$12=0.002
$13=0
$20=1
$21=1
$22=1
$23=2
$24=200.000
$25=5000.000
$26=250
$27=1.500
$30=1000
$31=0
$32=1
$100=80.000
$101=80.000
$102=80.000
$110=5000.000
$111=5000.000
$112=5000.000
$120=1000.000
$121=1000.000
$122=1000.000
$130=220.000
$131=290.000
$132=1.000
I’m a Marlin guy, so I have a big learning curve to understand the above.
Mike
Mike,
These are my original defaults, speed and acceleration is a bit aggressive. Tame it by setting $110 and $111 to 3000 and $120 and $121 to 400. Just an opinion, you certainly can tune your machine any way you like.
many g-code ‘senders’ will give you a description of what those mean. LightBurn will do it when you go into Edit-Machine Settings.
What Sal was recommending was to lower the max Velocity/speed to 3000 mm/s and lower the max acceleration to 400 mm/s/s. Things moving too fast or trying to accelerate too fast can cause some artifacts in the cut lines.
Doug, Is my ESL really so bad it need decomposition? 
LOL
I know I could have let him look up what $110 and $120 were but it’s lots to digest so I figured it wouldn’t take much to break the two down for him. He’d stated being a Marlin guy so had no clue what all the grbl settings were…
Tinkering with GRBL settings is an essential skill for any owner of any GRBL machine. There is actually nothing scary, takes maybe couple rounds of reads/refreshers to be fluent with it.
PSA: learn GRBL settings, understand it, tweak yours, don’t be afraid! It can be mastered in one session. There is not that much material to digest.
Jim, Et Al,
This is what I did:
That’s about as detailed as I can remember or extract from my history files.
I hope that helps someone,
Mike B.
Mike- thank you for your reply. This helped me sort out recovery of my JL1 that I stupidly tried to switch to GRBL using update.exe- except didn’t press the button.
At any rate, I did the recovery using a laptop with Ubuntu 22.04.
Before I tried the recovery, I opened the case and extracted the JL1 control board.
NOTE: You don’t need to completely dissassemble the control board box. I only had to pull the four screws on the side opposite the USB connector, and the board slid right out.
I then soldered a 4-pin header to the JL1 control board.
I next connected a $10 ebay ST-LINK V2 programmer, connecting the STLINK pins as follows:
STLINK GND to JL1 GND
STLINK 3.3V to JL1 V+
STLINK DIO to JL1 DIO
STLINK CLK to JL1 CLK.
The JL1 board was not connected to its power, but I did leave all other wire harness cables connected
I had to install stlink-tools to try the flash, but discovered that stlink-tools are unable to unlock the stm32 flash. (Or, maybe I’m just too dumb do get it to…)
I ended up downloading openocd and using that to unlock the STM32, and then back to stlink-tools to flash. I could probably have done it all with openocd- but, again I didn’t know how to do that.
Here’s the full sequence I used (I had downloaded the JL1v2.bin file from this thread.)
[Plug in stlink-v2]
sudo apt install stlink-tools
sudo apt install openocd
openocd -f /usr/share/openocd/scripts/interface/stlink.cfg -f /usr/share/openocd/scripts/target/stm32f1x.cfg -c "init;reset halt; stm32f1x unlock 0; reset halt; exit"
st-flash write JL1v2.bin 0x08000000What changes to the configuration did you make?
Mine acts a bit ‘odd’ but I think it’s probably configuration…
The ‘cube’ software works on Ubuntu… lets you look around the chip…
Jack, you never confirmed that you are flashed my latest edit (V2). That JL3 I recall you are running with offsets G54/G10. That possibly makes your behaving “odd”. You are correct this is kind of configuration thing.
V2 firmware set for proper homing and positive space, should have no oddities. By my observation Mike and Jim got V2 firmware.
I thought I had a jl1, but it wouldn’t surprise me to be on the wrong road.
Here is the link from which it came… is it a jl1 or?
-rw-rw-r-- 1 jack jack 45328 Sep 18 09:18 JL1v2.bin
-rw-rw-r-- 1 jack jack 1095 Aug 27 06:20 lzrsal-grbl-settings.txt
lzrsal-grbl-settings.txt (1.1 KB)
I have moved the Y axes limit switch to account for the larger laser on my machine, but have had limited time to spend on it… It would be nice to have it working properly…
I was never a wizard with gcode, so if I question anything I’ve done, it’s hand written gcode…
Jack,
I though you’ve succeeded to get my version of “a”(lpha) on but never bothered to update to V2. But I am in no position to be sure. Easy to check: “$I”, check the date of firmware on boot post. I recall my alpha was August and V2 - mid September.
V2 works better with defaults, except speed and acceleration I recommend later to be reduced to 3000 and 400 accordingly. Offsets better to reset to zero, it happily operates in exclusively positive space with no offsets. I have not noticed anything “odd”. If anybody seeing something odd - please let me know.
It is also possible that your application add some footer to the code, most apps do, like “go to absolute 0:0:” when job is complete. When offsets are set - this almost certainly will run you into the wall. This what I recall is possible problem with your setup. Not insisting, only suspecting.
If you like to iron all your wrinkles with JL1 - we can help.
Yes sir… I would like to ‘iron it out’…
Boot message
Waiting for connection...
ok
[VER:1.1f by LsrSal for forum.lightburnsoftware.com.August 25 2022, JL1 Build. Very Alpha. Use at your own risk!!!:]
[OPT:VM,35,254]
Target buffer size found
ok
Homing
error:5
Homing cycle is not enabled in your Grbl settings.
Have not enabled homing, so that’s not a surprise.
Other than auto homing being wrong … this is the device settings…
It thinks it’s home, from manual position of head are in the negative numbers if I ask for it’s location.
Don’t know if the offset holds when it’s rebooted… ?
Thanks…
Jack,
This is alpha without properly working home cycle.
Start from flashing V2. You have STLink. I know it is a lot of labor to crack that extruded case open, just conquer it. Flash that V2 firmware.
With V2 you do not need to preserve offsets. They will be reset/erased, but you no longer need them.
Also please make sure your home switches are clicking nicely, especially if you have fat laser head that most likely will not allow to reach original Y home.
Then, as already mentioned, change speeds and accels to 3000 and 400. If you like. You may leave defaults 5000 and 1000 but then “wobble” may be noticeable on fine burn details.
I would expect all your oddities with JL1 will disappear after that.
Please complete above and report about whatever else is not working.
I’m super happy the way my JL1 is working. I have no glitches whatsoever. I had DLC32 for a while but it is bulky and not in the native positive space, so I put my JL1 board back and very happy with it.
Let us know?
I have it and the st-link dongle out and ready… 
Moved it to the underside rail and there is plenty of ‘switch’ before the head gets near the frame. That’s an easy fix once it’s all working. Just a screw and slide it…
The only link I have is
and it gives me a 404 error… the other one I have is for jl2.
