PDA

View Full Version : CC35 cutoff problem with V1.22 firmware


Cycross
Oct 30, 2005, 12:58 AM
I had been using my CC35 for some time now and I recently upgraded its firmware to V1.22 beta. No issues previously with V1.14.

Following, I found a full power cutoff at a handlaunch takeoff with a nasty experience of heavy model, slow speed, no power, no height...Bad mistake not to test before launch. Restarts did not help much as it continued to cutoff. Model forced landed with bad scratches in view of safety to others.

Came back and tested further with a wattmeter. Results confirmed that I am drawing less than 14A loaded at any time, no spikes seen and always way below the 35A limit. As was in the field, power cutoff was repeatable at power settings anywhere 75-100% throttle.

I tried setting the current limiting from Standard Normal to Insensitive. It didn't help.

Lastly, without changing the physical setup, I reprogrammed the firmware back to V1.14 and set the current limit back to default Normal. And Voila, problem disappeared!

Will Castle Creations please do something to correct V1.22, or at least make a review to this issues? A CC35 can't be cutting off at half it's rated current.


Meanwhile I will stay with V1.14. Now I am also unsure if the V1.22 upgrade of my HV110 is safe from this. :(

BEC
Oct 30, 2005, 03:55 PM
Where is your LVC set? Did it get reset with the update?

Joe Ford
Oct 30, 2005, 04:19 PM
Cycross,

Sorry to hear you're having problems with the 1.22 software. What is your power system? Battery (manufacturer, capacity, and "C" rating please), motor, gearing (if any), and prop. Please try setting current limiting to disabled and use soft cutoff. Let me know what you find.

Joe Ford
Product Specialist
Castle Creations
joeford@castlecreations.com
785-883-4519 ext. 119

flasher2001
Oct 30, 2005, 06:24 PM
i am also using a Phoenix 35 with v1.22 firmware and i experienced motor power cutoff in flight. i was able to get power back by lowering the throttle to minimum, then back up.

my power system is a Himax 2815-1400 direct drive, 8x4E prop, Thunder Power 3S 2100 (10-12C) battery. my wattmeter showed no higher than 22 amps.

i will reset my firmware to v1.14 and hopefully my problem will be fixed. i will check back to see if CC has any other suggestions.

Cycross
Oct 30, 2005, 08:26 PM
Hi Joe,

Thanks for replying. I appreciate it.

My power setup is as follows:
Align 400F outrunner
EasyGlider stock gearbox (3:1)
CC35
E-TEC 1900mAh 3S1P (10-12C, 20C burst) (almost full)
Stock prop (10" X approx 6")

Setup max current draw as per wattmeter sustained: 11.2A
No spikes noted.
Voltage never at any time went below 10.5V.
This is static loading with prop, should be less in the air.

I reloaded V1.22 beta and tested as instructed, LVC not changed at 9.0V in both versions. I repeated the cutoffs with Current Limiting set to "Insensitive".

Switching from "Insensitive" to "Disabled", the cutoff did not occur.

I can't check the HV110 as I do not have a complete setup yet. But I can't afford to risk an investment of that size though. I hope you understand.

Thanks!

akcarl
Nov 02, 2005, 01:18 PM
I have had exactly the same problem with throttle cut-out in the full throttle range. I ran the CCP35 ESC in MP EZ* without any problems, put it in a MicroJet (updated the firmware to 1.22) and it started cutting out. As you can see from my msg below I swapped out just about everything else besides the servos in the plane because I "KNEW" that the ESC worked. I finally emailed CC and got the same response... What was left out of my message was that I updated the firmware and that I did try setting the ESC to insensative which didn't help. I haven't tried rolling back the firmware yet or changing the setting as it is working with the older P35 I put in there (not sure of firmware). This is disappointing from a customer standpoint though. We pay a premium for 'high quality' products like the CC brands. Whether this is a beta firmware issue or not I find their response to the issue inappropriate. While the setup that I working on now isn't that expensive I also have an AP platform that has over $1000 invested into it not to mention my time. I would like to know and trust that the equipment that I have in that setup works as advertised and expected.

REPLY FROM CC RE: CUT OUT PROBLEM AND MY ORIGINAL MSG

Carl,

Please try this...change current limiting to disabled and use soft
cutoff. If it does not cut out, the current limiting feature was set a
bit sensitive. Keeping it disabled will not harm the controller. Its
only purpose is to keep you from running too large of a prop (ie-too
much current). I disable this on all of my airplanes after verifying the
system is running within specs. Please let me know if you have any other
questions.

Joe Ford
Product Specialist
Castle Creations
joeford@castlecreations.com
785-883-4519 ext. 119



cmadson@[snipped] wrote:

>Hello,
>
>I am experiencing some problems with my P35 (F310) and I was hoping you would be able to help me out. The speed control will cut power to the motor after 5-20 seconds and end up with a blinking red light. It will reset by just dropping the throttle momentarily. Here is the setup I had originally as well as what parts I tried swapping out to solve this problem.
>
>Original setup:
>Multiplex MicroJet
>Mega Motors 16/15/5
>APC 6x4E prop
>CC P35
>TP 2S 2100mAh 15C LiPo
>Hitec 05S receiver
>
>Swapped out parts:
>Mega 16/15/6
>APC 5x5E
>2 TP 2S 2100mAh 15C LiPo hooked up in Parallel
>2nd Hitec 05S and electron 6 receiver
>Pulled the speed control out of the plane and ran it in the open air
>
>Okay, so after getting frustrated I finally put this this setup on a Fluke meter and here is what I got for power draw:
>
>With battery freshly charged
>No Load [0% throttle]
>8.6v
>0.1A
>
>Full throttle
>7.6v
>6.4A
>
>Finally what solved this was a second CC P35 (F221) and it doesn't cut out anymore.
>
>Do you have any ideas to troubleshoot this speed controller? I bought it from Bishop Power Products (www.b-p-p.com) this summer.
>
>Thanks,
>Carl

Cycross
Nov 03, 2005, 10:16 AM
Hi Joe,

Apparently this is not an isolated case. Does setting current limiting to "disabled" effectively mean no safe margin for overloading error?

Disabling the current limit seems like a bypass, not a solution. I agree with akcarl that the response in this case is inappropriate.

Please advise. Thanks!

Bernie Wolfard
Nov 03, 2005, 04:47 PM
Cycross,

If turning off current limiting won't change the risk of overloading. It also won't effect your warranty.

Bernie

Cycross
Nov 04, 2005, 10:26 AM
Cycross,

If turning off current limiting won't change the risk of overloading. It also won't effect your warranty.

Bernie

Bernie,

I am taking this offline. you have email. Tks.