LencoSolutions
commented
1 year ago I think this might be solved in the no hardware limits version. Anyway that fixed it for me.
Open LencoSolutions opened 1 year ago
LencoSolutions
commented
1 year ago I think this might be solved in the no hardware limits version. Anyway that fixed it for me.
I am currently facing an issue with the Vesc Tool. Specifically, I am experiencing difficulties with the compatibility between the Flipsky 75100 VESC and the MPU6050 IMU (Inertial Measurement Unit). Despite trying various troubleshooting methods over the course of a year, I suspect that the issue lies within the software.
Issue Details:
Hardware Configuration: I am using the Flipsky 75100 VESC along with the MPU6050 IMU. Previous Working Setup: Initially, I successfully configured the VESC for my DIY Funwheel project, and everything functioned correctly. Current Problematic Setup: However, after updating to the latest version of the Vesc Tool and configuring the VESC app to use UART communication, I encountered an issue. Whenever I power cycle the board, the MPU6050 IMU is no longer detected. Intermittent Solution: I have found that temporarily changing the loop frequency and then reverting it back can restore the IMU connection temporarily. Unfortunately, this workaround fails to persist after power cycling the board. Troubleshooting Attempts: To address this issue, I have attempted the following steps: Experimented with multiple IMUs from different manufacturers. Tested with various VESC units (at least three different ones). Verified the connection and wiring between the VESC and the MPU6050 IMU. Reverted to the Balance app, where the IMU functions correctly without encountering power cycling issues. Software Version: I am currently using the latest version of the Vesc Tool. Expected Solution: I am seeking your assistance in resolving this issue promptly. It is crucial for me to leverage the latest features offered by the Vesc Tool, particularly with the Float Package. Your guidance and support would be immensely appreciated.
If you require any specific logs, screenshots, or additional information to aid in diagnosing the problem, please let me know, and I will gladly provide them.