@Trampa I don’t think the library of cells you mentioned is worthwhile. Updating would be a nightmare and cells don’t perform at advertised limits. Plus there’s pack assembly and BMS considerations.
As for batt min settings and high speed brakes, that’s something Frank helped me with when I was having brakes issues with my initial setup. There’s still a big disconnect across the forums on what the proper values should be. The old recommendations of 100-200% max cell charge rate x P group flat out doesn’t work for 2p-3p battery users. We still have users pop up needing help with this.
Maybe a min bath minimum value? Or just red numbers below a certain value. Extra info in the “?” bubble
I have an idea that could use a second PWM channel input. A horn button on the remote that pushes some HFI like pulses to make the motors make some type of beep beep sound. Without requiring extra parts to make an actual horn.
@Deodand Would this be technically possible to get some sounds from the motors while riding without negatively affecting the main motor control functions?
You’d need some voltage overhead I think or you might lose a bit of power (i.e. you’ll take a bit off the top speed and heat the motors slightly). But yea its possible to superimpose a net zero force excitation that outputs audio. Just keep in mind motors aren’t designed to be speakers so it’s going to be a pretty inefficient conversion to noise.
@deodand is there a throttle curve section I missed? I saw the positive and negative ramping time but no graph with sliders like focbox UI.
Also, it would be great if the wrote configuration success green bar overlayed the settings screen. It’s mostly hidden at the moment. Maybe add total battery capacity vs individual cell capacity in the help notes for pack capacity just for clarification.
Other than that, everything was super intuitive and setup went exactly as expected.
Everything set up mostly well, ride is going well but I get weirdness at full throttle. Feels like my motors can’t keep up with input. Ends up feeling like a shaky onset of speed wobbles. Motor detection results match my old ones.
So I just need to activate can forwarding and it will automatically apply ALL settings to both motors? Or do I need to rerun wizards to apply to both motors again after enabling?
You scan, then activate and then change the same setting for the other VESC. Wizards and Profiles always consider both ESCs.Manual changes of settings are PER VESC only. So you need to tunnel to the other ESC and then do the same thing again.
That is why the profiles exist. They affect both sides. Write to all would probably be possible but could mess things up easily. You always WRITE the entire configuration, and the config of Motor A differs from Motor B. So you don’t want to copy the CONFIG over to the other ESC.
