Is it always doing that or only from time to time? You can also go straight to the App config and do the calibration there. It’s only the master unit that needs the info anyway.
I’ll try it when I get home.
How would you set the slave then after I config the master app?
Nothing required. The Master would only need to be set to : Multiple VESCs Over CAN >> True
Will report back as soon as I do this. Thanks!
For PPM: App settings general: APP to Use >>PPM and UART
Go to PPM APP and select Multiple VESCs Over CAN >> True
Do the PPM Mapping, apply changes and write App config to VESC.
I figure it’s like inception. If I say stable apis facing third parties can exist enough times, maybe everyone will start believing it. 
I wish you all the lick in the world
.
Do I understand this correctly from a pratical point of view that if the sensors of my motor fail due to whatever reason I will barely notice, since that is when HFI will kick in? Before HFI what would have happened if the sensors failed?
How do those clicks look like in the app?
No reason to be confused, I guess. If Benjamin wants to speak to you or somebody else, he will do so, I think.
MOTOR CFG -> FOC -> General -> Sensor Mode
HFI will not kick in automatically. You have to pick the mode you want.
Odd thing to wish someone. what if he doesn’t want all the lick?
Thanks a lot!
Yeah, I meant luck, long frikkin day 
I retried to do the input wizard. It worked this time
Weird.
So lets me get this straight. HFI needs to activated on sensors but NOT on sensorless?
This is a great upgrade, thank you so much to all involved in it!!
HFI is only needed when you do not have working sensors. You either use your sensors or you can use HFI.
Dude. can you share the set up on your board? 10s or 12s? what motors? what ESC? do you know what your amp settings were at?
on his video Vedder mentions a possible issue with skateboards at high current… yada yada, all that shit is over my head. but I want to try this out as I happen to have a motor with a bad sensor. the annoying part is i have to switch escs between the boards, but this looks promising and I think it will be worth it.
Jeffrey and Benjamin will try interact a lot more in future. We will probably see support for ESC designs using a shared processors for two ESCs. If you own a Unity for example, support for it is probably happening in a overlookable time frame. This way such devices get a future and do not suffer from lack of software updates, making them obsolete sooner than later. The integration of single processor support also allows new and potentially interesting HW designs.
I read through it all and this is what I care about most. Long live the Unity and praise be to Vedder and Jeffery! Very excited for what 2020 has to bring!
Running your motors at the stator saturation point (~80amps for me) with HFI could be a problem supposedly, but I didn’t test much.
I was running 60 motor amps and 40 battery amps per VESC with no issues.