Laserfiche WebLink
ARIES NETLink DACT DC-OS and DC-03 Protocol Mapping <br /> DC-03 <br /> The following table shows the event type codes for control unit events sent via the DC-03 <br /> protocol. Normal Status is achieved by the clearing of all faults and alarms and transmission of <br /> those clear events to the DACR. <br /> Cor�dition � C.od�e '' <br /> . . <br /> Alarm On FA <br /> Alarm Off FH <br /> Trouble On FT <br /> Trouble Off FJ <br /> Supervisory On FS <br /> Su erviso Off FV <br /> A/C Failure On AT <br /> A/C Failure Off AR <br /> Low Batte Volta e On YT <br /> Low Battery Volta e Off YR <br /> Ground Fault On YP <br /> Ground Fault Off YQ <br /> NAC Trouble On OU <br /> NAC Trouble Off OV <br /> De raded o eration due to micro rocessor failure On YX <br /> De raded o eration Off YZ <br /> Fault/ Loss of phone line#1 (No Dial Tone, Loss of Line LT <br /> Volta e, etc. <br /> Restore Fault/ Loss of phone line#1 (No Dial Tone, Loss of LR <br /> Line Volta e, etc. <br /> Fault/ Loss of phone line#2 (No Dial Tone, Loss of Line LT <br /> Volta e, etc. <br /> Restore Fault/ Loss of phone line #2 (No Dial Tone, Loss of LR <br /> Line Volta e, etc. <br /> Communication failure with MCB YX <br /> Communication Restore with MCB YZ <br /> Alarm/Event Codes Table <br /> The address value is the made up of the control unit node number, 0 to 64, and SLC loop <br /> number and device address in the case of Alarm per Point events. The device address is a <br /> single byte hexadecimal representation of the address(1 —255 maps to 1 —OxFF). <br /> All events shall have a Node Number but that number be zero on control units that are not <br /> networked with other control units. When non-zero, the Node Number is sent using the Area ID <br /> Modifier Code Packet. <br /> Page 4 <br />