Using IMFD 5.1e with DGIV for a free-return TLI

[Cale]

Howdy everyone,

It's been awhile since I've been on the site.  Most of my spare time over the last year has been spent with Flight Sim,
but I'm back orbiting for awhile.

Just wondering if there's any special trick to doing a free-return TLI using IMFD's Target Intercept program with the
DGIV.  I can get to the moon sure enough, but it seems that the engines burn too long and I end up with a trajectory
that would take me past the moon and to the great beyond.

I've tried the identical scenario with both a stock DG, DG-S and the XR1 with a perfect free-return trajectory, but am
still having problems with the DGIV.  Is there any issue or conflict with existing autopilot programs in the DGIV, or is
there a special configuration required, or is the Autoburn feature within IMFD not compatible with the DGIV?

Any help would be appreciated.

BTW, any idea what's going on with the main Orbiter forums?

Cheers,

Cale

[Pirx]

There are some problems with IMFD 5.1e but messing up TLI is not amongst them (for me). The result of a single Auto-Burn in Off-Axis mode, no course corrections:

http://img2.freeimagehosting.net/image.php?df1824b66f.png



Post Edited ( 03-24-08 08:24 )

[Cale]

Hmm, still getting the same problem..a hyperbolic trajectory that approaches the moon, but not a free-return..the XR1
did the burn perfectly.

I watched both crafts try to do the burn and I noticed that the DGIV's orientation prior to executing the burn was
quite a bit different than the XR1.  In terms of ship control, would leaving it in "ATM auto" rather than "RCS ROT" be
the cause, or maybe the engine gimbal control switches need to be different (though, based on your screen shot, it
was in the default position)?  When I get home from work, I'll try doing the burn manually using the burn vector
screen and see if it works.


Thanks for your help!

Cheers,

Cale

[ar81]

I am unable to get Hed in IMFD 5.1
I can get it in IMFD 4.2
I keep using 4.2 because of this.

[Cale]

ar81 wrote:
I am unable to get Hed in IMFD 5.1
I can get it in IMFD 4.2
I keep using 4.2 because of this.

You mean for the burn vector?  Hmm, will try when I get home.  Like I said, it's weird that I can get this to work with
other spacecraft but not DGIV.  

I know there's a scenario that came with IMFD 5.1e that already has a free-return trajectory set up, so I'll try that
when I get home later.  What I also may do is post the scenario and see if anyone else has any luck.

Cheers,

Cale

[ar81]

No, I mean Hed to take off from Earth.

[Cale]

Well, I just tried out the "Simple Free-Return" scenario that comes with the install of IMFD 5.1e and it didn't work
using AutoBurn...kept burning well past the cutoff time and the trajectory doesn't even come close to the
moon.

Wonder if it has something to do with how my DGIV is set up?  Will cut and paste a DG from one of the stock
scenarios and see if that works.

[Pirx]

Weird! If you have the non-spherical gravity effects turned off, this would cause some deviation (IMFD assumes they are on in its calculations) but not to the extent to not even get close to the Moon. And it would definitely affect all ships, not just DGIV.

What happens with AB in the following scenario:

Code: [Select]

BEGIN_DESC
Free return trajectory.
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 60247.3952497603
END_ENVIRONMENT

BEGIN_FOCUS
  Ship DGIV-02
END_FOCUS

BEGIN_CAMERA
  TARGET DGIV-02
  MODE Cockpit
  FOV 40.00
END_CAMERA

BEGIN_HUD
  TYPE Orbit
  REF AUTO
END_HUD

