Hi,
I have extracted:
from my own VESC. Here we can see the positions where the hall sensor changes state.
Now on the VESC6 I get:
Hello! I've been playing with a forked version of the vesc-tool and just found an easy way to add HM-10 compatibility alongside the NRF chip which is currently supported. The NRF chip is superior since it can operate at 115200 Baud and I find the HM-10 is stable only to 19200 Baud. I'd make this a pull request, but code is forked and now head is a few commits in front, also the changes are minimal so I'll just outline here. The key thing I found that made this easy was an AT command which creates adds a second characteristic to the HM-10 service UUID.
Hi everyone,
I apologize if this subject has been addressed before but I was wondering where do I go to read the fault or error codes of my VESC in the new VESC Tool?
I have been riding my e-board for about a total of two weeks now and all of a sudden my motor will not spin when I pull my remotes throttle. The VESC is flashing a red LED three times every time I pull the throttle and from what I have looked up online it seems there is some fault code that my VESC is producing and thus my VESC is stopping the motor from running.
I am working on my motor controller.... Suddenly I get "inappropriate ioctl for device" when pointing vesc_tool at my VESC device. I strace-ed vesc tool and:
open("/dev/ttyACM0", O_RDWR|O_NOCTTY|O_NONBLOCK|O_CLOEXEC) = 13
fcntl(13, F_SETFD, FD_CLOEXEC) = 0
ioctl(13, TIOCEXCL) = -1 ENOTTY (Inappropriate ioctl for device)...
ioctl(13, TCGETS, 0x7ffc165712a0) = -1 ENOTTY (Inappropriate ioctl for device)
The reported frequency of a signal varies PWM frequency and sampling mode. Is this a bug?
How to reproduce:
Hi,
Somehow my hardware measures "R= 0.00". To try and figure out what is going on I'd like to run the lambda detection. But this is blocked due to the R=0....
How Do I get past this?
.
I tried this on a MAC and a PC with VESC 0.94. It connects to both, but disconnects about 5 seconds later. The blue LED turns off too.
The Tool displays this message for a second or so: "Der E/A-Vorgang wurde wegen eines Threadendes oder einer Anwendungsanforderung abgebrochen."
"The E/A process was aborted due to a thread end or an application requirement. "
Hi there,
Relatively new DIY eBiker here. I'm providing current to my motor using a hall-sensing throttle on ADC (3 wire: 3.3V,GND,Signal). However, once everything is set up and written to the VESC, the connection between the throttle and VESC is very touchy. Any physical movement makes the motor spin up. This is a definite safety issue, so does anyone have an idea for a fix to this?
Best,
EBR
Hi,
For some reasons, I can't suddenly open VESC Tool after building it through Qt (no error while compiling).
I didn't touch to the BLE part (I'm working on integrating modes).
I get this message in "Application Output" tab.
qt.bluetooth.bluez: Missing CAP_NET_ADMIN permission. Cannot determine whether a found address is of random or public type.
The program has unexpectedly finished.
The process was ended forcefully.
Any ideas ?
Thanks !
Clément
Good afternoon,
First of all: Thank you for the VESC - a really well designed piece of hardware! After using it with the VESC Tool on Windows I thought it might be a good idea to start using the VESC Tool on Linux (Mint)...
I managed to install Qt SDK (Qt Creator 3.5.1 / Qt 5.5.1) and to clone the repository. When trying to build I get the following issue:
QSerialPort: No such file or directory
/home/.../vesc_tool/vescinterface.h
