tenka. (and before anyone rants, yeah IK the tenka acts weird for a vesc)
if you can give me a hand getting the sensors connected int he right order, or getting HFI working, or getting sensorless FOC working… honestly any of these seem like good options but I haven’t been able to figure them out on my own, the hall sensors really don’t wanna work for me (bad hall detection literally every time)
There’s nothing to it really, just set the motors to FOC and “sensorless” under the FOC tab. If you want smooth start you can search for “HFI” on the forum here to see how to tune it.
I’ll try that again but I got terrible results last time.
Edit: after watching Jeff’s video I now understand why. I have to tune this. Alrighty.
do you have any help with getting HFI working? I’m following all of the steps and threads I’m finding but things only look kinda right for one motor, the brakes are still super weak.
got RT data on motor 2, it looks very different to motor 1. straight vertical lines instead of dots forming curves. solder joints look ok
Have you tried swapping the motors between the ESC sides? That would help determine if you have a faulty motor, or a faulty ESC side.
When swapping motors, both start acting weird, though the stuttering is happening on the same VESC side regardless of the motor.
Are you certain something here is faulty? That sounds like my worst possible outcome. I really want to hold onto the hope that the correct settings can fix this.
I’ve also tried swapping phase wires around on the MR60 plugs.
This shouldn’t do anything other than make you run detection again, which you should do I you’re swapping sides and testing
Yes of course, I run detection religiously after any motor related physical changes
Well, HFI is very hit or miss, especially on older hardware.
Remember that in sensorless mode it’s expected that the motors might spaz out / refuse to spin before the ESC can detect their position correctly. I.e,. need to push to start, and then apply throttle and test.
Anyway, if one side of the ESC is giving you trouble, then it’s pretty likely that it’s faulty hardware. Unless you aren’t programming the sides identically or something. After watching your video, I’m pretty sure that’s an ESC issue. Are there any reported faults by any chance? Go to the terminal tab in vesc tool and type in “faults” after you reproduce that stuttering issue.
Nothing besides a weirdly usual bunch of faults after the auto-shutdown timeout (set to 30M). But that also happens on my other board with a different VESC. No faults while doing the tests or riding it. (Metr unity)
Would the tenka or the evolve gt 5055 motors be the "older hardware? (AFAICT same motors they used in the GTX and GTR)
I never got the Racerstar 5065 motors to work worth a fuck on HFI.
Try the ld_lq_diff measurement (measure_ind 0.2 in terminal) like in the video. What do you get? If it’s less than 10% of total inductance, just forget about HFI on those motors.
15% to 25% is good, the higher, the better.
I get about 25%. honestly I’m starting to think the tenka is being fucked, which probably sucks a lot for me
25% should be really good. My experience with those motors on HFI has been really bad though with multiple motors and multiple controllers.
Try the same controller on other motors to see which detail is causing the hiccups.
I gotta get the VESC to co-operate first, I reflashed stock FW and it started behaving worse after detection. sudden halting, one side not responding anymore, even louder noised when there shouldn’t be,…
and this is the 2n’d tenka after the first one blew while braking downhill. I’m so inclined to just think MassiveStator shipped me garbage twice in a row.
I’ll test with new motors but my hopes are pretty low for this VESC at this point.
Change the controller and see what happens leaving everything else the same
hmm if only I had a spare VESC I could trust.
I’ve got an FSESC 6.6 that refuses to see it’s internal CANBUS connection even after contacting them for support
I’ve got another FSESC 6.6 plus that died on me mid-ride, not inclined to trust that one.
I’ve got a Boundmotor ESC that works fine, but the remote battery puffed up and when I tried to replace it, I went through 3 remote batteries and couldn’t get any of them to charge off of USB (and the remote wouldn’t turn on) and idk what I fucked up there.
Oh, I guess I could rip the DV6 out of my current main ride. I was planning to try that as a last resort, but my first resorts have all turned to dust before my eyes.
the Boundmotor VESC doesn’t have a UART or PPM plug, it uses an integrated receiver.
you’re right though I can just use it for testing and use keyb control
it’s not sold by Boundmotor anymore, I’ll pair a photo to this post in a few minutes, but the only proof I have that it’s a VESC is that it works flawlessly with VESCtool, and the remote can be mapped and the curve adjusted and everything. based on 4.12.
(edited a few posts because I confused 2 brands)