VESC Configs

[_eXo_]

Hello together,

Is there already an VESC-Config for this Motor?

http://alienpowersystem.com/shop/brushless-motors/6374-sensored-outrunner-brushless-motor-130kv-3200w/

Best regards
eXo

 

[whitepony]

vesc detects all required parameters on its own and i think that works for most people!

 

[_eXo_]

I killed the DRV with my first Test. So its not that easy..

 

[WeeChumlee]

Oh dear.
I would assume there is a short somewhere to cause that form of catastrophic failure.
The magic smoke wanted out pretty sharpish to lift the lid of the chip.
Did you solder the VESC yourself of did you purchase one complete?
When exactly did the failure occur, only once you started the automatic detection?

 

[RogerD]

Same happened to me. I setup a VESC , all working fine on 2.4/2.5 (can't remember). Gave it to my mate. He flashed 2.8 FW and then on autodetection blew the same chip.

 

[WeeChumlee]

Hmm, not nice news.
I have two VESCs running in my dual and I must say the setup, using BLDC and not FOC, went very smoothly.
On my single motor build I have the same, though unsensored, 6374 motor from Alien that _eXo_ mentioned.
I am shortly going to be changing that to a VESC, hope the same does not happen to me.

 

[elkick]

Just be carefull when updating the VESC to a new firmware, choosing the a vesc_default.bin from the wrong directory will definitely kill your VESC! So, for HW 4.7 chose the directory hw_460_470/VESC_default.bin, for HW 4.10 choose hw_410_411/VESC_default.bin.

I'm not saying that this might have been your issue with it, but in general it happens way too often!

 

[RogerD]

Just be carefull when updating the VESC to a new firmware, choosing the a vesc_default.bin from the wrong directory will definitely kill your VESC! So, for HW 4.7 chose the directory hw_460_470/VESC_default.bin, for HW 4.10 choose hw_410_411/VESC_default.bin.

I'm not saying that this might have been your issue with it, but in general it happens way too often!

Could that result in a blown (physically) chip?

 

[elkick]

Yes, it kills the FETs and/or the DRV instantly during motor detection.

 

[Trbt555]

Note to self: don't run motor detection.
Ask others to provide motor parameters 8)

 

[elkick]

Note to self: don't run motor detection.
Ask others to provide motor parameters 8)

That won't help, detection is not the issue, but the wrong firmware is. First time accelerating will kill the VESC then, so it's better make sure that the FW is correct before doing anything.

Detection is the most reliable way to get the VESC operating correctly with your specific motor.

 

[_eXo_]

Note to self: don't run motor detection.
Ask others to provide motor parameters 8)

That won't help, detection is not the issue, but the wrong firmware is. First time accelerating will kill the VESC then, so it's better make sure that the FW is correct before doing anything.

Detection is the most reliable way to get the VESC operating correctly with your specific motor.

I had the correct firmware on my VESC. I've only tested my alien engines.
With my hubmotors and the same VESC I had no problem.

 

[chaka]

I know of another alien motor user who is consistently blowing drv chips might indeed be something to look into.

Also that chip looks like it got really hot during re-flow. High heat will remove the print on top of the chip. Could just be the photo angle.