Certified FOCBOX Suppliers | Get Focbox Unity

R-Spec Motor Repair/solder joint testing


#1

I bought a r-spec 6355 a while back and completed my board recently. After about a 5 mile test run it stopped spinning. I thought one of my bullet connectors might have come loose as my vesc seems to be fine. The motor neither spins nor makes any noises when I press the throttle, any ideas? I was thinking I had a bad solder joint either on the vesc or motor but even so it should still be touching under the heat shrink, right?


#2

@Fababuba [quote=“Fababuba, post:1, topic:2658”]
it should still be touching under the heat shrink, right?
[/quote]

nope, a bad join can disconnect even if the heat shrink is intact. In this case pics of the relevant parts of your build would help everyone on the forum to answer your question.

Possible issues: motor connectors disconnected, bad solder joint somewhere, controller’s receiver disconnected, controller’s battery dead, battery disconnection, vesc threshold exceeded (temp, voltage).


#3

There are so many ways to make ur board not go. Do u have a multimeter? That’ll clear up the simpler problems


#4

Ill post pics of my setup when I get home and I have a multimeter but I’m not too sure how to test the motor and vesc with it.


#5

I had each motor wire individually wrapped in electrical tape and heat shrink, just took it off to make sure the solder joints were still connected. Under the white pvc cover is a space cell.

https://drive.google.com/file/d/0Bw8ImCZYazEZWGtkSXFhRjhuRzA/view?usp=sharing -test video/ the vesc responds to the transmitter but the motor is completely unresponsive.


#6

@Fababuba did you modify any of the settings in bldc tool? Is it possible that you disabled the controller app? On the PPM tab make sure that you’ve chosen on of the non-disables options. Also check that you’ve chosen PPM in the general tab.


#7

Yup I checked all of that a PPM, current no reverse with brake, the plusewidth display also works. Everything was working fine for a good 2 miles until suddenly it stopped responding. I live in Chicago so everything is pretty flat and i’m pretty sure i never even got full throttle so I don’t think I overloaded it.


#8

@Fababuba Have you checked the soldering of the motor wires on the VESC, under the heathshrink?


#9

@treenutter Yes, it’s not the best soldering job but all 3 wires are connected.


#10

I see this all the time! Uninsulated phase connectors :fearful:

Mind your connections guys!

Edit: just read that you removed it for the photos but it looks like it is powered up?


#11

@chaka Its powered up but I made sure the connectors never touched. Do you know how to test if I shorted out the motor or if its something else?


#12

Do you get 3 red flashes from the vesc when you try to run the motors? If you do then you have a drv8302 fault.


#13

Nope, no red flashes at all.


#14

@Hummie Can you briefly explain how to test the motor and Vesc with the multimeter? Is there a way to test if the Vesc is actually delivering power to the motor?


#15

I don’t know much and others here would likey be a better help but did you try the motor testing on a pc since this happened? Id try that first. If nothing there then put ur multimeter up to the three phase wires (each possible combo of two wires) and see what u get. I’d think the motor would at least stutter if it was damaged. I’d be strange for the motor to completely die like that.


#16

Pretty sure at this point I’ve tried just about everything it and I can’t get it to work. Neither the vesc nor the motor show any signs of damage.

Edit: I actually found a single charred wire in the motor windings.

@onloop Do you have any ideas about troubleshooting it? Can I get a warranty? Even though its been over 60 days it has less than 5 miles on it.


#17

After some more testing the motor might actually be fine. Even though the Vesc seems to be working properly it shows no output current when I use the multimeter. It’ not my solder joints as I tested the Vesc board itself. Any one have any ideas about what might have caused a vesc to just stop working?