EICAS Message

[GerdD]

After several days of investigations in Manual and other sources
without having success, have to ask here. Hope the question is not
too trivial.
After some time on my flight from EDDF to KSFO I´m getting the
following EICAS message: "Runway 30 31" referencing to the
message " > Tire Pressure" caused by loosing pressure on a tire
during take off. The pressure-message appeared immediately after
take-off, the Runway-message a long time after.

What exactly does this mean and where can I get reference on this?

Many Thanks
Gerd

[Hardy Heinlin]

"Runway 30 31" is not an EICAS message.

Are you using PSX with an add-on?


Cheers,

|-|ardy

[GerdD]

Are you using PSX with an add-on?


Cheers,

|-|ardy

VisualPSX, TrafficPSX and AdaptPSX.

Gerd

[Hardy Heinlin]

The tire pressure messages are described on page 479.

"Runway 30 31" is certainly generated by an add-on. I can't answer that. I have never supported the idea of allowing non-747 message injections into the flight deck -- they've  pursuaded me to allow it :-)


|-|

[Ray_CYYZ]

The tire pressure messages are described on page 479.

"Runway 30 31" is certainly generated by an add-on. I can't answer that. I have never supported the idea of allowing non-747 message injections into the flight deck -- they've  pursuaded me to allow it :-)


|-|

It would be great if the add on folks could route stuff to the working printer with it's great little tear off sheets of paper that pop up when printed. It just makes more sense and they would have the space to identify the message source.  

[GerdD]

The tire pressure messages are described on page 479.

|-|

Ok, thanks. Understand now that tire pressure message has nothing
to do with the runway message.

@John, @Garry
any idea from You?

Thanks
Gerd

[Jeroen Hoppenbrouwers]

It would be great if the add on folks could route stuff to the working printer with it's great little tear off sheets of paper that pop up when printed. It just makes more sense and they would have the space to identify the message source.  

You know what?  This is probably a truly golden idea!


Hoppie

[Matt Sheil]

Or a simple option on off switch in the ad don
" Send messages to the UEICAS" yes. No

[Jeroen Hoppenbrouwers]

EICAS is ok but should be reserved for simple things that could also be done with a light. Warnings, cautions, that's about it. Especially since there is just one message slot per prio group.

The printer on the other hand gives you in this particular example a perfect report opportunity for what (I presume) VisualPSX tries to tell you, i.e., what runway it has selected and locked in. You can imagine tearing off the paper and sticking it to the check list as part of final check.

Code Select Expand

VISUAL PSX LANDING RUNWAY
Time: xxxx
Position: xx xx.xS xxx xx.xW
Selected runway: ABCD 21R

Runways Nearby:
xx xx xxx xxxxx x x x x xxxx

and then the reason why 21R was selected, for debugging.



Hoppie

[Phil Bunch]

Perhaps the addon(s) could tweet the PF and PNF?  

(insert a friendly grin appropriate for a potentially ineffective satirical humor attempt).

[Jeroen Hoppenbrouwers]

Don't laugh, we have been tweeting OOOI for years during World Flight   :-)

[Phil Bunch]

Is Matt's sim going to be running PSX in this year's World Flight?  (Just wondering...)

[John Golin]

The tire pressure messages are described on page 479.
"Runway 30 31" is certainly generated by an add-on.

Interesting - the only string I send to the EICAS is from AdaptPSX and it is ">SIM FREEZE" - sent as an EICAS caution  - it's not even a variable, it's explicit text.

This is really for the big sims - because Motion freeze stops PSX moving through space, but everything else keeps going, it could be missed by the flightcrew as they don't see the 'MOTION' prompt in PSX.

Or a simple option on off switch in the ad don
" Send messages to the UEICAS" yes. No

AdaptPSX has that option...

[Garry Richards]

