This guide will cover common VESC problems and potential solutions, explain how to diagnose and troubleshoot those issues, and illustrate how to effectively report issues to the community.
DISCLAIMER: The VESC Bible is currently being republished and rewritten to encompass all necessary beginner guides. All guides with a beta tag are still preliminary and need to be vetted and reviewed by VESC experts.
Motor Not Spinning
- Problem: The motor refuses to spin when throttle is applied.
- Possible Causes:
- Loose or disconnected motor wires.
- Faulty motor connector.
- Incorrect motor settings.
- Sensor detection failure.
- Damaged motor.
- Controller Failure.
- Troubleshooting:
- Check all motor connections making sure they are secure.
- Reseat the motor connector.
- Swap the phase wires to see if that helps.
- Inspect the motor connector for any bent or damaged pins.
- Rerun the motor detection wizard in VESC Tool. Make sure the motor is secured and cannot spin freely during the process.
- If errors persist, consult the motor’s datasheet for the correct specifications and manually verify and adjust the detected motor parameters.
- If all sensors are not detected, consider replacing the hall sensor connector.
- Verify the motor current and voltage limit settings are appropriate.
- Test the motor with a different controller, if possible, to isolate the issue.
Connection Errors
- Problem: Having trouble connecting to the VESC via USB or Bluetooth.
- Possible Causes:
- Outdated or missing USB drivers.
- Bluetooth pairing problems.
- Firmware compatibility issues.
- Troubleshooting:
- Install the latest VESC USB drivers for your operating system.
- Power cycle the board and try to reconnect to the board using Bluetooth.
- Ensure you’re using the correct Bluetooth connection if you have multiple connections available.
- Wait for the package to fully load after connecting to the board before navigating to other sections.
- Check to make sure you are actually connected to the controller. Using a module like the VESC Express might show you as connected to the module but not the controller. Press “Can” to scan the CAN bus and see your controller in the list of devices.
- If you are connecting from Desktop App, consider connecting Bridge, see our tutorial here Connecting to PC/Mac VESC Tool with Bluetooth (How To)
- Ensure the VESC and the connecting device are close enough for reliable Bluetooth communication.
- Update the VESC firmware to the latest stable version and ensure all mobile apps are up-to-date.
- Power cycle both the VESC and the connecting device.
Configuration Issues
- Problem: Board is behaving unexpectedly or undesirably, like erratic throttle response or sudden power cuts.
- Possible Causes:
- Incorrectly configured motor current, voltage limits, or control settings.
- Firmware bugs.
- Third-party app conflicts.
- Possible Solutions:
- Disable the (Re)Float package and make sure to hit the “Write” button to save your changes.
- Set up your motor and adjust the motor poles, gear ratio, and sensor type to the correct values for your setup.
- Re-run the motor wizard in VESC Tool.
- Rerun the IMU Setup in VESC Tool
- Set your voltage thresholds for tilt-back using values appropriate for your battery pack. For example, for a 20s battery, high voltage tilt-back should be set to 86V (2V above max) and low voltage tilt-back should be set to 60V (3V per cell).
- Update your archive by going to the “Package” section and pressing “Update archive”. Consider trying ReFloat instead of the Float Package.
- Adjust the “loop hers” in the reFloat config section to match your IMU frequency.
- Verify that the reading was successful after making changes in the app. Some versions of the app might not read the settings correctly and could set everything to default. Until a fix is available, always check your values to make sure they were set to the value you intended. It is good practice to have a backup of your settings in VESC Tool.
- Carefully review all VESC parameter settings, ensuring they are appropriate for your hardware and riding style. Pay close attention to voltage cutoff settings, as incorrect values can damage your battery.
- Update to the latest stable VESC firmware.
- Use version 6.02 of the firmware or older if you are using a momentary switch with the stock Spintend firmware. The momentary switch support was created in a very “hacky” way in this version of the firmware. Changes made in later versions (like 6.5) can cause a “shutdown timeout” to be triggered even if you are riding the board. There is a fix available.
Weird Board Behaviour and Troubleshooting
Unexpected board behaviour can result from a variety of problems. A systematic approach to troubleshooting is key:
- Safety First: Always prioritise safety when troubleshooting. Test in a controlled environment, wear appropriate safety gear, and avoid riding the board until you’ve identified and resolved the issue.
- Isolate the Problem: Try to pinpoint the potential causes by testing different components or settings. For example, disconnect the motor and check if the VESC powers on correctly.
- Data Logging: Utilise VESC Tool’s data logging feature to record relevant parameters during operation. This can provide valuable insights into the issue.
- Community Resources: Use the search feature on pev.dev or Discord servers, and YouTube tutorials dedicated to VESC troubleshooting.
How to Report Problems to the Community
If any of the troubleshooting guides don’t fix your issue, consider describing your issue in Help Desk or in VESCify issues chat channel.
When reporting problems, clear and detailed information will help others assist you effectively. Here’s what to include:
- VESC Tool and Firmware Version: Specify the exact VESC Tool version and installed firmware version you’re using.
- Hardware Configuration: Describe your entire setup, including battery type, motor model, and any other relevant components.
- Software and Apps: List the VESC Tool version, operating system, and any third-party apps involved.
- Symptoms and Behaviour: Clearly describe the problem, including any error messages (fault codes in VESC Tool), unusual noises, or unexpected actions.
- Troubleshooting Steps: Outline the steps you’ve already taken to diagnose and resolve the issue.
- Visual Aids: Include screenshots of your VESC Tool configuration, data logs, or even videos of your issue, if relevant.