FieldServer A Sierra Monitor Company FS-8700-123 Driver Manual Download Page 13 | Manualshive

Page: 13 / 22

background image

FS-8700-123 MetOne Particle Counter Driver Manual

Page 13 of 22

FieldServer Technologies

1991 Tarob Court Milpitas California 95035 USA

Web

: www.fieldserver.com

Tel

: (408) 262 2299

Fax

: (408) 262 2269

Toll Free

: (888) 509 1970

email

: [email protected]

5.9

Map Descriptor Example 6 – Select Device

Device selection is handled automatically by the driver and support for this message is provided mainly for testing purposes. The driver uses the Node_ID
parameter to learn the address/number of the device to be selected. Valid numbers are in the range 1...64. When the device responds, the driver stores the
device number in the Data Array element specified in the configuration.

// Client Side Map Descriptors

Map_Descriptors

Map_Descriptor_Name , Data_Array_Name , Data_Array_Offset , Function , Node_Name , Met1_Function , Length
Select Device

, DA_MODE_CTRL

, 0

, Wrbx

, MET1

, Device Select

, 1

Set length to 1 for this
Met1_Function

The Node_Name connects this Map Descriptor to the Node Descriptor
and that is where the driver finds the Node_ID parameter.

«
...
11
12
13
14
15
...
»

Summary of Contents for A Sierra Monitor Company FS-8700-123

Page 1: ...ABILITY EFFECTIVITY Effective for all systems manufactured after April 2010 Driver Manual Supplement to the FieldServer Instruction Manual FS 8700 123 MetOne Particle Counter HACH Ultra Analytics formerly Pacific Scientific Instruments Standard Protocol FX enhanced ENG110 ...

Page 2: ...ap Descriptor Parameters 9 5 3 3 Timing Parameters 9 5 4 Map Descriptor Example 1 Read Hold or Sample Times from a Device 10 5 5 Map Descriptor Example 2 Write Hold or Sample Times to a Device 11 5 6 Map Descriptor Example 3 Read the operating mode 11 5 7 Map Descriptor Example 4 Start Stop Counting 12 5 8 Map Descriptor Example 5 Change Mode 12 5 9 Map Descriptor Example 6 Select Device 13 5 10 M...

Page 3: ...the configuration of the FieldServer each device is identified by specifying its device number then the sub device code or port number and finally by a device type The device type will be used to interpret the status byte obtained from the device For each configured node each time the FieldServer sends a message to the device it will select the device and the select the sub device or port if speci...

Page 4: ...ONS 3 1 Connection to 2100 Particle Counter R2 R1 Gnd _ Gnd FG _ RS 485 Opto Isolated FieldServer P1 1 8 6 9 Pin Serial Connector on rear of 2100 Device 1 2 9 8 7 5 4 3 R x T x C O M FieldServer Part 8917 16 Pigtail for RJ45 Port Brown Blue white Orange White 6 9 Pin Serial Connector on rear of 2100 Device 1 2 9 8 7 5 4 3 Tx Rx GND OR Connector Pinouts FS Function RJ45 Pin 2100 Pin 2100 Function C...

Page 5: ...ieldserver com 3 2 Connection to 4308 Particle Counter R2 R1 Gnd _ Gnd FG _ RS 485 Opto Isolated FieldServer P1 1 8 8 6 13 Part of 4308 Device Back of Board 3 3 Hardware Connection Tips Hints The 2100 Device auto configures its serial port based on the pins connected There is no explicit setting or selector for RS 232 RS 485 Ensure other pins are not connected The FS 8917 16 cable is not needed fo...

Page 6: ...a Arrays to facilitate correct storage of the relevant data Section Title Data_Arrays Column Title Function Legal Values Data_Array_Name Provide name for Data Array Up to 15 alphanumeric characters Data_Array_Format Provide data format Each Data Array can only take on one format FLOAT BIT UInt16 SInt16 Byte Data_Array_Length Number of Data Objects Must be larger than the data storage area required...

Page 7: ...iver 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 optional parameter with the bold legal value be...

Page 8: ... Title Nodes Column Title Function Legal Values Node_Name Provide name for node Up to 32 alphanumeric characters Node_ID The Device Number 1 64 Protocol Specify protocol used MetOne Connection Specify which port the device is connected to the FieldServer P1 P8 R1 R2 1 PLC_Type Identifies for the driver the family of Particle Counters Manifolds connected to 237 Family 2408 or Manifold 4800 HF CNC E...

Page 9: ...Descriptor See Map Descriptor Example for recommended lengths Met1_Function Specify the function Additional notes and explanations are provided in the examples Refer also to Appendix B 3 Hold Time Mode Count Device Select Current Record SubDevice Port Select DA_Byte_Name A secondary Data Array is specified using this parameter The driver stores the read current record response byte for byte in the...

Page 10: ...set Function Node_Name Met1_Function Length Scan_Interval Read_Time DA_TIMES 0 Rdbc MET1 Hold Time 3 5 0s While not mandatory giving each Map Descriptor a unique name will help to diagnose configuration problems The name of the Node The driver uses this name to link the Map Descriptor to a Node Descriptor where it finds the Device Number specified with the Node_ID parameter The Node Descriptor pro...

