How difficult would it be to swap the microcontroller in a Convoy and run custom firmware?

In the past, Convoy lights used an ATtiny microcontroller that was relatively easy to flash with custom firmware. However, I recently saw here on BLF that Convoy now uses a different microcontroller that cannot be reflashed, but is cheap and readily available.

Assuming someone already has the necessary soldering skills and equipment, how difficult would it be to buy blank microcontrollers in bulk from China and develop our own firmware for Convoy lights, replacing the factory microcontroller?

Does anyone know which microcontroller Convoy currently uses in their buck and boost drivers? And what would be required to program and flash new firmware onto it?

1 Thank

Can’t be to hard.
But you have to doe some reveres engineering of the diver first.

This is all pure speculation but :
then maybe uses used wired Chinese SDK and programmer to flash a chip with a strange architecture.

don’t know how mush fun this is going to be.

I would say at this point why not make complete new open hardware version of the driver with a popular µC

1 Thank

Without a doubt, that would be the best option. The thing is, Convoy’s drivers are cheap and competent enough, I’d say. The only thing I’d really like to change is the UI.

Being able to have pre-flashed microcontrollers and simply swap them into the drivers would basically be the best of both worlds.

My hope is that the architecture isn’t too weird and that someone here already knows the ins and outs of it.

To swap in a different MCU, you’d need to do a few things…

  • Examine the driver to understand how it works, what each chip is, and what pins things are connected to.
  • Find a MCU in the same form factor with compatible features and pinouts.
  • Find a way to flash the new MCU. Without flashing pads on the driver, this can be tricky.
  • Remove the old MCU… which might be tricky if the circuit has components on both sides (when using a hot plate), or has little parts which could blow away (when using a hot-air station).
  • Write new firmware from scratch.
  • Find a way to test the firmware, ideally without having to unsolder and re-solder the MCU every time.
  • Put everything back together again.

People often find it easier to design and build a whole new driver circuit from scratch.

2 Thanks

That would definitely be the biggest pain. If we used the same MCU that Convoy uses, I’d have to throw away an MCU after every test. And even if I used one that could be reflashed, the thought of having to desolder everything for every single test is already discouraging.

Ideally, we’d have some kind of test PCB where we could develop and test the firmware without having to constantly solder and desolder components.

1 Thank

I like the idea of a test driver.
Something could probably be made with an SOIC 8 socket, such as this.
Ideally you would use the largest diameter driver to gain some real-estate.

1 Thank

You can reflash the microcontroller in current Convoy drivers: A tool to flash Sonix MCUs in recent Convoy drivers

But most drivers don’t have usable flashing pads

2 Thanks

It would be a lot simpler to just swap drivers. Swapping a controller is a lot more complex task, but kudos to you for willing to go thru all those troubles. I hope you get it working exactly as you want it. Keep us posted, It is an interesting project

You can use a PCB adapter for a new microcontroller like u/LoadsOfLumens did to mod 30mm 20.5A buck drivers with Anduril UI


L7 NV1010 is pretty good with it, custom Anduril UI is way better than default tail—on/off, side—click through 4mode, double click strobe

4 Thanks

GOAT! i knew someone must have already gone down this rabbit hole

Thanks! Take a look at this cilicagel’s work. He pretty much managed to figure it out.

1 Thank