SpartanRC DS760 Gyro Review and Setup Vids

[MarkWebber]

If you have a BlueLink or FlashLink, you can increase the Rudder Sensitivity in the configurations software for faster piro beyond your endpoints.

[LJS]

Hi Mark,

Ahh. I'll give that a try.

Thanks!:thumbup:
LJS

[LJS]

Hi All,

Well, I adjusted the rudder sensitivity to 120 and gave her a try this morning. With the new sensitivity, I had to bring the transmitter rudder endpoints down to 105 for the pirouette rate that I wanted.

I might readjust the rudder sensitivity down to 115. This will bring my rudder endpoints up a bit which will put them in line with my Futaba 611 adjustments on my other helis. It will also give me a bit better resolution on the rudder control.

BTW, I'm flying a Logo 500 3D at 2100 rpm with 85 mm K&B Dream Design tail blades in case you're wondering how the adjustments will compare to your setup.

Oh, and I'm now convinced this gyro is king of the hill. Holds great, is fully configurable, can be updated with new software, and is the smallest, lightest package around. Way to go Spartan!:thumbup:

Keep 'em flying.:YeaBaby:
LJS

[MarkWebber]

:thumbup:

[LJS]

Hi Angelos,

I had an issue today at the field where I lost my rudder sensitivity setting. I had set it to 120 last night. I tested it out this morning and all seemed great. I really liked the faster piro rate. But at lunch, when I went to fly, the gyro had set itself to something less. My piro rate was extremely slow.

I didn’t lose my endpoint settings. Is there any chance that in plugging the battery in, I cleared the rudder sensitivity setting only? I have upgraded to v1.08. Is there a solution for this issue?

Addendum: I read the gyro settings with the FlashLink Configurator when I got home and found that I didn't lose my settings. The rudder sensitivity was still 120 when I got home. So I am bewildered as to why I flew with my endpoints at 105 in the morning, but had to increase them to 150 at lunch to get the same piro rate. I flew again this evening and it seems to be holding at the 150 setting. My plan is to fly it as is since I'm now happy with the piro rate. But it would be nice to know why the gyro did that.

Thanks.:YeaBaby:
LJS

[Angelos]

Phew, I am glad you found didn't lose the settings because I couldn't think of a nice way to say that you are wrong :D With 1.08 it is extremely unlikely for data to be corrupted and go unnoticed and with the duplicated data storage the gyro will self repair any faults. For data validation we use 16bit CRC which is a very robust error detection algorithm widely used in computer data communication. The chance of the CRC missing an error are probably much much lower than winning lottery.

-Angelos

[Pulento]

Angelos,

Still fighting with my kickback on clockwise piro stops. Increase the arm to 16mm (from 14mm) didn't make much improvement, tried Curtis 95mm (from K&B 92mm) tail blades and improved a bit.

Now I'm looking the tail rod for some asimetrical flexing.

On a Automatic Control sense can I think this is something like a overshoot ? (to try to lower gain) But if better and a bit longer blades improved things I don't think that it's a high gain issue :(

BTW: Much better logo :)

Edit: History of my kickback http://helifreak.com/showpost.php?p=764384&postcount=758

[robert01]

I have been working on a CW stop bounce issue for two months on my T-Rex 500. Flash link, carbon blades,a 3400, a 8900. 8mm to 13mm arm, everything 90,13 tooth,deceleration adjusted in one degree increments,stop gain adjusted 5 % incremente, CCW no bounce but always a bit hard stopping even with stop gain way down. I followed all instructions with very little change. I am beginning to think this gyro is out of adjustment. Is there a problem with the 500 tail? I have heard others talk about this same thing but have never seen it get resolved unless the gyro was swapped.

[Augman37]

I have been working on a CW stop bounce issue for two months on my T-Rex 500. Flash link, carbon blades,a 3400, a 8900. 8mm to 13mm arm, everything 90,13 tooth,deceleration adjusted in one degree increments,stop gain adjusted 5 % incremente, CCW no bounce but always a bit hard stopping even with stop gain way down. I followed all instructions with very little change. I am beginning to think this gyro is out of adjustment. Is there a problem with the 500 tail? I have heard others talk about this same thing but have never seen it get resolved unless the gyro was swapped.

I have done everything you have done and put on a microheli metal tail everything. I still have a soft bounce back on CW piro but is rock solid on CCW piro. I am at a loss too. I am planning on going to a club field in Atlanta where Matt Botos flies and see if he has any ideas. I will let you know what happens.:o

[robert01]

Oh yah.... I put a Kasama tail on as well. Thanks, I'll be watching Augman.

[Augman37]

Oh yah.... I put a Kasama tail on as well. Thanks, I'll be watching Augman.

