dectenor1 Posted Thursday at 03:59 PM Posted Thursday at 03:59 PM (edited) You can see the inconsistency here, on the SURV page it shows the ADS-B TRAFFIC OFF, but on the ECAM it shows it as ON Edited Thursday at 04:39 PM by dectenor1
Eddie Posted Thursday at 08:39 PM Posted Thursday at 08:39 PM This is intended behaviour, yes. EddieCommunity Manager IniBuilds Ltd. | inibuilds.com
dectenor1 Posted Thursday at 09:42 PM Author Posted Thursday at 09:42 PM (edited) 2 hours ago, Der Michel said: I think it’s correct as it is; 2 hours ago, Eddie said: This is intended behaviour, yes. My understanding is that this is not correct behaviour. If ADS-B TRAFFIC is set to OFF on SURV page you should never get the ADS-B TRAFFIC ON ECAM memo because the ADS-B TRAFFIC is not ON. It is OFF. The ADS-B TRAFFIC ON memo would appear if XPDR/TCAS is in STBY, but ADS-B TRAFFIC is set to ON on the SURV page. - Non-normal. Normally in TCAS/XPDR STBY, the ADS-B TRAFFIC would be OFF, and so the memo ADS-B TRAFFIC ON is telling you that you have turned ON ADS-B TRAFFIC on the SURV page. Note there would not be a ADS-B TRAFFIC OFF memo, in a normal situation, because it is expected to be OFF Your shot from the FCOM is if ADS-B TRAFFIC on SURV page is set to ON, not to OFF, whist it would be expected to be OFF - i.e. XPDR/TCAS in STBY. As the FCOM shows here: You should actually get ADS-B TRAFFIC OFF as an ECAM memo if the ADS-B TRAFFIC button is OFF but only if XPDR in is Auto and you manually turn off the ADS-B TRAFFIC. Or if the TCAS or XPDR are on STBY in flight - non-normal. Basically any ADS-B TRAFFIC ON or OFF memo is due to a non-normal situation. So as I said it is the wrong way around in the iniBuilds aircraft. We should never see any ADS-B TRAFFIC memo unless we are in a non-normal situation. When it is appearing in the inibuilds is wrong, there should be no MEMO at all. This is because the ADS-B TRAFFIC is OFF on the ground with the XPDR/TCAS in STBY. When we turn the XPDR/TCAS to AUTO, the ADS-B TRAFFIC should turn on (the switch not the MEMO), but there should be no MEMO as it is expected to be ON with XPDR/TCAS in AUTO. If we were then to manually turn OFF the ADS-B TRAFFIC, we should get a ADS-B TRAFFIC OFF MEMO. Conversely, when in XDPR/TCAS in STBY. We should only ever get a MEMO saying ADS-B TRAFFIC ON, if we manually turn on the ADS-B TRAFFIC switch on SURV page. Sorry I am waffling. To summarise. XPDR/TCAS in STBY - Default is ADS-B TRAFFIC switch OFF - Only get a MEMO if we manually turn ON ADS-B TRAFFIC switch on SURV page - MEMO would be ADS-B TRAFFIC ON. XPDR/TCAS in AUTO - Default is ADS-B TRAFFIC switch ON- Only get a MEMO if we manually turn OFF ADS-B TRAFFIC switch on SURV page - MEMO would be ADS-B TRAFFIC OFF. I hope that make sense.... Edited Thursday at 10:50 PM by dectenor1 1
Der Michel Posted yesterday at 05:41 AM Posted yesterday at 05:41 AM I think you nailed it. FCOM's are often not 100% easy written. But your explanation matches fully with airbus philosophy. So @Eddie it's a bug. One of yout technical advisors should be able to confirm it, with a look into the ESLD document.
dectenor1 Posted 17 hours ago Author Posted 17 hours ago (edited) 7 hours ago, Der Michel said: I think you nailed it. FCOM's are often not 100% easy written. But your explanation matches fully with airbus philosophy. Yeah they can take a bit of working out. But I am pretty sure I am correct here, plus rw experience of course. Would be great if @Eddie could acknowledge the change of opinion and forward this one! Edited 17 hours ago by dectenor1
Eddie Posted 15 hours ago Posted 15 hours ago Hello, I've double checked with our team and they assure me the current implementation is the expected behaviour. EddieCommunity Manager IniBuilds Ltd. | inibuilds.com
dectenor1 Posted 9 hours ago Author Posted 9 hours ago 5 hours ago, Eddie said: Hello, I've double checked with our team and they assure me the current implementation is the expected behaviour. I have to disagree here based on real world experience and what the FCOM states, but lets leave it for now, there are more important issues upon which to focus. As ever, thanks for engaging and speaking to the dev team, and thank all for continued work on the A350, we'll get there eventually!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now