General discussion

.

Is it possible to configure VESC to ignore the remote control signal, for example, depending on the state of a circuit coupled to a REED switch?

Is there a command I can issue to VESC based on the state of REED switch, so I can disable VESC response to the PWM control signal?

Is there a command I can issue to VESC based on the state of REED switch, so I can enable VESC response to the PWM control signal?

Hello, I have built this contraption of a vehicle we call the "tot rod" it has dual brushless motors a controlled by an 8 channel radio transmitter. I have an unnecessary amount of 20v power tool batteries at jus disposal, I've been running up to 4 of these depending on how far we are going.  20v get this around 12mph @ 20v with 4 batters at 20v it will drive around for hours. With 4 batteries at 80v it did wheelies and immediately burned up the ESC... this began my learning curve that brought me here. Ideally 40v is plenty. Can i rebuild these smoked esc units?

Is it possible for this software to control via an analog input instead of a pwm input? 0-5v reference signal. Not looking for complicated but this is the signal i can produce in my project. 0-2v %20 power, then a variable rate from there on increasing power to 100%. This will be a steady state application. Motor will stay on for long periods at low power then for short burst (max 10-20secs) be pushed towards full power.

Folks,

Which twist throttle and break lever works better with the VESC tool? 

Regards,

Hi everyone,

I am using a vesc 100/250 with an internally geared QS138v3 on 22S

Thus far I have the phase current at 320a and it is plenty of power. No issues.

I am wondering if I can get more RPM through the use of field weakening. There is no question that it will work but the question is if it will kill the vesc.

I am unsure about the inner working of field weakening however I was under the impression that it may increase the BEMF voltage at peak to above what the mosfets in the vesc are rated to and cause a melt down.

Good afternoon all,

I've a VESC 6 Mk5 that I am using in conjunction with a Teensy 4.1 in an escooter application.

To provide a robust and reliable emergency stop, I have a big ol' red e-stop button hooked up between the VESC and Battery via a solid state relay.

I had a bricked vesc that failed to program via swd then failed to even connect via swd. I did a fair amount of searching and came across a tip on the spintend website that deserves to be posted here for all to find more easily. First check if your vesc to vesc swd connection works the normal way. Watch the video: https://youtu.be/PFFiVxFHDM4 starting at 5:40. If that doesn't work, try this:

Procedure:

Dear All,

I got kicked into a project where they previously used a 2x(JETI controller and a Motor brushless outrunner (Hemotec 105.20 KV135)). Due to my little experience with the VESC 6 I was able to convince them to go for the VESC 100/250 - because and also of the CAN capabilities.

So I am using a VESC for a project where I am re-doing an Kreweser electric trike-cooler-scooter-thing and have done most of the wiring but hit two spots that I could use some insight on:

Hi,

just bought the Maker GO-FOC Hi200 ESC from Maker X. It had 5.02 firmware on it but I could not get the input wizard to run on the latest Vesc Tool. It said something about unsopported firmware. The Motor Wizard worked just fine. So I upgraded(to 5.03) and now both wizards runs fine but something is wrong with the motor settings because the motor is very jerky which is was not on 5.02. So lets downgrade I thought. But I cannot get it to 5.02!!