Machine Origin and job origin are 2 different things. Machine Origin is the corner your machine homes to and is always the same. Job Origin is where your engraving starts from and is user selectable on a per job basis.
It would be less confusing if the same word wasn’t used for both.
The firmware is, but the board is not. It’s one of the most used control boards and reference design. It’s still not perfect, but a very solid solution. The MKS firmware is bad, you should consider changing to FluidNC here. That’s the next-generation firmware with full support of the DLC32 (except the display, which is stupid anyhow). It’s also much easier to configure.
Yes, that’s easy as flashing an Arduino The only thing you need is a configuration file for the board. There is one in the repository, that is mainly targeted on a K40 laser, I think. I also created some configurations, I think I posted them here (bottom of the page): Mainboard Replacement - Diode Laser Wiki But you can take this as a base and change it as you need.
That’s really great to know. It would be nice if the display gets supported. If FluidNC is O/S, then I bet it will. Once this round of machine modifications are complete, I’ll look at switching over.
I’m using the laser version. From what I have gathered, the firmware version I noted above is laser with Z. It seems from reading other issues/complaints about the firmware, the devs forgot that a lot of laser cutters need a Z axis. I have just discovered that the firmware doesn’t support G28.2, which is a bummer.
I gave up and went back to Arduino controller that I know would work.
I still struggle setting it up but, knew it was doable since I have it on my other machine.
For what it’s worth, I’ve had good results with an MKS DLC32 v2.0 board and TS-25 display running v2.08 laser firmware. Including extensive z-axis use.
Some day I want to try FluidNC but had bought the display (for $8, oh my) so that I could test things as I designed and built my laser cutter without adding a computer, connectivity and LightBurn to the mix.
The USB connection gave me some periodic grief (probably the laptop USB ports going to idle power modes). I wanted to be untethered, anyway, so connected the MKS board to a Digi AnywhereUSB device… after experiencing flakiness with connecting via HTTP to the device. I guess the sort of things you may expect from bundled firmware of a controller you can buy for dozens of dollars. If you’re that cheap you’re probably not stellar on both the hardware and software sides.