Hi first time for me to write a post here. I´m really have to say thank all off you and especially vedder for this great work.
I´m stuck a bit and wonder if the answer to my question is so simple as I think it is and I´m the stupid one... please do not blame me.
Hi,
I've two VESC boards and I'm trying to update the firmware, they both report as running fw3.38 and hw4.10 (though have 4.12 on the board...) in the VESC tool (0.95).
I can connect, it says the firmware is too old and to update it. I go to the firmware page, select VESC_default.bin then click upload, it completes, throws the COM error as expected and after 30 seconds I cycle the power. It still says it's running 3.38 and can only connect in limited mode.
Has anyone tried such configuration?
Having a Nucleo F302 board to use as controller for prototype, would be nice is there is a F302 version exists somewhere.
Failed to found it here, that's the reason of this topic.
Thanks a lot.
i would like to see a vesc compatible board with a single microcontroller (maybe requiring a faster processor or package with more IO) but able to drive 2,4,6,8 motor drivers for use in multirotor drones etc
I'm reading the servo signal input routines in "servo_dec.c", and if my reading is correct, some preparations are in place to support multiple servo inputs, while in fact only one is supported. Right?
Just been updating my vescs on my carver for my son. Everything was going well. I was just fiddling with the rmp limits and throttle curves. So all set up of the dual vescs was ok. Now i am getting a message when i try to connect to the vesc saying cant detect firmware.
Help!!
@frank
Hello
Did anyone use Keil IDE and AMDK ARM compiler to build the VESC project?
Thanks
Hi, i have vesc from hobbyking hw. 4.12
When i downloaded vesc tool i must flash new fw (3.38)
After flash my vesc in vesc tool show fw:4.10 and i cant complete motor wizard. In motor detection i have: detection failed and motor is dead.
After this i write faults in terminal, this is output:
Hello,
I have problem wit sorting out how CAN Bus is working in VESC. I'm trying to controll current and brake current in both VESCs connected with CAN magistral.
Master (device with connected receiver) VESC Tool Setup looks like this:
Slave VESC Tool Setup looks like this:
Hello,
If I send a PWM signal of 700 microseconds pulse length to the VESC, the VESC tool shows a length of 1000 microseconds. If I send 1700 microseconds, it shows 2000 microseconds. Is this a known bug?
Can anybody reproduce this? Using a FOCBOX with FW 3.38 and the newest VESC tool.
Uwe
