VESC Tool

Hi, 

I'm testing high rate current control over 1kHz using USB-Serial connection.

For testing, I changed the baudrate in VESC-TOOL. I tested from 1152000bps baudrate.

In my case, the connection was successful at below bps.

115,200 bps : ok

230,400 bps : ok

345,600 bps : X

921,600 bps : ok

I was surprised when 921,600 bps works even the 345,600 bps is not working.

Do you know why and Is there any body who knows the maximum baudrate in USB-Serial?

Do I really need the HM-10 to make a bluetooth connection with Vesc Monitor Mobile for Android?

I have a METR bluetooth dongle on my Vesc 4.12 installed.
The METR app and PerMETR apps are working just fine.

But I cant get the Vesc Monitor app to connect to the VESC with my phone.
It does find the bluetooth dongle, but won't connect to it.

Heello everybody!

Well... I need help to solve some questions with the settings with VESCTool. I have a little project which objetive is only charge a battery with the wind energy.

I have:

Motor-->  https://diyelectricskateboard.com/products/electric-skateboard-motor-637...
Features:

Hi guys,

I've been using a VESC 4.12 for my eBike since two years now and upgraded recently to the new firmware and the new gui.
I also swiched to a more powerfull motor, so I tried to ramp up the current step by step to see the capabilities.

The VESC 4.2 should be able to handle 240A continuous, from the IRFS7530 datasheet (with proper cooling, I know). Currently it's configured at 100A and is doing pretty good, not warming up too bad as I have a fan forcing fresh air in the case and temp monitoring.

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....