Merlin negative G cutout too quick?

[WTE_Galway]

Originally Posted by IvanK

A second related document is in the UK National Archives "AVIA 18/1281 Tests of RAE devices for the reduction of "Negative G" engine cutting on merlin engined fighter aircraft". This document details flight test data on 3 devices (Including the Schilling orifice ... though its called the RAE Restrictor .... PC in action back in the 40's).

It compares each of the devices to an unmodified aircraft. In the tables presented the G used to induce cutout are in the order of -0.5G up to -1.5G. Though emphasis of the document is on the time taken to recover from cutout rather than preventing it, despite the document title.

Its worth pointing out that the Shilling modifications (which involved more than just fitting the famous flow constrictor) main effect was to substantially delay the onset of the second stage flooding cut-off. The shilling orifice was a stopgap.

The "Shilling Orifice" did not actually fix the problem, just delayed its onset a few seconds. Sustained inverted flight was still impossible in a Shilling equipped Spitfire, that required a pressure carburetor.

[Crumpp]

which seems a tad excessive.

What you need is a G meter. That does seem kind of excessive. I got the game and can check it out.

[klem]

Originally Posted by Crumpp

What you need is a G meter. That does seem kind of excessive. I got the game and can check it out.

The chart I made is based on acceleration measurements taken from the game and are effectively a G-meter (accelerometer):
cur_Plane.getParameter(part.ParameterTypes.Z_Overl oad, 0); is acceleration in the fore/aft plane
cur_Plane.getParameter(part.ParameterTypes.Z_Overl oad, 1); is acceleration in the lateral plane
cur_Plane.getParameter(part.ParameterTypes.Z_Overl oad, 2); is acceleration in the vertical plane, renamed G-force on the chart.

At the moment of the 0.5G cut there were very small fore/aft and lateral g-forces of -0.04g and +0.02g respectively (slight speed reduction and slight sideslip). Its close enough to indicate that the cutout occurs well before 0.1G.

Readings were taken every 300 mSecs. Unfortunately we cannot add instruments to the cockpit so we can only draw data from the game parameters.

Originally Posted by klem

The chart I made is based on acceleration measurements taken from the game and are effectively a G-meter (accelerometer):
cur_Plane.getParameter(part.ParameterTypes.Z_Overl oad, 0); is acceleration in the fore/aft plane
cur_Plane.getParameter(part.ParameterTypes.Z_Overl oad, 1); is acceleration in the lateral plane
cur_Plane.getParameter(part.ParameterTypes.Z_Overl oad, 2); is acceleration in the vertical plane, renamed G-force on the chart.

At the moment of the 0.5G cut there were very small fore/aft and lateral g-forces of -0.04g and +0.02g respectively (slight speed reduction and slight sideslip). Its close enough to indicate that the cutout occurs well before 0.1G.

Readings were taken every 300 mSecs. Unfortunately we cannot add instruments to the cockpit so we can only draw data from the game parameters.

Ok that already helps a lot. But I still do not know which point the acceleration provided by cur_Plane.getParameter(part.ParameterTypes.Z_Overl oad, 2) corresponds to (I assume z-axis here is body axis not lift-axis which should have to be confirmed by devs too). Does it really correspond to the acceleration measured by the g-meter in the flight tests that stated a 0.1g threshold for the second stage cut-out? It is important to make sure that we do not compare apples with pears.

[klem]

Originally Posted by 41Sqn_Stormcrow

Ok that already helps a lot. But I still do not know which point the acceleration provided by cur_Plane.getParameter(part.ParameterTypes.Z_Overl oad, 2) corresponds to (I assume z-axis here is body axis not lift-axis which should have to be confirmed by devs too). Does it really correspond to the acceleration measured by the g-meter in the flight tests that stated a 0.1g threshold for the second stage cut-out? It is important to make sure that we do not compare apples with pears.

The maddox parameters do not tell us but I assume it is through the CoG. I have to assume that the parameters returned by the game are those used by 1C in development.

As far as I know there is no historical data to identify the location of the accelerometer used in the 1940 tests but it seems reasonable to suppose it would be close to the CoG to aviod variable components like moment arms during rotation. As a repeatable reference it may not have been necessary to measure the g figure at the precise location of the carburettor bowl if the reduced/negative G were induced gradually.

Of course, rapid rotation would create a larger g force at a remote moment arm-end than at the CoG but if the accelerometers in the 1940 tests and the 1C model are both at the CoG then they are a reasonable comparison.

As you say the devs know the answers to this, ours is really a side discussion with proposals wildy varying from "any g reduction" to "-1.5 or more". I just thought readers would be interested to know what the game is telling us.

Is there a way to show the flown z-axis g load while flying, for instance in one of the windows? Would be great to do so for flight testing.

[bolox]

Originally Posted by 41Sqn_Stormcrow

Is there a way to show the flown z-axis g load while flying, for instance in one of the windows? Would be great to do so for flight testing.

you can use a method such as this?
http://simhq.com/forum/ubbthreads.ph...ml#Post3347984

just change parameters to the one(s) you're interested in