GRBL 1.1 Running on a Smoothieboard 500 mm/s, 79,000 steps/s 0.3 mm pixel spacing

@Arion_McCartney The slate looks awesome! What do you have in the End-Gcode? I got that strange move also once, when I had a G0X0Y0 at the end.

@Jim_Fong CoreXY kinematics is implemented, but needs to be compiled in with a compile flag. I’ve made a special firmware.bin for you to test. (see https://github.com/cprezzi/grbl-LPC/releases/tag/beta05-corexy-v1.1f).

@cprezzi great thanks, that saves me lots of time by not having to figure out a build compile. I had to compile 1.1 for corexy so I assume it was also needed for lpc version

I would like to see if the arm can push a few more pulse per second on this setup.

Edit. Downloaded firmware and installs fine I can run gcode and see the step pulse output. I’ll make a video of it controlling the corexy machine next. Thanks a bunch.

Edit2 Seems to run gcode much much slower than the non corexy firmware.bin. Interesting…

Edit3. Laserweb4 wont connect. Says no supported firmware detected. However grbl panel connects and can stream gcode to it. The non corexy firmware had no problem connecting.

@cprezzi ​ I only have M5 and M2 in end-gcode.

Strange. I need to make some tests then.

What welcome string do you get when connecting to that firmware?
We will not accept if it’s different than grbl >1.1c.

@cprezzi grbl panel reports it as 1.1f.20170131

I reset the PC and it streams gcode much faster now. Joys of running Windows.

@cprezzi Did some testing this morning with the end-gcode commands. Sure enough, putting M2 command in the End-Gcode creates a random position. Without it, i can engrave all day without position being lost! I don’t seem to encounter any issues when running multiple gcode jobs without the M2 command at the end of the gcode, so I am going to leave it out for now. M5 does not affect position. I only had M5 and M2 in the end-gcode. I tried removing both one at a time and found that M2 was causing the issue (directly or indirectly…). Hope that helps.

Ok, now i got all changes from claudio and fix the y axis homing. Please try download the latest firmware over my github link above. Homing works now :slight_smile:

@cprezzi doesn’t look like the corexy kinematics is enabled for the firmware you gave the link for. Can you check to make sure the compile flag was enabled.

I get standard Cartesian xy output.

@Jim_Fong ​ ok, I will check again.

@Jim_Fong I have checkd the config, recompiled and replaced the firmware.bin in the release page https://github.com/cprezzi/grbl-LPC/releases/tag/beta05-corexy-v1.1f. Could you try again?

@cprezzi ok thanks. I’m at work so it will be late tonight until I can try it.

@Frank_Herrmann Homing works great! Must add the following to the homing gcode in LW: G10 L2 P1 X-300 Y-200 for correct coordinates after homing.

@Frank_Herrmann What other changes did you make other than homing?

@Arion_McCartney just homing, the base code is from @cprezzi

@Frank_Herrmann ​ awesome thank you!

Nice guys! Together we get it done! :slight_smile:

@cprezzi ok that worked, thanks. You get both step outputs working simultaneously when doing a single axis move. Hooking up the board to the machine and will post a video soon.

@cprezzi short video grbl-LPC corexy.

grbl-LPC 1.1f set at
60,000mm/min (1000mm/sec) speed
10,000mm/sec^2 acceleration
Automation Direct nema17 76oz-in stepper motors
10 microstep
Parker E-DC stepper drivers
42volt power supply


Panucutt re-ARM with a RAMPs plugged in. External high performance Parker stepper drivers.