As usual the solution is simple!!! Thanks Bill.
There are some other anomalies which I'm sure have been noticed before.
When I was setting up the gauges I tested them at various temperatures and noticed that the base EGT is higher then the ambient temperature if it's above 20c. It's obviously built in to the formulation of EGT.
oat 20 > egt 25
oat 25 > egt 35
oat 30 > egt 46
oat 35 > egt 56
oat 40 > egt 67
oat 45 > egt 78
oat 50 > egt 89
It's easy enough to compensate when starting up but not so easy after landing (assuming it's an en route stopover).
And to Geoff. Last night I tested to see how long the temperature actually took to get to the exact level of ambient = 3 days and nights of sim time!!!!
vololiberista
To go right down to ambient would indeed take a good long time. Last time I was in a real 717 cockpit before flight it was the first flight of the day (the aircraft had been sitting on stand for about 8 hours) and the TGT readout was around 30 degrees above ambient...
By the way, how did you 'simulate' your "3 days and nights of sim time". If you are using the same code as mine then the cooling rate will not be affected by the sim rate so that wouldn't make a difference.
In my setup, I have a gauge that runs only during panel loading and it makes an iterative calculation based on a timestamp saved on the last panel save (dsd L:var saving) and the last recorded TGT so that if I stop the engines, exit the flight and then load it some hours later, the TGT will not still be unrealistically hot... (If the panel is loaded with a different aircraft registration then a default of 10 hours cooling is applied)
Having said all that, I agree it was not cooling fast enough from higher temperatures on the ground with the previous code. I am going to modify it a bit so that the cooling rate vs temp difference above 200 is nonlinear.
Geoff