careful, a friend of mine had the kasama tail blow apart mid flight! I saw it. Probably was a manufacturer defect but the grip just blew off mid flight.

[robert01]

Thanks I'll keep an eye on that tail Augman. My gyro has promted me twice to e-mail a file to spartan. has anyone else had this happen? Is this an indication of a problem? still having CW piro bounce back with deceleration one from the bottom.

[BruceW]

I upgraded to version 1.08 (from 1.07) last night and it seems that my piro speed is more consistent. All I did was save my settings before flashing then reapply them with no other changes. What I noticed was that previously when I put the helicopter into a tail slide and spin the tail it would seem to change speed through the rotation. Now it seems to be consistent all the way down.

Not sure if there was a change to this part of the firmware or if it was just something in my setup, but I like it.

[Pulento]

I have done everything you have done and put on a microheli metal tail everything. I still have a soft bounce back on CW piro but is rock solid on CCW piro. I am at a loss too. I am planning on going to a club field in Atlanta where Matt Botos flies and see if he has any ideas. I will let you know what happens.:o

:(

I know that bounces are more frequent on little helis by experience I haven't eliminated CW bounce on my Dragonus with JR770.

I'm wondering if I play with the delay. I mean I have set the servo to 8900G (that's what I have) but wonder if I increase the delay from 0.05 to 0.08 to test, on GY401 increasing delay gets rid of bounces.

[Pulento]

One last question. If my direction is reverse, do the stop gains reverse also ? I mean if I want to change CW stop gain with reversed gyro do I need to change the CCW stop gain ?

[4cyclic]

Just fine tuning mine yesterday and although the gyro feels great on piro consistency and overall feel, I also cannot get rid on the CW bounce on my 700N. No tail bounce on CCW. I have the USB flash-link and playing with the decelaration and CW stop gain did not produce any noticable reduction in the bounce. The bounce was faster or slower, but did not stop. Running 15mm on the 8900g servo, 5.5v.
Any ideas ?

[raptorheli2]

i have the bluetooth link but i have not put it on my 700 yet to get the gyro fully setup.

generally speaking you need to balance stop gain with decel slider. i'm going to guess about 60% on the decel slider and 130 stop gains will be where i end up ish but i'll not get a chance to try it for a week. will post back settings when i have done so if you still have trouble.

cheers

[4cyclic]

I'm used to the 611 gyro. The stops are the same in CW as CCW on it, so I don't understand why it should be any different with the DS760 ?
I have the tail neutral pitch at 8 degrees so it 's not drifting in normal mode and no drifting at all in AVCS mode. High pitch is 100 and low is 120.

[raptorheli2]

it's different because the 601/611 stop gains are very powerful (hence the synergy blowing tail gears with the 601/611 when it first appeared, then people realised they should be turned down). your worrying about nothing, the gyro just needs adjusted to suit that heli. as i said i won't be able to get settings till weekend from my own.

cheers

[4cyclic]

Thanks for info. I'm not worried really, just excited with this gyro and to bring it to full potential. Just having fun now with 25 flights on it. the crisp stops are nice to have, but I can do my 4 point tic tocs quite well already.

[Pulento]

High pitch is 100 and low is 120.

Looking Bert Kammerer's config for his 600N it seems that he is using quite a long servo arm because his endpoints are low and his slider is quite offcenter (58 and 140). Longer arm means less resolution but higher response speed which maybe is what we need to avoid the bounce.

This weekend I'll continue my tests but I'm shooting in the dark :(

[MarkWebber]

58 and 140! Geez that's off. If he were to set that up better mechanically, he would have an ideal setting of 100/100. He is using the correct hole for his heli, though. You want the endpoint settings to add up to 200, if practical. So, his resolution is dead on right now.

[Finless]

Well you have to understand a Trex's tail geometry. Unlike some helis, on a Trex when the pitch slider is centered you have 0 tail blade pitch. Thus to get 8 degrees of offset, the slider has to be move closer to the tail case and then your going to have one end point really low and the other much higher.

Again I tried setting it up with the slider center (0 blade pitch) so the ends point settings were as close as possible and to be honest I noticed NO DIFFERENCE if flying characteristics! My conclusion is I dont think you absolutely need to set up with 8 degrees of pitch on a Trex helicopter. For those having a problem I suggest you try it and see if it works for you.

Bob

[MarkWebber]

I gotcha, Bob. You'd think they'd design in equal travel distance.:thinking

[robert01]

Does anyone with a T-Rex 500 and a Spartan have equal stops CW to CCW? I have even removed the gyro from the tail block and placed it upside down on the lower shelf, to see if the bounce would follow the normal/reverse and switch to a CCW bounce, it did not.