Increasing problems with the Flycolor XCross V3 160A

Hi everyone,

I haven’t posted here in a long time. Most of my updates have been on Instagram because work has kept me busy, and more recently I had some health issues. I’m finally getting a bit more time again.

We’ve been using the Flycolor XCross V3 160A ESCs for more than three years. In the beginning they worked flawlessly. Our 6384 120 kV motor with 12S3P Molicell packs delivered the full ~4 kW to the prop, and our DIY E-Devils performed great. We were always impressed by the power.

Last autumn myself (about 90 kg rider weight, 50L, 900-1300 Foils) started getting cutoffs during hard acceleration from a standstill. At first I blamed our aging batteries.

Around the same time BLHeli32 was discontinued, so I bought several newer Flycolor ESCs and programmed them with the Sequre Test Activator app. Unfortunately, the cutoffs became much more frequent and started to get really annoying.

During the winter I switched my new DIY board to a Harrydrive (available from EasyFoil). It’s still a VESC, but much higher quality, with SD logging, Wi-Fi and Bluetooth. Very promising so far, it runs noticeably hotter, so it has its own challenges, but those seem manageable.

However, we still have three boards running Flycolor ESCs, and I’d really like to keep using them. Titus is pushing his Flycolor always to the limit (65kg 30L small foils 550-700) in crazy stormy conditions (Denmark up to 40+kn). But eh even reports cut off more and more often.

One important thing I discovered is that corroded motor cables can definitely reduce performance. I have now installed two completely news motor rebuilt, fully potted motors with new cables. Performance is noticeably better, but the cutoff problem remains, especially with foils smaller than about 1000 cm².

The boards are still rideable, but if you apply full throttle too early, the ESC instantly cuts out. It immediately recovers, so you can continue riding, but it’s frustrating.

The problem is much less noticeable with 12S4P packs or LiPos, so it seems related to voltage sag.

One interesting observation: our older Flycolor ESCs, which were programmed with the original BLHeli32 software, show this behavior much less often. The newer firmware used with the Securee Test Activator app seems considerably worse in this regard.

My current suspicion is “Low RPM Power Protect”. Since we demand very high torque at very low RPM, I’m wondering whether disabling this feature might solve the problem.

Has anyone tried running “Low RPM Power Protect = OFF”? Any ideas or experience would be greatly appreciated.

Thanks,

Olli & Titus

P.S. The world of foil assist and DIY is becoming more and more connected, and that’s something we really enjoy. We’ve had amazing trips to France, Spain and Portugal, meeting fellow DIY builders and riders along the way.

Titus is starting another trip through southwest Europe next week, and I’ll follow in mid-September.

If you’d like to meet the BEENEE E-Devils, exchange ideas, compare DIY builds, or simply go foiling together, follow us on Instagram:

@b_e_e_n_e_e
@tituz__



Feel free to send us a message. We’d love to meet fellow DIY builders, discover new spots, and get to know the people behind the projects.

1 Like

Hello,

I would point the rampup power. Try to lower it maybe to 30%. It will probably give a softer throttle reactivity.

Maybe it’s too high and the Esc gives too much current at startup which reaches the 150amp current protection.

1 Like

Did you you have any experience with Low RPM off?

What about the Sequre firmware? any difference?

THX

olli

Motor cable connectors on board side?
Or corroded cables?

Had similar problems with a VESC. Cleaning everything helps for a bit, then it starts again.

Will have to redo the motor side cables at some point.

Can you reliably avoid the issues by slowly ramping up the remote?

From what I understand Low Rpm plays a role between 0 and 1% and the rampup power takes over for the rest.

I’ve got 2 Sequre 12200 on Blheli coupled with outrunner and a 14200 on Escape 32 with inrunner and I’m very happy with these.

Don’t hesitate to use Claude AI to set up and troubleshootings. It works very well !

Great! Gonna try. I have even a wp14200 Escape32 and will give it a 2nd chance :slight_smile:

Thx olli

Should we open a thread dedicated to Escape32 setup? I’m trying to figure out mine :joy:

I’ve tried with Claude and Gemini… but they seem to disagree :scream:

1 Like

Did a intens config session yesterday to find out what causes the cutoff at 50% throttle while stand up in demanding conditions (wind and waves) and small setup (Flycolor (old firmware), 6384, 12s3p, 85kg, 40L, 900m2 Foil) :

Low RPM Protect off: no effect
Lower Ramp Up: no effect
Timing to 12-18: very bad
Demag off: worse
Raise current protection to 200A: slightly better
Accelartion 0,2%: best feeling but still cutoffs

What´s frustating, that the Flycolor with the config above does an excellent job for years in the past. Don’t know why we have these cutoff problems now.

Have you checked all the soldering connections? Sometimes the connections get so hot, that it partly melts away.
I surfed half a year with a bad connection from Esc to motor and didn’t realize it until it came off completely. After I redid it I was totally amazed how much power I had

If its degenerating over time, its a hardware issue.

Your changes either reduce max current or allow more current.
Just masking the issue a tiny bit.

I’d be very suprised if any software setting could solve the problem.

no everything was fresh soldered, new cables etc. Was hoping although. Anway last hope is PWM high and low. What are your experience with a 6384 120KV (small board, small foil, heavy rider!)