Lift the correct plastic tab with like an exacto blade and the female pin will easily pull out…
Then you can simply push it back in again when you wish to use it again
2 Likes
So here is the graph and motor temp marked right before a fault at 18:53
Defaults -
Motor Temp Cutoff Start- 85c
Motor Temp Cutoff End- 100c
Acceleration temperature decrease- 15%
looks like wild motor temps to me. not 100% sure of the scale, but I think it looks worse than mine above, which looks worse than other people’s it should ideally move very smoothly. no big jumps in temp.
Looks to me like you have the issue.
1 Like
Thanks, I will give this a go tomorrow. Anything else i should be weary of while running without these sensors?
1 Like
You’re planning on running with all your sensors except temperature, right?
ride it like you stole it, hand check the motor temps occasionally until you’re sure you’re not cooking the motors.
2 Likes
worth noting you can “upload” your metr record and share the link on it’s own line and it will get embedded.
Also worth noting that there’s a little split icon you can use to get both motor temps if you were connected via CAN or have a unity.
This is a record from a ride on a second board with the exact same setup as the one I have problems with above. motors/vesc/battery all the same. you can see the temperatures are much smoother.
even in the noisy spots it’s not really jumping by more than a degree. that’s more like what yoyu wnat to see.
1 Like
So I’ve got em pulled out and heat shrinked
Sanity check me just in case, but metr is no longer displaying motor temp so pretty sure I got it right.
Diagram
Right
Left
Thanks for all the help on this guys, and @fessyfoo for metr tips and logs too
2 Likes
and… i triggered it one more time. because I haven’t gotten around to a better fix. and the 120c cutoff isn’t “safe” enough.
would love a disable temp sensor boolean option in vesc tool the way focbox ui has.
still fw3.65
1 Like
If you’re daring FW5.02 [beta] is supposed to have addressed the temp. Sensor filtering
Thank you.
yes I am aware.
that is part of the question. been waiting for 5.02 to be more beta’d.
but also I kinda want to finish the journey in this thread and see if I can eliminate some of the actual noise somehow hardware wise. though I’ve just stalled out on it, thinking about my builds instead.
Jeff and I had some discussions about the neg, wire and the temp. wire running closer together, and away from the phase wires… there was talk about twisting those pairs or a shield…
and also @DerelictRobot had some sort of a setting kludge that he surmised would trick the VESC…
I just de-pinned mine till 5.02 is a final…
1 Like
yeah. Jeff commented in the known bad versions thread and posted a picture of the issue.
I should do this until either I do 5.02 or actually mess with the shielding or routing of the wires.
1 Like
Caught this from a guy in the lacroix owners fb group. these are the wildest temp swings I’ve seen yet.
his metr logs https://metr.at/r/2Xzc4
it’s interesting htat both motors appear to go crazy at the same time. this is on a unity/nazare.
2 Likes
Just pull that temp wire out of the jst plug till the beta fw is an actual release and hopefully really fix that issue?
1 Like
yes. that’s the mechanical “switch” … which I will probably do.
unity fw has a boolean setting to just disable motor temp throttling which would be easy peazy. sadly this is lost in it’s transition to bldc/vesc fw5.1
if I had that i’d have “done it already”
1 Like
This is obviously not how temp changes. But why such swings? Bad sensors? EMI? Bad wire connection? Anyway feels scary with such unreliable measurements to let VESC cut off power based on temp
3 Likes
and funky temp filtering
1 Like
yeah. EMI is what everyone is saying.
but that guy with the super wild swings on the unity. that’s crazy. even for EMI
I was excited to get motors with temp sensors but reading all of the triggered faults lets me think i unplug the temp cable.
3 Likes
This doesn’t happen to every setup. probably not even the majority.
1 Like