I am by far not an expert on maker X escs but this seams like a bad idea. Back when 5.xx fw came out this setting was set default to 100% and caused alot of bad cutouts at high speed. Be very careful with this…maybe someone else can correct me if i am wrong.
I got an injury 3 years ago from a stormcore that had this setting at 100% and my ankle is still not fully recovered.
Noted! I’ll change it back to 85% and do more testing
Also good data point: Metr still won’t fully sync up with both esc’s. Wondering if the latest Metr firmware is partially the cause of the weird behavior… I need to check if the termination resistor needs to be set or something… My Megan also just showed up today, so I may pull the Metr out completely and run the wiring for the Megan to be mounted this long weekend.
Interestingly, when I had the setting set to 100% I couldn’t get the motors to lose sync (right-to-left) freewheeling. After programming 85% again (individually programming per side with a direct cable connection, not using CAN forwarding,) I got them to lose sync twice on the bench. The only other thing I haven’t tested is a power cycle between programming and testing. Sitting on the board and playing around with acceleration and braking, at ±90A phase, ±80A battery, and 135A absolute max per ESC, it’s still ever so slightly unpredictable; unsure if it’s a throttle scaling issue or a CANBUS comms problem, but something weird is happening. Tomorrow I’ll bump braking down to 80A (my wheels can lock up and slide at 90A and 80A doesn’t have that problem) and wrap extra padding all over and go for a test ride. I am still suspicious of the fact that my Metr can’t communicate properly to one of the two ESC’s any more and had zero problems the first day I set it up; I don’t know if that’s an issue with the Metr or an issue with the D100S, but here’s a data point nonetheless.
Raise this to 350 or 400, whatever the max allowable figure is, VESC overshoots current limits like nobodies business, and the only function of this setting is to throw a fault.
I was getting faults at 350 I am running 400 without faults now
Same for me. Actually I got some at 405-410A. Setting traction control OFF made them to disappear.
i think the general consensus is that tc still sucks
The risk is if both are connected via CAN and you supply power to one but not the other.
MakerX refuses to fix this issue.
so both have to be powered on at the same time. that’s what i thought but then saw that
Yes. Both at the same time.
No they do not need to be powered on at the same time. The risk is only when you initially plug them in.
welp now i need someone to confirm one or the other. also while i’m at it, they just have to be connected via the can h and l, not also the 5v and gnd for awd right?
I use 2 buttons. It’s nice to have an led indication of the esc’s being on. There’s the off chance using one button that only one esc will come on and you’ll be stuck trying to turn them on/off in alternating states.
i didn’t think that was possible but good to know. is just your can h and l connected together?
Yep, and I connected the gnd of one esc to the shield
how exactly does that look cause imma have to do that too
@YUTW123 I found hardware configurations for some of your ESCs in bldg.git repository, but DV4s does not seem to be present among them. Can you please provide missing files?
When I have time, I want to do some experiments and maybe work on custom firmware for inline skates, where only one motor at a time is engaged (for the wheel that has ground contact).
they’re lazy assholes who wont host it themselves. I have it publicly hosted
somewhere further up in the thread they dropped a zip file with the source, this is pulled directly from there