BEGIN_MFD Left
  TYPE User
  MODE Interplanetary
  Scenario Old2
  MapMFD V5
  Reference Auto
  Target moon
  Center Moon
  Data 0 1 1.44960827881826e-005 0 1 0 1 2 1 0 0 0
  MassLimit 1e+020
  CMode 2
  Config 1 1 1 1 600000 0
  ExtMode 2
  Periapis Moon
  END
  CorMFD V4
  Reference Earth
  Target Moon
  Source DGIV-02
  ActiveProg 1 1
  DataA 0 3 0 0 0 0
  DataB 38.443359375 1 60247.39749402992 0 0 1.650350900800771 0 60250.27786362612 0
  DVProg 0 0 0 1
  AdvConf 0 0 7134895.700611976 2 0
  Guidance 1
  END
  EjectMFD V5
  Reference Auto
  Data 0 1 3 0 1 60246.68919493399 10
  Guidance 0
  END
  BaseAprMFD V2
  Reference Auto
  Target none
  Source none
  DataA 0 0 120000 0.10821 0.366519 1 1 60246.68919493399 60246.68919493399 0
  DataB 0 3 0 1 0 1
  END
  SlingMFD V4
  Reference Auto
  Source none
  Data 0 1 1 3 0 1 60246.68919493399 0
  END
  LaunchMFD V4
  Target moon
  Data 0 1 100 3 1 0 60250.27810504973
  END
  CF1_DataA 1 0
  CF1_DataB 60246.6871004201 10 120000 1 5 150000
  CF1_SecTgt
  mfdShare 1
  mfdProgram 4
END_MFD

BEGIN_MFD Right
  TYPE User
  MODE Interplanetary
  Scenario Old2
  MapMFD V5
  Reference Auto
  Target moon
  Center Moon
  Data 0 1 1.44960827881826e-005 0 1 0 1 2 1 0 0 0
  MassLimit 1e+020
  CMode 2
  Config 1 1 1 1 600000 0
  ExtMode 2
  Periapis Moon
  END
  CorMFD V4
  Reference Earth
  Target Moon
  Source DGIV-02
  ActiveProg 1 1
  DataA 0 3 0 0 0 0
  DataB 38.443359375 1 60247.39749402992 0 0 1.650350900800771 0 60250.27786362612 0
  DVProg 0 0 0 1
  AdvConf 0 0 7134895.700611976 2 0
  Guidance 1
  END
  EjectMFD V5
  Reference Auto
  Data 0 1 3 0 1 60246.68919493399 10
  Guidance 0
  END
  BaseAprMFD V2
  Reference Auto
  Target none
  Source none
  DataA 0 0 120000 0.10821 0.366519 1 1 60246.68919493399 60246.68919493399 0
  DataB 0 3 0 1 0 1
  END
  SlingMFD V4
  Reference Auto
  Source none
  Data 0 1 1 3 0 1 60246.68919493399 0
  END
  LaunchMFD V4
  Target moon
  Data 0 1 100 3 1 0 60250.27810504973
  END
  CF1_DataA 1 0
  CF1_DataB 60246.6871004201 10 120000 1 5 150000
  CF1_SecTgt
  mfdShare -1
  mfdProgram 2
END_MFD

BEGIN_PANEL
END_PANEL


BEGIN_SHIPS
ISS:ProjectAlpha_ISS
  STATUS Orbiting Earth
  RPOS 1471949.60 -6382439.04 1497949.43
  RVEL -7294.813 -1175.876 2165.407
  AROT 123.70 -56.86 113.54
  VROT 0.03 0.06 0.08
  PRPLEVEL 0:1.000
  IDS 0:588 100 1:586 100 2:584 100 3:582 100 4:580 100
  NAVFREQ 0 0
  XPDR 466
END
Mir
  STATUS Orbiting Earth
  RPOS 6372069.93 394571.64 1856753.94
  RVEL -2179.014 346.673 7428.303
  AROT 156.33 -14.80 80.64
  IDS 0:540 100 1:542 100 2:544 100
  XPDR 482
END
Luna-OB1:Wheel
  STATUS Orbiting Moon
  RPOS -1922877.74 1144402.13 2641.42
  RVEL -757.491 -1271.954 -1.700
  AROT -0.11 0.04 -46.44
  VROT -0.00 -0.00 10.00
  IDS 0:560 100 1:564 100
  XPDR 494
