Can Burny 2.5 Run Modern Plasma-Cutting G-Code Safely?

The stored patterns still run, but the lost programming laptop leaves no proven workflow for turning revised drawings into code the Burny 2.5 and the existing plasma table can execute. Keep the old controller in service while you identify its accepted code and transfer method; do not replace hardware or load untested code just to recover the design workflow.

Avoid quick fixes that leave the machine unverified

Three shortcuts can consume shift time without solving the compatibility problem:

• Load generic router G-code. A file extension or the fact that a CAM package can generate G-code does not establish that its commands, torch controls, motion behavior, or program format match this Burny installation. A router post may omit plasma-specific torch sequencing or emit unsupported commands.
• Install LinuxCNC on a Raspberry Pi and connect it. A controller replacement is not a software-only swap. Motion hardware, drive interfaces, machine I/O, torch control, limits, homing, and safety circuits all need a compatible design and commissioning. A computer running control software does not automatically interface safely with the machine.
• Replace the Burny before checking the existing workflow. If the machine still cuts its stored patterns, the immediate failure is the missing programming and transfer path—not necessarily a failed controller. A retrofit may be appropriate, but it adds electrical and commissioning work that low-volume production may not justify.

For a handful of parts, outsourcing the revised cuts is also a valid temporary production option. Compare its cost and lead time with recovering the old workflow or replacing the control, rather than committing to a retrofit before identifying the machine interfaces.

Separate drawing, CAM, postprocessing, and transfer

A CAD drawing describes part geometry; it is not automatically a cut program. The workflow has four distinct jobs:

1. Create or revise vector geometry. Use the CAD or vector-editing tool to define the part outline at the intended scale. Inkscape is one free vector-editor option mentioned for creating vectors that can be imported into CAM.
2. Generate the cutting path in CAM. Plasma CAM places the geometry on the sheet and determines toolpaths, cut order, lead-ins, pierce points, kerf compensation, and process settings. These decisions affect whether the torch pierces and cuts the intended contour.
3. Postprocess for the controller. The postprocessor translates CAM operations into the command dialect and output conventions expected by the machine. SheetCam is a plasma CAM package worth evaluating, but confirm that its available post can be configured and tested for this specific Burny 2.5 setup.
4. Transfer the program. A separate communication or file-transfer method may be needed to move the output to the controller. Identify what this machine uses; do not infer it from the age of the control or from a file extension.

Keep these stages separate during troubleshooting. A drawing-import problem, a bad toolpath, an incompatible post, and a failed transfer can all look like “the new program does not work,” but each needs a different correction.

Identify what the Burny and table accept

Before creating production code, inventory the installed control and machine rather than relying on a generic Burny example. Record the controller’s displayed identification, available manuals, existing program names and formats, and the way operators currently select and run the stored patterns. Preserve copies of known-good programs without editing them.

Use a known-good program and machine documentation to determine:

• How programs reach the control and how the operator selects them.
• Which command syntax, units, coordinate conventions, and motion commands the working programs use.
• How the program commands torch on/off and any machine-specific cutting functions.
• Whether the machine has a torch-height control or other process I/O that the program or control must coordinate.
• How the machine homes, handles limits, and establishes the program origin.

Do not guess at interface type, serial settings, commands, or machine ratings. Read them from the control and machine documentation, or identify them with a qualified CNC technician. A postprocessor is a configuration item to validate against the installed machine, not a promise that a controller bearing the same family name uses identical settings.

Use a matching plasma post before cutting a part

Once you know the expected code and process behavior, evaluate a CAM package such as SheetCam. The practical question is not whether it can export a file called G-code; it is whether the post produces a program the Burny can interpret and that correctly operates this table’s torch and motion sequence.

1. Import a simple test profile and check that its scale and orientation match the drawing.
2. Set the material and process values from the machine’s established cutting procedure or the applicable equipment documentation; do not copy guessed values from a different plasma system.
3. Generate the toolpath with the intended cut order, lead-ins, pierces, and kerf compensation.
4. Inspect the posted output against a known-good program and the controller documentation. Look for unsupported commands, different units or coordinate assumptions, and missing or misplaced torch commands.
5. Confirm the generated program can be transferred and selected by the established method before introducing it to production.

If the CAM package has no verified post for the installed configuration, ask the software provider or a qualified integrator whether the post can be adapted. A post modification must be tested on the actual controller and machine; do not treat an example post or a successful export as proof of compatibility.

Test the new program without risking a production plate

Use a controlled commissioning sequence. Keep the existing proven programs untouched, and make the first new-program test on a safe setup that does not create an unexpected torch strike or axis move.

1. Transfer a copy of the test program and verify that the control displays or selects the intended file.
2. Review its start point and path in the CAM preview, then compare that path with the drawing and intended sheet placement.
3. With the torch disabled using the machine’s documented method, check that the axes follow the expected profile, direction, and start/end points. Confirm that coordinate scale and origin match the setup.
4. After the motion test passes, make a supervised test cut on suitable scrap using established machine settings. Observe torch sequencing and motion through pierce, contour, and end-of-cut behavior.
5. Inspect the cut against the required geometry and dimensions. Correct CAM geometry, process setup, or post output according to the fault observed, then repeat the test before releasing the program.

Do not bypass guards, interlocks, or safety circuits to make a test program run. If the control’s documented safe test method is unavailable, stop before enabling motion or the torch.

Use symptoms to locate the failed stage

When a test fails, identify whether the fault appears before transfer, at program interpretation, during motion, or during cutting. Change one stage at a time so that a correction can be verified.

Observed symptom	Likely stage to check	First diagnostic
The drawing imports at the wrong scale or with broken contours.	Geometry or import	Check drawing units, scale, and whether the contour is closed and usable as a cut path.
The CAM preview is not the intended part path.	Toolpath setup	Check contour selection, cut direction, lead-ins, kerf compensation, and cut order.
The control cannot select or interpret the transferred program.	Postprocessor or transfer	Confirm the transfer method and compare output conventions and commands with a known-good program and control documentation.
The axes move, but the path is misplaced or scaled incorrectly.	Units, coordinates, or setup origin	Compare the program’s units and coordinate assumptions with the CAM setup and machine work origin.
The motion path is correct but the cut does not start or finish correctly.	Torch/process commands or machine setup	Check torch sequencing and process settings against the established procedure and machine documentation.

These symptoms are diagnostic branches, not confirmed faults on this particular machine. Use the control display, program behavior, and measured cut to decide which branch applies.

Choose between recovery, retrofit, and outsourcing

For low-volume work, first price the simplest viable route: recover the CAM and transfer workflow for the installed control, outsource the altered parts, or replace the control or machine. Compare recurring production needs, availability of compatible programming support, machine condition, and the cost of electrical integration and commissioning.

Retain the Burny if a compatible, testable post and reliable transfer path can be established and the machine continues to perform its existing work. Consider a retrofit when the current control or its programming path cannot be maintained, or when future production needs justify the engineering effort. A retrofit must account for the existing drives, feedback, I/O, torch interface, motion limits, operator controls, and safety functions; determine these from drawings and inspection before selecting a new controller. LinuxCNC may be part of a retrofit, but it is not a plug-in replacement that can be assumed to run the machine from a Raspberry Pi alone.

FAQ