Compatibility
Will it drive your table?
AlgoNest ships with 82 post-processor presets covering more than forty controller and machine families. A preset is plain data — codes, formats, header and footer — so you can open one, read it, copy it and change it without waiting for us.
Read this before you count your machine as supported
There are three honest levels here, and we label every preset with one of them. Only the first means we have watched steel being cut with it. The other two mean the codes are right on paper and nobody has yet stood next to the machine while it ran.
If your controller is on this page at level two or three, we would very much like to hear how it went — good or bad. That is how a preset gets promoted, and it is the whole reason the demo exists.
Cut with, on a real table
We loaded the output into that controller and cut parts with it. Three presets, one machine — ours.
Built from a machine's own working definition
The codes, framing and formats come from post definitions that shops run on these machines every day. Sixty-five of them.
Written from the published codes
Correct on paper, from the controller's documentation or a known torch-code family. Run it on air first, torch off. You should do that anyway.
The list
What is in the box
| Preset, exactly as it appears in the program | Torch on | Torch off | File | Level |
|---|
Nothing matches that. Try the builder's name, the controller, or a code like M07 — and if your machine genuinely is not here, we will write the preset.
All machine and controller names are the trademarks of their respective owners and appear here only to say which dialect a preset produces. AlgoNest is not affiliated with, endorsed by, or connected to any of them.
Not on the list?
We will write the post-processor for your machine.
Fixed price, no estimating, no hourly rate that grows while you watch. You send two things, we send back a preset that produces code your controller accepts.
Send us a sample program
A real NC file that your machine has actually run and cut correctly. Not a fragment, not a file that “should work” — a whole program, from the first line to the last, that came off the table with parts attached to it.
Send us the drawing that sample represents
The DXF (or a dimensioned PDF) of the parts in that program. This is the half people forget, and it is the half that matters: without it we can read the codes but we cannot prove what they meant. With it, we can regenerate your own program from your own drawing and compare the two line by line.
We build it and you check it on air
You get the preset, a note of what each code does and why, and our own comparison against your sample. Run it with the torch off first. If something is off, we fix it — that is included, not extra.
It goes into the standard set
Unless you ask us not to. Your machine's preset ships to everyone else in the next release, and yours keeps working when the format changes. If you would rather it stayed yours alone, say so and it will.
Custom post-processor
Per controller dialect, not per machine — if you have four identical tables, it is still €249.
- Built from your own sample program and drawing
- Compared against your sample, line by line
- Corrections included until it runs
- Documented, editable, not locked
- Maintained in later releases
Price excludes VAT. Bespoke work, so it is not refundable once delivered — which is precisely why we ask for the sample and the drawing before quoting anything.
Or do it yourself, for nothing
Presets are data files, not compiled code. Copy the nearest one, change the torch codes and the header, save it under your own name. If you get it working, send it to us and we will ship it to everybody — with your machine's name on it and none of ours.
Try it on your own machine first.
The demo produces real G-code, up to three parts per plate. That is enough to load a program into your controller and find out whether AlgoNest and your table understand each other — before any money changes hands.