END
DGIV-02:DeltaGliderIV
  STATUS Orbiting Earth
  RPOS -877770.51 -631659.84 -6422036.26
  RVEL 7747.116 314.764 -1086.930
  AROT 164.38 -81.48 -158.96
  VROT 0.00 0.07 -0.00
  PRPLEVEL 0:0.517 1:0.992 2:0.983
  IDS 0:45 100
  NAVFREQ 94 524
  XPDR 0
  ;-------------------------- Skin parameters must contain directory name of skin (without space)
  MeshSkin spacetech
  ;-------------------------- Cargo payload must contain name of config file or "none".(see doc)
  CargoPayload DGIVCargoA4
  NOSECONE 0 0.00
  GEAR 0 0.00
  AllDoorsState 0 0.00 0 0.00 0 0.00 1 1.00 0 0.00 0 0.00 1 0 0.00
  But1Cockpit 0 0 0 2 2 2 0 2 2 2 2 2 2 2 2 0 1 0 1 1 1 5
  But2Cockpit 0 0 0 0 0 0 0 0 2 2 2 2 2 0 3 0 0 0 1 1 0 0
  TransEffect 0
  LifeBut1State 0 2 1 2 1 2 2 2 2 0 0 0 0 1 0
  LevelBatt 100.0002
  Emergency_power 10000.0000
  VoltageStartBus 0.0000
  VoltageGen1 96.2820
  VoltageGen2 96.2819
  VoltageGenBus 96.0000
  O2tankALevel 99.6883
  N2tankALevel 99.9993
  O2tankBLevel 100.0000
  N2tankBLevel 100.0000
  CabinO2Level 21.3923
  CabinCO2Level 600.0000
  CabinTempLevel 21.1002
  CabinPressure 14.7000
  CabinMoistLevel 36.0000
  CabinDustLevel 0.0002
  CabinO2Setting 21.4000
  CabinTempSetting 21.2000
  CabinPressSetting 14.7000
  AntennaTarget no_target
  O2ConsumptionSetting 2
  FuelConsumptionSetting 2
  MainenginePower 1
  ;------------------Crew parameters  UMMUCREW Function-Name-Age-CardiacPulse-WeightKg (fonction of Pilot must be: Capt)
  NoOneOnBoard 0
  NoPilotOnBoard 0
  UMMUCREW Capt-Jeroen_Roos-32-60-71
  UMMUCREW Sec-Fuechslin_Beat-41-68-84
  UMMUCREW Tech-David_Whitson-41-95-67
  FailGearFailure 0
  FailGearCollapse 0
  FailLeftMainEngine 0
  FailRightMainEngine 0
  FailHoverEngine 0
  FailRcs 0
  FailSurfaceControl 0
  FailComputer 0
  FailComputerBlueScreen 0
  FailAutopilot 0
  FailExtRadiator 0
  FailAirbrake 0
  FailNoseCone 0
  FailCanopy 0
  FailAntenna 0
  FailLeftTurbo 0
  FailRightTurbo 0
  FailCargoDoor 0
  SpacesuitTimer 0
END
END_SHIPS

BEGIN_ExtMFD
END


Post Edited ( 03-25-08 07:34 )

[Cale]

Thanks Pirx,

Am on my way to work right now, but will give this a shot tonight.

BTW, tried to do my free-return scenario manually with the DGIV, but even though I cut the engines at the specified
time, I still missed the moon...will try your scenario and let you know.

I also checked my preferences in the Orbiter Launchpad and Non-Spherical Gravity Sources was unchecked (for AMSO v1.17).  Will see if that makes the difference.  That would be interesting...if it worked, then obviously the DGIV is more sensitive to this than either the stock DG/DG-S or the XR1 (which were all able to perform the burn with no problems).

Thanks for your help sir.  Based on other IMFD-related posts on this forum, you're an Interplanetary guru!

Cheers,

Cale



Post Edited ( 03-25-08 14:58 )

[jarmonik]

There has been some problems with DGIV and IMFD before. I am not exactly sure what is wrong but..

if DGIV is using AddForce function to add some additional "thrust" acceleration, it will be unknown to IMFD and it will
fail.

