So I got everything to work, motors spinning and responsive breaking but then decided to configure my VESC for the space cell and motor because I wasn’t sure if the VESC was optimized. I got bldc tool 2.5 and updated my firmware to 2.7 from 1.14 and changed the current limits settings to optimize it for the space cell. Now its no longer responsive to my controller and the motors don’t spin. I’m not sure whats wrong at all… I tried reloading the firmware to the VESC and loaded the xml file that onloop posted for the r-spec motors.
Also is there a difference in the firmware that you load? I know the file is named default.bin but each folder has its own default.bin file. I currently have the default.bin from hw_410_411 loaded.
@EnertionSupport Thanks, but I already update my firmware this morning and I now my motor won’t respond to my inputs, can you help me out?
This was in my earlier post
So I got everything to work, motors spinning and responsive breaking but then decided to configure my VESC for the space cell and motor because I wasn’t sure if the VESC was optimized. I got bldc tool 2.5 and updated my firmware to 2.7 from 1.14 and changed the current limits settings to optimize it for the space cell. Now its no longer responsive to my controller and the motors don’t spin. I’m not sure whats wrong at all… I tried reloading the firmware to the VESC and loaded the xml file that onloop posted for the r-spec motors.
Also is there a difference in the firmware that you load? I know the file is named default.bin but each folder has its own default.bin file. I currently have the default.bin from hw_410_411 loaded.
WARNING: If firmware is incorrectly installed you can damage the hardware.
Make sure you have the correct app selected.
Go to: “App Configuration” Tab
In “General” Tab (choose PPM)
Click “PPM” Tab (choose “current no reverse with brake”)
@EnertionSupport
Is there a way to check if I incorrectly installed my firmware? Will the VESC show any specific symptoms? The BDLC tool recognizes firmware 2.7 and reads all of its settings, both leds are also functional on the VESC.
Or is there still a possibility that updating the firmware broke the VESC?
If there are no obvious hardware faults, if everything seems normal it probably is, so your problem is probably due to some settings being incorrect. You would need to screen capture all the BLDC pages for me to know if your settings are wrong.
have you tried getting your motor to spin with the detection tool? Using the detection will give you nearly the same numbers as the XML file for the R-SPEC motors. The difference is that the motor will spin up in the process, would should help us to pinpoint the problem.
If the detection is successful, than you can confirm the VESC is able to spin the motor, and then it is just down to finding any settings that could be conflicting.
While the detection is going, see if there are any faults in the “realtime data” section. The fault code can be seen in the bottom left of that page. You can see some examples of troubleshooting a VESC with the realtime data in this thread:
If the detection is unsuccessful, hopefully the fault code will give you a clue as to what went wrong.
As for the PPM, have you turned on the “PPM display” (located at the bottom of the PPM tab) to see if the VESC is at least reading your inputs? after turning your PPM to “disabled”, check that little box and see if the bar moves with throttle/brake inputs from your remote.
Hopefully this will help us get one step further to having your VESC up and running.
