Related Manuals for MSA fieldserver FS-8700-144
Summary of Contents for MSA fieldserver FS-8700-144
- Page 1 Driver Manual FS-8700-144 Hochiki Packet APPLICABILITY & EFFECTIVITY Effective for all systems manufactured after September 2022. Driver Revision: 1.00 Document Revision: 2.D Hochiki Packet Driver Manual MSAsafety.com...
- Page 2 MSA Safety 1991 Tarob Court Milpitas, CA 95035 Website: www.MSAsafety.com U.S. Support Information: +1 408 964-4443 +1 800 727-4377 Email: smc-support@msasafety.com EMEA Support Information: +31 33 808 0590 Email: smc-support.emea@msasafety.com Hochiki Packet Driver Manual...
-
Page 3: Table Of Contents
Contents Description ............................4 Driver Scope of Supply ........................4 Provided by the Supplier of 3 Party Equipment ..............4 2.1.1 Required 3 Party Hardware....................4 Hardware Connections ........................5 Data Array Parameters ........................6 Client Side Configuration ........................ 7 Client Side Connection Parameters .................. -
Page 4: Description
Description Description The Hochiki Serial driver allows the FieldServer to read data from Hochiki FireNET panels over RS-232. The FieldServer acts as a Client and reads the event log queue to record the status of the panel and various devices connected to the panel. The protocol used by the FieldServer is independent of the user interface language of the panel. -
Page 5: Hardware Connections
Installing the FieldServer Hardware Connections The FieldServer is connected to the Hochiki panel as shown in the connection drawings below. Configure the Hochiki panel according to manufacturer’s instructions. Hochiki Packet Driver Manual... -
Page 6: Data Array Parameters
Configuring the FieldServer Data Array Parameters Data Arrays are “protocol neutral” data buffers for storage of data to be passed between protocols. It is necessary to declare the data format of each of the Data Arrays to facilitate correct storage of the relevant data. -
Page 7: Client Side Configuration
Configuring the FieldServer Client Side Configuration For detailed information on FieldServer configuration, refer to the FieldServer Configuration Manual. The information that follows describes how to expand upon the factory defaults provided in the configuration files included with the FieldServer (see “.csv” sample files provided with the FieldServer). This section documents and describes the parameters necessary for configuring the FieldServer to communicate with a Hochiki FireNet panel. -
Page 8: Client Side Map Descriptor Parameters
Configuring the FieldServer Client Side Map Descriptor Parameters 5.3.1 FieldServer Specific Map Descriptor Parameters Column Title Function Legal Values Map_Descriptor_Name Name of this Map Descriptor. Up to 32 alphanumeric characters Name of Data Array where data is to One of the Data Array names from Data_Array_Name “Data Array”... -
Page 9: Map Descriptor Examples
Configuring the FieldServer Map Descriptor Example s 5.4.1 Read Event Log Queue This Map Descriptor will read the number of events that exist in the log queue at the panel and then it will read new events one by one and store them on Passive_Client Map Descriptors as described in Section and Section 5.4.3. -
Page 10: Store Slc Loop, Nac Board And Io Board Events
Configuring the FieldServer 5.4.3 Store SLC Loop, Nac Board and IO Board Events These Map Descriptors will be used to store SLC loop, Nac and IO Board events read by ‘Md_1_logEvents’ described in Section 5.4. Refer to Section for details on the data value representing the type of events. // Client Side Map Descriptors Map_Descriptors Map_Descriptor_Name , Data_Array_Name , Data_Array_Offset , Function... -
Page 11: Read Panel Version Information
Configuring the FieldServer 5.4.5 Read Panel Version Information This Map Descriptor will read panel version information and will store it in DA1_Version. This information could be useful for troubleshooting. // Client Side Map Descriptors Map_Descriptors Map_Descriptor_Name , Data_Array_Name , Data_Array_Offset , Function , Node_Name , Hoc_Task... -
Page 12: Useful Features
Additional Information Useful Features Data_Type “Others” The Driver uses the Data_Type parameter in Passive_Client Map Descriptors to determine the location to store data for the known Address_Types (0. 2, 3, 4, 7, 8, 9). If a message is received from another Address_Type, the Driver will not be able to store the data and will print a message which identifies the Address_Type. -
Page 13: Data Synchronization
Additional Information Data Synchronization The Hochiki panel logs event as they occur up to a maximum of 500 events after which the oldest event is overwritten. When the panel is rebooted, it clears the log and logs the first event as “System Initialize”. When the FieldServer is connected to the panel, it will read the first event in the log. -
Page 14: Troubleshooting
Additional Information Troubleshooting Error Messages Error # Screen message Meaning Suggested Solution Screen Correct connection Connection params are %d Non-Standard parameters in HOC_PKT#01 DRIVER %d %d Even/Odd/None connection configuration file if they Timeout=%0.3fs parameters are used. are not as expected. Make sure other protocol Write-thru not Possible. - Page 15 Additional Information Error # Screen message Meaning Suggested Solution Screen Discarding too long packet Received packet is Take a FS Toolbox HOC_PKT#09 DRIVER of %d chars. See Driver too long to process. capture and contact Manual for details. Driver will ignore it. technical support.
-
Page 16: Capturing Events With Address_Type 6
Additional Information Capturing Events with Address_Type 6 Address Type 6 is not one of the known address types and therefore has no allocated Data_Type. During testing it was found that the Hochiki panel logs events for Address Type 6 when a user presses/releases any button on the panel. -
Page 17: Reference
Additional Information Reference Panel Level Events Storage Structure Panel level events include System Initializing, Low Battery Voltage, Battery Disconnected, etc. The number of events of each type is stored in the Data Array as an integer value at the offset reflected in the following table. -
Page 18: Devices Address Reporting Events With Address Type 6
Additional Information Devices Address Reporting Events with Address Type 6 The Driver will store a numeric value in the Data Array depending upon the type of event. Address Device (Button or Input) Description TBL Input RES Input INT Input CNT Input SIL Input Prog Input 1 Prog Input 2...