Decorative gear background
Back to Projects

AutoPOL Bending Automation

Client: Dumaco
AutoPOL Bending Automation

At Dumaco, an engineer used to load each sheet metal part into AutoPOL (FCC Software AB), pick a bending machine, set up the settings and run the program by hand. A Windows service now does this. It picks up parts exported from SolidWorks, chooses a machine and settings for each one, and runs the bending program.

How It Works

Engineers design in SolidWorks as before. An add-in exports the parts to a folder, and the service picks them up from there and queues them. Each part goes through machine selection, program generation and a check of the output, and the result is logged. The queue is kept on disk, so a restart does not lose pending work.

Pipeline from the SolidWorks export folder through the background service to finished bending programs and a detailed log

From the SolidWorks export folder to finished bending programs.

Machine Selection

Each machine is defined with its limits: allowed thicknesses, maximum weight, and the length and thickness it can bend. Machines are tried in priority order, and a part goes to the first one it fits. That keeps the larger machines free for parts that need them. Machines are defined in configuration, so adding one does not need a new build.

A part tested against three machines in priority order; the first one whose limits it fits is selected

A part is tested against each machine in priority order.

Settings per Part

A heavy plate needs different tooling settings than a thin bracket. The service checks a list of conditions on mass, thickness, material and machine, and applies the matching AutoPOL settings before the program runs. After each part the settings are reset to a default.

When a Program Fails

A bending program can fail because the settings were wrong for the part, or because the machine cannot bend it. The service reads AutoPOL's output to tell which. Wrong settings are retried with a list of fallback settings. If the machine cannot bend the part, the program is generated again for another machine. Each part is retried a limited number of times, and every attempt is logged.

A failed run is split into a settings cause, retried with fallback settings, and a capability cause, re-queued on another machine

Wrong settings are retried; parts the machine cannot bend move to another machine.

The Export Manager

The Export Manager shows what the service has done. For each order it lists every export run, with the time, the number of parts that came out bendable, unbendable or filtered, and whether the run produced output. When a part has been exported more than once, the run that produced the current program is marked.

Export Manager listing every export run for an order with bendable, unbendable and filtered counts

Export runs for an order, with part counts and the active run.

It also holds the approval step before production. Each part is shown with a 3D thumbnail, its flat pattern, unfolded dimensions, thickness and material. An engineer approves or declines each part, or approves the whole order at once. A declined part stays out of production while the rest of the order continues.

Pre-production approval queue showing each part with a 3D thumbnail, flat-pattern DXF preview, dimensions, thickness and material

Approving parts before production.

Supporting Tools

A few smaller tools sit around the service. A service monitor shows operators the queue length and whether processing is running normally. A queue optimiser reorders waiting jobs so similar parts are bent one after another, which saves tool changes. A stock tracker follows how much raw material each program uses. A converter turns each part's STEP file into an HTML page, so the part can be viewed in a browser without CAD software.

Technologies Used

AutoPOL (FCC Software AB)
SolidWorks API
C#
.NET
Windows Services