Can you try connecting to it from the Windows computer now that you’ve loaded the firmware? Would rule out any driver issues.
I am as soon as my spousal unit wakes up and tells what she did with her computer 
Well, I’m about to sit down for dinner and eat a BIG bowl of CROW…
Grbl 1.1f ['$' for help]
[MSG:'$H'|'$X' to unlock]
[MSG:Caution: Unlocked]
ok
It talks on the windows machine. The default numbers are all messed up, so I need to know where @JVL got @LsrSal configuration information.
@JVL can you save the configuration that Lightburn reads, add a .txt appendage to it and post it so I can just load it.?
Thanks to all 
Appreciate it…
Don’t know what to do with the Linux box, never had this issue before that it wouldn’t talk…
I thought this to be the module…
jack@Kilo:~$ lsmod | grep ch341
ch341 24576 1
usbserial 57344 3 ch341
jack@Kilo:~$
1 Like
Jack, so you did flash it. Disregard my DM then.
You can try LaserGRBL to see that board does speak to PC. I’m sure it does.
Now figure out why your Linux machine does not want to see it. And this is entirely different topic.
GRBL settings are irrelevant for now. If and when I compile properly working firmware - I will put JL1 defaults there. For now I guess you are up to read a lot of Linux reference. LightBurn should see it as legit hardware and talk to it as it should.
Here are the settings, but they will not bring board with my incomplete firmware to functionality, I told you that already. This is as far I can take you for now.
Now I need time to work on that TIM1 to B0 pin partial remap. If and when I successfully complete that move - I will compile functional firmware.
JL1 GRBL Settings.txt (1.1 KB)
I’m wondering if this is the common issue of the wrong driver being loaded.
Take a look at this post:
https://learn.sparkfun.com/tutorials/how-to-install-ch340-drivers/linux
Apparently a lot of problems with CH340 on Linux.
For Windows - there is signed driver and installation of it is very trivial.
Interestingly, pretty much any GRBL source for STM32 has support for built in USB and probably intended for Blue Pill, that is commonly has 128K. I had to comment out USB support and default to first USART. JL1 is proper chip with “only” 64K, but it also has Winbond 256Q64 on SPI, that is 64Mbit flash! Most well compiled GRBL versions are ~40K. But adding support for built in USB will bring it over 64K.
It is surprising that with on-chip USB and massive flash available - JL1 designer still chooses to use external serial-to-USB. STM32 built in USB to serial is “class compliant” meaning no special drivers needed, any OS already has it. Even if I assume that USB excluded for speed considerations - other sources have no problem with it, I’m sure JL1 would not have problem either.
But whatever…
It is fun head scratchier…
1 Like
Put this in the systemd.conf file
CONFIG_USB_SERIAL_CH341=m
Reboot, then it didn’t connect right up, but I did get a header and it appears to be talking.
When I attempt to move it, they steppers are not working quite right, they move a bit, wait and then move back. Have to put my finger on it to feel it move…
I’ll hang in there until @JVL can drop the .lbcfg file for me to update the configuration…
Thanks a bunch to all, including Lightburn who upped my license for a 3rd machine, the Windows box…
Still don’t understand how come modprobe load of the same module didn’t fix it after a logout/in…
1 Like
Good morning all.
Jack, what is an lbcfg fille?
Do you mean the grbl settings?
Sal posted them in post 156
Sorry, I thought it was the configuration file extension, but it’s lbset.
-rw-rw-r-- 1 jack jack 12965 Feb 1 2022 20220101-no-rotary.lbset
I have a stack of them, depending on what I’m doing.
“Machine Settings → ‘save’” and it will write the current configuration to ‘whatever.lbset’.
I can use Lightburn to read it in and write it back to the controller… quick and accurate. Entering $ commands from the console reminds me of entering a bootloader from a binary panel before I can use it… very error prone.
I’ll see if I can paste it into the command window, but a loadable file would be nice…
Sorry about the hose up of the names… I shouldn’t ask questions when I’m tired, sometimes I make a left turn and leave everybody at the popcorn stand…
Thanks…
Jack,
If you’re replying to my post, then you’ve gone waaay over my head.
I don’t have half a clue what you’re talking about.
Sorry, yes it was your post… I’ve used large and small systems since the mid 70’s, if I’ve learned anything it’s don’t do it manually, it’s time consuming and error prone. This isn’t so much of a problem as the entries are rather minor.
Read this through the write, read, load and save descriptions. This writes the current configuration out as a machine readable format, I think it’s xml… Instead of 5 minutes cut/paste, I click load, get the data and write it to the controller… not even a minute and accurate.
We’re always leaning about Lightburns capabilities, but this seems like a no brainer and few seem to use it…
I have multiple ones, one for a ‘fast/slow’ rotary, fast/slow ‘no rotary’ for engraving … and test configurations. I can’t keep track of all that junk…
Made the changes…
I believe the long axes is x and makes the machine wide … either left or right arrow move the head in one direction, increasing the X values. It thinks it moves back, as X will decrease if I click the other direction arrow, but the head always moves in one direction away from the front/right, home or where the controller/switches are.
Identical operation with the Y axes.
Not sure where to look to correct the single direction issue… The connectors have never been removed, so they are not the problem.
IMHO, I think this topic is becoming a megalith ‘thread’ and we should split these out to something more specific and easier for the user (like me) to find. It’s confused me many times… this is post 162
Thanks for the time and assistance.
Jack,
I’m still not sure that I understand.
But if this helps you out, these are the only 2 file that I used.
(Sal provided both of them.)
JL1 GRBL Settings.txt (1.1 KB)
upgrade.zip.txt (38.4 KB)
First run the exe file then turn on Lightburn and make the changes to the configuration.
It runs perfectly other than it doesn’t have homing, that’s ok because I don’t need or want homing. Also the red laser cross hair pointer doesn’t work, again, I don’t know what its supposed to be for and don’t need it.
This machine is now doing everything I want it to.
2 Likes
While watching the FedEx golf tournament, put my new Cenoz to work doing its first tiles. I installed my new Z-lift and first did a NWT grid pattern tile with this new 3W(claimed) laser… with Grbl 1.1f firmware on the original JL1 controller and under Lightburn control
Using the test tile, I determined 1250mm/min and 100% power to give the “best black”…
image lasered and before paint removal…
Paint removed with acetone… “best black” block is far left (100%) and 5 down (1250mm/min)
and finished image (w/o flash). Stern look is to scare away daughter’s suitors…
Finished image with flash… LB processing - Jarvis dither, 339 dpi, all else defaults
– David
2 Likes
Looks good. Mine still has issues. Both axes have the problem, the motors drive it one direction. The X value will show the correct move, but the motor doesn’t reverse.
Don’t have a clue what is going on with it.
The firmware that @LsrSal provided you is a WIP. I believe he mentioned that laser PWM as well as motion was not functioning correctly. Only that you should get a reliable serial connection.
I used the ROM.bin that came with the upgrade.exe program, so it should be the same as @JVL and @dkj4linux are using… I hope. The only difference is theirs was loaded via the ‘upgrade.exe’ program and mine was loaded via st-link.
I have no clue what kind of setting would cause the motors to travel in only one direction.
I’ll try a reload of the ROM.bin, although I’m not optimistic…
It’s odd, I can change the direction bits and it will change the direction, but it will only go one direction…
Oh. I was under the impression that the one you had tested was based on @LsrSal’s build.
So you’re saying that the standard ROM.bin loads to 0x08000000? I wonder if that means that everyone’s bootloader is wiped.
Did you try loading @Lsrsal’s GRBL configuration?
If you can change Grbl settings, you might disable soft and hard limits for now. A motor will not go in a direction where it thinks it’s at its limit?
I did not try @LsrSal configuration. Not sure where it is now… I did check/change it based on @jvl post 162, that zip is also contains the ROM.bin.
That’s what shows up when I load ROM.bin and write it. I don’t enter anything for addresses. I hope it’s in the bin file, usually is.
I can’t image it running at all if it’s not loaded at the right offset.
This is odd, and I haven’t mentioned it. With the controller box front right as shown. I expected the right and left arrow to move the laser head, but it moves the Y gantry instead of the X laser head.
When I click the right arrow (X) it moves the Y gantry and vice versa… mean anything special…?
