hey who stole “Stoner Ram” ???
easy enough just to depin the temp. sense wire from the plug and test it…
I had some wonky riding situations, disconnected the temp. wire and no mas problemos…
I may try FW5.02 when it comes out of beta… or may not… everything runs purrrfect now…
Alright, I may try this then. So i just yank it out, or cut it clean? And I assume I can re-attach if I’d like thereafter if needed?
Also trying to find a schematic to determine temp sensor wire for these Haggy Motors -
De-pin the temperature sensor pin from the JST connector… pull “gently” up on the little plastic tab and the female pin will slide out of the JST… insulate it from shorting anything, and you can always just slide the pin back in the connector
Most of the time the Temp. wire is adjacent to the 5v, find a pin out of your VESC and it will show the location…
You’re getting overtemp motor at 43c?? What are your values for
motor temperature cutoff start
motor temperature cutoff end
Acceleration temperature decrease.
if they’re anywhere near defaults. ( 80c - 100c - 15% ).
then you’re definitely getting spurious readings to have it say 43c in the fault and not be anywhere close to those settings.
but since you have metr you should be able to upload a record of you ride and share the url with us. you can see the noisy temp readings on the temperature graph.
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
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.
Thanks, I will give this a go tomorrow. Anything else i should be weary of while running without these sensors?
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.
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.
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
Thanks for all the help on this guys, and @fessyfoo for metr tips and logs too
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
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…
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.
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.
Just pull that temp wire out of the jst plug till the beta fw is an actual release and hopefully really fix that issue?
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”
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
