GRBL 1.1e ?
Your working program used 25538 bytes (83%) of storage space. Up to 30720 bytes.
Global variables use up to 1516 bytes of memory (74%). There are 532 bytes left for local variables. Up to 2048 bytes can be used.
I need to do a thorough code cleanup
When t2 laser program GRBL 1.1 is loaded, it works diagonally
x and y directions required
except that GRBL 1.1 is faster than the first one
also laser dynamic workable
continue research ... can you suggest resources in this regard?
I have GRBL 1.1e installed on my EleksLaser-A5 it's running on mac using UGS and I have also successfully connected using Laserweb (which I am just getting my head around)
@Zax now I have 1.1e installed F#NAN# appears to do nothing thus I currently can not control the speed of each directional burn, what I have do is set $110 and $111 and a much slower rate to compensate just to confirm the g-code is correct right ??
this works fine except F1000 or F1 has no effect, however I'm sure it did with GRBL 0.9
X10 Y10 M03 S1000 F1000
X10 Y0 M03 S1000 F1000
X0 Y0 M03 S1000 F1000
X0 Y10 M03 S1000 F1000
@nebiaydogdu That's because my Grbl 1.1e is for a Cartesian (standard XY) not a CoreXY coordinate system.
@gerryghall You need to use the G01 command for F values to have any effect. The default is G00 rapid feed.
Hey @Zax, yeah I learnt that last night while playing about I altered the feed rate to compensate as the laser is only small, I got the A5 version due to the lack of space but think I'll upgrade the laser just for better performance as I'll be cutting wood most of the time..
@gerryghall Feel free to contact me if you have questions, I wrote T2Laser from scratch after getting the machine and being unable to get Benbox to work on my machine (or download actually, it had malware so my protection kicked in and deleted it).
Yeah well I come from the MS word developed VB6, ASP and DOTNET, these days though I kick around with Java, GO, Swift node php mainly.
I see you mention Tlaser run in a VM ? I'm going to give it a go I think LaserWeb has quirks the main one, it is really slow at vector rendering and producing Gcode.
@gerryghall I do have quite a few customers using VM's, the most popular seems to be Parallels.
I have a local server running docker I remote access to it, I should still be able to expose the usb-serial port but if not I have Virtualbox, I did have parallels historically but due to mainly development reasons started using Vbox.
Is there any grbl1.1 firmware work for elekdraw?
@nebiaydogdu I'm also interested in updating my Eleksdraw to GRBL 1.1.
I'm pretty handy with Arduino - is it just a matter of downloading the grbl code, configuring it for CoreXY, creating a .hex and flashing it, or is there more to it?
You are probably referring to my "default" firmware in T2Laser. If so, no it will not as it is configured for a Cartesian axis laser.
As dylanmc said, you can compile Grbl 1.1 with CoreXY and Servo support but will need to remove other features, like homing to get the size low enough to fit on the Nano.
I recommend sticking with the mana.hex (Grbl 0.9) on the EleksDraw for ease, since EleksZ did a great job making it selectable for both axis and laser or servo. There's not much benefit on the EleksDraw to use 1.1, the main benefits are for dynamic laser control and real time overrides.
I probably should have waited for @Zax's reply, but I tried to flash a freshly built grbl1.1. avrdude started out fine, then reported a ton of messages. Now I think I need to reflash the bootloader, because when I try to flash even just a tiny program, avrdude complains "programmer not responding".
I've got an ICSP programmer - is there a way to start from scratch that way? Alternatively, I have a few Arduino Nano clones - could I plug one in in place of the Eleksdraw's nano?
Finally, I realized I configured the gerbl software for CoreXY, but didn't see any options for configuring Servo support - how does one do that? Thanks!
You can install Uno Optiboot (smaller bootloader) to your Nano using a ICSP or Uno/Nano as programmer. That gives you a little more memory and should make it possible to enable CoreXY and Servo support without too much trouble.
Of course you can always swap the Nano, they're all the same.
@Zax - thanks for the info -- you're a superb help to the community. Oh, and Happy New Year!
@Zax I successfully flashed the EleksROM.hex to a new Nano (my ICSP programmer is at work). I was surprised that by default it doesn't use CoreXY mode, and I had to use EleksCAM to set it to that mode, as well as the Servo mode. I'm sure there are $ grbl commands to do that, but didn't know what they were. Happy that it's 100% working again, but still interested in being able to build my own grbl1.1 version. It seems that the EleksMaker fork of grbl should be out there, which would help folks like us merge their cool changes into the current grbl version.
My build of the grbl-servo 1.1 fork installs fine, but doesn't respond to any serial commands - I can't really tell what's gone wrong yet.
@dylanmc Yes, being open source EleksMaker should publish it.
T2Laser has a menu to change the settings / modes, and also shows what the commands are in case you are interested.