The end of BLHeli_32 and impacts on X-cross ESCs

As quite a few use the X-cross at this stage, I thought it might be important to include this:

1 Like

Can confirm this is now affecting ESCs being purchased. Suppliers are putting dodgy old test firmware on the Flycolour Xcross ESCs that can not be programmed in BLHeli32.

If anyone gets stuck with one of these. Flycolor have an ā€˜offlineā€™ software for editing variables. Message them directly or try this link

https://drive.google.com/drive/folders/1c0qE1IEsP8rAEJi4HnhLdljo7l11t1vL?usp=sharing

1 Like

I too have now experienced the issue. My replacement to my blown x cross arrived today and I hadnā€™t seen peoples reports of issues but can confirm I cannot program it.

Iā€™ve sent you a message.

Thanks.

Hey Foiled1, do you end up replacing the firmware on the XCross? Would you mind giving a little more information about the process and whether you still have all the programming options as with BL Heli32
Thanks

Hey guys, try this link. I tested it and it all connects and programs fine (have tested the esc this morning and all seemed fine). Use at your own risk of courseā€¦

https://drive.google.com/drive/folders/1c0qE1IEsP8rAEJi4HnhLdljo7l11t1vL?usp=sharing

1 Like

I didnā€™t replace the firmware, Flycolor just provided an ā€˜offlineā€™ :wink: version of the BLHeli programming tool that happens to work with the old test firmware they are now putting on the esc. Flycolor made the call to do this instead of changing to a different firmware (such as AM32). I asked if they intended to change in future and whether this was a temporary workaround for them and they replied they have no intention of changing firmware.

2 Likes

The version you uploaded works fine with the ā€œprotoā€ version of blheli my latest hv3 arrived with. Thanks :grinning: