Timbr canonical manufacturing manifest
timbr.canonical-schemaCo działaSchema 1.0 with structural and semantic validators. Every adapter projects from it.
application/json
Projekty timbr mają być wykonane, a to znaczy dotrzeć do maszyny lub programu, którego już używasz. Ta strona to uczciwa mapa tej pracy: co potrafimy dziś wyeksportować, co jest planowane, a co zablokowane i dlaczego.
Każdy eksport zaczyna się od jednego kanonicznego manifestu produkcyjnego: elementy ze stałymi identyfikatorami, materiały, oklejanie krawędzi z jawnie podaną polityką wymiarów oraz operacje obróbcze zapisane jako intencja narzędzia, a nie kody maszyny. DXF, listy rozkroju i G-code są rzutami tego manifestu. Decyzja produkcyjna nigdy nie zapada najpierw w pliku pochodnym.
Ma to znaczenie, bo każdy format gubi coś innego. Gdyby głębokość otworu istniała wyłącznie w nazwie warstwy DXF, nic nie mogłoby jej sprawdzić — a w dniu, w którym Twój importer zażądałby innej konwencji warstw, zmieniłaby się razem z nią.
Łącznik sięgający maszyny jest krytyczny dla bezpieczeństwa. Opublikowanie długiej listy logotypów byłoby łatwe; opublikowanie tego, co faktycznie sprawdzono, jest użyteczne. Dlatego każdy cel niesie ze sobą klasę dowodu, a żaden nie może zadeklarować produkcji certyfikowanej wyłącznie na podstawie dokumentacji podmiotów trzecich — ta reguła jest egzekwowana w kodzie, nie umownie.
Norma ISO 6983-1:2009 stwierdza w swoim własnym zakresie, że zgodność nie gwarantuje wymienności programów sterujących między maszynami. „To przecież zwykły G-code” nie jest planem.
Klasa C jest najbardziej użyteczna przy poznawaniu formatu i najbardziej niebezpieczna w produkcji. Klasa D może otworzyć dochodzenie; nigdy nie może go zamknąć.
Te formaty możesz wyeksportować teraz. Żaden z nich nie jest certyfikowany produkcyjnie — przeczytaj README w archiwum, zanim cokolwiek trafi na maszynę.
timbr.canonical-schemaCo działaSchema 1.0 with structural and semantic validators. Every adapter projects from it.
application/json
timbr.dxf-profileCo działaProfile-driven per-part DXF with configurable decimal encoding, horizontal-drilling representation flag and declared target-profile lineage. Not yet imported into any named vendor CAM.
.dxf
Real vendor profiles encode decimals as letters (HO9p5 = 9.5), so decimal encoding is a profile parameter, never a constant.
timbr.cutlist-csvCo działaMapping engine plus a Timbr default profile. Optimizer-specific mappings ship as unverified hypotheses until run through the real importer.
.csv
A generic CSV is not enough: delimiter, decimal format, field mapping, material codes and optimisation settings are all part of the adapter.
timbr.step-exportCo działaAnalytic B-Rep solids with bores, grooves and rabbets cut as real geometry. Every file is read back with the same kernel and checked for solid count, volume, bounding box and surviving cylindrical faces. Not yet imported into any named vendor CAM.
.step.stp
Promoted from fallback to a primary OEM path in spec v2: woodWOP 7.0+ imports STEP natively, 7.1 adds bore recognition, 8.0 adds 3D groove/pocket recognition. Analytic geometry is the whole point — a faceted export has no cylinders, so feature recognition finds nothing and every hole is redrawn by hand.
timbr.iges-exportCo działaThe same analytic solids as STEP, written as IGES and verified by reading back. For importers that read IGES more reliably than STEP.
.iges.igs
woodWOP has imported IGES since 7.0, alongside STEP.
timbr.stl-exportCo działaBinary STL at 0.1mm linear deflection. A MESH: it carries no cylinders, so no importer can recover a bore from it. For visualisation and collision checking, not for machining.
.stl
woodWOP added STL import in 7.1. Offered because it is asked for, labelled as a mesh because that is what it is.
timbr.dxf3d-exportCo działaThe same solids as STEP, tessellated to 3DFACE entities. A MESH: a bore is a ring of triangles, so nothing downstream can recover it as a hole. For targets that genuinely cannot read STEP.
.dxf
SCM documents 3D DXF alongside STEP/IGES/STL as Maestro source geometry. Offered for that case only — STEP carries features, this does not.
generic.iso-gcodeCo działaPost DSL and 3-axis drilling/routing output behind an explicit opt-in, with a mandatory operation report. No controller profile is certified; every file carries an uncertified banner.
.nc.tap.prg.txt.cnc.anc.plt
'ISO' and 'Fanuc-compatible' are families, not a complete dialect. M-codes, canned cycles and macros are machine-builder specific.
tpa.tcnCo działaHoles on all six faces, programmed by diameter so TpaCAD resolves the tool from its own technology database. Routed features are reported, never approximated. Nothing has been opened in TpaCAD.
Obejmujefelder, format4, busellato, vitap, biesse-brema, biesse-vector
.tcn.f4g
Highest machine-coverage-per-engineering-month in the portfolio: one adapter reaches five OEM badges. This is why it is P0 despite shipping nothing yet. Spec v2 correction C2: Felder does NOT run generic ISO G-code. U4 is now largely answered for DRILLING: the vendor documents the hole working in full. A complete opcode dictionary for routing is still outstanding.
nesting.optimizersCo działaCut-list CSV with material, thickness, grain, quantity, label and part id. Column mappings for named optimizers are unverified hypotheses.
Do not encode drill or pocket operations in nesting contour files unless the optimizer explicitly supports them. Keep the machining packet linked by part id.
buildingsmart.ifc4Co działaIFC4 via IfcOpenShell, verified by reading the file back. Carries placement, size, material and the Timbr part id — NOT machining.
.ifc
For BIM and interior coordination. Never a CNC carrier — the spec is explicit that IFC must not be the sole source of machining truth.
d2m.btlxCo działaParts and dimensions as BTLx 2.0, VALIDATED against design2machine's own published XSD — the only adapter whose output is checked against somebody else's formal definition rather than our own tests. Machining is not included: BTLx operations are timber joinery on reference sides RS1-RS6.
.btl.btlx
Correctly out of scope for panel furniture - it is a timber-construction format - but far cheaper to implement than v1 assumed: the XSD is public and BtlViewer is open source. Implementer trap: BTLx 'Height' means component THICKNESS.
grbl.desktopCo działaA GRBL controller profile in the post framework, uncertified and opt-in.
Desktop controllers lack industrial drilling blocks, aggregate semantics and machine-safe macros. Do NOT reuse industrial posts unchanged.
Nie zostały zapomniane. Każda czeka na konkretną odpowiedź, której nie będziemy zgadywać.
homag.tapioBlokujeU5 - partner programme commercial and technical requirements. This is a commercial conversation, not an engineering one.
Converts the HOMAG problem from 'reverse-engineer a proprietary format' into 'become a partner and ship an app'. SWOOD and Palette CAD already have comparable arrangements.
homag.woodwopBlokujeOnly the NATIVE .mpr/.mprx path is blocked — on U1 (.mprxe structure) and on legal review. The machine itself is reachable now: woodWOP 7.0+ imports STEP and IGES natively, 7.1 recognises bores, 8.0 recognises 3D grooves and pockets. The layer-coded DXF path remains blocked on U8 (which DXF Import profile the customer runs).
.mpr.mprx.mprxe.dxf.step
The published layer vocabulary (Z_xx, HOxx, NZxx, FZxx, S_xx, FK-) is grade C and is a hypothesis to verify against the ACTIVE profile, never a table to hard-code.
biesse.bsolidBlokujeOnly the native CIX->BatchRun->BPP chain is blocked. U2 is now answered and the answer is negative: BppLib carries no licence, so it cannot be used or ported. bSolid imports STEP as source geometry today.
.cix.bpp.cid
Direct-to-NC is possible (the control accepts BPP,DXF,CID,CIX) but a CIX loaded that way cannot be edited or debugged, so it is expert-only and disabled by default.
Znane zagrożeniabSolid has historically mis-imported some BPP process options: Z and depth swapped on stepped vertical milling, negative step increments on horizontal stepping. Any regression suite must assert on stepped operations specifically.
scm.maestroBlokujeOnly the native .xxl/.xcs -> XConverter -> .pgm chain is blocked, on U3. Maestro imports STEP, IGES, STL and 3D DXF as source geometry today.
.xxl.xcs.pgm.pgmx
.xxl and .xcs load into Xilog/Maestro but do NOT by themselves make a machinable part. This is a hosted-conversion integration requiring a licensed install on the customer side. X/Y mirroring and Z sign convention are documented sources of silent part-flipping errors.
vectric.vcarveBlokujeU7 - whether .pp posts are redistributable or reference-only.
.pp.crv.dxf
Dual purpose. Vectric's .pp is the best publicly documented post DSL in existence, and its variance set (decimal separator, decimal places, per-variable format overrides, unit multiplier, file extension, rotary wrapping, dwell) is the minimum feature list Timbr's own post framework implements.
hexagon.alphacamBlokujeU6 - whether xAPI permits an unattended server-side integration under licence.
Buys breadth of machine coverage through one partner. The saving is coverage, not escaping per-machine certification.
holzher.nchopsBlokujeNative .hop is blocked: no public schema and no open-source implementation exists in any language. aCADemy imports DWG/DXF, and NC-HOPS takes 5-axis CAD/CAM through a post-processor interface.
.hop
NC-HOPS is a hub, not just an OEM tool - it drives Biesse, Busellato, HOMAG and SCM machines too. Renaming another format's output to .hop does not work; the structure genuinely differs.
Kolejność wynika z tego, ile maszyn obejmuje dana pozycja na miesiąc pracy inżynierskiej, a nie z rozpoznawalności marki.
mozaik.cncŚcieżkaExport part and BOM definitions into Mozaik; let its post library reach the machine
Mozaik's published file-type list (.cix, .mpr, .nc, .xcs, .xxl, .tcn, .tap, .prg, .txt, .cnc, .anc) independently cross-confirms the format universe in the spec.
hexagon.cabinet-visionŚcieżkaPartner/API job import preserving Timbr part ids; DXF+CSV as a fallback that is not equivalent to a native job
Same vendor group as Alphacam - a combined partner approach may be more efficient than two conversations.
microvellum.toolboxŚcieżkaIntegrate at project/part/manufacturing-data level and let Microvellum's Integrated Post Processor reach the machines
Geometry alone loses Microvellum's product intelligence, construction rules and machining tokens.
imos.ixŚcieżkaPush configured order and manufacturing data through iX Connect or an agreed database/API interface
eficad.swoodŚcieżkaSOLIDWORKS/SWOOD plugin or structured STEP plus metadata; SWOOD handles the certified machine posts
SWOOD Connect is a bookable tapio interface to HOMAG productionManager - the precedent for homag.tapio.
topsolid.woodŚcieżkaCreate TopSolid documents and manufacturing features through the Automation API, then use certified WoodCam posts
autodesk.fusionŚcieżkaAdd-in or importer creating components, setups and operations from the Timbr manifest; Fusion's own CPS posts reach the machine
Post processors are executable logic and safety-critical. Pin the post revision and machine configuration.
onshape.restŚcieżkaREST API creating documents, parts and assemblies with Timbr part ids preserved as metadata
Best cloud-native CAD connector candidate. Document microversions and element ids must be pinned.
trimble.sketchupŚcieżkaRuby extension importing assemblies as components with manufacturing attributes
Faces and edges alone do not encode thickness, machining depth, face side or edge banding. The manifest must travel alongside.
dassault.solidworksŚcieżkaNative parts and assemblies through the COM API with custom properties for materials, edges and part ids
erp.odooŚcieżkaCanonical order/BOM/work-centre events over REST and webhooks, with CSV/SFTP fallback
Never write directly to database tables.
homag.cutriteŚcieżkaMapped cut lists, board data, labels and part ids; consider reaching it via tapio intelliDivide rather than direct file integration
vdma.opcua-woodworkingŚcieżkaConsume the companion specification's WwMachineType information model rather than a bespoke telemetry mapping
chinese.controller-tierŚcieżkaPrimary research required before any work
Large global installed base on low-cost nesting routers, absent from v1 entirely. Evidence grade D: this tier needs primary research, and grade D may never close an investigation. RichAuto DSP posts commonly emit .plt.
Zgadnięcie parametru obróbki to incydent bezpieczeństwa, nie skrót. Pozostają otwarte, dopóki nie odpowie producent, klient albo audyt u klienta.
Produkty konkurencyjne, z których się uczymy, zamiast się z nimi łączyć.
Najcenniejsze, co możemy usłyszeć, to dokładna maszyna, sterownik i oprogramowanie w prawdziwym zakładzie. To zmienia kolejność na tej stronie szybciej niż jakiekolwiek badania zza biurka.
Napisz nam, czego używasz →