also if DGIV is using fuel-source-efficiency factors other than 1.0 those are unknown to IMFD and the thrust
acceleration is incorrectly calculated by IMFD.  All such efficiency factors should be included in ISP for proper operation.

If there is DGIV specific problem in IMFD, I think these are the first two things to check out.

Jarmo

[jarmonik]

There is actually new API call "GetThrusterResource" that can be used to get the fuel-efficiency factor. So, if that's the
problem I can fix it form the next release.

[ar81]

In previous version of IMFD I enabled data sharing for MFDs.
In latest IMFDs I share both MFDs IDs and it becomes useless.  
MFD0 shares with ID1 and MFD1 shares with ID0
Course program is not working.

I can only eject using Higher and Lower orbit.
I tried to look for some information on how to use later IMFD and found no useful info.
Manual does not help.

I used stock DG and had the same problem.
It is not very efficient to use Higher and Lower orbit.

[Cale]

First off, thanks for the input..but I've figured out what went wrong..mostly that I'm a bit of an idiot

When I looked at Pirx's scenario, I realized that all the settings for his TLI burn were pretty much the same as
mine..except for the EIn.  In my scenarios, the EIn was well over 2.   Once I aligned planes, my scenarios seemed to
work fine with the DGIV.

It is interesting, however, that the XR1 was still able to function in spite of the Inclination error.  Dunno if that means
its parameters are more forgiving, or IMFD just seems to work better with it.

BTW Pirx, your scenario worked perfectly.  Thanks!

Jarmonik, good to hear from you again.  What can I say, your MFD rocks!!  I'll enjoy using it even more when I learn to
use it properly

Cheers,

Cale

[James.Denholm]

ar81 wrote:
In latest IMFDs I share both MFDs IDs and it becomes useless.  
MFD0 shares with ID1 and MFD1 shares with ID0
Course program is not working.

Pablo, your problem is that you are sharing BOTH MFDs. You should only enable sharing on one of them, not two.

Leave IMFD 0 un-shared, and put IMFD 1 to share with IMFD 0. That should fix it.

[Pirx]

Cale, I have no problem with DGIV TLI even if EIn > 2.00 deg. How much is "well over 2" for you? Any chance you were using off-axis burn mode and manually activated the turbo pump during the burn?


Jarmonik, thank you for joining the discussion and, of course, thank you for the great navigation tool! As I said above I have no DGIV-specific issues, but I am going to use the opportunity to report 3 problems with IMFD 5.1e:

1. Occasionally wrong (too low) outbound velocity is calculated by the Course - Target Intercept program.

Code: [Select]

BEGIN_DESC
Contains the latest simulation state.
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 65694.0875929989
END_ENVIRONMENT

BEGIN_FOCUS
  Ship DG-01
END_FOCUS

BEGIN_CAMERA
  TARGET DG-01
  MODE Cockpit
  FOV 40.00
END_CAMERA

BEGIN_HUD
  TYPE Orbit
  REF AUTO
END_HUD

BEGIN_MFD Left
  TYPE User
  MODE Interplanetary
  Scenario Old2
  MapMFD V5
  Reference Jupiter
  Target Io
  Center Io
  Data 0 1 1.942342778487991e-007 1 0 1 0 0 1 0 0 0
  MassLimit 1e+020
  CMode 2
  Config 1 1 1 1 0 0
  ExtMode 2
  Periapis Io
  END
  CorMFD V4
  Reference Jupiter
  Target Io
  Source Europa
  ActiveProg 1 1
  DataA 0 3 0 0 0 0
  DataB 1 10 65694.09108321882 0 0 4.912908384460053 0 65695.36238997182 0
  DVProg 0 0 0 1
  AdvConf 0 0 1 0 0
  Guidance 0
  END
  EjectMFD V5
  Reference Auto
  Data 0 1 3 0 0 65694.09107173729 2580.86
  Guidance 0
  END
  BaseAprMFD V2
  Reference Auto
  Target none
  Source none
  DataA 0 0 120000 0.10821 0.366519 1 1 65694.06780490864 65694.06780490864 0
  DataB 0 3 0 1 0 1
  END
  SlingMFD V4
  Reference Auto
  Source none
  Data 0 1 1 3 0 1 65694.06780490864 0
  END
  LaunchMFD V4
  Target None
  Data 0 1 1 3 0 1 65694.07153379753
  END
  CF1_DataA 1 0
  CF1_DataB 65694.06707965401 10 120000 1 5 150000
  CF1_SecTgt
  mfdShare 1
  mfdProgram 3
