Phoenix Firmware V4.02 released

[61Espo]

Originally Posted by RC Mike

V4.02 firmware, low timing, and PWM of 12 is the way to go. 16 will make the ESC run hotter and not do anything for the motor.

+ 1

[BakedMopar]

Originally Posted by RC Mike

V4.02 firmware, low timing, and PWM of 12 is the way to go. 16 will make the ESC run hotter and not do anything for the motor.

Some motors needs the higher PWM for it to run correctly. On one of my setups it would cut out on anything less than 16.

As for the xspare are you using an external governor? I don't think there was any changes from 4.01 besides the external gov mode.

[xspare]

BakedMopar (aka CrispyChrysler?)

I'm using Internal gov only - I try to keep things updated but am going to revise my practices. My primary beef is that I might still have a motor if the "Insensitive (80A)" current limiting had been respected.

I switched:

1. Motor - Timing from Low (0) to Normal (5)
2. Motor - PWM rate from 12 kHz to 16 kHz
3. Throttle - Governor gain from Custom (20) to Medium (25)
4. Throttle - Head Speed Change Rate from Custom (16) to Medium (5)

Clint had advised me (back in May) to use at least 15 on Head Speed Change Rate - for auto bailout. I also failed to heed his warning of needing to recalibrate the throttle "Anytime you upgrade firmware".

[vojta]

Originally Posted by newbheliusr

In a fbl controller it's predictive instead of reactive.
The fbl controller knows your cyclic and collective pitch ranges.
A gov inside an esc reacts to load changes.

Originally Posted by tshelby73

with vbar the new firmware allows the castle software to softstart then hand control over to vbar.
their is a new setting in castle software called external governor.

This option is especially for governors in the new FBL units with ability to get info about load changes from ESC through the Power cabel (namely, VBar mentioned in Castles's documentation, and a future release of Align's 3GX).
Castle's ESCs are able to send such an info through the Power cabel with the firmware v.4.01 and above.
With such a combination, you will get a predictive governor with possibility to respond to the current load, too.

[malc1]

Will this update work with Hobbywing and Hyperion phase sensors? - I've got one of each here.

Anyone tried both yet?

[Chris Sexton]

Originally Posted by malc1

Will this update work with Hobbywing and Hyperion phase sensors? - I've got one of each here.

Anyone tried both yet?

Requires digital rom sensor. Hyperion won't work. That has been confirmed by Clint.


Sent from my iPhone using Tapatalk

[malc1]

OK thanks, Hobbywing it is then.

[RC Mike]

Originally Posted by malc1

Will this update work with Hobbywing and Hyperion phase sensors? - I've got one of each here.

Anyone tried both yet?

Hyperion sensors have just become obsolete technology – donate them to a museum – LOL.

Currently Hobby Wind digital sensor is the only one that will work until CC comes out with their digital sensor.

.

[malc1]

That will make them even harder to get hold of then.

[tshelby73]

I ordered 3 hw sensors direct

[ualdrivr]

After I upgraded to 4.02 on my ICE 2 120HV the ESC can't be throttle calibrated. I'm at a loss. I initialize my electronics, setup my T/Cs to 0-50-100 and my end points to around 30% HI and LOW.

With the Stick hi, I plug a battery and the ESC counts the cells and after that it arms. It shouldn't do that, right? I can't calibrate the throttle anymore. Auto is on and it was setup. What I'm I doing wrong?

[Bob O]

Make sure you're in the flight mode that has the linear curve.

Sent from my phone

[ualdrivr]

Originally Posted by Bob O

Make sure you're in the flight mode that has the linear curve.

Sent from my phone

Thanks Bob, I am. Maybe I need to re-bind with 100% end points? I'm using a 9503 TX with the AR 7200 BX.

OK , I managed to do it, but it took some "doing". First I went to 100% end points and linear curves. I re-bound the TX. Then I started with 60% Low and Hi end points. When I did that the ESC was counting cells and it stopped, it wasn't arming any more like it did last night, but, it wasn't calibrating the High throttle (BTW I had the stick in high, as per CC video). Out of curiosity I went to Low throttle and what do you know, it calibrated the low....weird, right?

So, I had an idea to go in and INH the T/H, so I did. I started over and bingo. Hi and Low were calibrated. What I also noticed was that the points of calibration were lower than before, I was 97 Hi and 130 Low now I'm 92 Hi and 126 Low with Auto enabled. After I saw that I figured to do the Autorotation calibration as well. No big changes there, just one point from 16%, down to 15%.

You guys think it's a bug on the Beta version? You shouldn't have to do all that to recalibrate the throttle. I never had that problem before and I have done countless recalibrations on my ICE 75 that I have on my good ole' 500.

Any how that's what worked for me this morning....

[ualdrivr]

The ever hard working and excellent CC rep. Clint Akins send me this link about the AR 7200BX and the fact that it needs to see 0 throttle first and then be calibrated.

http://www.rcgroups.com/forums/showthread.php?t=1649655

Thanks Clint.

[tshelby73]

Originally Posted by ualdrivr

The ever hard working and excellent CC rep. Clint Akins send me this link about the AR 7200BX and the fact that it needs to see 0 throttle first and then be calibrated.

http://www.rcgroups.com/forums/showthread.php?t=1649655

Thanks Clint.

Make sure you rebind after calibration so it know your new 0 throttle. You may have to go back to your old settings for throttle to get beast x to release the throttle channel then do calibration. I find this a PITA with beast X but good safety.

[msallua]

I have a Align 700DFC HV all stock, comes with 750mx, 530kv and 10 pole count, and of course comes with a CC120A HV ...

PWM rate is 8Khz or 12khz?

Thanks in advance

[Dr. M]

Originally Posted by msallua

I have a Align 700DFC HV all stock, comes with 750mx, 530kv and 10 pole count, and of course comes with a CC120A HV ...

PWM rate is 8Khz or 12khz?

Thanks in advance

I'd use 12kHz on that one assuming a 12s power system.

[Bob O]

Originally Posted by Dr. M

I'd use 12kHz on that one assuming a 12s power system.

+1 if you go by THIS formula.

[msallua]

Originally Posted by Bob O

+1 if you go by THIS formula.

Yes, but the CC website confuse me...the recomendation is 8Khz in the pdf file, I send an email to CC but not answer.

[Bob O]

Originally Posted by msallua

Yes, but the CC website confuse me...the recomendation is 8Khz in the pdf file, I send an email to CC but not answer.

That was a different motor though right? A 700MX? Not sure if the pole count is different or something. Don't know.

ADDED:

I just looked at the site with the specs. Seem to be the same. But they also spec 3.27 firmware. I don't think it will hurt to run at a lower pwm, but maybe you would want to hear back from Castle before trying anything just to be on the safe side.

http://www.castlecreations.com/suppo...0mx-530kv.html