I have just finished my board with 10s lipos ( 30amps 40 max 8000mah Zippy).
I’m using moded firmware from @Ackmaniac. I have adjusted the watt mode to 300. Went for a ride. All good but not a lot of power. Then changed it to 700 and my board after 2 seconds stopped responding.
Fuse is fine( vedder anti spark) but when I connect it to bldc tool there is no connection. Tried also re flashing boot loader but also no connection. I only get blue ligh let and the led next to it is red but very dim… nothing is flashing on startup as before. Have I burned my vesc ?
Flashing went fine, no errors and was using for a day moded bldc tool. I just had a chat with @Martinsp and after probing vesc with multimeter it looks like CAN chip is fried as my 3.3V line is shortened. Anyone in UK who fixes Vescs? Or at least can change a chip? My soldering is bad AF
The CAN transceiver only has 6 pins, its much easier than swapping a DRV. And its only a few bucks. If you get desparate give it a wack yourself. I can usually get away without adding any additional solder or flux when changing those.
Hi, any more info on this senario?
Mine is now intermittent. Blue light on VESC when I opened up enclosure then no connection with Vesc Tool.
Then randomly light changed to normal and remote worked.
So, now I have to turn the vesc on and off about 15 times for it to work correctly. What would cause this!!?
Did you flash the bootloader or update the firmware? Where did you get the vesc from? I suspect this is a hardware related issue not a software related one.
Nah, I changed some parameters within the Vesc Tool (I was playing it safe before so was advised on here to change some parameters). I then too a ride for a few miles and it was pulling great and totally fine. Then next day, turned it on an nothing. Then I opened it up and took pics. The turned of and on a few times to try to connect to vesc tool and failed. Then randomly started working. Rode it for a further 8 miles totally fine. Now it takes 10-15 goes at powering on.
I think it would be wise to start your own thread about this. This looks like a hardware issue. Start by measuring with the multimeter and go from there.