END_MFD

BEGIN_MFD Right
  TYPE User
  MODE Interplanetary
  Scenario Old2
  MapMFD V5
  Reference Jupiter
  Target Io
  Center Io
  Data 0 1 1.942342778487991e-007 1 0 1 0 0 1 0 0 0
  MassLimit 1e+020
  CMode 2
  Config 1 1 1 1 0 0
  ExtMode 2
  Periapis Io
  END
  CorMFD V4
  Reference Jupiter
  Target Io
  Source Europa
  ActiveProg 1 1
  DataA 0 3 0 0 0 0
  DataB 1 10 65694.09108321882 0 0 4.912908384460053 0 65695.36238997182 0
  DVProg 0 0 0 1
  AdvConf 0 0 1 0 0
  Guidance 0
  END
  EjectMFD V5
  Reference Auto
  Data 0 1 3 0 0 65694.09107173729 2580.86
  Guidance 0
  END
  BaseAprMFD V2
  Reference Auto
  Target none
  Source none
  DataA 0 0 120000 0.10821 0.366519 1 1 65694.06780490864 65694.06780490864 0
  DataB 0 3 0 1 0 1
  END
  SlingMFD V4
  Reference Auto
  Source none
  Data 0 1 1 3 0 1 65694.06780490864 0
  END
  LaunchMFD V4
  Target None
  Data 0 1 1 3 0 1 65694.07153379753
  END
  CF1_DataA 1 0
  CF1_DataB 65694.06707965401 10 120000 1 5 150000
  CF1_SecTgt
  mfdShare -1
  mfdProgram 2
END_MFD

BEGIN_PANEL
END_PANEL


BEGIN_SHIPS
DG-01:Deltaglider
  STATUS Orbiting Europa
  RPOS -1444933.58 87799.79 -717935.29
  RVEL 609.564 9.435 -1250.492
  AROT 179.56 -25.79 177.08
  PRPLEVEL 0:0.925 1:0.998
  NAVFREQ 0 0 0 0
  XPDR 0
END
END_SHIPS

BEGIN_ExtMFD
END

If in the above scenario you start adjusting TIn on the right MFD, the needed dV "jumps" from below 3 km/s to above 3 km/s. The values below 3km/s do not seem to be correct solutions, for example if you perform orbit ejection, you are not going to get near Io. I have also seen such behaviour when planning an Earth-Mars transfer.

2. Switching to a transfer method other than Off-Plane shows very high Plane Change velocities - on the order of magnitude of the source/target orbital velocities. Reproducible in any scenario, including the one above. I believe this problem exists since the first IMFD 5.1 version I tried.

3. CTD if an invalid target name is entered in the Map program.



Post Edited ( 03-27-08 08:44 )

[Cale]

Hi Pirx,

With regards to EIn, it was 5.17..so that's pretty well over 2 8o

Off-axis burn mode was used as well.  According to the instructions I read in the IMFD manual, this was the preferred
method when in LEO..Realtime was more for course-correction burns.  Can't remember if there were any other
options available in this variable (perhaps I could have selected Prograde, if available?).

Turbopump was off.

Cheers,

Cale



Post Edited ( 03-27-08 16:15 )

[jarmonik]

Pirx wrote:
Jarmonik, thank you for joining the discussion and, of course, thank you for the great navigation tool! As I said above
I have no DGIV-specific issues, but I am going to use the opportunity to report 3 problems with IMFD 5.1e:

