CadActiveSupport

howto

XML and NWF Format

Creo Schematics rsData XML and Neutral Wire Format files AutoAssemble reads as routing inputs.

XML and NWF are routing / schematic inputs, not BOM tables. The file dialog groups them as Routing File. Run the command with Assemble from a File. Walkthrough: Schematic Assembly. Sibling formats: CSV and Excel Format, JSON Format.

Each designated connector becomes a component in the current assembly. These files do not use LEVEL tree-builder headers.

How they differ from CSV and JSON

  • Auto Assemble File — .xlsx, .csv, .json (table or instruction list)

  • Routing File — .xml, .nwf (schematic / logical design data)

XML (Creo Schematics rsData)

The XML root element must be rsData (Creo Schematics / RSD export). Other XML roots are rejected. The file must contain connectors and/or components.

For each designated connector, AutoAssemble:

  • Creates or retrieves a part named from the schematic model name

  • Copies designation, connected-to component, and connected-to port from the schematic

  • Reads connector parameters named COLOR, COMPONENT_TYPE, and the interface-name parameters (MODEL_PLACEMENT_INTERFACE / MODEL_INTERFACE_NAME, MATED_RECEIVING_INTERFACE / MATING_RECEIVING_INTERFACE / MATED_INTERFACE_NAME) when present

xml ]]>

NWF (Neutral Wire Format)

.nwf files use the same schematic path as XML. Use NWF when the logical design is exported from Creo Schematics or cabling as Neutral Wire Format rather than rsData XML.

What XML and NWF will not do

  • Will not build a nested BOM tree (no LEVEL)

  • Will not parse a generic XML table of MODEL_NAME columns — only rsData

  • CSYS-to-CSYS columns (MODEL_CSYS / MATING_CSYS) are CSV, Excel, or JSON, not XML