VESC Tool

Hi all,

I am trying to read a voltage [0-3,3V] from ADC1(SCK_ADC_EXT) but I always get an error: ReferenceError: val is not defined

While setting up 2 motors via serial + can forwarding I noticed that during the last stage of Setup Motors Foc's Run Detection the motors seem to turn very smoothly and slowly. I have tried to replicate this via RPM, Duty, Current and Pos control and have been unable to do so. Looking through the code I similarly failed to find what commands this magical wizard uses. Furthermore I have modified the code to print all commands sent to serial via vescinterface.cpp and nothing is sent during these movements.

Would be a nice addition to the mobile app to have the option to use my phone to connect to the USB otg for firmware or setting changes instead of my laptop as it's a always a rock solid connection.

My experience with the BT function is hit and miss, sometimes I have no end of trouble just trying simple changes, I'm resorting to installing some micro USB extensions and tucking them away outside the enclosure. I'm getting over the BT function, I didn't notice this before with 5.2 but I do with 5.3.

Hi everyone,

 we use 3 vesc 75/300 with can-bus config (1 master, 2 slaves).

All 3 have identic motors but on one we have big difference in RPM (50% lower).

Configuration is: master in middle and the outer ones (left and right) are set as slaves.

Running auto-detect-function identifies one motor to lower power-values. Why? 

brs,

Peter.

    Okay.......im currently building a Direct Drive Motor for use in sim racing games. Im using a Mige 130st-m10010 AC servo motor/FSESC 4.12/Stm32F407 Discovery board/24V/15A DC power supply/Can-Bus/ and vesc tool and honestly, everything is working as it should....encoder detected, FOC detected and App settings are filled in using an .XML file....My problem is, that when i leave VESC Tool to go do anything, like calibrate the wheel in a seperate app(EMC Utility) it doesnt register my encoder!

Vesc tool works fine on my computer, but cannot get the app to work. No matter what I do it connects and then says "could not read firmware version, make sure the selected port really belongs to the vesc". I have the correct Bluetooth chip installed in the correct port, uart is enabled at the correct baud rate, I have flipped the rx/tx pins, I'm on vesc firmware version 5.3. What else could be wrong? Would upload pictures of the error but can't figure out how

Hey team,

I was out riding my VESC little focer v3 and wanted to turn on 'Realtime Data Logging'. Enabled it and Clicked on Browse as I wanted to change the storage location of the log files.

Clicking on the file path loaded a screen about configuring my inputs and wiped all my existing settings. I had not realised it had wiped everything and tried riding and it would not engage.

Anyways when I got home I ran through the wizard to get everything back setup but wanted to log this if anybody else has had the issue?

Hi I got the flipsky 75100 connected to domino throttle using the 3.3v comm from the vesc.  I am using the desktop vesc tool.

I ran a logic analyzer on the vesc and the signal reaching the controller is clean for the throttle but I can't seem to see the input of the throttle on my tool gui.

Is my settings off ? 

Vesc is reading esc temp, battery voltage all fine.  And controller is working as expected.  It's some issue with my settings...

My appreicate a helpful 👏

Thanks for your help! Total beginner here.

I tripped over my usb cord and ripped off the usb nib on my Makerx h200 VESC. so no usb connection to my pc!

I initially got around the issue by connecting  a bluetooth module to  the VESC and then using the Mobile VESC tool but after getting almost all parameters set the app now says "This VESC is not paired to your local version of VESC Tool. You can add the UUID manually.........

Hi, lately I've been having the issue of reading/writing to the slave sometimes causes the loss of the can bus connection mostly when using the android app via BT and the esc stops responding. If I reboot the esc's it's back again, I'm using v5.3 on flipsky 6.7 esc's. Similar problem happens on dv6 maker-x also, is there something I'm just doing wrong or a known issue?
Tried searching but couldn't find anything about it.