Thanks about reporting these problems. I have succesfully repeated all of them and I have some ideas about what is
causing them.  But the real problem is that the code of the IMFD is badly broken right now due to code modifications
and I can't build a release for a while. Unless... I am so lucky that I have a backup of 5.1e that is still intact.

[jarmonik]

I was able to find 5.1e backup intact.

[jarmonik]

Hello,

I have uploaded a bugfix release. I haven't implemented fuel-efficiency factor yet but IMFD will display a message if
the factor is other than 1.0
5.1f release should fix the three issues reported earlier and AMSO GET sync problem.

[Pirx]

Jarmonik, thank you for addressing these problems so quickly!


I can confirm that all 3 of them are fixed in 5.1f and also that a message is displayed if fuel efficiency is not 1.0. It seems fuel efficiency > 1 is how DGIV implements its different "Fuel Reserve" settings. For example, it is 1.1 for "Default - ISS & Moon", 1.5 for "Big - Trip to Mars", and so on. But even with 1.5 it does not seem to completely break IMFD operation. I suppose some factor that does not have too big effect, like the rate at which ship's mass changes, is affected. I am definitely not getting 1.5 times the planned dV.

Edit: "does not seem to completely break IMFD operation" above is obviously very bad wording considering that most of my interplanetary travel is done with DGIV in long range configurations. I suppose what I should expect once this efficiency factor is taken into account is off-axis (only?) burns to result in even more precise interception trajectory.



Post Edited ( 03-28-08 19:32 )

[jarmonik]

I have implemented the efficiency factor and uploaded IMFD 5.1g, hopefully it works better.

There seems to be minor bug in DGIV.  Atleast some parts (fuel eff. factor) of the engine configuration defined with
DG4Config.exe seems to become valid after engaging the engines.  So, you must validate the engine configuration by
hiting "+" key after loading a scenario or changing a configuration.

[Pirx]

Well, today I spent some (quite a lot of) time comparing IMFD 5.1f and 5.1g and I must say I was baffled.

The testing was as follows:

1. Load a free-return scenario with a bad (> 7 degrees deviation) orbital plane:

Code: [Select]

BEGIN_DESC
Contains the latest simulation state.
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 60247.3894405706
END_ENVIRONMENT

BEGIN_FOCUS
  Ship DGIV-01
END_FOCUS

BEGIN_CAMERA
  TARGET DGIV-01
  MODE Cockpit
  FOV 40.00
END_CAMERA

BEGIN_HUD
  TYPE Orbit
  REF AUTO
END_HUD

BEGIN_MFD Left
  TYPE User
  MODE Interplanetary
  Scenario Old2
  MapMFD V5
  Reference Auto
  Target moon
  Center Moon
  Data 0 1 3.405705399845423e-005 0 0 0 1 1 1 0 0 0
  MassLimit 1e+020
  CMode 2
  Config 1 1 1 1 600000 0
  ExtMode 2
  Periapis Moon
  END
  CorMFD V4
  Reference Earth
  Target Moon
  Source DGIV-01
  ActiveProg 1 1
  DataA 0 3 1 0 0 0
  DataB 38.443359375 1 60247.39082800243 0 0 1.630883194115738 0 60250.19194185535 0
  DVProg 0 0 0 1
  AdvConf 0 0 5594703.597865339 2 0
  Guidance 1
  END
  EjectMFD V5
  Reference Auto
  Data 0 1 3 0 1 60246.68858318637 10
  Guidance 0
  END
  BaseAprMFD V2
  Reference Auto
  Target none
  Source none
  DataA 0 0 120000 0.10821 0.366519 1 1 60246.68858318637 60246.68858318637 0
  DataB 0 3 0 1 0 1
  END
  SlingMFD V4
  Reference Auto
  Source none
  Data 0 1 1 3 0 1 60246.68858318637 0
  END
  LaunchMFD V4
  Target Moon
  Data 0 1 1 3 1 0 60250.19810109147
  END
  CF1_DataA 1 0
  CF1_DataB 60246.6879950498 10 120000 1 10 150000
  CF1_SecTgt
  mfdShare 1
  mfdProgram 4
