The following article was created to clarify the differences with Keyscan Aurora software & hardware and how it gets implemented into different installations, particularly with Community or Ambiance
Hardware By Channel
Controller Type | Sold Through Keyscan | Sold Through Multihousing |
1 Door Control | CA150 | COMM-CA150-KIT |
2 Door Control | CA250 | COMM-CA250-KIT |
4 Door Control | CA4500 | COMM_CA4500-KIT |
8 Door Control | CA8500 | COMM-CA8500-KIT |
1 Cab Elevator | EC1500 | COMM-EC1500-KIT |
2 Cab Elevator | EC2500 | COMM-EC2500-KIT |
* Keyscan Aurora KC panels are not currently integration compatible
Hardware Differences
Standard CA/EC Panels | COMM CA/EC Panels |
| Will not natively support Kaba 17 byte credentials, nor the integration | Will not fully support the standard reader format list within Aurora, targeting Kaba 17 byte as the primary reader format |
| Firmware can be upgraded with FWSACU, if the firmware is not v9.47+ and the reader firmware can be upgraded with COMM-CF10010 (CA150) or COMM-CF10004 to work with the integration | Cannot be downgraded to work with a standard Aurora system |
| Work with a variety of Wiegand readers, including those from other manufacturers | Designed for the COMM-SRK family of readers |
Software Differences
Keyscan Aurora | Keyscan Aurora Integration |
| Aurora part number (AURORA) | Aurora part number (COMM-EAURORA-S) |
| System is managed via Keyscan Aurora | Integration is managed via Community or Ambiance |
| People/Credentials are managed within Aurora, allowing optional fields/features to be used | People/Credentials managed within Community or Ambiance, most options fields/features are not available |
| PINs are managed within Aurora | PINs are managed within Community or Ambiance |
| Can utilize Active Directory | Cannot utilize Active Directory |
| Can be adapted to a Community or Ambiance integration with additional licensing and hardware | Cannot be reverted to a non-integrated state |