As soon as I get some free time, I’ll ask vedder about how I can implement this. If VESC 6.0 still hasn’t been released in the next month or two, I’ll figure it out and keep you guys updated!
Can’t we just use the pin in the hall sensor plug? I mean it literally says it is for motor temp measurements 
2 Likes
So - how is it going for you?
Did you come up how to add external temp sensor to a vesc?
Or are you gonna wait for vesc 6 then 
That’s exactly what I plan on testing!
I haven’t gotten time yet. I’ll probably tackle this during spring break. I’ll keep you guys updated.
3 Likes
Any luck with adding the temp sensor?
I implemented the motor Temps sensor check once for Duffman in the firmware but the tests were not successful. If anybody has a temp sensor wired in the same configuration as the PCB temp sensor (same resistors) then I am happy to help with the software. It’s not hard to implement temp cutoffs in that case. But I don’t have temp sensors installed. Another cool feature would be to add another temp sensor to the slave vesc which checks the battery temperature. But no cutoff is needed there because these Temps will never be a issue as long as the battery isn’t undersised for the system. So it only would be for interest.
OH and the motor Temperatur isn’t added to the actual 2.18 firmware. It’s only avaliable in the bldc-tool but does nothing in the firmware.
How is it going with temp-sensor “inplementations”. 2.18 is still the actual Firmware,… So will the VESC 4 Firmware actually be further developed, probably not cause of the VESC6. So it would be up to some of you coding-freaks out there to finish this work, ahh ? ,-)
The trampa motors have a built in temp sensor. So surely someone has these and version 4 vescs.
It would be really cool if you can get this to work with your firmware. I wonder if it will work on the new 3.1 firmware?
As to the people who asked what you need to hook one up? A 10k ohm thermistor. From the temp pin in the motor angle sensor set, - thermistor - back to ground.
But that does not mean that it is supported by the VESC.
what ? a new FW, is it just for VESC 6 or also for VESC 4 ?
greets
Gernot
Do you need anything else? how is that hooked up, since theres only 2 pins?
I don’t think so, one leg goes to the sensor pin on the vesc and the other leg to ground. Simple.
I have trampa motors, HW 4.12 and FW 3.26, the motor temperature realtime data is working and motor temp cutoff should work, too but I never got the motors that hot.
So you have a VESC 6, right ? Semms the motor temp is implemented then in the new Firmwares.
what maximum Watts or Amps*Volts are you using on the Motor ?
No, I have dual V4.12 with the new 3.26 firmware and the new VESC tool instead of BLDC tool. Additional to VESC 6 Vedder programmed new firmware for the old hardware 4.xx, too in combination with VESC tool. I’m a beta tester but the new firmware and VESC tool should be public soon.
Yes, but FW 2.18 and BLDC tool can’t deal with motor temp sensor, but FW 3.26 can do it. In VESC tool you can monitor realtime data of mosfet temp & motor temp, it’s great! Here a screenshot, it’s T Motor 
On my MTB I run my motors in FOC and 45A motor max each, just for safety but I also gonna try 50-60A (the motors are rated 60A) and see if there is a difference but it’s still very powerful. I found out that motors with hall sensors need FOC for proper startup, The new firmware has a lot of improvements regarding FOC.
2 Likes
Whoo, I’m really looking forward to the release, can’t wait to see the functions of the new tool.
one Question in advance: does it have a “Watt-controll” like @Ackmaniac 's BLDC-Tool and the option of adding cruise controll to a RC-> PPM control like (GT2B-receiver)??
greets Notger
There is no Watt control mode but adjustable throttle curve. There are also improvements in FOC. I doubt cruise control is possible like in FW 2.54 but I’m sure @Ackmaniac will work on a new mod once FW 3.26 is public. I hope so because his app is not working with the new FW and V4.12
The app works with it, but only for like 5 minutes. Then it doesn’t work anymore (could be 5 min or after a restart). just thought the UART connections are fried because of a broken Bluetooth module. But when you flash the firmware back to 2.54 it works again. So it must be software related. But at the moment it only is possible to show the reltimedata.
Hey Ackmaniac, love your app, had it running a couple of days with FW 2.54 and 2.18. With FW 3.26 the app connects to the HM-10 but the realtime data values stay zero. After FW downgrade it worked again as you said. I run FOC with FW 3.26 now and won’t downgrade again so I’m looking forward to use your app in the future because it’s great, thumbs up!
I’m assuming vedder has changed the firmware quite a bit. Just as started putting together the 2.18 firmware in my mind.
Is there any way I can get my hands on this firmware? Need to update my app asap for this firmware.
As far as I know it should be released soon.