As quite a few use the X-cross at this stage, I thought it might be important to include this:
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
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
I didnāt replace the firmware, Flycolor just provided an āofflineā 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.
The version you uploaded works fine with the āprotoā version of blheli my latest hv3 arrived with. Thanks
Looks like I got a dead ESC. I tried multiple bootloaders including the offline version and it wont connect. Do I need to use a higher voltage battery? Iām using an old 3s Lipo just to see if I can get everything working before ordering batteries but Iām not getting a beep when plugging the ESC into the battery. The supply voltage is at 11.5v.
The situation with Esc firmwares is looking bad!
Manufacturers release esc with testing versions.
With my testing of 12200 blheli32 31.10.1, it has a starting problem that I cannot solve by tuning the settings.
And not that there are other options, because my testing of am32 and escape32 on 12200 revealed they have big problems , at least with 6384.
@nekitesurfing @Foiled1 Did you notice any problems with Xcross using the Blheli32 special version? What version is it?
Between the firmware problems, bearing failures, leaking cases, fried ESCās, etc⦠that many people have had here Iām thinking of just saving up for a Foil Drive or may risk buying the new Chinese knockoff for $2k. I have only purchased a motor, remote, and now dead ESC so Iām not past the point of no return for scrapping my build plans.
Buy a foil Drive second hand thenā¦
Apart from an annoying beep when the remote loses connection theyāve been working fine with saite 6374 and 6384 motors using the test firmware that Flycolour provide. Likely a setup issue or a faulty ESC if itās not working.
Edit: Iāve only used the test firmware with Xcross escs from Flycolour - so not the 12200 from sequre
Takes a bit of tinkering and popping a few electrical boards to get a DIY setup working well but once you get there (if willing to put in the time) youāre better off as youāll be able to maintain yourself and Foildrive is great when in warranty but theyāre not exempt from the issues youāve listed.
Please tell me the version of your firmware
BLHeliSuite32Test_31.10.0.1
Iāve not had any problems. Iām using BLHeliSuite32Test_31.10.0.1
Thanks.