Did 8 ish miles and walked away unscathed.
4 Likes
You must have had a good wifi connection
5 Likes
True story at was at work and doing this underneath the wireless AP with the carbon fiber lids off and wearing a tin foil hat for maximum reception
2 Likes
sHFI woks fine here , vesc6 trampa + freerchobby motors
had issues whith sensors , with sHFI no sensor needed now ! thx
2 Likes
On my sHFI test board with Trampa 6 ESCs and torqueboard motors, I forget that I donât have the sensor cables plugged in. Itâs really good. With a full face on I canât even hear the click when the motors stop from a dead start.
2 Likes
I have some sk3âs with broken sensors, maybe I will try it out on them. I could use either TB6 or focbox, wonder which will work lol
1 Like
I would put my money on TB6 playing better with sHFI
1 Like
Same, theyâve been sitting since I bought them lol, probably gonna try this on the honsra build
2 Likes
i found SHFI would run 1 if not both motor backwards too much to be near cars
and on fw6.0 my vesc on canbus would cutout at random (might have been a faultcode but canât check without a logger) and being thrown off at 35mph hurts lol
That might have to do with the motors and the flux linkage and how well the motors are dialled in.
For example: We tested with the big 63100 motors a while back because we wanted to help a customer using this motor. The air gap (magnets to stator) is pretty big and the magnets might have less strength as well. In consequence the flux linkage is a lot lower then on the Trampa motors or the Hoyt St. and some others motors with a strong flux linkage. This has an impact on the sHFI behaviour.
I guess all motors with big rotors and without support bearing in the front will probably need a bigger air gap to avoid magnets touching the stator and in consequence the sHFI capabilities might suffer a bit.
At least that is what we have seen so far. The Ld-Lq difference and the flux linkage value are good indicators on sHFI capabilities. Higher values = better.
4 Likes
You should try lowering the âHFI Gainâ parameter from 0.300 to 0.100 . This 100% fixed 1 of the motors occasionally running in reverse for me on sHFI.
3 Likes
I have a Unity I am running 23.64 on.
Today I tried to flash the 6.0 firmware using my android phone via Bluetooth and it does not really go anywhere.
Right away it says bootloader timed out.
I have been able to go back and forth between 23.64 and 5.1 or 5.2 before just using my phone.
I know.
I like to live dangerouslyâŚ
I am bummed because I was wanting to try running 5.2 and now i have to open the enclosure like a caveman.
You try loading bootloader first with generic then 6.0?
1 Like
No.
Updating from Android seems to be broken, bust out the PC.
3 Likes
Does PC mean cable? No way to do wireless right???
Dunno, you can try Bluetooth to a PC first.
1 Like
Tcp/ip I suppose
1 Like
But I am running 23.64. I donât know if that works or not .
I could not figure out how to get TCP connected earlier today.
But I had never done it before, so not sure if I was doing it right.
I wonder if TCP only work if you are already running some sort of Vesc firmware.
First question is your unity running the OE ble? Cause that may be your issue to start. The later apps are very wonky on the original Bluetooth. Thereâs a revised one that the xenith has and I think the massive stator ones have now.
2 Likes