Tebis PPD Documentation: Configuring Graphical HTML Output

Tebis documentation workflows expose a practical split: DOKU > PRINT can populate parameters for one selected TLP, while PPD output can append data whenever PUT NC runs. To place several NC programs, formatted parameter tables, and a shaded view on one sheet, generate HTML instead of plain text and assign each HTML fragment to the PPD section where its data is available.

Define the required document output

Select the HTML and PPD workflow

The evidence describes an early HTML result as not being produced through FRM or PPD, but the later, tested implementation explicitly copied HTML fragments into PPD sections. Treat this as an evolving implementation rather than proof that every installation follows one fixed route. The documented working method used Word to create the layout, saved it as filtered HTML, inserted selected source fragments into the PPD, and generated an HTML file instead of a TXT file.

1. Create the document layout in Word with the required header, logo area, tables, fonts, colors, and image space.
2. Save the layout as Web Page, Filtered to obtain relatively clean HTML.
3. Separate the generated HTML into header and NC-parameter fragments.
4. Copy each fragment into the PPD section that exposes its required data.
5. Add IF/ELSE branches where different program types require different rows or layouts.
6. Configure the documentation output as HTML, not TXT.
7. Generate multiple NC outputs into the same document and confirm that the header appears once while program data appends.
8. Open the result in Word if images or other post-generation edits are required.

Build a compact graphical template

Use HTML tables to align program parameters and conserve page space. Keep the company logo and fixed document identity in the header, place NC data in repeatable rows, and allocate a bounded area for the shaded model view. This structure supports different font sizes and colors without forcing operators to reconcile separate plain-text reports.

Do not rely on formatting alone to communicate machining conditions. Use explicit labels and arrows in the graphical view when the machine operator must identify a location, orientation, or clearance. The evidence also identifies a human-factors requirement: the sheet must remain understandable to personnel who do not use the CAM system.

Place variables in the correct PPD sections

If a value is blank or incorrect, first check whether its HTML fragment is in a section where that parameter exists. Moving an NC parameter into SECTION_HEADER, for example, does not establish that the value is available there.

Prevent repeated headers when appending programs

Guard the header with NEWFILE. Without this check, every appended program can reproduce the complete heading. The source describes the following approximate section structure; adapt the content fields without changing their data scope:

IF (NEWFILE) THEN
  SECTION_HEADER
    setup-document header
    part-basis field
    NC-document header
    parameter column headings
  SECTION_END
ENDIF

SECTION_FIRST
  milling-parameter output
SECTION_END

Use SECTION_TOOLP instead of SECTION_FIRST when every selected TLP needs its own row. Use SECTION_LAST only when the last selected TLP is the intended source. These are different selection policies, not interchangeable formatting choices.

Handle unavailable totals and variable scope

Do not assume that every postprocessor-programming variable is available to a PPD. Attempts to use corresponding PP variables for total NC-block count and total path length were reported as unavailable. The available PPD choices were values from the first TLP, the last TLP, or each TLP separately.

Timing has the same context problem. During NC output, a total may be available in the program context; when the PPD is written, the toolpath may already be loaded and only the current TLP time remains available. Linking all paths can consolidate the calculation, but the evidence states that linking is not possible when paths use different orientations.

The manuals were reported to document special underscore-prefixed PPD variables, including _SetTime for set totals. No equivalent variable for ordinary TLP totals was confirmed. Therefore:

• Use _SetTime only when the documented object is a set and its semantics match the required total.
• For unlinked TLPs, output each supported value separately or calculate the total outside the PPD only after verifying the inputs.
• Do not present the first, last, or current TLP value as the total for the NC file.
• Request confirmation from Tebis through an official support channel before using undocumented PP, viewer, or underscore-prefixed variables.

Separate NC documentation from tool-assembly output

Tool-assembly documentation is a related but separate deliverable. The evidence states that TSET documentation can output a ZSB list of the complete tools used in the tool magazine. A compact component table and a layout matching the NC document were planned, but the evidence does not confirm that this template was completed. Keep this output separate until its fields and generated results have been verified.

Verify the generated document before release

Generate a new HTML document and confirm that the fixed header appears once. Append additional NC outputs and verify that each expected program block follows the previous block without repeating the header. Test SECTION_TOOLP, SECTION_FIRST, and SECTION_LAST against a known selection so the displayed values can be traced to the intended TLP.

For files containing multiple unlinked toolpaths, compare every displayed block count, path length, and time with its actual scope. If the document cannot produce a verified aggregate, label the rows by TLP and omit the total. Finally, open the HTML in its intended editor or viewer, check table alignment, fonts, colors, logo placement, and image visibility, then print a sample and confirm that operators can identify the required machining information without opening the CAM file.

FAQ