The logic of machine program formats
The common denominator: tabular description
Section titled “The common denominator: tabular description”Practically every production line works from CSV. This is a simple, text-based, tabular format that almost every LGS design tool can produce.
Its logic is direct: each row describes one operation or one member, with a position and a parameter. An operation repeated many times — a series of identical holes, say — appears in the file as many times as it is actually performed. A longer file, but a direct description.
Manufacturer-specific formats
Section titled “Manufacturer-specific formats”Some manufacturers use their own format. These carry essentially the same information with different logic: instead of listing operation by operation, they describe a run — how far the given part extends — and the line’s software decides how closely to space the operations along it.
A shorter file, one layer more abstract. In practice this causes no problem: when the program is prepared we know which machine it is going to, and we issue it in the right format.
Why this matters: machine independence
Section titled “Why this matters: machine independence”Because most controls accept a standard, tabular format, the same design work can be issued to any compatible machine. The brand of machine does not limit which projects can be taken on.
This matters particularly to those who bought a cheaper machine and did not get a full ecosystem with it — software, training and support in one package. For them machine independence is not a theoretical question: they have a machine that can produce, but nobody to give them a manufacturable design and program.
What the format does not solve
Section titled “What the format does not solve”Machine-specific parameters
Section titled “Machine-specific parameters”The format is common, the content is not: profile set, tool positions and maximum length differ between machines. Hence the machine-specific template. Machine-specific template.
Geometric verification
Section titled “Geometric verification”A file being readable does not mean the machine can produce what is in it. Trial production proves that. Trial production.
Model exchange
Section titled “Model exchange”A machine program is production data, not a model. Collaboration between disciplines needs a model format — typically IFC.
The point
Section titled “The point”The format is rarely the obstacle. The obstacle is usually not knowing the machine-specific parameters — and those can be surveyed.