VESC X, SK3 6374 configuration problems

ESK8 Electronics
#1

Hello All

Attempting new setup: VESC X v1.3 (firm 2.18) - SK3 6374 - 9S - BLDC compatible with 2.17 & 2.18

The motor detection in FOC sometimes fails and on the odd attempt where it says it has worked I still cannot control the motor with the arrow keys as it either hums/stalls or it is very jittery. I have also tried BLDC but that constantly gets bad detection results.

Voltage settings are Min 6V, Max 42V, Batt cutt start 32V, Batt cut end 29V. All other motor config default.

let me know what other info will help.

#2

Just set the max Voltage to 57 V and give that a try.

#3

Hi, gave the 57 volts setting a try but same result. Motor has intermittent problems detecting and when I do get a clear run through the Measure R and L, Measure (Req: R) etc I have a humming motor which will not spin.

To note I have gotten the motor to spin previously just seem to get varied results.

#4

please show a picture of your motor connections and soldering.

#5

Apologies as I do not have great lighting tonight. Photo shows wiring and then I have removed some heat shrink to show a couple of the joints. Also I get some red lights flashing on the vesc during detection but when I view Fault in the Terminal tab I get FAULT_CODE_NONE

20170207_212733.jpg1344×2390 992 KB
20170207_212801.jpg1344×2390 1.03 MB

#6

Please post screenshots of the Motor General, BLDC, FOC and Advanced Tab. And also the Applications General and PPM Tab. And please check the voltage in the Realtime Data Tab when you enable “Activate Sampling”

#7

Motor Config.png1620×847 68.6 KB
BLDC.png1620×844 61.4 KB
FOC.png1620×843 67.1 KB
Advanced.png1620×836 42.2 KB

#8

To confirm testing battery voltage on the XT60 which connects to the VESC I am getting 37.6 volts but battery voltage on Realtime is 6.8 volts?

App General.png1620×841 43.4 KB
App PPM.png1620×840 48.5 KB
Realtime.png1620×848 103 KB

#9

OK there we go. The battery voltage is absolutely wrong. 6.8V is not even close to a charged battery. So please check the battery with a voltage meter. Could it be that the battery is damaged. Normally with a LiPo it shouldn’t go below 3.3V a cell (29.7V in your case for a 9S) And for a 9S Battery (i guess a Lipo) the cutoff start should be 32.4V (3.6V a cell) and end 30.6V (3.4V a cell). Also the FOC detected values can’t be correct. They are too low. So first your battery issue needs to be solved and then you can do the FOC motor detection again. Don’t run the motor with those settings because you will damage the VESC with these FOC values.

1 Like
#10

Thanks for the assistance. I will have to wait until after work to do anything further. I assume I will have to open up the VESC to determine where the 37.6 volts drops down to 6.8 volts?

#11

No need to open the VESC. Check you battery first with a multimeter if it really has that voltage.

#12

Yes I have checked the battery several times and have gotten between 37.8 and 37.5 volts each time. I have not tested while connected as everything is insulated. I will just have to cut some away some spots along the wiring harness so I can test it whilst powered up/under load.

I will separately test the batteries individually under load just to try and eliminate everything I can.

#13

Ok so I have checked the voltage whilst powered up and it is currently sitting at 37.4 volts. I have checked the power on the connections to the VESC and it is also sitting at 37.4 volts. At the same time I have run the Realtime data and Battery voltage is saying around 6.4 volts. This does not make sense does it? So am I correct in saying there is something wrong with the VESC?

Still getting FAULT_CODE_NONE in the Terminal tab.

#14

Update: Enertion support are arranging a replacement of the VESC X. Thanks to Ackmaniac for the fault finding assistance and Enertion for monitoring the posts and offering the replacement before being approached about it.

#15

Try using different USB cables, I had an issue with my vesc where it wasnt connecting properly and tried 4 different USB cables and finally one of them made the vesc work correctly.

1 Like
#16

Hi Tampaesk8er, I can try this next time but I have already sent back the VESC for a replacement. Thanks for the tip.

1 Like