Castle Hydra Firmware

[Joe Ford]

Let me know if you have any questions on the previous post...

[Darin Jordan]

Wow... That's amazing info. Explains a TON (well... for me anyhow)...

Thanks for the support Joe... Sounds like I can now upgrade to 1.04 without worrying.

OR, is there a 1.05 coming soon??

[Joe Ford]

We will have a v1.05 or 06, but not sure when. I haven't tested it yet...busy busy busy.

[Boatman]

Im sure I speak for some in saying we appreciate all the work you have to go through but where does the new info leave us? version 1.04 is correct but with running with 1.03 and having good results are we risking warranty issues?

[Ub Hauled]

Good info Joe,
Thanks

[Raydee]

I for one am looking forward to the new Firmware.

[Flying Scotsman]

I for one am looking forward to the new Firmware.

Ray, did you recalibrate as Joe describes for V1.4 and still have higher temperatures? I am still leerry of V1.4, and how did V1.3 get past QC with the timer errors? What type of motors are you running?
Plus, this can not be a cause for the HV controllers to self destruct on hook up.


Quote
2) Those who calibrated their unit and noticed a decrease in top end. This was probably accompanied by lower ESC and motor temperatures. This was caused by the timing being 'fixed'. You can see the numbers above, and if the user sets their timing to 'Highest' on v1.04, the unit should run exactly as it did using the v1.03 firmware."

Douggie

[Ub Hauled]

Doug, I think it does boil down to software, the components CC is using are top of the line and the circuits boards have been used for a while with success, leaves us with software (am I off?).
I sure hope they fix this little hiccup pronto... one thing is for sure, I am not happy with the "plug and burn" game of the ESCs and then have to pay for it... I also wrote my concern to their staff... I like CC speedos, but if I have to send in one controller every time I connect it to the main power that would be a bad investment on my side... obviously I am exaggerating.
You have raised great questions about their QC process and I have wondered that myself before, how is it that these big issues are not coming up on the final analysis prior to production?
Anyway, I wanted to end this post positively... I like that they were REALLY thorough and gave us the details on the findings, thanks again.

[Fluid]

The "plug and burn" issue goes back to the Barracudas, it isn't just a Hydra firmware issue. A couple years ago I watched two B125s smoke the very first time they were plugged in on the bench, and they were not plugged in backwards. Knock wood I haven't had that happen to me, so far at least.

But that issue is rare, even the HVs can be reliable in high-volt racing applications. This leads me to think that it may be a component issue - one of their suppliers may not have the best QA/QC program. But I still like the Castle products and while I have burned up my share, those instances were really my fault. Sadly, ESCs are expendible items, even the Hacker 77 and 99 and other Jeti controllers had a limited lifetime under hard use.

Bottom line - I am thankful that we have a US supplier like Castle who is interested in meeting our needs and providing excellent customer service.


.

[Darin Jordan]

Bottom line - I am thankful that we have a US supplier like Castle who is interested in meeting our needs and providing excellent customer service.

Well said Jay. I agree...

[Flying Scotsman]

Well said Jay. I agree...

I also agree, but their QA/QC department need to SMARTEN up.

Not to knock North American manufacturers, but we are screwing up big time on quality and R and D ...no new ideas.

Douggie

[Ub Hauled]

I know my post sounds... hmm, negative.
I am glad we have a US based ESC manufacture and if you
look under the hatch of my boats, it's all CC. I really do like them...
have you ever heard the term "tough love"? Well, that's kinda what I am doing, I wanna see them grow better, more powerful and reliable. If there were no complaints to make the developers look deep into the ESCs, we would never evolve... that goes for a lot of things in live.

[Flying Scotsman]

UB, no need to applogise. I also have CC products and what you state is very valid.
CC listen to your customers!

Douggie

[Darin Jordan]

CC listen to your customers!

Douggie

Douggie... They DID listen to their customers! And now they have the results of that support, and were GRACIOUS enough to publically post the info to their customers, risking this kind of ridicule in the process...

When GM, Ford, or Chrysler stand up and do the same, without the need for a court-order to do so, give me a call...

Again, Thanks for taking the time to support your product, Joe... You have many loyal customers out here who really appreciate the effort...


OH, and for the record... I've run B80s, B125s, and Hydra 240s, in every type of 2S and 4S application... and have run them VERY hard... All using the 1.3 firmware, set to either LOW or NORMAL timing (so basically EXTREME in this case)... I've yet to blow or burn one up. I did have ONE cap fail on an older (original version) B125, which Castle replaced with a newer B125 for the minimal repair costs, after a year of use...

Just some testimony to perhaps get people to do some self-reflection on exactly WHERE their CC ESC issues might be based... It's NOT always the ESC...

[Flying Scotsman]

Darin, this what blows me away also. I chose low with V1.3 for my Feaigo motors and no apparent problems???

Douggie