FarDriver Display Settings and Telemetry Accuracy for ONYX RCR

This article separates display configuration from the hardware calibration used to measure current, voltage, and temperature on the FarDriver-equipped ONYX RCR.

Reference Applicability

The explanations and tables below are the blog’s recorded FarDriver parameter reference, not a universal tune. The complete settings snapshot remains in Jaws Mode Settings. The parameter reference and settings snapshot have unresolved differences: 500 RPM is 100% versus 98%, 2250 RPM is 80% versus 58%, and LowSpeedPhaseRatio is 65% versus 60%. Their revision/hardware basis is not recorded. Do not combine the records or overwrite motor-specific learned values.

Firmware labels, scaling, motor pole pairs, installed wiring, and battery limits determine applicability. Interpret descriptions of riding feel as the source’s explanation, not proof of an outcome on every build.

Check the Measurement Before Changing the Controller

Compare GPS speed with displayed speed under consistent conditions using the GPS performance-meter guide. Verify the actual wheel/tire geometry, configured pulse or pole-pair basis, and supported communication protocol. A display mismatch alone does not prove a current-control fault.

The coefficients below belong to the recorded reference. Do not copy them to another controller. Hardware-level current, voltage, offset, and temperature calibration is not routine rider tuning. A change can affect protection as well as the number shown on screen. Where a device-specific calibration method is absent, preserve the existing calibration and resolve the sensor or configuration issue with the applicable documentation.

DISPLAY

Core behavior:

• Display parameters define how internal controller data is translated into readable output
• They do not affect performance directly, but they determine accuracy of speed, current, torque, and system feedback
• The system converts electrical signals (RPM, pulses, current) into human-readable values

Core relationship:

Displayed Speed ∝ (Motor RPM × Wheel Geometry) ÷ GearRatio

Interaction layer:

• Speed Pulses + SpdPulseNum define digital speed calculation
• WheelR, WheelRatio, and GearRatio define physical scaling of speed
• CurrentCoeff and TorqueCoeff scale displayed electrical values
• CAN settings control external display/communication systems
• Incorrect display values can mislead tuning decisions even if system is operating correctly

Real-world behavior:

• Correct configuration -> accurate speedometer and telemetry
• Incorrect wheel or gear ratio -> speed reads too high or too low
• Incorrect current/torque scaling -> misleading performance data
• Riders rely on this system for feedback, not control

Limits and failure modes:

• Incorrect calibration -> false speed and performance readings
• CAN misconfiguration -> no communication with external displays
• Poor scaling -> incorrect tuning decisions based on bad data
• Display errors do not affect actual performance, only perception

Tuning Guidance (ONYX-Specific)

• Set WheelR, WheelRatio, and GearRatio to match actual ONYX + QS setup
• Verify speed accuracy with GPS after configuration
• Do not modify pulse settings unless required - these are typically correct from factory
• Ensure CurrentCoeff and TorqueCoeff align with real measurements for accurate diagnostics
• Treat display system as measurement layer, not performance layer

FIXEDPARAS

Core behavior:

• Fixed parameters define low-level calibration constants used by the controller firmware
• They ensure that measured values (current, voltage, temperature) match real-world values
• These are not tuning parameters - they are part of the controller’s internal accuracy system

Core principle:

Measured Signal × Coefficient + Offset -> Real Value

Interaction layer:

• Directly affects:
  • Current measurement (LineCurrCoeff, PhaseCoeff)
  • Voltage measurement (VoltageCoeff, BattVoltage)
  • Temperature measurement (TempCoeft)
• Feeds into:
  • Protection system (cutoffs depend on accurate readings)
  • Display system (reported values)
  • Control loops (PID and current control rely on correct data)

Real-world behavior:

• Correct calibration -> accurate readings and stable system behavior
• Incorrect calibration -> mismatched readings leading to:
  • Early or late cutoffs
  • Incorrect power perception
  • Unstable control behavior

Limits and failure modes:

• Changing these values incorrectly -> system misbehavior at a fundamental level
• Incorrect current scaling -> overheating or underperformance
• Incorrect voltage scaling -> battery damage or unexpected cutouts
• Incorrect temp scaling -> loss of thermal protection

Tuning Guidance (ONYX-Specific)

• Do NOT modify Fixed Parameters unless performing hardware-level calibration
• These values are typically factory-set for the controller and sensors
• If values are incorrect, correct the root hardware issue - not the coefficients
• Treat this section as read-only reference, not a tuning layer

Related Articles

• Compare speed with a GPS meter
• Controller parameter behavior