Issues using a different VESC #68
Replies: 2 comments 2 replies
-
Hi @alimohammadhadi - unfortunately we only support VESCs with HW version 4.12 and don't have any experience with using VESC 75/300. I have looked around a little bit and haven't been able to find a 'servoout.bin' file that matches your hardware version. In fact, does the VESC 75/300 even have a physical output for controlling a servo motor? I agree that it would be very risky to upload the HW version 4.12 'servoout.bin' to your VESC. The only advice I can give is to instead buy the VESC listed in our bill of materials, sorry that I don't have a better answer. |
Beta Was this translation helpful? Give feedback.
-
Hello, Do you know if a VESC 4.20 would make it? It is very difficult to find at a reasonable price the 4.12 version but we can more easily find the 4.2 one. Thank you for your answer. Best regards, |
Beta Was this translation helpful? Give feedback.
-
Hello everyone.
I am using a VESC 75/300 with 5.2 firmware preinstalled. I used windows based VESC tools and easily tuned the PID for the motor. The Windows PC was successfully able to run the motor. The firmware was the default file and there is no custom file with "servoout.bin".
However, now that I am in Linux, I can't run BLDC tools because of the version mismatch. I thought that it wouldn't be a problem because I have already configured the VESC in windows but I get this error:
terminate called after throwing an instance of 'serial::SerialException'
what(): SerialException device reports readiness to write but returned no data
What I do not understand is that BLDC Tools GitHub provides the file "tool/firmwares/hw_410_411_412/VESC_servoout.bin." which may not be compatible with my VESC. Should I somehow force this file to my VESC even if it can potentially damage it?
Does anyone know how to resolve these problems that arise due to different VESC or hardware?
Beta Was this translation helpful? Give feedback.
All reactions