Skip to main content
FW version: Stable

III. Accelerator Configuration

Disambiguation

The term 'throttle' originates from gas/combustion engines, where it refers to a control element for acceleration. As we transition to electric vehicles, we prefer the term 'accelerator'. Both terms can be used interchangeably as synonyms.

This section covers accelerator range calibration and also demonstrates SWTools functionality to help with further steps.

info

This configuration is optional

Default values are typically sufficient, though you may notice significant deadbands at accelerator extremes.

The objective here is to measure accelerator analog input values at minimum and maximum positions, then configure these as range parameters. We will determine the values of /acc/asc/min and /acc/asc/max.

Accelerator analog readings (in [mV]) are available in two locations:

  • /acc/asc/in state
  • /common/gpio0 state (GPIO0 is mapped as accelerator input by default)

Motor Deactivation​

warning

First, disable the motor using the stop command. This suspends LYNX drive control until either power cycle or run command execution.

Motor Stop

Signal Visualization​

Use the scope tool to monitor accelerator signals:

  • Launch Scope
  • Configure Plot 0:
    • /acc/asc/min - accelerator minimum
    • /acc/asc/max - accelerator maximum
    • /acc/asc/in - raw accelerator reading [mV]
  • Configure Plot 1:
    • /acc/asc/out - normalized accelerator reading [0-1]

GUI Setup

Scope Analysis​

tip

Signal noise indicates potential wiring or sensor issues. Use scope monitoring to diagnose vehicle input problems.

Scope Display

Range Configuration​

  • Access /asc folder (right-click → Open)
  • Enable Autopull for automatic value updates
  • Move accelerator through full range
  • Spot the minimum/maximum values
  • Set /acc/asc/min and /acc/asc/max accordingly

Range Setting

Motor Reactivation​

Test new settings by either:

  • Executing run command for immediate activation
  • Power cycling after saving parameters

The motor then resumes LYNX control (for accelerator response verification).