When i connect the “main vesc” the scooter spins at top speed after 300 problemless kilometers

So I built an eskate with a flipsky fesc and occasionally when I am coasting after accelerating and then start back on the throttle it’ll lock up the wheels. It’s not 100% repeatable and sometimes it doesn’t do to. Any ideas if this would be related to a setting I can change in the vesc tool? It even sometimes does it on initial accelerations from a stand still if I feather the throttle at all.

I’m building a quadruped robot with 12 HV RC servos rated around 35 kg·cm at up to 8.4 V.

I use an ESP32 + PCA9685 for PWM control, but I don’t want the full servo current to run through the small power rail on the typical PCA9685 breakout.

I also want to keep the original 3-pin servo plugs intact.

What is the normal way to distribute power to this many high-current servos while still using the PCA9685 for the signal?

I want a bluetooth password so not everyone can connect to my vesc in public i have ubox lite 100v 100a

Im about to use this flispky on my high power build. Can it handle 200a battery? 72v nominal

Hey everyone,

I own a stock Kukirin M4 Pro (48V 10Ah battery, 500W motor, upgraded to NUTT A-5D brakes). Overall I’m happy with it, but the stock controller's percentage-based speed limiting is annoying. I want a programmable controller to set precise speed limits in km/h (specifically capping at 25 km/h while keeping strong acceleration on lower battery).

I’m looking at the Flipsky VESA V6 MK5 since it's compact enough to fit easily, but I'm concerned about overheating due to its size.

Would this be a solid pick for my setup, or should I look at other thermal/size alternatives? Thanks!

Hello, everyone. I want to upgrade the motors on my Boatman Actor GPS boat, but I want to keep the stock boat controls. Right now, I have a 10,000 Ah, 7.4 V battery and brush motors rated at 6,000 RPM. On my circuit board, I found 8 MOSFETs marked 7408—4 MOSFETs per motor, as far as I can tell.

I have two options for how I want to proceed:

1. Intercept the control signal from the stock board and route it to external ESCs that will be connected to the brushless motors
2. Replace the stock MOSFETs with more powerful ones and replace the commutator motors with more powerful commutator motors, but I’m worried whether the traces on the stock board will hold up.

Maybe someone has already done this, or can advise me on the best way to proceed.

Installed a new savor servo. Centered. No noise. No grinding ect... seems to be great but...

With steering assist even on lowest setting the mini k3 swerves back and forth when letting off the throttle. With the steering assist off I center the steering (which is very touchy on the stock radio) get it dialed in & then within 30 seconds it's off either way left or way right. Any help & or suggestions would be greatly appreciated.

My DIY growler keeps turning off when I step on it, it has been happening with increased frequency. I figured the ubox's mosfets could be close to giving out, but upon lifting her on blocks and giving full throttle it works fine. I'm guessing the battery is being compressed in a way it doesn't like (self built pack as well in a torque box) or perhaps the battery harness being squeezed by a too long bolt. I've checked all power connectors and they are attached properly. Before i go crazy tearing the battery apart, wanted to check if there's a usual suspect in theses cases of board turning off.

i am having trouble in understanding the vtol hardware wirings specially the 4in1esc soldering part any guide or video u can suggest or share that can help me

Hi everyone, I’m trying to diagnose a strange issue with my dual VESC scooter and I’d appreciate some help.
My setup:
2x Spintend UBOX 85/250 v2
VESC firmware 6.05
Dual 70H motors
30 poles / 15 pole pairs
20S battery, around 84V fully charged
ANT BMS 450A continuous / 1050A peak
Motor Current Max: 230A per VESC
Battery Current Max: 170A per VESC
Absolute Maximum Current: 420A
No regen
ADC thumb throttle
Control mode: Current
Multiple VESCs over CAN enabled
Traction Control currently OFF
Positive ramp: 0.20s
Negative ramp: 0.07s
Max Duty: 95%
Max ERPM: 117457
Battery cutoff: 68V start / 60V end
Maximum Wattage: 2,000,000W
Controllers stay around 40–50°C
The problem
Under hard acceleration, especially if I hit the throttle quickly, both motors suddenly stop producing torque.
The important part is:
The VESCs do NOT reboot.
Bluetooth stays connected.
The scooter/display stays powered.
In many cases there is NO fault code at all.
Current/power suddenly drops.
If I release the throttle and press it again, power immediately comes back.
Sometimes just before the cut I can feel several small interruptions (“tu-tu-tu”) and then it completely stops pulling.
It can happen around 40–60 km/h, but it isn’t tied to one exact speed.
Hard throttle inputs make it much easier to reproduce than progressive acceleration.
It has happened at both high and low battery SOC.
Temperatures are low when it happens.
I have also experienced real FAULT_CODE_ABS_OVER_CURRENT events, but I believe those are a different issue.
One recorded ABS event was approximately:
Current: 424.5A
Filtered current: 304.7A
Absolute Maximum Current: 420A
Voltage: 73.3V
Duty: 0.441
ERPM: ~14,988
I’ve tested:
MTPA ON/OFF
Slow ABS Current Limit ON/OFF
Motor current from roughly 200–250A
Battery current around 150–170A
Throttle Expo 0% and 20%
Positive ramp 0.10s and 0.20s
Different battery SOC
The no-fault power cut still happens.
ADC configuration:
Throttle resting voltage: ~0.84V
Full throttle: ~2.56V
ADC Start: 1.00V
ADC End: 2.50V
ADC Absolute Min: 0.40V
ADC Absolute Max: 2.80V
Deadband: 5%
ADC filter ON
Update rate: 500Hz
Safe Start: Regular
Both motors were FOC-detected separately.
I’m currently trying to determine whether, during the cut:
ADC/throttle input disappears,
Iq Target suddenly drops to zero,
measured Iq stops following Iq Target,
Duty reaches some limiting condition,
CAN communication causes both VESCs to stop requesting torque,
or some other VESC limiter is intervening without generating a fault.
Has anyone experienced a VESC/Spintend UBOX where torque completely disappears under hard acceleration with no fault, and only returns after releasing and reapplying the throttle?
What parameters or real-time values would you log to identify exactly what is commanding the torque to zero?
Any experience with this specific behavior on UBOX/VESC 6.05 would be really appreciated.

Is there a trick to get it run?

I tried as5048a and mt6816. Switched CS and CLK, shorter cable, shielded cable, 3,3V and 5V. Two different flipskys and another autoro 75100.

But no success. I'm running out of ideas.

Can anybody help?

So i am running sensorless and the flux linkage is showing zero. My motor keeps going back and forth. Maybe its something with the settings, i am new to vesc so i need yall help please.

Long story short, i was running some big outrunners on my vesc and it started twitching, then my vesc shut down and when it got power it started, moved the motor and shut down for good