So yesterday when I finally go the machine to move, I could jog it around just fine. Then I opened up the file for the tile (above) and now the machine will not jog.
What should my starting point be today?
What does the Console say when jogging and locking up? Pics/screenshots help…
And where is the laser head when you’re trying to jog?
Finally got around to working on a Z-lift mechanism…
Need an adapter plate (printing now) with 4mm holes… to replace the wooden slat 
– David
Silly me… don’t need an adapter plate. Laser is small and I assumed it was too narrow… but it wasn’t
The head is in the last place when I torned off the machine.
I do not have homing cycle because I don’t need it.
I just got it working.
If it helps anyone out, here are my current settings.
EDIT.
DONT USE THE SETTINGS THAT I JUST POSTED.
I DONT KNOW WHATS GOING ON YET BUT THEY ARE WRONG.
You’re talking about the jogging? What was the fix?
i made a couple of changes in the setting and the jogging started working.
So now I have a tile burning, I check settings in the console, and they are different.
Don’t know why.
Is there maybe a step that I’m missing to lock in the settings?
Typically no. They should be written immediately if allowed.
Jan,
I got through this confusion and realized that board constantly tripping into safety lock. This is due to out or range positions and home/end sensors.
Find my other thread with GRBL settings dump. Set it up and it will run smooth. No home cycle though.
Can you post them again please?
Jack,
With original boot loader, that firmware can load at different address and may start from boot loader then just jump to that firmware address. We may never know, because that firmware is locked. I know for sure that it does not run from default address.
That 0x8000000 point is the beginning of the flash and default execution start with boot pins default configuration. As that firmware does not run from default flash beginning - there is very little hope to actually make it run at all, not without original boot loader or unlocked firmware.
The best shot we have is to recompile from some source.
Me too already got DLC32 and already printed box case for it. It runs just fine tethered. I got big screen (3.5") and realized that I probably will never use it. If I would need screen again - probably will get smaller one. More likely - no screen at all.
With that - It is fun challenge to make firmware for original board. I will work on it in spare time. I believe I’m making progress with that hardware timer relocation (TIM1_CH2N) to make PWM proper.
That STM32 is very different from Atmel. That HAL CubeMX spitting a lot of code that to me is very difficult to manually sort through.
I;ve tried to find another source, like to Atollic, but none that I’ve tried compiled cleanly, and cleaning these warnings and errors is beyond my intentions.
So, for a while I will stay with that Embitz compiler and try to generate HAL config for that code with CubeMX.
Any volunteers to star shared project on GIT?
I need help to figure out how to move TIM1 from A8 to B0. This is done through “partial remap” but so far I see no PWM on B0. Requires duplication of all registers for CH2 from CH1 and then do proper timer output configuration on B0. That pin relocation also forces to use CH2 of TIM1, instead of CH1.
The only way I can upload to the controller is via the st-link hardware. You can’t write to it or read it without wiping the firmware. That’s security of the micro…
With st-link, I’m not using a boot loader, so I think discussion is moot, unless the boot loader handles the serial communications port, doubtful.
I’d love to load your binary and see if it will talk, that would give me some satisfaction.
The IDE you use is only available on a Windows platform, from what I can tell. I have the ‘cube’ programmer and their IDE (Eclipse, I think) on my Linux machine, so it would be nice if I could get it to compile…
Just adjusted my settings to match lsrsal.
turned the machine and Light burn on and off a few times and the setting seem to be holding.
Everything works perfectly and currently running a tile.
Thank you Sal.
1 Like
Loads ok at the 0x8000000 address, but Lightburn won’t connect.
The same message
Waiting for connection...
Port failed to open - already in use?
That’s I’ve been getting… Thanks for uploading it… Might want to just delete that post before someone loads it while in hua mode.
Jack,
I’ve gotten that message before too.
Found that I just had to choose another com port on the laser tab.
That is not firmware, that is port selection.
Don’t follow you…
In the application, select com port. If not sure: pull USB out, check what ports available. Plugin back - see which one appeared new and select to be use by the app.
I know what com port it is, that’s not in question.