Hello everyone,
Does the firmware support standard CAN where the id uses 11 bits? It seems that the comm_can.c file uses "comm_can_transmit_eid" and never uses "comm_can_transmit_sid".
Hi All,
I am currently using the VESC in a robot application which uses mixing to control the steering. The issue I am having is on standard remotes the mixing method basically makes the corners go beyond 100%. This triggers a failsafe on the VESC as the pulse is out of range causing the robot to stop.
I am trying to modify the app_ppm file to mitigate this however I am unsure where this is contained.
From reading the source I thought this section would be responsible for limiting ranges in servo_dec.c.
Hello folks,
I'm new to this forum and before asking my question I'd like to say that this project is amazing.
I am planning to control a PMSM with 5 pole-pairs.
So if I want to have 20000RPM (for example) I'd need a sine-wave of (20000RPM*5pole-pairs) / 60seconds = 1.666 kHz right?
I was wondering, where I can find information of the maximum possible sine-wave frequency (or the therefore needed pwm-frequence of the fets).
Does anybody have a link / hint for me ?
Thank you!
Dear Guys,
we build a self balancing Scooter with 2 brushless motor and control them with 2 VESC.
We control the VESC with an Arduino Mega over PPM signal. but now we facing some problems.
I need continuous incremental position control for my robot. I'm using this fork of vesc-FW, where tlalexander, raess1, and greymfm have added support for position control with AS5047P absolute encoders.
Hello,
I am having trouble updating my original VESC 4.12 to a newer Firmware version (desired version is 3.31).
In short: Updating the firmware over the VESC-tool or through flashing the newer firmware directly on the chip with an st-link, results in no led blinking and the VESC not being recognized as USB-device and consequently not being able to connect with VESC-tool -> basically bricked.
Information soon
Just wanted to point out that this fork branch has Continuous Integration set up for the vesc firmware, along some extra info in the README
https://travis-ci.com/paltatech/bldc
https://github.com/paltatech/bldc/blob/powerdesigns-dev/README.md
Hopefully we'll see this as part of the mainstream repo.
Unit testing and code coverage would be awesome, maybe someday...
I have tow question,Need to consult
1：switch (comm_step) {
case 1: curr_samp_volt = (1 << 0) || (1 << 2); break;
case 2: curr_samp_volt = (1 << 1) || (1 << 2); break;
case 3: curr_samp_volt = (1 << 1) || (1 << 2); break;
case 4: curr_samp_volt = (1 << 0) || (1 << 1); break;
case 5: curr_samp_volt = (1 << 0) || (1 << 1); break;
case 6: curr_samp_volt = (1 << 0) || (1 << 2); break;
Hello,
I'm new to the VESC and having fun messing with it, but it seems many of the things I want it to do with ADC inputs I'm having to create external analog circuitry.
I'm sure that changing the firmware / code could create the same effects for me, but I'm completely lost as to how to make these updates.
Specifically: I want to have it look at ADC inputs and do certain if / then / else with it. I'll figure out the coding later.
