Has anyone gotten this to work on flipsky 6.6 ?
The HFI algorithm we built operates withing the framework of the FOC algorithm cleanly.
Adapting it to BLDC would be pretty challenging, especially with things like changing pwm frequency depending on rpm of the motor which occurs during bldc operation. Probably would need to just build it again from ground up. Pretty sure BLDC isn’t using anything like HFI already.
I sent my mate @xsynatic my fsesc and his motor only clicks, when he clicks on the full brake button and when he is using HFI. No plot appears and nothing happens. Do you know something?
Just curious, isn’t a signal injected on BLDC sensorless to determinei the rotor position?
Pretty sure its more of a stutter/pulse to get any kind of BEMF, to determine position.
I’ve notice some discrepancies with motor detection between the old algorithm and the new one with the quicker and more accurate LR detection. The biggest discrepancy is the L value not being consistent or being very different from the old FW. The difference is significant enough to cause non-ideal operation of the motor with lost torque and severe cogging under load. This is all been with my own hardware so that could be a discrepancy in itself. Just curious if anyone has experienced something similar or my case is isolated.
You mean like this?
For me it can be up to a 10uH difference between FW3.62 and the latest FW. Motor then runs well under FW3.62 but not newest FW. As stated before, could also be hardware differences at play.
4.1 “HFI” sensor mode
Control Mode: Current Hyst Reverse With Brake
sensorless ERPM HFI: 3500
Max ERPM for direction switch: 870
Seems pretty smooth 
The high pitch sound does make it sounds like your board is ready to take off to the moon 
Seeing as I am accustomed to BLDC and actually don’t like the quietness of FOC, it’s unnerving to me when the HFI turns off and it’s silent as an owl
This HFI is really the only feature that could have caused me to begin using FOC…and the feature is very, very nice.
@Deodand Can’t wait for that in BLDC mode… is that planned?
Also I’d like to point out that this is the EXACT sound our commuter trains around here make when you’re a passenger.
I know 
But I asked again on purpose 
To be fair, even though there are advantages to BLDC, FOC is superior in principle. Pure sine wave is well sought after in many industries.
I’m literally having to dig through commits right now trying to figure out which one is actually 1.20
Why? Because I’m developing and need to validate against a previous known good and replicate exact details like firmware version for this test. But really,
it was a firmware & VESC-TOOL version that was literally released last September, and stable, it should be available for posterity and for the benefit of developer reference.
So annoying.
I’m just glad that nobody is pretending these coding practices are normal anymore. Oh wait.
This is the primary reason I was still using Ack 3.103 until yesterday. I could trust that it wasn’t going to chuck me off the skate due to some new bug I’m the first to discover.
But for me anyway, HFI changes everything. I need HFI, so 4.1 it is… for now…
It’s funny how we’re perfectly happy and satisfied with something until a new thing comes out then all of a sudden it’s not good enough 