VESC Tool

Hi,

I'm in the process of building a custom firmware to disable NRF module (too much 2.4Ghz devices in a close space, Bluetooth connection is not steady).
I modified app and info xml files to match my new parameter (and those modified like the FW number) but the changes seem to not be saved (even if I click on the disk and I get the green ack).
I tried to run VESC Tool in Sudo permission, but no luck.

What do I miss ?

Thanks,

Cheers,

Clément

Hi everyone,

as I stated a few days ago, I was requesting a boost current feature to allow a short term increase in the maximum motor current, Intended for motors without temperature sensors ( i.e. Turnigy SK3 ) , to increase performance and acceleration without risking motor overheating during long term increased load, for example climbing up a long hill .

I went ahead and made a github branch together with my buddy Tom, dug into the code for 2 days and managed to add this boost current feature to the interface as awell as updating the firmware.

Hello

I will try to make it simple

I have a vesc hw 4.12 that I can connect and works perfectly under vesc tool 0.83 FW3.30

But impossible to go under the new 0.87,

it remains in limited mode. At the connection it appears the message that the firmware is too old it goes into limited mode,

I go on the firmware tab, I download to the vesc, the cursor goes to 100%,

and the following message appears in red at the bottom right: "Status serial port error: a peripheral device attached to the system does not work properly"

Hello,

I have a problem that my vesc ( 4.12) is reading a 130°C Temp on the FET. R1 and R2 are both around 8-9k Ohm and I don't really see any damage. 
I use my vesc for a very timid setup on my dual esk8. 
Instead of fixing the hardware, I would want to run the risk of increasing the limits from 120 to 160 °C since I have never hit the Temp limit and I ride my esk8 now for 1 year. 
If the Vesc breaks I have a reason to upgrade the latest vesc 6 :D

VESC_TOOL 0.87 (and not 0.84) has support for something called "BLUEZ". I suspect it has something to do with bluetooth. I've never used bluetooth,

So when I start vesc_tool, I have to wait 30 seconds for the message: "Cannot find a running Bluez. Please check the Bluez installation.". 

FYI, 

I just had to restart some things, and it has cost me half an hour to get things to work again....

I searched for a compatible VESC_TOOL because all of them said: The attached vesc is too old, please upgrade with a programmer. I may have a "slightly older" vesc6, and I don't currently want to risk bricking it by trying (and failing) to upgrade the firmware.... 

Alright guys so I have a cheap vesc that was able to update to ackmaniac's 2.54 which is nice. I am not able to get my motor detection to work and the motor doesn't get a signal to it at all. No sound coming from motor, no movement, no nothing at all.. The voltage parameters and everything checks out correctly, but still testing hall sensors and motor detection are failing with no faults.. I tested the motor on a esc does that mean the motor is ok and should work with detection? Or should I check the coils out and take the barrel off?

Hi there

I have an VESC 4.12. As I soldered around on the Vesc it seems like the ADC1 is broken now. Im using mine for an diy Ebike so i have a hall throttle hooked up to it. The signal seems stuck on 2V even when i havent pluged in anything to it. So i checked the ADC2 which seems to be still working well. My problem is now that i cant use ADC2 for Current Control. Is there a way to exchange those signals in the software. It would be sad if i had to buy a new vesc just because of one broken ADC pin.

Thank you in advance

Dom

I have a self built VESC 4.12 with 3.34 Firmware, Haiyin 5000mAh 20-30C battery, Turnigy SK3 6374 149 motor.

I can't get the Motor Setup Wizard to complete.

Please can anyone supply a set of BLDC Parameters that may work?

I have limited the battery current to 15 Amps for safety (is this a problem?) until I get it going on the desk.

I'm looking for I, w, D values that will work for this motor.

BLDC mode, I always get Detection failed, tried a few different values.

Hi, Ben.

Previously, I used 'udp-uart-bridge' to communicate with vesc frequently. In the new vesc, There is TCP connection instead of UDP.

Could you explane how to use this TCP connection method?

Thanks,

--

Dongil Choi