Howdy all, if you remember from the FW5.3 thread, there was some weird stuff going on with the foc wizard spitting out VERY different values than good ol FW5.2. Here’s my experience and log of what I’ve done to fix this. As of writing this first post, I’m in the middle of troubleshooting.
Here’s the issue:
After running the board near max duty cycle’ there would be frequent stutters and faults. Also, the motors made some strange noises on hard accel/hard decel. I don’t have that on video so you’re just going to have to trust me there
To start, here are the FOC values between FW5.2 and FW5.3 after running the FOC wizard on the same board.
Update #1, after manually entering the values in… nothing seemed to change. I’d like to blame it on this
value as I don’t know what to put there.
Rerunning motor detection with the old FOC wizard built into vt did nothing
Next up I’m gonna run VT3.0 foc wizard on FW5.3 to see what happens
nvm that didn’t change much of anything
For science I’m gonna test the beta for firmware 6.0, which is what comes after 5.3. Numbers work in strange ways…
The differences in R and L look correct. They are defined in a different way now and the L measurement is improved, so the difference you are seeing is expected.
@drdrs showed some logs of the duty cycle issue running a ZESC on 5.03 beta, but Vedder wasn’t sure why and there didn’t seem to be a resolution.
Yikes. 5.3 is completely unusable for me. Faults galore and my motors are making weird noises. I guess at that point, any solution I had in mind goes down the toilet and I go back to FW5.2. No 2nd uart