END_MFD

BEGIN_MFD Right
  TYPE User
  MODE Interplanetary
  Scenario Old2
  MapMFD V5
  Reference Auto
  Target moon
  Center Moon
  Data 0 1 3.405705399845423e-005 0 0 0 1 1 1 0 0 0
  MassLimit 1e+020
  CMode 2
  Config 1 1 1 1 600000 0
  ExtMode 2
  Periapis Moon
  END
  CorMFD V4
  Reference Earth
  Target Moon
  Source DGIV-01
  ActiveProg 1 1
  DataA 0 3 1 0 0 0
  DataB 38.443359375 1 60247.39082800243 0 0 1.630883194115738 0 60250.19194185535 0
  DVProg 0 0 0 1
  AdvConf 0 0 5594703.597865339 2 0
  Guidance 1
  END
  EjectMFD V5
  Reference Auto
  Data 0 1 3 0 1 60246.68858318637 10
  Guidance 0
  END
  BaseAprMFD V2
  Reference Auto
  Target none
  Source none
  DataA 0 0 120000 0.10821 0.366519 1 1 60246.68858318637 60246.68858318637 0
  DataB 0 3 0 1 0 1
  END
  SlingMFD V4
  Reference Auto
  Source none
  Data 0 1 1 3 0 1 60246.68858318637 0
  END
  LaunchMFD V4
  Target Moon
  Data 0 1 1 3 1 0 60250.19810109147
  END
  CF1_DataA 1 0
  CF1_DataB 60246.6879950498 10 120000 1 10 150000
  CF1_SecTgt
  mfdShare -1
  mfdProgram 2
END_MFD

BEGIN_PANEL
END_PANEL


BEGIN_SHIPS
DGIV-01:DeltaGliderIV
  STATUS Orbiting Earth
  RPOS -1486512.72 -2208571.65 -5947111.70
  RVEL 6963.402 2408.192 -2629.953
  AROT 138.04 -62.75 -120.42
  VROT 0.00 0.07 -0.00
  RCSMODE 2
  PRPLEVEL 0:0.333 1:0.828 2:0.983
  IDS 0:45 100
  NAVFREQ 94 524
  XPDR 0
  ;-------------------------- Skin parameters must contain directory name of skin (without space)
  MeshSkin transworld
  ;-------------------------- Cargo payload must contain name of config file or "none".(see doc)
  CargoPayload DGIVCargoFUEL
  NOSECONE 0 0.00
  GEAR 0 0.00
  AllDoorsState 0 0.00 0 0.00 0 0.00 1 1.00 0 0.00 0 0.00 0 0 0.00
  But1Cockpit 0 0 0 2 2 2 0 2 2 2 2 2 2 2 2 0 1 0 1 1 1 3
  But2Cockpit 0 0 0 0 0 0 0 0 2 2 2 2 2 0 50 0 0 0 1 1 0 0
  TransEffect 0
  LifeBut1State 0 2 1 2 1 2 2 2 2 0 0 0 0 1 0
  LevelBatt 100.0002
  Emergency_power 10000.0000
  VoltageStartBus 0.0000
  VoltageGen1 96.2820
  VoltageGen2 96.2819
  VoltageGenBus 96.0000
  O2tankALevel 91.8696
  N2tankALevel 100.0000
  O2tankBLevel 100.0000
  N2tankBLevel 100.0000
  CabinO2Level 21.3916
  CabinCO2Level 600.0000
  CabinTempLevel 21.2000
  CabinPressure 14.7000
  CabinMoistLevel 36.0000
  CabinDustLevel 0.0001
  CabinO2Setting 21.4000
  CabinTempSetting 21.2000
  CabinPressSetting 14.7000
  AntennaTarget no_target
  O2ConsumptionSetting 1
  FuelConsumptionSetting 1
  MainenginePower 1
  ;------------------Crew parameters  UMMUCREW Function-Name-Age-CardiacPulse-WeightKg (fonction of Pilot must be:
Capt)
  NoOneOnBoard 0
  NoPilotOnBoard 0
  UMMUCREW Capt-Daniel_silva-43-60-73
  UMMUCREW -Erik_Baltzer-31-66-81
  UMMUCREW Capt-Ben_Longden-22-72-76
  UMMUCREW Capt-Kevin_Grace-41-83-79
  FailGearFailure 0
  FailGearCollapse 0
  FailLeftMainEngine 0
  FailRightMainEngine 0
  FailHoverEngine 0
  FailRcs 0
  FailSurfaceControl 0
  FailComputer 0
  FailComputerBlueScreen 0
  FailAutopilot 0
  FailExtRadiator 0
  FailAirbrake 0
  FailNoseCone 0
  FailCanopy 0
  FailAntenna 0
  FailLeftTurbo 0
  FailRightTurbo 0
  FailCargoDoor 0
  SpacesuitTimer 0
END
END_SHIPS

BEGIN_ExtMFD
END

2. Perform a short burn (Ctrl-NumPad-+, NumPad-*) to let IMFD "sniff" the engine.

3. Adjust the offset radius so that on Map (Plan activated) PeA - Moon gets as close to 100.0 km as possible.

4. Perform Auto-Burn, Off-Axis mode.

5. Write down the PeA (Plan deactivated) after the burn.

6. Repeat with FuelConsumptionSetting = 0, 1, 2, 3

I was expecting to see a change from bad to much better but in reality it was from good to nearly perfect



Such a small change simply cannot explain the problem described by Cale. Could it be that IMFD 5.1f already had some changes related to fuel efficiency <> 1.0? I noticed with both 5.1f and 5.1g that after step 2 (short burn) the trajectory displayed on the Map changed. Unfortunately, I did not keep IMFD 5.1e or earlier so I was not able to test them.

There was another test with a trip to Mercury but there was little interesting about it: The PeD (Plan) displayed on the Map immediately before the burn was compared with PeD (actual) after the burn. With 5.1f the difference increased as fuel efficiency increased but stayed below 10%. With 5.1g the difference was below 1% for all DGIV fuel consumption settings.



Post Edited ( 03-29-08 19:10 )

[jarmonik]

That's really nice report Pirx.  It looks like I over estimated the importance of the fuel-efficiency issue and you are right
it's not behind the problem described by Cale. But anyway it's good that the efficiency factor is now implemented.

I did some more testing with DGIV and founded something more critical. If you load a scenario and press (Ctrl-I) to
open an information window.  Maximum thrust of the main engine is 180kN.  When the main engine is engaged the
thrust will change into a one defined in DGIV configuration. This would make the IMFD or any other MFD to use wrong
engine specs unless the engines are use before planning a flight. Also activating the turbo-pump would cause similiar
failure.

[James.Denholm]

jarmonik wrote:
Also activating the turbo-pump would cause similiar failure.

That is a problem, when you consider that the ascent autopilot uses the turbo-pump.

[Pirx]

James.Denholm wrote:
That is a problem, when you consider that the ascent autopilot uses the turbo-pump.

Not really, as for the final adjustments the auto-pilot throttles down. And IMFD, if active, will "see" the correct values for vacuum, turbo off. The real problem we have here is someone caring a bit too much about his post count

jarmonik wrote:
I did some more testing with DGIV and founded something more critical. If you load a scenario and press (Ctrl-I) to open an information window.  Maximum thrust of the main engine is 180kN.  When the main engine is engaged the thrust will change into a one defined in DGIV configuration.

Confirmed. Obviously due to my style of flying the missions without saving and loading too often I did not run into it frequently enough to notice it. So the recommendation is

For each DGIV in the scenario, make sure the engine is fired at least for a short time (Ctrl-NumPad+, NumPad* or just tap NumPad+) after you open IMFD and before you start using it for a first time

right? And we wish Dan success with FsPassengers "X" and hope for at least DGIV.I, which will set the actual engine parameters immediately after the vessel is instantiated. Or is a burn required to obtain the efficiency?



Post Edited ( 03-31-08 04:47 )