10S custom skate ESC: testers wanted!

I got one of the latest enertion vesc 4.10 batches and tried it today - flashed 1.14 to the 2.7 FOC release. autodetection worked flawlessly, motor spinup was smooth, probably needs a slighty increased startup boost, otherwise Im really exited about the unit and the little noise it makes. :)

really really great job - basically I had no idea about VESC useage and it took me 20min to set everything up. doesnt get any more user friendly! :D

[youtube]n9nQEWt5TYY[/youtube]
 
scoobiext said:
That looks awesome Chaka, how do you have the CAN bus wired? Are all 4 controllers on the one bus? What are the plans for the board/s?

The heat shinks are the icing on the cake, nice work.

I set this up wired for ppm input split off one receiver and also made a CANBUS splitter in case the customer wanted to implement that at a later date.
 
Hi guys!

I just fot my VESC 4.10 a few days ago, and I'm still finishing my first eBoard!
It's my first time with BLDC and VESC too, so I'm still confuse about many things... But it works!

However, I was giving a try to this new FOC feature, and when I try to read the parameters (R, etc) from my r-spec motor, it fails and kind of blocks the motor, starting an annoying sound after failing, and blinking the red light on the VESC...
:( :shock: any idea?
 
chaka said:
Are you sure it is failing? Have you checked for faults? Does it still work running under BLDC configuration?

You were right, I was being dumb. When I hit "measure R and L", after a first quiet noise, it started doing a really loud noise for more than two seconds, and I thought that something was going wrong, and concerned about the life of the motor, I switched off the power of the VESC everytime to prevent any kind of motor damage :roll: ... But yes, now it's working fine, thank you!

The only thing now, is that I really don't appreciate any difference between BLDC and FOC... I'm sure it has to be different, so, what should I be looking for :lol: ? The only thing is that in BLDC my motor reaches 44000rpm, and in FOC it only goes to 41000rpm...

And, another thing related to this; how many rpm should I be getting with a rspec190KV, 9S Zippy Lipo 5000maH? I'm getting inconsistent lectures and speeds within the same charge (yesterday only 30.000rpm, and a few minutes before, way more than 50000rpm)

To sum up, is there any guide (or a XML file) to really set up my VESC to fully work with my rspec motor :p ?
 
FOC is almost silent while under load and a bit more efficient than using BLDC. As you have noticed FOC will shave a little off the top end compared to BLDC.

You are running with a very low capacity pack. Double or triple the capacity you currently have and it will have a much happier life and smooth out the voltage fluctuations under load. This is my best guess to the fluctuation you are seeing on your max erpm.
 
Hello guys

Anyone know how can i measure the motor temperature in BLDC Tool? i connected my motor temperature sensor to VESC but there is no way to tell if it's working, and in the terminal help there is no command for temperature
 
it'd be great if someone who at least had a half-decent grasp of setting it up could do a video for dummies. Maybe I'm missing some of the videos out there. I've seen vedder's and (I forget his name now but the European guy who sells them) but they don't go through all the features. If I hadn't had a friend come over and set it up with me I likely wouldn't have gotten even the bldc program downloaded and going. I'd like to set up the foc but don't know where to search for info. I find the vesc is not complicated to set up but until you know what you're doing it is. I never do anything on a computer but watch my shows, shop, play chess, and get on ES so the set-up was foreign. If there was a resource that answered all the questions then we wouldn't constantly be asking questions.
 
jacobbloy said:
updated BLDC TOOL for the vesc to FW2.8 with FOC to day for windows and OS X.

hope every body enjoys.

windows
https://drive.google.com/file/d/0Bym9XrdeViekNVdRVUN0M2VTMkE/view?usp=sharing

OS X
https://drive.google.com/file/d/0Bym9XrdeViekNVdRVUN0M2VTMkE/view?usp=sharing

That's great!

Can someone tell me why I always get ''unknown error''? I have Version 1.1, HW 4.7. Tried on both BLDC tools (yours and for FW 1.1). After the Error I have to repower my VESC otherwise it does anything and can't be detectef from BLDC tool.
 
You might try the following on BLDC-Tool v2.8:

- start BLDC tool 2.8 and connect USB cable to VESC
- connect
- Firmware Tab: choose Firmware 2.8 (in folder hw_460_470!)
- hit upload (now you will be stuck, but no worries)
- leave everything like it is (BLDC must stay where it is)
- power VESC off and on again (don't disconnect USB cable!)
- hit connect again
- acknowledge "outdated Firmware"-message
- hit upload again and it should now upload the FW

If this doesn't work you might have to reinstall the bootloader with a STlinkv2 again. Were you ever able to update your FW before?
 
thx, very fast reply
elkick said:
You might try the following on BLDC-Tool v2.8:

- start BLDC tool 2.8 and connect USB cable to VESC
- connect
- Firmware Tab: choose Firmware 2.8 (in folder hw_460_470!)
- hit upload (now you will be stuck, but no worries)
- leave everything like it is (BLDC must stay where it is)
- power VESC off and on again (don't disconnect USB cable!)
after that point it's like i did anything, uploading firmware seems to just disconnect and freeze my VESC till i restart it.

elkick said:
If this doesn't work you might have to reinstall the bootloader with a STlinkv2 again. Were you ever able to update your FW before?
What is that? Didn't try before.
 
If you have not yet tried to upload a new firmware until now it could be that your VESC is not containing a bootloader which is required to upload a new firmware to your VESC.

I know that there were some VESCs without bootloader (or not functioning ones) in the past. I was having four of those from different sources. The only way solving this is by uploading the bootloader manually with a STlinkv2 connection under Ubuntu. If you're in Europe I could do that for you (for free of course, that only takes a few minutes).
 
okp said:
hope it helps guys.

great effort, just one little details: you measure lambda before you measure R (resistance). in the lambda measurement, it explicitly says "req. R", so if you just follow the GUI, you should measure R and L (inductance) before measuring lambda?
 
Yes, I think I read that somewhere; I will ask Benjamin and modify this if necessary.

vedder said:
R and L can be autodetected without starting the motor, and lambda (flux linkage) can be detected by spinning up the motor in bldc delay commutation mode. These are the important parameters to get the sensorless observer running. There is also automatic PI current control parameter calculation as described here (the time constant has to be chosen, but this is not critical for eboards):
https://e2e.ti.com/blogs_/b/motordrivec ... ve-part-ii.
 
okp said:
hope it helps guys.

[youtube]Ahe-u3cZ2Po[/youtube]

hey, tour vid is great, just wanted to add that there is an apply button in v2.8 for motor detection that will copy the limits in automatically saves 1 sec lol
 
Guys, caution with firmware 2.8, i don't know if is fault but it is the only thing i changed

Is was ridding a few minutes ago and in max speed the VESC suddenly applied full brake, hands and one of the knees aching pretty bad, but is superficial

From now on i will only ride with full protection

What i found strange is the full brake way beyond the max brake current, so probably has nothing to do with the radio, when i tried to plug it in the BLDC tool as soon i touched the usb connector the motor started spinning to both sides at random, weird again, since reverse is disabled, and for last there were no faults logged

Ride safe
 
i would start with refreshing the firmware, then re doing motor detection while also checking all of your wiring, then make sure that where your are located there isn't crazy amounts of rf, it can interfere but very unlikely, there is a study done buy 2 guys who hacked and controlled a boosted board e-go ad evolve just but filling the 2.4 spectrum with noise they did this because the same thing happen to one of them on his boosted board.
 
jacobbloy said:
i would start with refreshing the firmware, then re doing motor detection while also checking all of your wiring, then make sure that where your are located there isn't crazy amounts of rf, it can interfere but very unlikely, there is a study done buy 2 guys who hacked and controlled a boosted board e-go ad evolve just but filling the 2.4 spectrum with noise they did this because the same thing happen to one of them on his boosted board.

I just downgraded to 2.7 and re-configuring it, but probably wont ride in the next few days, i live in a few kilometers away from town, and i was ridding in the road that connect it to the city, so not much there except from a low voltage power line that was more than 10m away, and i rode this exactly place lots of times

But in this case you mentioned they did that by confusing the raio input, since in my case i were full brake for the motor, a lot more than i can get giving full brake in the remote via current control i suspect something happened in VESC itsel. I re-checked all configuration and there was nothing that would cause full brake in case of signal loss

okp said:
hey pedro, sorry for that... which transmitter were you using?

I am using the NRF modules with arduino and connected to vesc via PPM, as i said above, due the nature of the brake force i don't think is was related to radio communication, in the arduino code i have a fail safe to reset everything to neutral in case i get radio drop or problems with communication

Did you update to 2.8 yet?

EDIT:

Hum, apparently my NRF module was a little loose on the connector, i was delaying to weld everything because i was ridding a lot lately , but even if it came loose it does not explain the full brake

EDIT2:

And again, apparently my fail safe is not so safe in fails, it works good with a signal loss, or if the remote shut down, but if remove the module the PPM output goes crazy and start to oscillate between 0 and 100% at random several times per second

Maybe this could cause some trouble on VESC? even after i could get up again the motor remained full on full brake

And a tip for everyone duct tape is not a good measure to prevent vibrations from disconnecting connectors :|
 
Back
Top