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…
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
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
Hy @All !!
Im also running into the issue with the over temp readings
Im running a dual setup with 2 focboxes and 2 aps6374s motors
Im getting the temp error also when i lift my board up and let the wheels spin in tge air so without lot of wheigt on the board
Regarding my xmatic readings the temp jumps from 54 up to 75 and then over and over till the error pops up
The motors are not very hot i can touch them with ease
Now before im going to remove the temp wire i wanna ask if a firmware update could solve this?
And my next question is which firmware can i upgrade my focboxes too without damaging them
Im runnin the ackmaniac tool btw
Thx very much guys
That’s some wild temp swings. possiboly more than noise. possibly broken cables.
Wild temperature noise should likely be addressed at hardware maybe some of these solutions.
fix broken wires.
better routing of sensor wires. ( avoid unpaired routes to avoid receiving emf. )
twisting of phase wires to reduce emf.
shielding the sensor wires from the phase wires.
as a workaround you can depin the temperature sensor wire.
Newer 5.02 beta firmware (actually 5.01 but that has other issues) has increased software low pass filtering which will take care of some noise but won’t a fix for everything.
so short answer to your specific question. It might help.
@Sharky I’ve heard of people taking shielded HDMI cables, and just using that for the sensor wires. Could also use a shielded USB cable but they only have 4 conductors and you need 6 for sensors + temp.
Is it possible to have the vesc ignore the temperature as a security (i.e faulting over it) but still displaying it?
I’ve been running motors without temp sensor ever since i started, now i have new motors with it but don’t want to risk a software based fault. Of course its there for a reason but i know my motors and have yet to bring them to a critical state. I’m just interested in the value, but not the safety aspect as stupid as it may sound.