The machine program: what we hand over
What the controller expects
Section titled “What the controller expects”The line does not get a drawing but a file describing, member by member and position by position, what the machine has to do: where to cut, where to punch, to what length. The machine does not get a drawing.
CSV and RFY
Section titled “CSV and RFY”Practically every line works from CSV — a simple, text, tabular format that almost every LGS design package can produce.
FRAMECAD differs: it uses its own RFY format. It carries the same information described with a different logic — CSV lists the operations directly, RFY describes a stretch and the line’s software decides the spacing. The logic of machine program formats · What the system exports.
In practice this causes no problem: when we produce the program we know which machine it is going to, and we issue it in the right format.
What goes with the program
Section titled “What goes with the program”- panel drawings member by member, with position numbering,
- material take-offs,
- the assembly sequence, where it makes sense,
- and the machine-specific settings the program is built on.
Why it is not a generic file
Section titled “Why it is not a generic file”Because the program is tailored to that machine’s parameters: profile range, punch positions, maximum length, marking method. The same model gives a different program for a different machine.
If you work with a machine we do not know, a survey comes first. Machine survey.
Who we hand it to
Section titled “Who we hand it to”Whoever manufactures: you or the manufacturer, as agreed. If you do not have your own machine, we can recommend one who works from our drawings. We design, we do not manufacture.
The point
Section titled “The point”The machine program is not a by-product but the result of the shop design. It works because we know which machine it is going to.