The CANmod.input uses a JSON file placed on the
CONFIG volume for configuration (for more information on how to access the volumes via USB refer to the USB Section).
The JSON format makes it easy to configure the device using custom tools, scripts, JSON editors or plain text editors. The configuration rules (min, max, …, etc.) are defined using a Rule Schema (JSON Schema). The Rule Schema serves as a guide for populating and validating the Configuration File.
A default Configuration File and the Rule Schema are automatically generated by the device and placed on the
The Default Configuration File and Rule Schema can be downloaded below:
For most cases, it is convenient to use a graphical Configuration Editor for editing the configuration file. By doing so, the editor can verify if the configuration satisfies the limitations described by the Rule Schema. Visit www.csselectronics.com to access the latest Configuration Editor1.
Configuration loading sequence¶
The Configuration File loading sequence is illustrated below.
Boot: The device mounts the
Validate: The device attempts to load the custom configuration stored in
Load default: No custom config found. The device loads the default configuration from the
Load custom: A valid custom configuration is found. The device loads the custom configuration from the
The configuration editor uses a User-Interface-Schema-File (uischema) to describe the visual layout of the configuration file. The uischema file is located on the device USB drive.
For more information on the volumes, refer to the USB Section.
The device validates the custom configuration file against the rules defined by the Rule Schema. If the configuration satisfies the rules, the configuration is loaded. If one or more rules are violated, the device rejects the custom configuration.
A rejected custom configuration is indicated by the device LEDs. For information, refer to the LED Section.