.BNC File Format

Overview

.bnc is a text-based press-brake program container for bending machines. It combines structured process tables with embedded geometry and preview payloads.

The file has three main parts:

a short file header
a sequence of named table sections with metadata and records
embedded model and preview blocks at the end of the file

This file is 11896 lines long and ends with ED.

Top-Level Structure

C
BD
SET_METRIC
C
BEGIN_SECTION
ZA,MM,<field-count>
MM,AT,...
...
ZA,DA,<row-count>
DA,...
...
ENDE_SECTION
C
...
START_MODELLDATEI_<id>
... payload ...
STOP_MODELLDATEI_<id>
C
START_VORSCHAUDATEI_<id>
... payload ...
STOP_VORSCHAUDATEI_<id>
C
ED

Header And Terminator

The file begins with:

C
BD
SET_METRIC
C

BD identifies the file as a BNC-style data container.

SET_METRIC declares metric units.

The file ends with:

ED

Common Record Types

`C`

C is used as a separator line between logical blocks.

`ZA,MM,<n>`

Declares a metadata table with <n> field definitions. The following logical rows are MM,AT definitions.

`MM,AT,…`

Defines one field in a section. Observed format:

MM,AT,1,<field-id>,0,0,,'<field name>',,'<unit>',<type>

Relevant parts are:

<field-id>: section-local field identifier
<field name>: display label, mostly German in this file
<unit>: optional engineering unit such as mm, sec, deg, kg, kN, or Stl
<type>: data class

Observed types:

T: text
Z: numeric value
E: enumerated value
B: boolean value

`ZA,DA,<n>`

Declares <n> data rows for the section. The following logical rows are DA records.

`DA,…`

Stores one data row, ordered exactly like the preceding MM,AT schema.

`*`

A line beginning with * continues the previous DA row. This is used for long records split across multiple physical lines.

`GE,PA,…`

GE,PA is a relationship row. It appears immediately after some DA rows and links a parent identifier to one or more child identifiers.

Examples from this file:

GE,PA,'WzgGrp001','Wzg001','Wzg002'
GE,PA,'WzgStat001','WzgGrp001'
GE,PA,'ModPict001','ModPos001','ModPos002',...

This means the .bnc format is not only tabular; it also carries graph-like references between records.

Section Pattern

Most structured sections follow this pattern:

BEGIN_<name>
ZA,MM,<field-count>
MM,AT,...
...
ZA,DA,<row-count>
DA,...
...
ENDE_<name>

Structured Sections In This File

Section	Lines	Data Rows	Purpose
`KONFIGURATIONSDATEN`	5-17	5	Machine and software configuration records.
`FERTIGUNG_AUFTRAG_TMP`	20-31	1	Job-level order record pointing to the generated BNC program path.
`BIEGETEILSTAMM`	34-66	1	Master data for the bend part, including material, thickness, dimensions, IDs, and timestamps.
`WERKZEUGSTAMM`	69-95	4	Tool master data for punches and dies.
`WERKZEUGGRUPPE`	98-114	2 plus `GE,PA`	Tool group definitions with references to member tools.
`WERKZEUGSTATION`	117-131	2 plus `GE,PA`	Tool station definitions with references to tool groups.
`MODELLSTAMM`	134-152	10	Model catalog describing embedded models.
`MODELLSTATION`	155-198	25	Placement and transform data for models.
`MODELLABLAUFDATEN`	201-216	4 plus `GE,PA`	Bend-step picture/model grouping for process visualization.
`ANSCHLAG_SETZEN`	219-260	4	Backgauge positions, speeds, increments, and related settings.
`TEIL_KLEMMEN`	263-287	2	Clamp and mute-point settings for each bend step.
`TEIL_BIEGEN`	290-323	2	Pressing and bending parameters such as angle, force, bottom position, and speeds.
`TEIL_FREIGEBEN`	326-341	2	Release and opening motion after each bend.
`BIEGESCHRITTDATEN`	344-380	2	High-level bend-step records linking stations, gauges, clamp data, bend data, and release data.

Section Details

`KONFIGURATIONSDATEN`

This section stores configuration key records. In this file it includes machine, controller, programming system, and backgauge finger configuration.

Representative values:

TruBend
5320 (6-axes)
Flux
BackgaugeFingerLeft
BackgaugeFingerRight

`FERTIGUNG_AUFTRAG_TMP`

This section stores one temporary manufacturing-order record. The record contains the full generated program path:

C:\ProgramData\Metamation\Flux\Output\Code\1001-E420-0002[4].bnc

`BIEGETEILSTAMM`

This is the main part master-data section. It defines 25 fields, including:

part ID and drawing number
timestamps
operator
material and sheet thickness
weight
enclosing rectangle size
number of bend steps
processing time
part X/Y/Z dimensions

Its single DA record is split across multiple physical lines using * continuation.

`WERKZEUGSTAMM`

This section defines the individual tooling records. Observed fields include:

tool name
tool type and kind
angle and radius
height and length
depth values
die width
material number

This file contains four tool records.

`WERKZEUGGRUPPE`

This section groups tools into logical assemblies. Each DA row is followed by a GE,PA row that lists the tools belonging to that group.

