Whereās your competing product?
In development
You put me into a recursive loop with that answer xD
Maybe best to spend time on this friend.
I spent this past week verifying my inductance measurements, trying to get the most accurate values.
Went to try it out. Starts almost as smooth as hall sensors.
Sounds 10/10
Just curious, are you on FOC sensorless or BLDC sensorless?
FOC sensorless with HFI
Noted on that Iāll give it a try later
Yeah, I was about to say the same as @tipsy did, right now you are being like the employee that sees a problem, but doesnāt actually do anything to fix it, they just point and shout at it.
I am all for catching issues when they are discovered, but whereās your solution? Why shout negative feedback without offering a solution? Your solution may be your own competing product, but without proof of it, the general feeling is that youāre just being a dick lol
I understand most of what you are saying and people can say what they want about Frank and the whole ordeal of VESC but they are doing good work here, and frankly (lol) any positive updates in the software are great news for the common end user that wants a reliable speed controller
I see what you did there
How are the brakes?
As I said, working on getting the most accurate measurements as possible and keeping the firmware light and efficient so fewer things can break. Already made notes of future revisions so hardware circuitry can shut down the power stage in case of fault and cut software out of the picture during fault conditions. I hope to eventually fit it in 128kB of flash. This keeps costs down for the end user and helps keep software bugs from rearing their ugly head.
The current sensing stage is 25% of the BOM. I spent several days designing the 3.3V supply to minimize ADC noise.
@Deodand @Trampa is there a risk that motors lock up due to a faulty measurement when using HFI?
I also didnāt fully understand yet if the HFI is only active till a specific rpm like it is with sensors or itās active all the time?
@Trampa @Deodand the question is inevitable, so Iāll be the monkey.
Can / will the Unity support HFI in future?
Hi Andy, HFI is only used to start up the motor. As soon as the rotor has some speed, BMFs are used to track the rotor (as usual). If you would get trouble, only at speeds below walking speed .You also hear the transition, The high frequency noise cuts out after transition.
@malJohann : Unity is a two battery side shunt design. Three shunts work best for HFI. Three phase shunts are king, three battery side shunts are also OK. @Deodand, correct me if I am wrong here. You designed the Unity.
@Gamer43: The VESC-Tool is OS and neither software, nor HW layouts are a fixed thing. VESC-Tool is not trying to compete, we try to build an awesome tool through collaboration. That is why I contacted Jeffrey and organized a meeting with Benjamin. If you are unhappy about things, github offers plenty of options to contribute. It can be code contribution or a qualified comment: https://github.com/vedderb/vesc_tool/issues
the never-ending storyā¦ i watched the movieā¦ didnāt like it muchā¦
but what I DO like is @Deodand and B. Vedder working together for the common good! If only @Trampa wasnāt the middle manā¦
Frank one more question, from Benjaminās video I understood that the HFI is limited to around 40A as the stator saturates. Does this mean that I can max pull 40A motor side when starting off and after the vesc doesnāt deliver more power? I worry that that isnāt enough if you start up on a steep hill or when your wheels locked in a mud hole or any other bad place.