Metamation Developer Notes

  • Developer Notes
  • Resource Map
  • Tools
    • Code Formatting
    • Configuring Git
    • Assignments
    • Testing with Windows Sandbox
    • Single Binary Applications
    • Self-Updating Applications
  • Flux Workflow
    • Flux Workflow
    • Flux Development Style Guide
    • Release notes for Flux
    • SonarCloud analysis for Flux
    • Build a Flux SDK Program
    • Shipping Flux
    • Flux.Test
      • BasicBendAuto Test
      • LaserAuto.cs Detailed Documentation
      • Laserexample:Test1
  • Technical Notes
    • File formats
      • .FX File Format
      • Au(Gold) streams
      • .GEO File Format
      • .LST File Format
      • .LST file - technology
      • .BNC File Format
      • .WAD Files: Flux Resource Packages
      • .Curl Files: ASCII config information
    • Folders App
      • Data\Bendtools
      • Data\Machines
    • FluxCode
      • Welcome & Repo Map
      • Architecture & System Context
      • Subsystem *Bend* (Press Brake)
      • Subsystem *BCell* (Bend Cell Automation)
      • API Maps
      • Data Model Catalog
      • Design Patterns -- A Reader's Guide
      • Tests and Golden Paths
      • Guided Code Tours
      • CAM Glossary with Code Mapping
      • Assignments
      • Flux Onboarding Handbook
    • Data flow
      • Part
        • Part.Dwg
        • Part.Load
        • Part.Load to Part.Dwg
      • BendTech.cs
      • Bend Technology
      • Laser Cutting Technology
    • LTS (Long term support mechanism)
    • Machine ID Scheme
  • FluxTester
    • Commands and Scripts
    • Command Cookbook
    • Script Commands
    • BendTooling.cs Test Inventory
    • LaserTooling.cs Test Steps
    • Fluxtester Recipe Book
    • Nesting.cs Overview
    • Nesting.cs Recipe Book
    • Job.cs Overview
    • Job.cs Recipe Book
  • Software license
  • 3d party software
    • Python
  • Documentation
    • Bento documentation
      • Structure of a Bento page
      • Attributes
    • Software
      • Software Requirement
      • Installation
      • Git workflow for documentation contributors
    • Quick start guide
    • Workflow
      • Roles and responsibilities
      • Analyze
      • Edit
      • Proofread
      • Pre-Publish
      • Publish
      • Release cycle
      • Information required for Documentation Team
      • Checklist for Documenters
    • Styleguide
    • Flavoring
    • Translation
      • Ordering translation for a new document
    • Citations
    • Annotation
Technical Notes
/
LTS (Long term support mechanism)

LTS (Long term support mechanism)

The FX data exchange format between Flux and e.g. RA control creates the need of a mechanism to avoid issues if the compatibility gets compromised. The situation is:

  • Customers update their desktop software quite frequently but don’t want to update the machine. We will have different FX versions between Flux and RA.

  • FX is a self descriptive data format where additional data could be added without a compatibility issue. The only problem comes if we change the interpretation of the data / data format but the FX format is already quite mature.

In order to allow the customer to run different versions of RA and Flux, a stepping mechanism is introduced from Flux build 602 and RA 182.

  • We start with stepping version 1 in all systems

  • We increase the stepping version in case we need to do an incompatible change in the FX format.

  • Flux checks the stepping version while loading a FX file. If it is identical or lower, then the file could be loaded without issues

  • If Flux identifies that a file has a higher stepping version then it will raise Flux.APIException with VersionMismatch code. RA catches the exception, checks the code and tries to call an external downgrade application "Flux.Stepper.exe" which is located in the binary folder of RA. It will save a fx file with a lower stepping version and can be loaded into RA.

  • External application takes 3 arguments which are source fx file, target fx file name and target stepping version.

  • External application can contain different version of Flux.API than the one installed in the machine and can be installed at any location. In that case, environmental variable FLUXSTEPPER should be set to the directory containing Flux.Stepper.exe.

This means that if we need to introduce a new stepping version we will deliver to all customers this Flux.Stepper.exe which could be installed instead of upgrading the machine.

  • If the build version of Flux and RA is different but the stepping version is identical we will not display a warning message.

  • If the stepping downgrader gets executed we will display a warning message in RA that we are using an external application to downgrade the fx file.

Laser Cutting Technology Machine ID Scheme

      Copyright © 2025 TRUMPF Metamation. All rights reserved.

    Compiled by Bento