Example structure:

DA,'WzgGrp001',...
GE,PA,'WzgGrp001','Wzg001','Wzg002'

`WERKZEUGSTATION`

This section defines stations and links each station to one tool group through GE,PA. It adds positional information such as total height, total length, and base coordinate system.

`MODELLSTAMM`

This section is a catalog of embedded model identities. Each row references one model ID such as Model001 through Model010 and records model type and file flags.

`MODELLSTATION`

This section defines where models appear in space. Its fields include rotation matrix elements and translations:

RotateX1 … RotateZ3
VerschiebungX
VerschiebungY
VerschiebungZ
linked model ID

The section contains 25 placement rows.

`MODELLABLAUFDATEN`

This section groups model positions by bend number and bend orientation. Each row is followed by a GE,PA relation listing the model positions used for that process image.

`ANSCHLAG_SETZEN`

This section contains backgauge setup records. It defines 30 fields including:

left and right gauge coordinates
correction values
axis speeds
wait time
retraction values
sensor mode
finger support flags
increment values

There are four backgauge records in this file.

`TEIL_KLEMMEN`

This section describes clamping behavior for each bend step. Fields include mute point, clamp point, tool-table position, wait time, closing speed, sheet-thickness correction, and LCB preparation positions.

`TEIL_BIEGEN`

This section stores the actual bend-process parameters. Fields include:

target angle
bottom dead point
press correction
hold time
press force
bend speed
crowning
sensor positions

This file contains two press records: Press001 and Press002.

`TEIL_FREIGEBEN`

This section stores opening and release motions after bending. It includes release path, opening path, opening speed, and LCB extraction positions.

`BIEGESCHRITTDATEN`

This is the orchestration section for bend steps. Each record links together the other setup records by identifier. Observed link fields include:

station IDs for top and bottom tooling
backgauge ID
clamp ID
bend ID
release ID
die-group ID

This means BIEGESCHRITTDATEN is effectively the execution plan for the program.

Embedded Model Blocks

After ENDE_BIEGESCHRITTDATEN, the file switches from table sections to payload blocks.

There are ten model blocks:

START_MODELLDATEI_Model001 … STOP_MODELLDATEI_Model001
START_MODELLDATEI_Model002 … STOP_MODELLDATEI_Model002
START_MODELLDATEI_Model003 … STOP_MODELLDATEI_Model003
START_MODELLDATEI_Model004 … STOP_MODELLDATEI_Model004
START_MODELLDATEI_Model005 … STOP_MODELLDATEI_Model005
START_MODELLDATEI_Model006 … STOP_MODELLDATEI_Model006
START_MODELLDATEI_Model007 … STOP_MODELLDATEI_Model007
START_MODELLDATEI_Model008 … STOP_MODELLDATEI_Model008
START_MODELLDATEI_Model009 … STOP_MODELLDATEI_Model009
START_MODELLDATEI_Model010 … STOP_MODELLDATEI_Model010

The payload begins with text such as:

15 Flux SAT Writer 8 ACIS 3.0 24 Wed Jan 01 08:00:00 2014

and then continues with ACIS SAT geometry records like body, face, vertex, edge, straight-curve, and plane-surface.

These blocks are raw geometry payloads and should not be parsed as DA records.

Embedded Preview Block

After the model blocks, the file contains one preview block:

START_VORSCHAUDATEI_Preview001
424D...
STOP_VORSCHAUDATEI_Preview001

The payload starts with 424D, which is the hexadecimal signature of a BMP bitmap. This block therefore stores a preview image as raw hex data.

Parsing Notes

When parsing this file, the main rules are:

skip standalone C lines
use BEGIN_* and ENDE_* to delimit structured table sections
read MM,AT rows as the schema for following DA rows
merge lines beginning with * into the preceding DA record
treat GE,PA as parent-child relationship records
treat START_MODELLDATEI_* … STOP_MODELLDATEI_* as raw ACIS SAT geometry payloads
treat START_VORSCHAUDATEI_* … STOP_VORSCHAUDATEI_* as raw preview-image payloads
stop at ED

Summary

This .bnc file is a hybrid container format. The first part is relational and table-driven, describing a bending job, tools, stations, gauges, clamp data, bend data, and step planning. The second part embeds geometry and preview assets directly into the same file.

In practice, the structure is:

header
machine and process tables
cross-reference rows with GE,PA
embedded ACIS model blocks
embedded preview-image block
final ED terminator

.BNC File Format

Overview

Top-Level Structure

Header And Terminator

Common Record Types

C

ZA,MM,<n>

MM,AT,…​

ZA,DA,<n>

DA,…​

*

GE,PA,…​

Section Pattern

Structured Sections In This File

Section Details

KONFIGURATIONSDATEN

FERTIGUNG_AUFTRAG_TMP

BIEGETEILSTAMM

WERKZEUGSTAMM

WERKZEUGGRUPPE

WERKZEUGSTATION

MODELLSTAMM

MODELLSTATION

MODELLABLAUFDATEN

ANSCHLAG_SETZEN

TEIL_KLEMMEN

TEIL_BIEGEN

TEIL_FREIGEBEN

BIEGESCHRITTDATEN