Graphene LiPo’s, 6374 192kV SK3’s.
2 Likes
This values is to high. And with 150 Battery A you should set higher absolute.
My suggestion if you have big motors is to set 80 motor A, 140 battery A, 220 absolute.
Also i think your battery regen is way to high and might damage your battery?
Dont forget to activate thermal throttle with this extremely high settings for a Unity or normal motors…
3 Likes
Max charge rate for these batteries is 10C, so I’ll set that setting to 60A.
Also, absolute current doesn’t go higher than 200A.
Got same error’s just from starting up board. Can give logs if useful.
3xABS_OVER_CURRENT
2xDRV
Running same settings from 23.46 on the 5.0
-
- 80 amps on motor. +80 and -32 amps on batt. Don’t know why but I think it’s because I have the setting hyst reverse on.
This sounds like you didn’t apply a config or something? What do you mean starting up board?
Tried hifi on older pair of hummies (the small ones), with hope that it’d help with the sensorless startup, they meassure in at around 70uH, tried fiddling around with settings but didint get it running properly. Maybe I’m to conservative with the voltage, followed the video and curves seemed to track pretty well but no cigar
2 Likes
Installed latest FW dated 2020-04-04 last night and set it up. Had a fair amount more cogging on HFI this morning with the same voltage settings.
It was basically not much help and the slightest incline would see my motor just rocking back and forth.
The last good experience I’ve had with HFI was based on the FW labeled 2020-03-22-v2 that I had installed until last night.
1 Like
Just noticed, I can’t connect to the second VESC ID on Unity, whether CAN is green or not, it either gives an error, or just connects to the first VESC ID.
It detected both motors just fine last night though.
is your motor -> FOC -> Advanced -> Observer gain at minimum duty set to 30 instead of 5 by any chance?
3 Likes
Can’t check, because I reverted to the FW 5.0 2020-03-22-v2 and everything is fine again.
With the latest FW I couldn’t connect to VESC ID 2 to fine tune anything.
1 Like
We have the versioning working for beta releases now so we won’t have this whole date version confusion hopefully. But I’ll look into this. Connecting to motor 2 for me has not been a problem.
8 Likes
Strange, because no matter the VESC ID / CAN button combination, I couldn’t connect to VESC 2 (IDs were 110 and 111 in this case).
By “everything is fine again”, I mean I can connect to VESC 2 (with CAN selected) and HFI isn’t cogging like with the FW 5.0 2020-04-04.
Just some more data, cogging was noticeably absent today, so definitely something up with the latest FW @Deodand.
Not sure if metr Pro recordings help, but this one was with the new FW and cogging at startup with HFI.
…and this one was this morning on the old FW and no cogging at startup with HFI. Same settings on current and voltage.
2 Likes
just reporting in that im up to ~100 miles of abuse now and not had any problems yet 
1 Like
Nice ! Thanks for reporting !
Could you specify what beta version you’re running ?
1 Like
the 22/03 one
2 Likes
Sorry for the late reply wanted to investigate before answering.
I wasn’t really configuring anything.
3xABS_OVER_CURRENT
This one happend only 1 time (one for each motor and then a split second a second one for motor 1)
Weirds is that It was before doing a ride so no actual high currents. Maybe from going in reverse and then slamming forward throttle very briefly?
2xDRV
Again this is one for each DVR, so only 1 time. This was well before doing the ride. No idea here. It also said ‘No DVR8301 faults’ at the bottom
Anyhow. Today I rode with the same config and I wasn’t able to recreate any error’s
Best version yet, I’ve gone back and forth between that and newer versions, but for my Unity this is the one so far.
1 Like
New version is up now. The firmware can now affectionately be called " BETA 3" Thanks @Pimousse!
A good amount of bugfixes in this version, give it a go if you have some time. Thanks!
11 Likes
how do we get this? just download new tool from git and flash firmware? i will try update tomorow 
1 Like