Save / Load Settings

Save / Load Settings

Overview

DISPLAX Service allows you to save and load all device settings and calibration data between Touch Controllers of the same model and firmware version.
This feature is useful for backup, replication, and fast deployment across multiple identical installations.

You can:

  • Save current settings to a file

  • Load saved settings onto another compatible Touch Controller

  • Restore settings after system reinstallation or hardware replacement

Important Requirements

Before using this feature, ensure:

  • Both Touch Controllers are the same model

  • Both are running the same firmware version

  • The target device is connected and accessible via DISPLAX Service

  • File paths are valid and accessible by the operating system

Save Touch Controller Settings

To save (download) all current settings and calibration values to a file, run:

displaxservice -a 127.0.0.1 --device-settings download "path-to-save-location"

Example:

displaxservice -a 127.0.0.1 --device-settings download "/home/user/displax_backup.cfg"

This creates a backup file that can be reused later or transferred to another system.

What Settings Are Saved?

  1. Touch status (enabled/disabled)
  2. Gain (values 0 – 7)
  3. Threshold (Values range from 0 to 50 from firmware version 1.5.0 onwards, and between 0 and 15 on firmware versions equal or previous to 1.4.0)
  4. Shield level
  5. Palm detection status and palm rejection area values / Massive Clearance and Massive Minimum Size
  6. Disabled columns, rows or cells
  7. Number of touches
  8. Geometric Calibration

Load Touch Controller Settings

To load (upload) previously saved settings onto a compatible Touch Controller, run:

displaxservice -a 127.0.0.1 --device-settings upload "path-to-the-file"

Example:

displaxservice -a 127.0.0.1 --device-settings upload "/home/user/displax_backup.cfg"

All supported settings and calibration data will be applied to the device.

Best Practices

  • Always back up settings before making major configuration changes

  • Restart the Touch Controller after loading settings to ensure full application

  • Do not load settings between devices with different firmware versions

Common Use Cases

  • Cloning configurations across multiple identical touch displays

  • Creating a baseline configuration for large deployments

  • Restoring settings after testing changes in configurations

  • Migrating configurations to replacement hardware