At first let me say that I'm new using VESC, I'm working on an E-Bike project so I built a custom board based on VESC HW 4.8 solution.
In BLDC mode everything is working fine for me with the default FW 2.18 using BLDC Tool (duty cycle and rpm control, sensorless and using hall sensors...), but when I want to switch on FOC mode and I try to measure R and L, in this process my card disconnect.
Motor configuration that worked for me :
I tested also with the default FW 5.10 with the VESC Tool and I got :
- Same problem when measuring R and L in FOC mode.
- Over current fault when reaching 50% duty cycle control in BLDC mode.
- RPM control not working in BLDC mode.
I'm working with a rear hub motor 250W 36V and 10S Lithium Ion battery.
Is there someone who had this problem before ? Any help ?
Btw you don't need to make everything bold.. This isn't the Trampa product page lol.
If you want help with custom hardware you might need to tell us a bit more about your design. A schematic and some pictures of your board would be perfect.
Usually the problem you are referring to is caused by some problem with phase sense resistors, current shunt amplifier or just noise from poor layout.
I would certainly stay away from older firmwares as they have many problems. Use the latest one.
Thank you for your response,
Its okay I'll make it simple now without bold words
So this this some pictures of the schematic :
What is connected to STM32 reset pin?
To reset using a switch, other MCU, or JTAG
Unfortunately posting snapshots of your schematic doesn't tell us about the boring things that are vitally important: decoupling capacitors, logic power supplies, board layout etc...
If it works when the motor is un-driven but driving the motor causes the USB to disconnect then it's probably noise. Have you tried the nicest USB cable you own? How much decoupling do you have on the USB connector, any EMI filtering? What's the PCB layout like? Do you have high voltage high speed traces near sensitive parts/traces? Hows the ground plane?
I have a similar problem, though maybe not as bad. My motor can detect easily on a power supply, and sometimes on batteries, but other times the fets explode and catch fire during detection. I have good separation between my shunt signal traces and a ground plane above and below them.
When running, I always get an overcurrent fault around 35-40A where the current goes to -nan. Sampling on fault shows this issue happens in 1 sample. I will make a separate post about this. Perhaps we can discover a big "dont" about the layout process.