Let me know if you have any questions on the previous post...
Let me know if you have any questions on the previous post...
Joe Ford
Product Specialist/Surface Team Manager
Castle Creations
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??
Darin E. Jordan - Renton, WA
"Self-proclaimed skill-less leader in the hobby."
We will have a v1.05 or 06, but not sure when. I haven't tested it yet...busy busy busy.
Joe Ford
Product Specialist/Surface Team Manager
Castle Creations
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?
Good info Joe,
Thanks
:::::::::::::::. It's NEVER fast enough! .:::::::::::::::
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
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.
:::::::::::::::. It's NEVER fast enough! .:::::::::::::::
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.
.
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.
:::::::::::::::. It's NEVER fast enough! .:::::::::::::::
UB, no need to applogise. I also have CC products and what you state is very valid.
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...
Darin E. Jordan - Renton, WA
"Self-proclaimed skill-less leader in the hobby."
Darin, this what blows me away also. I chose low with V1.3 for my Feaigo motors and no apparent problems???
Douggie
Originally Posted by Raydee
Dougie I did re-calibrate after each firmware change and the problem was and still is there. I won't use 1.04 EVER, sorry there is just something off with it and I can't afford to smoke another controller or fry a motor. I run all Neu motors ranging from a 1515 can to a 1527. I ran my Hydra HV 180 only a handful of times last season because EVERY time I ran it I was scared that my boat would end up on fire using the 1.04 firmware. I am looking forward to a new firmware so I can run my hydro next season.
Thanks Ray, you confirmed my suspicions.
I also used and abused BC80, BC125, H120, H240. I had no problems with my BC80 and BC125, rock solid. I have a 240 that will just not give up, on the other hand I had 2 others that gave me problems.
I had a H180HV and that did not work well for me. That brings me to the point I mentioned somewhere, the inconsistency. I think that if you are going to use your name on a product you need to make sure that it is 100% up to your standards, don't you agree? All I am asking is, tighten the QC a bit, the rest will solve itself in time. The flat fees for fixing are not that convenient anymore,
that's why I wanna make sure that things don't burn when on powering up anymore.
Flat Fee Repair Costs - Boat Products
25v Speed Controls
Hydra-120 - $105.00
Hydra-240 - $150.00
50v Speed Controls
Hydra HV-60 - $140.00
Hydra HV-120 - $172.50
Hydra HV-180 - $225.00
Hydra HV-240 - $270.00
I always start very gentle on a new ESC, just to make sure that there isn't a problem. Once trust is established I start going a little faster until I deem a good cruising point (temps vs. performance).
Last edited by Ub Hauled; 12-11-2008 at 06:40 PM.
:::::::::::::::. It's NEVER fast enough! .:::::::::::::::
Darin and Joe, we await your answer.
Sorry, Mr.Smock, I took away your trademark
Douggie
I just downloaded the latest link 3.12 and firmware 1.04 and my timing values are as followsThis obviously was not correct and was fixed in version 1.04. In version 1.04 the timing values are consistent if programmed via Castle Link or stick programming. The values are as follows:
Low: 4.75 degrees
Norm: 9 degrees
High: 12.75 degrees
Highest: 16.25 degrees
Custom
Low: 0 degrees
Norm: 7 Degrees
High: 14 degrees
Highest:20 degrees.
I have 2 Neu motors a 1515 1Y and a 1515 2d can someone tell me which timing degree i should set these at for racing?
Also have a Feigao 2 pole motor so which timing should that be set at for racing?
Cheers
Heath
Hmmm... must be on the newere interface... mine doesn't show numbers, only the "low, normal, race, extreme"... I'll have to upgrade.
I'm not sure what you "should" do, but I do know that Neu recommends the lower timing setting... That being said, and based on the info that with the 1.03 firmware I've had my timing set at "extreme" when the Link says it's on low... I've run all of my D-Wind motors for two years with these settings without issue...The Y motor i had set on Normal And the D wind i had set to race after starting off at low. Should i go back to low on the D wind and maybe high on the Y wind?
Heath
Still, I'd set back to normal or even low in the future. This might explain why my 1515 1D would get hotter than my 1515 1Y, all else being equal...
Darin E. Jordan - Renton, WA
"Self-proclaimed skill-less leader in the hobby."
Now, I am really confused. WHAT ARE THE TIMING DEGREES.
Joe Ford says this is the timing on V1.4 and a customer states this what I see on new software
For extreme applications in the future for me, it will be MGM or Schulze
Douggie
Last edited by Flying Scotsman; 12-12-2008 at 04:25 PM.
Darin,
I downloaded the new castle link v3.12 yesterday so don't know how old it is and it showed the actual degrees in numbers but they are different to the ones Joe stated..Maybe he'll chime in with WHY.
So according to v1.3 firmware i had my Y motor at normal 16.25 deg and my D motor at race 10.75 deg.
Guess it's back to the drawing board
Heath
No big repair bill or smell. I will take the protection
Douggie
That's funny... I KNEW you were going to come back with that... BUT you must have missed the part where I said I FINISHED the race! r.e.: NO REPAIR BILL or SMELL... except for the sweet smell of victory!
Again, to each his own... Maybe someday, if I burn one down at some point, I'll rethink my position, but 4-years of successful CC ESC use isn't a bad string... I think I'll stick with them!
Darin E. Jordan - Renton, WA
"Self-proclaimed skill-less leader in the hobby."
Oh nevermind, IMHO,you guys are ALL right!
Thanks Joe!
Doug
MODEL BOAT RACER
IMPBA President
District 13 Director 2011- present
IMPBA National Records Director 2009-2019
IMPBA 19887L CD
NAMBA 1169
Bookmarks