See site in english Voir le site en francais
Website skin:
home  download  forum  link  contact

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length

Author Topic: DGIII and AutoFCS  (Read 2578 times)

0 Members and 1 Guest are viewing this topic.

Offline Cale

  • Newbie
  • *
  • Posts: 16
  • Karma: 0
06 May 2005, 20:23:41
Hi there,

Have tried out Mikey451's excellent AutoFCS module (de-orbit to wheels-stopped autopilot designed for the shuttle)
with both the stock DG and the DGIII.  Here's what I've experienced:

1.) Stock DeltaGlider seems to work fine using Mike's default trajectory numbers, usually within 100 m/s or
thereabouts. I recommend disconnecting the AutoFCS (hit the "U" key)when distance to KSC or EAFB is approximately
50 km. The only drawback (mirrored by DGIII) is that the AutoFCS seems to result in very jerky movements in both
pitch and roll. It's also not able to fly the HAC.

2.) DGIII also works fine, but due to its lower gliding capabilities (compared with the stock DG), you need to use the
altered trajectory numbers that were supplied by Foxboy earlier on this thread. I lowered my main fuel level to just
under 15%, giving me a gross weight of just under 15,000 kg. Like the stock DG, AutoFCS control results in
somewhat jerky movement of pitch and roll. While Foxboy recommends disconnecting AutoFCS at 50km distance from
the base, I recommend doing it earlier (between 150-100km away)to extend your gliding capability.

On approaches into Edwards, I had barely enough energy to reach runway 4, and I think that was because the
runway heading was very close to my actual flight vector, which meant that I had to expend less energy to align
myself for approach and landing. Runway 22 is difficult unless you crank up the engines. Landing at KSC was more
difficult due to the runway heading as compared to my flight vector. I was only able to make an unpowered landing
once on KSC 33, and even then I damaged the landing gear. I'm going to try and adjust the parameters in AutoFCS
so that Entry Interface occurs at between 6.0 and 6.1M and see what results.

When comparing this autopilot with the available A/P in the DGIII (PRO104SPEC40), I concluded that the DGIII A/P
was more efficient in terms of energy (in fact, I had to do a lot of S-turns to bleed off speed).  However, AutoFCS
seems to do a much better job in terms of horizontal guidance to either KSC or EAFB.  In either case, I highly
recommend downloading and using Dave413's GPCMFD during the last stages of the approach, as it'll tell you how far
off you are.

My goal was to achieve unpowered landings in both spacecraft. With specific regards to this superb add-on, you'll
probably find the stock DG a little more forgiving. I'm at work right now, but I have created several scenarios for both
spacecraft that are designed for use with AutoFCS. Let me know if you're interested and I'll post them tonight when I
get home.

Cheers,

Cale


« Last Edit: 06 May 2005, 20:23:41 by Cale »