Hey @shaman, just wanted to say I have successfully assembled, flashed and run a full config on my first CheapFOCER2 v0.9. Outstanding work, thanks a lot! However, the test has been on a regular turnigy SK3 while waiting for a PEI scooter 800W 6" hub, so I’m also interested in the onewheel specific tweaks that @doomy is after.
I had to scavenge an IMU from a breakout board because of the shortage of that chip everywhere, but hey, if it works, it ain’t stupid!
Hello all,
First, Thank you very much @shaman all the other contributors for your contributions.
I ordered 5 copies of the V 1 (JLCPCB has the DR8301 back in stock), received them, Followed the insctructions. But when I power them nothing happens and they reach the current limit of 100mA. I flashed the firmware and it looked like everything was working fine.
I have no idea what the problem could. When I power it using the st-link communication, the fault LED blinks.
The VESC Tool detects when it’s powered using the ST-link.
What might be the problem (Here are a few opictures of the board, please forgive my poor soldering skills)?
Is there a way of getting the error ?
The VESC tool tels me that the firmware is old, Can I update it using the VESC tool ?
PS: Sorry if this is the wrong place to post, please tell me where to do so if that’s the case.
I reposted the text with pictures since I couldn’t edit the older one.
Nope…nope…nope…no forgiveness from me.
I urge you to get a better soldering iron, better solder, lots more flux, and to redo all the connections. It looks like at least one of the FET pins actually isn’t soldered and most of the high power connections need work.
Until then we can’t even begin to work with you to sort out any other possible issues.
If ot does not turn on at all i would guess its the 22uH coil if you soldered it yourself. Otherwise probably the DRV. Did you do the diode test on the input?
Thank you for your reply.
It doesn’t turn on because the power supply activates the current limiting protection, (110 mA), which means the problem is why is it reaching 100 mA.
Which diode test ? If it’s the orientation, I checked, it is oriented correctly.
The DRV was soldered by JLCPCB, so I guess that’s shouldn’t be problem ?
I noticed that if I test the continuity between the two poles of c39 I get a bip ! I will investigate that also.
So its probably a shortcut somewhere before the buck converter in the drv. There is a simple test you can do on the pos neg pins with a multimeter diode tester. Its noted in the first post of this thread.
Shoot, I didn’t realize there were different firmware versions for HW v0.9 and v1.0. On my v0.9 CFOC2’s I’m running Firmware 5.10 (marked as 5.01 in the distribution from your Github repository, but shows up as 5.10 in Vesc_tool).
Which version number should I be using on the v1.0 hardware?
Also, can I save a configuration from my v0.9 CFOC2’s and use it on the V1.0 boards?
They should be if you use the same vesc tool version. I had some trouble (the motor started suddenly) when transferring the app config to vesc tool 3.0. so better redo the whole config. Recently i also did the resistor upgrade on a few 0.9 controllers but when flashing the v1.0 firmware trough vesc tool they did still show the old one after a reboot. I had to reflash the generic bootloader and then flash the new firmware.
Not right now. I thought about doing another group buy, but i would have to up the prices. Jlcpcb is now around 35% more expensive. The good news is that they have the drv8301 chip in stock again.