Page 11: ...e driver reads the operating mode from the field device The driver stores a single element of data extracted from the response The driver stores a C to indicate the field device is counting a H to indicate the device is holding and an S to indicate that it has stopped If the mode is not recognized the driver stores a If another protocol reads these states from the FieldServer it will probably disp...

Page 12: ...nd to change the mode of the field device The command sent is determined by the value found in the specified Data Array location In this example the function is set to Wrbx This means the command message will be sent each time the value found at the specified offset in the specified Data Array is updated even if it is not changed Client Side Map Descriptors Map_Descriptors Map_Descriptor_Name Data...

Page 13: ...rposes The driver uses the Node_ID parameter to learn the address number of the device to be selected Valid numbers are in the range 1 64 When the device responds the driver stores the device number in the Data Array element specified in the configuration Client Side Map Descriptors Map_Descriptors Map_Descriptor_Name Data_Array_Name Data_Array_Offset Function Node_Name Met1_Function Length Select...

Page 14: ...Offset 0 1 2 3 4 5 6 7 8 9 10 Data Status Byte Date Month Date Day Date Year Time Hours Time Minutes Time Seconds Period Count 1 Count 2 Count 3 5 11 Map Descriptor Example 8 Dumping the Current Record In this example a secondary Data Array has been specified Each time a response is received the driver dumps the response byte for byte the secondary Array in addition to the storage specified in the...

Page 15: ...ot sent in the message from the counter When the driver sees this label it stores the date and time stamp extracted from the record it is processing in 6 consecutive locations in the data array mm dd yy hh mm ss The driver also checks that the value found in the LOC label matches the device port number this is a requirement for storage For example When polling a 2100 connected to a multi port mani...

Page 16: ...ata_Array_Offset Function Node_Name Met1_SubDev_or_Port Address Met1_Function Length Scan_Interval Read Record DA_DATA 0 Rdbc MET1 SubDevice 3 Current Record 20 1 0s 5 14 Map Descriptor Example 11 Selecting a Sub Device Port This procedure is automatic Support for this message is provided for testing purposes only The driver uses the Address parameter to learn the number of the Sub Device or Port ...

Page 17: ...el 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com 6 CONFIGURING THE FIELDSERVER AS A METONE PC SERIAL SERVER The Server side of the driver was developed to support FST s QA program It is not documented or supported If you are interested in using the driver to emulate a MetOne Particle Counter then contact the FST Sales group ...

Page 18: ...b device select message or did not respond to the poll for data or the command poll Exception Stats If the driver selects a device sub device or port and the return code from the device is unexpected the this stat is incrmented by 1 Ignored Stats If the current record is read and there is more data than can be stored than specified by the Length of the Map Descritor then this stat is incremented a...

Page 19: ... is printed when a response to a poll for the Sample Hold time returned a response whose time cannot be correctly understood by the driver If this error occurs rarely it may be a consequence of an occasional corruption If it occurs consistently take a log ensure this event occurs at least once during the log and contact Tech Support The FieldServer web site provide tools and instructions for takin...

Page 20: ...al diagnostics are triggered This should never be the case in an operational system Take a log and contact Tech Support The FieldServer web site provide tools and instructions for taking logs MET1 12 FYI Use an Array called s to expose diagnostic info This message can be ignored For more information read Appendix B 2 MET1 13 Err Node d cant be selected because not defined in config The reported de...

Page 21: ...erating command code of the most recently commanded device sub device port This is done by the Server side of the driver 4 When the driver stores current record counts by label then the driver stores the 1st character of the label here This gets overwritten each time new label data is stored 5 See previous 2nd Character 6 See previous 3rd Character 7 See previous 4th Character 8 Increments by 1 ea...

Page 22: ...h time Client side sends a message this stat increments by the number of bytes in the message 25 Increments by 1 each time a complete response is received from the field device 26 Increments by the number of bytes contained in a complete response received from the field device 27 Increments each time the device responds with to indicate there is no current record Appendix B 3 Sample and Hold Times...

Reviews:

No comments

Related manuals for A Sierra Monitor Company FS-8700-123

Brand: AccuBANKER Pages: 40

Brand: Magner Pages: 10

Brand: Garland Pages: 32

Brand: DIEBOLD NIXDORF Pages: 80

Brand: Veeder-Root Pages: 12

Brand: Polar Electro Pages: 8

CONNECT People Counter

Brand: ratiotec Pages: 20

Brand: Uniwell Pages: 130

Brand: Olympia Pages: 4

Brand: ICT Pages: 12

Brand: JCM Pages: 11

EnergyCam Open Wire

Brand: Fast Forward Pages: 2

Brand: DIEBOLD NIXDORF Pages: 51

Brand: TEC Pages: 97

Brand: Sam4s Pages: 2

Brand: Pergamon Pages: 2

Brand: B+K precision Pages: 23

SurePOS 700 Series

Brand: IBM Pages: 60

Brands by name

0 1 2 3 4 5 6 7 8 9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Popular brands

Load more brands