Profile Format
There are 3 major sections of the lighting profile. The profile is written in JSON and then converted to MessagePack before you send it to the Amp. Check out the sample profile to see how it all fits together.
These settings configure if and how the Amp should automatically react to deceleration, turns, and orientation changes.
Setting | Description | Type |
autoOrientation | Automatically detect orientation changes and shut off lights | boolean |
orientationTrigger | Amp board orientation direction | |
autoBrake | Automatically detect braking | boolean |
brakeAxis | The axis to use for braking detection | |
brakeThreshold | Deceleration threshold (g) to activate brakes | float |
autoTurn | Automatically detect turns | boolean |
turnAxis | The axis to use for turn detection | |
turnMin | Minimum angle (degrees) at which to activate indicators | float |
turnMax | Maximum angle (degrees) at which to activate indicators | float |
These settings configure the type of LEDs connected to each channel, how many LEDs, and which lighting regions they correspond to
Setting | Description | Type |
channels | Array of lighting channels with type and quanity of LEDs | |
regions | Array of sections of lighting channels that correspond to braking, turning, etc. |
These settings configure what lighting effects should be applied to the different lighting regions and actions. This section is different from the others in that each key corresponds to an Action. The value for each key is an array of RegionEffect
Setting | Description | Type |
<action name> | String version of Action |
Last modified 2yr ago