No not really. The algorithms are quite different so things don’t translate very well in that way. What are you hoping to achieve?
1 Like
Still at 95% for the top one to be overly clear?
1 Like
yes, you almost always want the want the “maximum duty” to be 95.
the “duty cycle current limit start” is hat you want to set lower to enable gradual current limiting
4 Likes
Thanks. That’s what I thought it defaulted to but wanted to confirm before trying on the road again. Motors are responding normally to accel and braking again. Hopefully it was just me changing the wrong setting 
I will try again when the weather is cleared up.
6 Likes
thanks for all your help brother!
I was able to get HFI working acceptably on my board and unity!
I do have a few questions… as I understand if the HFI voltages should be identical from one motor to the next across the board… but one of my motors is a little funky and cogs a bit while the other motor is quite happy on lower voltage settings…
can I safely up the voltages on the cranky motor to get it to work properly and then apply the higher voltages needed to both motors?
and, is there a place in the fone app that I can run detection from? perhaps I don’t wish to go thru the wizard. is that the only way to just run motor detect without affecting any settings?
or should I just go back to the desktop tool…
thanks buddy!
I would use the lower voltages on one motor and the higher ones on the other one.
1 Like
hmmmmmmmmmmmmm
1 Like
I think he was referring to just not bothering to go through the testing procedure on the second motor and copying them over. I could be wrong though.
1 Like
Yeah… That’s where I got to when I decide to ask… I upped the voltages on the cranky offending motor and then switched to the other nice motor and upped the voltages to match…
I just thought I’d ask if this was acceptable, and the preferred method before i ventured further down this rabbit-hole… If you can run differing HFI voltages on different motors, on the same board was acceptable it would make tuning the board with the app so much simpler…
1 Like
hopefully this will upload… what you can see is the right wheel spinning up and the left wheel locked (unloaded) this causes a short spin out of the right motor till the left motor kicks in…
come to think about it, skating today I noticed the left (cranky motor) to only have a “hitch” or a cog (for a better word for it) in only one position on the stator, and I did notice a magnet slightly displaced last time I took this motor apart… could that slight magnet displacement cause the motor to loose HFI tracking in that position?
you can even see the left, topmost motor track backwards slightly just prior to it tracking straight.
just a slight jostle or nudge or hip-flick or tiny kick is enough to get HFI working on the cranky motor… am I on a fools errand adding voltage to this motor to smooth out HFI tracking?
Should the voltages then be transferred to the other motor so both motors HFI voltages are the same?
or should I just lower both motors voltage to the working motor’s HFI voltages and live with the hitch or cog in that one rotor position???
1 Like
Still useful for friends that never stood on a powered board tho!
1 Like
I’ve always just let them ride a CarbonGT with 800 cycles on the battery that kicks to ECO mode after 2 meters on a full charge
1 Like
That board sounds like a waste of space, also I dont carry a extra board with me for newbies to try 
4 Likes
This is what I meant.
HFI voltage should be the same for both motors, but it sounds like one of your motors might be a bit special. I really haven’t tried HFI on a huge range of motors and I don’t usually keep slightly broken motors around so it’s hard to know if that is the reason your motor is being funny. Sorry I am not more help!
3 Likes
I am getting this weird braking/HFI behavior on FW 5.02. I was previously on FW 4.00. I’m running HFI on a FSESC 4.20+ Dual with TB6355. Whenever braking, as soon as the tracking switches from sensorless to HFI there is a grinding sound and vibration throughout the board. The brakes are strong while decelerating until I get below the sensor less ERPM threshold and into HFI tracking then they suddenly become weak. The grinding only happens while HFI is on. The grinding increases intensity until the speed reaches around 1mph and then there is a jolt where the it goes away and braking gets super strong again.
Here is a video of me going down hill and slowing down at the same time.
You can hear clearly near the end of the video where the grinding goes away and suddenly breaking power returns.
Did you go through the whole setup process for HFI?
Yep, I used that exact video. My first time on FW 5.02 I just transferred the same HFI settings over from doing it the first time on FW 4.00 but just to be sure it wasn’t my old configs I reinstalled the FW and went through the whole HFI configuration again.
3 Likes
Adding this here as well.
1 Like
95% sure this is not FW related, this sounds like faulty hardware. I’ve had similar behavior with a damaged unity before.
3 Likes
Anyone running a unity with a VX1 on the newest version? Any issues?
I read about some issues previously. That may have been on the unity fw