The RUNWAY 30 31 EICAS caution message was generated by VisualPSX. It is an undocumented, but delightful and useful feature and is one of three caution messages that VisualPSX could place on the upper EICAS display. Each is automatically removed after 10 seconds. Thanks to Hardy for providing the facility for addons to display messages.  

One or other of these messages will be displayed when VisualPSX cannot exactly match an FSX airport code and runway number with those provided by PSX. The purpose of the message is to alert the pilot that there is no exact match between PSX and FSX runways and that the runway offset may be incorrect.

The cause may be as simple as the runway being approached may be labelled 30 in PSX and 31 in FSX or it may be that the FSX airport has a different ICAO code. In such cases the pilot will be forewarned that the FSX aircraft will be aligning with a runway that doesn't match the PSX airport and/or runway name.

This feature exists in VisualPSX because the FSX runway database was never accurate and has never been updated. Real world airports are continuously undergoing changes such as creating and removing runways and taxiways and renumbering runways when a new parallel runway is added. PSX reflects these changes but FSX does not.

The EICAS caution messages that could appear are:

1
RUNWAY 27L 27, indicating that PSX is using runway 27L, but the matching FSX runway is called 27. They might be the same runway with different numbers or there might be no such runway in FSX and the offset will be aligning the FSX aircraft with a different runway. An example would be where the original real world runway was numbered 27, but is now 27R because a new runway 27L has been constructed. In this situation PSX would still land on 27L while the FSX aircraft landed on the original runway 27.

2
ARPT ABCD EFGH, where ABCD is the airport code used by PSX and EFGH is the best airport match for the specified runway. In this case the runways would match, but not the airport codes. They would probably be the same airport with different codes.

3
ABCD27L EFGH27, indicating that PSX is using runway 27L at airport ABCD, but FSX has matched runway 27 at airport EFGH.

Oh the joy of dealing with offsets and obsolete scenery databases!

[John Golin]

... undocumented...

Aha! Garry's fault

Garry - would it be a good idea to prefix it with something to show it is not a PSX generated message?   I prefix with a generic 'SIM' as the message relates to a Simulator function not the aircraft systems themselves...  I didn't really want to put ADAPTPSX or ADDON - too long...

A generic ADD?
Or VIS?
Or EXT? (External)

e.g.

SIM RWY 30 31
VIS RWY 30 31
ADD RWY 30 31
EXT RWY 30 31


>ADD FREEZE
>EXT FREEZE

Though I fear you will run our of characters... maybe just one letter - X?

X RWY 30 31

>X FREEZE

I originally floated 'SIM' as a suggestion for addons, but that may not be the best solution as it uses 4 characters (SIM+ space )

[Phil Bunch]

What about using non-standard colors for the external text string?  Something like "screaming neon green", perhaps blinking, would get the pilot's attention, for sure.  

As usual, just a thought, not even a suggestion due to my multi-faceted ignorance.

[Matt Sheil]

Is Matt's sim going to be running PSX in this year's World Flight?  (Just wondering...)

Maybe  

[Hardy Heinlin]

Double caret:

Code Select Expand

>>RWY 31 32


Or parantheses:

Code Select Expand

(RWY 31 32)


Or a pair of dashes:

Code Select Expand

-RWY 31 32-


Double slash:

Code Select Expand

//RWY 31 32

[Jeroen Hoppenbrouwers]

Caret the other way ...  very subtle, and does suggest to look in other doc than the QRH.

Code Select Expand

[John Golin]

Double caret:

Code Select Expand

>>RWY 31 32


Or parantheses:

Code Select Expand

(RWY 31 32)


Or a pair of dashes:

Code Select Expand

-RWY 31 32-


Double slash:

Code Select Expand

//RWY 31 32

All better suggestions than mine  dammit  :evil:  

I like the parentheses...


edit:

Caret the other way ...  very subtle, and does suggest to look in other doc than the QRH.

Code Select Expand





I like that too - and it's only one character...

In fact Hardy could even force it as his end if he wanted to make sure people included such an indicator...