Did anyone get it when not arming the cabin doors?

I did not get it in my last flight. One door was closed but not armed.

I have no idea what triggers it, but so far it has worked beautifully each time :-)

Hi all,

 

Didn't I read somewhere that you have to have the "seatbelt" switch set to "Auto" to enable the Cabin Ready signal, but what triggers it to light up I have no idea. I got it on a take off the other day and just before a landing too, perfect!

Guys, seriously...it's not distance to the runway.

Distance may be involved, but that would be distance travelled taxiing, not distance to the runway. As some randomness appears to be involved it's difficult to isolate the logic, and it may be a combination of things, such as flaps set for takeoff. It will be interesting to hear if you've ever got cabin ready before starting to taxi, as per FAA rules you mentioned.

 

Hi all,

 

Didn't I read somewhere that you have to have the "seatbelt" switch set to "Auto" to enable the Cabin Ready signal, but what triggers it to light up I have no idea. I got it on a take off the other day and just before a landing too, perfect!

I use the Seatbelt ON position and still get Cabin Ready.

 

-----

 

I love this touch but the one that makes me smile more is the Cabin Ready chime before landing. It always takes me by surprise, though it seems to come quite late. I usually get it on final approach, I would expect it earlier in the descent. Cabin is usually secure long before the approach starts. Maybe I'm just late putting the seat belt signs on.

I doubt if it as complicated as some of the theories here!

At a certain point in the Start-up checklist the crew will indicate by whatever means for the cabin to initiate the safety briefing. Done properly that should take about 5 minutes. So let's assume it starts during pushback or when the engines are running in the case of rear engined a/c. Part of the taxi check should include e.g. "Steward's report received". In other words the a/c should not procede until the cabin is secure. So in either case shortly after the ground crew have finished the call will be made.

In this example below the call is shortly after the end of the safety briefing finishes (obviously!!). The safety briefing itself is triggered by accumulated points (not shown here) indicating at what stage the start check list has reached triggering a call to the cabin to initiate the briefing. (also not shown here).

<Gauge Name="Safety Vid" Version="1.0">
<Image Name="SWAP.bmp"/>
<Update>
(L:Monitor_Sound, bool)
if{ (L:Sound_BAsafety,enum) ! if{ 0 (>L:Monitor_Sound, bool) 1 (>L:Sound_mes2,enum) (P:local time, seconds) 6.5 + (>L:CAB LIGHT 2,number) and }
}
</Update>

<Element>
      <Select>
         <Value>(L:safety,number)</Value>
         <Case Value="0">
            <Image Name="SWAP.bmp"/>
         </Case>
         <Case Value="1">
            <Image Name="SWAP.bmp"/>
         </Case>
      </Select>
   </Element>

   <Mouse>
<Tooltip>Cabin Safety Briefing</Tooltip>
  <Cursor Type="Hand" /> 
         <Click>1 (>L:Sound_BAsafety,enum)
1 (>L:Monitor_Sound, bool)
</Click>
   </Mouse>
</Gauge>

I doubt if it as complicated as some of the theories here!

At a certain point in the Start-up checklist the crew will indicate by whatever means for the cabin to initiate the safety briefing. Done properly that should take about 5 minutes. So let's assume it starts during pushback or when the engines are running in the case of rear engined a/c. Part of the taxi check should include e.g. "Steward's report received". In other words the a/c should not procede until the cabin is secure. So in either case shortly after the ground crew have finished the call will be made.

In this example below the call is shortly after the end of the safety briefing finishes (obviously!!). The safety briefing itself is triggered by accumulated points (not shown here) indicating at what stage the start check list has reached triggering a call to the cabin to initiate the briefing. (also not shown here).

(L:Monitor_Sound, bool)if{ (L:Sound_BAsafety,enum) ! if{ 0 (>L:Monitor_Sound, bool) 1 (>L:Sound_mes2,enum) (P:local time, seconds) 6.5 + (>L:CAB LIGHT 2,number) and }}               (L:safety,number)                                                                        Cabin Safety Briefing            1 (>L:Sound_BAsafety,enum)1 (>L:Monitor_Sound, bool)

Yes it could be very simple, but there doesn't appear to be one single flight deck action which triggers the cabin to respond a few minutes later. I suppose it could be a closed loop item in the ECL, which would trigger the logic whether the ECL was used or not.

 

It's rather ironic that the very thing we are talking about, the trigger, is "not shown here" in the XML logic you provided.

Hey guys.... I am a mainline flight attendant for US Airways in real life and I am based in Philadelphia, Pennsylvania. 

 

