background image

 

  

 

 

 

 

 

 

 

 

 

 

 

 

A Sierra Monitor Company

APPLICABILITY & EFFECTIVITY 

Effective for all systems manufactured after May 1, 2001 

Instruction Manual Part Number FS-8700-52 

5/22/2002 

 

Driver Manual   

(Supplement to the FieldServer Instruction Manual)

 

 

FS-8700-52 Notifier AM6000 

 

Summary of Contents for FS-8700-52

Page 1: ...y APPLICABILITY EFFECTIVITY Effective for all systems manufactured after May 1 2001 Instruction Manual Part Number FS 8700 52 5 22 2002 Driver Manual Supplement to the FieldServer Instruction Manual FS 8700 52 Notifier AM6000 ...

Page 2: ...BY USER ERROR BOOKMARK NOT DEFINED 3 HARDWARE CONNECTIONS 3 4 CONFIGURING THE FIELDSERVER AS A NOTIFIER AM6000 CLIENT 4 4 1 DATA ARRAYS 4 4 2 CLIENT SIDE NODES 5 4 3 CLIENT SIDE MAP DESCRIPTORS 6 4 3 1 FieldServer Specific Map Descriptor Parameters 6 4 3 2 Driver Specific Map Descriptor Parameters 6 4 3 3 Timing Parameters 7 Map Descriptor Example 8 5 DRIVER NOTES 10 5 1 MAP DESCRIPTOR KEYWORDS 10...

Page 3: ...M6000 driver is a seial driver It allows the FieldServer to transfer data from a Notifier AM6000 panel over either RS232 or RS485 using Notifier AM6000 protocol There are eight RS232 and two RS485 ports standard on the FieldServer The FieldServer can only a passive Client The driver receives messages intended for a system printer interprets these messages by filling in data arrays in the FieldServ...

Page 4: ...server com E mail support fieldserver com Page 2 2 Driver Scope of Supply 2 1 Supplied by FieldServer for this driver FieldServer Technologies PART DESCRIPTION 8915 10 UTP cable 7 foot for RS232 use UTP cable 7 foot for Ethernet connection 8917 02 RJ45 to DB9F Connector adapter 8917 01 RJ45 to DB25M connection adapter SPA59132 RS485 connection adapter Driver Manual ...

Page 5: ...Technologies 1991 Tarob Court Milpitas California 95035 408 262 2299 fax 408 262 9042 Visit our website www fieldserver com E mail support fieldserver com Page 3 3 Hardware Connections Configure the Notifier AM6000 according to manufacturer s instructions ...

Page 6: ...for Notifier AM6000 communications the driver independent FieldServer buffers need to be declared in the Data Arrays section the destination device addresses need to be declared in the Client Side Nodes section and the data required from the servers needs to be mapped in the Client Side Map Descriptors section Details on how to do this can be found below Note that in the tables indicates an option...

Page 7: ... Specify stop bits 1 Protocol Specify protocol used AM6000 Handshaking Specify hardware handshaking None Poll Delay Time between internal polls 0 32000 seconds default 1 second Example Client Side Connections Connections Port Baud Parity Protocol Data_bits Handshaking Poll_Delay P8 2400 Even AM6000 7 None 0 100s 4 3 Client Side Nodes Section Title Nodes Column Title Function Legal Values Node_Name...

Page 8: ...escriptor above Data_Type Data type Register Coil AI DI Length Length of Map Descriptor This value is important when a Block Ack message is received as it tells the driver how much of the data array to zeroise 1 1000 Address Loop Device Address In the format mmnn where mm is the loop number and nn is the device number Together they forma a composite device number 501 302 AM6000 Driver specific par...

Page 9: ...ogies 1991 Tarob Court Milpitas California 95035 408 262 2299 fax 408 262 9042 Visit our website www fieldserver com E mail support fieldserver com Page 7 4 4 3 Timing Parameters Column Title Function Legal Values Scan_Interval Rate at which data is polled 0 1s ...

Page 10: ... must be passive This keyword indicates that this map descriptor will only be used to process device state messages This makes the address and length parameters very important Connects this map descriptor to a node whose name is node_a and thus connects the map descriptor to a port The device address of the first device to be processed by this map descriptor Devices are allocated to loops The devi...

Page 11: ...at will be updated when this map descriptor is used All map descriptors for the AM6000 Notifier driver must be passive When a Block Acknowledge or System Reset message is received the driver will set the portion of the data array DEVICE_STATES_LO OP1 starting at Data_Array_Offset for Length number of elements to zero System Trouble Messages are processed using this map descriptor Only one map desc...

Page 12: ...rs define the range of devices processed using the map descriptor A device address consists of a loop and device number This driver treats the two parts as a single device address Thus loop 5 device 2 becomes address 502 for this driver and a map descriptor with an address of 500 and a length of 100 would process a message from device 2 on loop 5 system trbl System Trouble messages are processed a...

Page 13: ...you want to maintain separate array s for each state the you use this parameter For one device address range you would have multiple map descriptors each with a different AM6000_Status keyword You should note that the keyword erase results in the data array value being set to zero when a message reports the device state as ERASE The keyword eraseon sets the value to one when the same message is re...

Page 14: ...nection to the Am6000 Notifier device Count of received messages and bytes A complete received message is 82 bytes long and thus if all messages are received correctly the byte count should be a multiple of 82 This indicates the number of times a Block Ack or System Reset message have been applied If you have 5 Ackable map descriptors and one Block Ack message was received a count of 5 would be re...

Page 15: ...ent manufacturer adds new features to the protocol FieldServer Technologies needs to be informed of any such messages so that this driver can be updated Secondly you may have omitted to define a map descriptor which tells the driver what to do with the data from an incoming message For example say a map descriptor is defined for address 501 with a length of 50 but a message is received from device...

Page 16: ... that this is the last map descriptor in the csv file The map descriptor requires a data length of at least 82 and when using RUI_Debug you should view the data array in S tring mode The driver will place any ignored messages in this buffer You will be able to read the message in S tring mode an make a decision on the necessary corrective action If there are multiple messages being ignored the buf...

Page 17: ...8 FAILURE OR OVERLOAD ON AUXIL SUPPLY 9 FAILURE ON BATTERY CHARGER 10 DISCONNEC BATT OR FUSE FAILURE 11 BATTERY EXHAUSTED 12 BATTERY CHARGER UNBALANCED 13 AUX SUPPLY DISCONNECTED 14 AUX SUPPLY USER FUSE 15 MAIN SUPPLY USER FUSE 16 SIREN FUSE 17 EARTH TROUBLE 18 SIREN SUPERV LINE INTERRUPTED 19 BATTERY FAILURE 20 WIRE CUT ON LINE 21 SHORT CIRCUIT ON LINE 22 PRINTER OFF LINE BUFFER FULL PAPER END 23...

Reviews: