Originally Posted by saabguyspg

Yes!! thanks Jim that's the one!!!

This is what we are looking for!

aaaahhhh teamwork!!! I am cheering for CC to come out with a killer ESC!

Steve

unlike Tom and I, at least you didn't go out and buy 4 just for a quad!!!
Al

Originally Posted by RC Man

The copter control settings - bring the output rate down

Ok I just did as you suggested. Copter control allows the following and result is listed

60 hz - unflyable severe delay
276 hz better but unflyable
333 hz flyable but not good
400 hz best of the bunch but still same slow ESC response as I described above.

I fooled around with Pids some more. Still no joy very sluggish response (actually it sounds unlike any multirotor I have flown - one doesn't hear the the rapidly changing motor speed)

If I increase p value - slow oscillation. If you purposefully start an oscillation by moving the stick back and forth then let go, the oscillations keep building untill I had to cut throttle and hard land it.

Maybe the faster refresh didn't make it in the "release" version of the castle firmware - can someone from castle actually confirm that the version we can install from your software actually has this 0-100% throttle 50x/second???

Al

Originally Posted by alros_100

Ok I just did as you suggested. Copter control allows the following and result is listed

60 hz - unflyable severe delay
276 hz better but unflyable
333 hz flyable but not good
400 hz best of the bunch but still same slow ESC response as I described above.

I fooled around with Pids some more. Still no joy very sluggish response (actually it sounds unlike any multirotor I have flown - one doesn't hear the the rapidly changing motor speed)

If I increase p value - slow oscillation. If you purposefully start an oscillation by moving the stick back and forth then let go, the oscillations keep building untill I had to cut throttle and hard land it.

Thanks for your testing & report !

Originally Posted by alros_100

Maybe the faster refresh didn't make it in the "release" version of the castle firmware - can someone from castle actually confirm that the version we can install from your software actually has this 0-100% throttle 50x/second???
Al

What a great thought………I sure hope that is actually the case!

Tom

In case you guys missed it, over on the Hoverfly Vendors Thread, Cossacs posted the following regarding the Castle Creations new multi-rotor firmware:

“It looks like Castle Creations added "multirotor" options but forgot to add firmware support for it
Throttle response is not "very fast", it is very slow, much slower than "throttle response 10" in aircraft mode. Motor rpm change reactions on my Phoenix Ice 75 many times slower comparing to HK BlueSeries 40A ESC with Simonk firmware. All cuttoffs were disabled.
I think it is just some silly mistake in firmware. “

I wanted this to be included in this Castle Creations Vendors thread so that their tech people will see what is being experienced by end users and aide them in finding a fix to the problem so I copied his comments over here.

Tom

Folks

For the hell of it, I reset the castle 25 firmware to airplane mode and set throttle response to custom "10"....

guess what it works!!! it isn't perfect but it is totally flyable and adjustable !

So it has to be a bug or an omission in the firmware.

Tom do you still have the castle stuff on your DJI or did you remove them - Do you want to try in airplane mode ?

Al

Originally Posted by alros_100

Folks

For the hell of it, I reset the castle 25 firmware to airplane mode and set throttle response to custom "10"....

guess what it works!!! it isn't perfect but it is totally flyable and adjustable !

So it has to be a bug or an omission in the firmware.

Tom do you still have the castle stuff on your DJI or did you remove them - Do you want to try in airplane mode ?

Al

Al -- We'll check on it ASAP. Something wrong in the release code.... --

Originally Posted by alros_100

Folks

For the hell of it, I reset the castle 25 firmware to airplane mode and set throttle response to custom "10"....

guess what it works!!! it isn't perfect but it is totally flyable and adjustable !

So it has to be a bug or an omission in the firmware.

Tom do you still have the castle stuff on your DJI or did you remove them - Do you want to try in airplane mode ?

Al

I have used the airplane mode and it does work very well. You need to make sure that you select the fixed-endpoints mode and you are good to go.

.

Originally Posted by RC Man

I have used the airplane mode and it does work very well. You need to make sure that you select the fixed-endpoints mode and you are good to go.

.

yes did that !

Al

Originally Posted by alros_100

Tom do you still have the castle stuff on your DJI or did you remove them - Do you want to try in airplane mode ?
Al

Hi Al,

No I removed them right after doing the testing and put the Chinese ESC’s back in so I could fly it.
As soon as Patrick announces the fix I’ll put them back in. It is just time consuming and a pain in the neck to switch them over in my particular build.
I sure hope that it gets resolved soon since I have a feeling that these are going to be great once this issue is sorted out.

Tom

Originally Posted by Patrick del Castillo

Al -- We'll check on it ASAP. Something wrong in the release code.... --

Thats great Patrick - looking forward to seeing a fix!

al

Hi all,
are those controllers will work correctly with tigermotor mt 3506 motors? http://www.rctigermotor.com/show.php?contentid=142

I'm asking, because 4 of 5 my chinese controllers have issue when working with this motor. The issue is sync loss on high current, when throttle increasing very fast. It look like this:

срыв синхры (0 min 16 sec)

Only avionix 12a works good with this motor O_o

Any Updates Patrick ?

Al

It usually takes a while to develop the code and do the alpha testing before they are ready to release a beta version for all of us the try. I would not expect anything for a few months.

I was under impression the beta was already "ready"

Originally Posted by timecop

I was under impression the beta was already "ready"