Just get the latest one from the site. Beta will always say newer version if you use it on another fw last time i checked
Ffff board is 44 lbs, didnât want to haul it upstairs. Laptop might be getting a dusting off.
2 Likes
You only need to download the zip on your phone, install the correct apk and youâre done?
Again, release version, not beta
1 Like
Ah they have the apks up too nice.
Iâm vesc tool stupid coming from unity ui, thank you for the help.
I ran motor detect and input of the remote setup fine. What all needs changed after hitting can forward activate? Just motor params?
3 Likes
O boi here we go
So, foc wizard will put everything you need to get you rolling, but if you care about stats you need to manually go into motor config, additional info (from first menu) on the slave side and fix that shit.
I found that sometimes the wizard doesnât do battery values right either so do into current tab and triple check every value, then voltage tab for cutoffs. Switch back an forth on canbus until youâre sure theyâre the same.
Lastly, if you care about your ass go into the advanced tab and set fault stop time to 50ms (or anything lower than default really. Not too low that you wonât feel) and duty cycle CURRENT LIMIT START at 85%
Oh and foc switching frequency is nice at 30khz as well
Consider your unity as 2 completely separate devices that refuse to speak to each other except over canbus
4 Likes
Perfectly laid out. Thank you dude. I think I got everything squared now.
Round 2, here we go.
1 Like
Alright went very well for the most part. Still getting -99° motor temps though
I recall this being an issue a while back. Is it still?
This happened to me. The versions on the website didnât work. When I went to the play store and updated the app and then used the app to install fw, it fixed it
1 Like
Rubbish temp data means no temp sensor usually?
Yeah but theyâre sensored and temps were picked up fine previously by the unitys FW. I remember a few ppl saying the same thing. Weâll see if they chime in.
5.1 UNITY fw has no motor temp. Neither foc_openloop, I use it for discharging battery in metr app. Those 2 reasons why I stay on 23.46
1 Like
Any clue why this is? Seems like a silly thing not to have when the capability looks to be there
1 Like
Bug. I think it was fixed long time ago, but 5.2 has never arrived.
4 Likes
Donât know how my issue was fixed then. I just went through this and when I reinstalled fw through the updated app it fixed the issue.
I think Unity is enertion not Trampa
1 Like
something I noticed is that I could no longer set Lifepo4 when configuring batt cutoff, have to calculate and enter it manually.
FWIW, I definitely didnât feel 50ms. and I triggered multiple temp faults in a row. (dual focbox 1.7 canbus ) @Deodand was recommending higher to keep your focbox safe. @b264 recomending low 50ms to keep yourself safe.
3 Likes
Iâve started using 75ms personally
But 500ms is way too long, Iâve eaten asphalt a few times with that number.
âjust long enough to feel and protect FETs, but not long enough to knock you off balanceâ is the goal here, I think
5 Likes
Dumb question but I tried searching but couldnât find a simple answer. Is hfi automatically enabled? Iâm currently running newest firmware on 100D and couldnât see a hfi enable or disable option, just saw the tab in vesc tool (running from pc). Run in dual sensor less foc mode but will be dual sensored foc soon. Just asking bc I just re installed newest fw and re ran motor detection bc my sensor wiring wasnât fixed well⌠and to increase motor amps a little.
So all Iâm asking I guess is is hfi auto enabled and if so can I simply disable and run unsensored foc. Sorry for the diatribe.
No.
Itâs turned on in Motor_Settings > FOC > General > Sensor Mode