Overall System Architecture — purpose?
Visualizes components and their interactions.
Components of central alarm system?
Controller, detectors, display, communication modules.
Hardware modules — interactions?
Modules communicate via RS485 bus and interfaces.
Detector_t structure — role?
Stores detector data: address, type, state, description, timing.
Configuration table — purpose?
Holds all detectors' configs and current statuses.
Detector data fields — examples?
Address, type, state, description, zone, last_seen_tick.
Detector initialization — process?
Load configs from EEPROM and prepare detectors for operation.
Loading configs — source?
From EEPROM/Flash during system startup.
RS485 frame format — start byte?
0xAA header.
RS485 command codes — example?
0x01: poll, 0x02: reset alarm, etc.
Response codes — example?
0x81: normal, 0x82: alarm, 0x83: fault.
CRC validation — purpose?
Ensures data integrity over RS485 frames.
Polling engine — function?
Interrogates detectors and updates statuses.
Alarm handling — steps?
Update detector state, log alarm, display info, activate outputs.
Display_ShowAlarm — displays?
Alarm details: type, address, description, zone, value.
EEPROM storage — purpose?
Persistently saves configuration data across power cycles.
UART config interface — use?
Configure detectors and system via serial commands.
Main loop — tasks?
Polling detectors, updating display, handling events.
Answer 9 questions on Central Alarm System Architecture and Communication.
1. How does the overall system architecture influence the system's effectiveness in detecting alarms?
2. How can the detector configuration table be effectively used during system operation to update detector parameters?
Go over the full study guide for Central Alarm System Architecture and Communication.
Read the study guide →Upload your class notes and Revizly writes your flashcards in about a minute.
Flashcard maker