A321
Flight Crew Air Transport Pilot (ATP)
Confusion; Human-Machine Interface; Troubleshooting
Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
General Declared Emergency
Aircraft
At cruise FL320 we requested FL340 per flt plan; upon starting climb ECAM warning came up stating excessive cabin altitude. We donned masks; and started ECAM actions.  I noticed that the cabin altitude on pressurization system page was steady at 5200 ft; normal for our altitude so I consulted QRH  but found no futher guidance. Upon consulting ECAM non normal supplemental manual; I found further guidance stating to rely on cabin excess altitude warning and not rely on SD [pressurization System Display page] cabin altitude so we declared emergency; performed emergency descent and initiated diversion to our destination which was the nearest suitable airport. Upon reaching 10000' we cancelled emergency and performed a slow descent into [our destination] and landed normally. Aside from conflicting information which caused some confusion initially we found it difficult to get ATIS and comunicate with dispatch due to this aircraft having the new ACARS system which both First Officer and I have little to no experience with other than reading the ops bulletin.
An A321 received an ECAM excessive cabin altitude warning despite the cabin altitude displaying only 5200 MSL.  When researching the dichotomy they determined the ECAM warning takes precedence; declared an emergency; performed an emergency descent and proceeded to the nearest suitable airport; their destination.  A complicating factor for their troubleshooting was a new ACARS interface with which they had minimal training and little experience; thus compromizing their efforts to communicate with the company.