To answer your question, the "Cabin Ready" is actually a button that the head flight attendant pushes in the main control panel (Usually at the 1L door in first class above the jump seat) that tells the flight crew that all duties of preparation of the Galley (Forward, Middle and aft), Emergency Demo has been completed , the passengers are all seated with their seat belts securely fastened, all the bins are closed, all the bags stowed and Exit Row Briefing have all been completed prior to departure (Take Off) and landing and all the flight attendants are seated in their respective jumpseats. This can take anywhere from 10 to 20 minutes depending on the type or aircraft, number of passengers onboard and length of taxi.

 

The flight crew assumes that all pax are seated with their seat belts fastened prior to the aircraft movement. This "Cabin Ready" button doesn't have to be pushed prior to taxi but MUST be pushed prior to entering the active runway and up to 5 minutes prior to landing. If the flight crew doesn't see the Cabin Ready signal during taxi, they will stop the aircraft, call the head flight attendant with a two bell signal and wait for the button to be pushed.

 

They will call the flight attendant through the phone at the 5 minute mark (signaled by four bells) to have him/her have the cabin ready Immediately and push the button. Believe me, it has happened to me a few times because I simply forget to push the button. I hate it when I hear that dreadful bell from the flight deck! :-)

 

This is a simulated event added by PMDG to make the 777 experience more real from the flight attendant perspective. Hope that helps answer your questions!!

 

Reagards,

Llavi01

Awesome reply, Llav01,  thanks!

 

Bruce.

Hey guys.... I am a mainline flight attendant for US Airways in real life and I am based in Philadelphia, Pennsylvania. 

 

To answer your question, the "Cabin Ready" is actually a button that the head flight attendant pushes in the main control panel (Usually at the 1L door in first class above the jump seat) that tells the flight crew that all duties of preparation of the Galley (Forward, Middle and aft), Emergency Demo has been completed , the passengers are all seated with their seat belts securely fastened, all the bins are closed, all the bags stowed and Exit Row Briefing have all been completed prior to departure (Take Off) and all the flight attendants are seated in their respective jumpseats. This can take anywhere from 10 to 20 minutes depending on the type or aircraft, number of passengers onboard and length of taxi.

The flight crew assumes that all pax are seated with their seat belts fastened prior to the aircraft movement. This "Cabin Ready" button doesn't have to be pushed prior to taxi but MUST be pushed prior to entering the active runway and up to 5 minutes prior to landing. If the flight crew doesn't see the Cabin Ready signal during taxi, they will stop the aircraft, call the head flight attendant with a two bell signal and wait for the button to be pushed.

 

They will call the flight attendant through the phone at the 5 minute mark (signaled by four bells) to have him/her have the cabin ready Immediately and push the button. Believe me, it has happened to me a few times because I simply forget to push the button. I hate it when I hear that dreadful bell from the flight deck! :-)

 

This is a simulated event added by PMDG to make the 777 experience more real from the flight attendant perspective. Hope that helps answer your questions!!

 

Reagards,

Llavi01

It's rather ironic that the very thing we are talking about, the trigger, is "not shown here" in the XML logic you provided.

 

I wouldn't say it's "ironic" at all! There are numerous ways it can be triggered. But it can only be triggered once. So, there are a number of parameters that have to be tested. For example, is the a/c on the ground, is the a/c under ground or APU or engine generated power, how many (if any) engines have been started, is pushback approved or under way, has the cabin call button (or intercom) been activated - if so how many times, has the cabin been given the all clear to start the safety briefing. That's the minimum at least!

I wouldn't say it's "ironic" at all! There are numerous ways it can be triggered. But it can only be triggered once. So, there are a number of parameters that have to be tested. For example, is the a/c on the ground, is the a/c under ground or APU or engine generated power, how many (if any) engines have been started, is pushback approved or under way, has the cabin call button (or intercom) been activated - if so how many times, has the cabin been given the all clear to start the safety briefing. That's the minimum at least!

Ironic in the sense you didn't mention the simple trigger but went into some detail about the mechanism. Now you've listed a number of things that are involved as a minimum, so that doesn't seem any more simple than other people were speculating.

As Kyle says, it's definitely not triggered by distance to the runway. I did a little flight yesterday with quite a long pushback and before taxi flow... Before I even started taxiing, the Cabin Ready Message was visible on the MFD.

As Kyle says, it's definitely not triggered by distance to the runway. I did a little flight yesterday with quite a long pushback and before taxi flow... Before I even started taxiing, the Cabin Ready Message was visible on the MFD.

Distance travelled could be still part of the logic. Pushback is also distance travelled. There could be several logical conditions, any one of which could trigger the cabin ready advisory if true. Or it could be something really simple like the aircraft moving starting a randomised timer.

 

I imagine PMDG reading all this speculation with amusement, waiting for someone to come up with the correct answer.

I imagine they have bigger fish to fry, right now.

 

Anyway, I never mentioned distance traveled, I mentioned proximity to the runway. That part only got greater while pushing back...