Feature Requests

Hi,

I made custom board that has AMC1301 powered from mosfet bridge driver. Problem is that when start it calibrates current without AMC1301 powered and then it reports invalid currents. I tried power all AMCs from battery with diode and it worked without problem. I think this should by fixable by software.

Is it possible to make some extension that will at freewheel operation switch one lower mosfet ON? This should power all AMCs.

I tried some changes in code but I only keep blow fuses.

Thanks,

Anton

Hi, 

It would be nice if we have lights configuration tab in VESC TOOL so we can set things like:

1. Protocols as WS2811/2812B
2. Number of addresses(RGB(W) LEDs) in front and back - for white/red lights and turn lights
3. Auxiliary addresses like underglow and high beam(external high power led with narrow beam), which can also be controlled from WS2811 IC over PWM.

Also we will propably need to have more buttons on the nrf remote.  

Hi

I would like to control position, start, stop and rpm with Matlab.
Therefore an enhance position and rpm interface would be great.
Possible solutions:
a) enhanced VESC/PC terminal commands -> e.g. set_position [degree], set_rpm [rpm], start, stop 
b) enhanced app -> control typ of app can also be position -> e.g. PPM min ... max = 0 ... 359°
c) arduino implementation -> kind of clear text bridge -> e.g Matlab send to arduino set_position [degree] -> arduino translate to VESC-language

With this controller gaining more and more usage in the combat robot world we robot dudes will need some special features that wouldn't normally be necessary for skateboards.

I was thinking of diving into the firmware modification myself, but I'm hoping somebody who is more familiar with the project could maybe give it a go, or at least tell me if it is even possible.

SINE/COSINE Encoders are seen in higher powered PMAC motors like the Motoenergy ME1304. These encoders take the place of hall effect sensors. This feature would be helpful in high power VESC designs like the BESC which would be very useful to drive such large PMAC motors.

For a motor without a temperature sensor installed, would it be possible to measure/estimate the motor temperature based on the resistance of the motor coils? Would it be possible to measure that while the motor is running, or only when still? Has anyone ever done this with a VESC? 

I have a sealed motor, so installing a NTC on the coils would be difficult. The VESC runs the motor very well at first, but struggles to start correctly 100% of the time after the windings get hot. 

if any one can help i am trying to find the best way to run my Chinese bldc in hub motor with hall sensors this is not on a skateboard so dosen't need high torque just needs to run smoothly at low rpms and start cleanly controed by a pwm rc controler im using a 50W vesc v4.12 at the moment and getting best results using bldc set up over foc but its not ideal as its for a camera rig i was using arduino with puls in and a stepper motor but that was ok but still pretty clunky and noisy even using interrupts any help would be much appreciated nice one ig

It would be really nice if the VESC firmware included an option for trajectory/position control, beyond the single rotation currently supported. At the ODrive they recently implemented a trajectory planner, and it would be really nice if VESC's supported this too. Maybe having the source code available also makes it easier to implement. https://discourse.odriverobotics.com/t/ ... anner/1104

Is it possible for VESC with push button on/off anti-spark switch to have auto power off?. Can this be implemented?

I would like to build a VESC based on 4.12 HW with a single shunt in the ground line, to overcome switching losses and have 100% duty cycle. BLDC mode would be sufficient. It shall work without sensors. It shall be used to drive an outrunner with prop. Phase current and battery current shall be limited. This would boost the capability of the 4.12 to drive high currents a long time without overheating, because the switching losses exceed the ohmic losses already now.

Is there a configuration possible with the existing code?