manualshive.com logo in svg

FieldServer Omron FINS FS-8704-16, Driver Manual

Share
Download
FieldServer Omron FINS FS-8704-16 Driver Manual Download Page 10

FS-8704-16 Omron FINS Manual 

 

 

 

 

Page 7 of 37 

 
 

FieldServer Technologies

 1991 Tarob Court Milpitas, California 95035 USA  

Web

:www.fieldserver.com 

Tel

: (408) 262-2299   

Fax

: (408) 262-9042   

Toll_Free

: 888-509-1970   

email

: [email protected] 

Example 

 

//    Data Arrays 

 

 

Data_Arrays 

 

 

Data_Array_Name, 

Data_Format, 

Data_Array_Length, 

DA_CIO, 

UInt16, 

5143 

DA_WR, 

UInt16, 

511 

DA_HR, 

Uint16, 

511 

DA_DM, 

Uint16, 

32767

 

 

1.06 

Driver Specific FieldServer Parameters 

Section Title 

FieldServer 

Column Title 

Function 

Legal Values 

Title 

Name for FieldServer 

Text 

 

System_Node_Id 

Specify physical node Id on 
network. 
This is the last byte of the 
IP Address of the 
FieldServer.  eg. If 
FieldServer’s IP Address is 
192.168.1.81 then this 
parameter should be set to 
81 

1-126 

 
Example 
 

//    FieldServer Driver specific parameters  
FieldServer 

 

Title, 

System_Node_Id 

Fins Client, 

81 

 

1.07 

Client Side Connection Descriptors 

Section Title 

Adapter 

Column Title 

Function 

Legal Values 

Adapter 

Adapter Name 

N1, N2

2

 

Protocol 

Specify protocol used 

Fins, omn_fins or fins_udp

 

Udp_port_number Specify UDP port number 

0, 

9600 etc

 

 

 

                                                 

2

 

Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for 

details of the ports available on specific hardware.

 

Summary of Contents for Omron FINS FS-8704-16

Page 1: ... A Sierra Monitor Company APPLICABILITY EFFECTIVITY Effective for all systems manufactured after May 1 2004 Driver Manual Supplement to the FieldServer Instruction Manual FS 8704 16 Omron FINS ...

Page 2: ...elated Map Descriptor Parameters 9 4 1 2 Driver Related Map Descriptor Parameters 9 4 1 3 Timing Parameters 10 4 1 4 Map Descriptor Example 1 IO Read 11 4 1 5 Map Descriptor Example 2 IO Write 12 4 1 6 Map Descriptor Example 3 Clock Read 13 4 1 7 Map Descriptor Example 4 Clock Write 13 4 1 8 Map Descriptor Example 5 Read CPU Cycle Times 13 4 1 9 Map Descriptor Example 6 Run Stop PLC 14 4 1 10 Map ...

Page 3: ...408 262 9042 Toll_Free 888 509 1970 email support fieldserver com Appendix A 2 PLC status to execute commands 22 Appendix A 3 End Codes 23 Appendix B Driver Notes 30 Appendix B 1 Data Storage 30 Appendix B 2 Driver stats 32 Appendix B 3 Driver Error Messages 33 Appendix C Troubleshooting tips 35 Appendix C 1 Connection Tips Hints 35 Appendix D Revision History 37 ...

Page 4: ...vices with a remote PLC connected on an Ethernet Network It can also be used by remote devices such as PC s and FieldServer s to transfer data and perform other services The protocol uses the Ethernet protocol called UDP to carry the FINS messages back and forth The UDP protocol is not connection based and reliability is achieved by using confirmation messages This Ethernet Driver can be used to t...

Page 5: ...eldServer Technologies PART Description FS 8915 10 UTP cable 7 foot for Ethernet connection FS 8704 16 Driver Manual 1 02 Provided by the Supplier of 3rd Party Equipment 2 1 1 Required 3rd Party Hardware Part Description 2 1 2 Required 3rd Party Software CX Programmer Software or any other compatible Software by Omron to setup the PLC 2 1 3 Required 3rd Party Configuration The Omron PLC device nee...

Page 6: ...Connections The FieldServer is connected to the PLC as shown in connection drawing Configure the PLC according to manufacturer s instructions to work with other FINS supported device 1 03 Hardware Connection Tips Hints If communication doesn t start check the following 1 Are the FieldServer and PLC on the same network 2 Are all intended Nodes configured to communicate on FINS 3 Are all FINS Nodes ...

Page 7: ...witches If this is not possible then either the IP address table method or the combined method must be used for address conversion For details refer to 4 2 CPU Bus Unit System Setup If the FINS communications service is not being used over the Ethernet network then there is no problem if the node number duplicates that of another Ethernet Unit The node number must still be set from 01 to 7E howeve...

Page 8: ... or 1 All bits in the host number field set to 0 or 1 All bits in the subnet number field set to 1 The beginning of the IP address set to 127 7F Hex Example 127 35 21 16 Note 1 When using the automatic generation method for address conversion set switches 7 and 8 to the same values as the node number setting and set the rest of the host number to zeroes For details regarding the host number refer ...

Page 9: ...Data Arrays Descriptors The configuration file tells the FieldServer about its interfaces and the routing of data required In order to enable the FieldServer for FINS 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 nee...

Page 10: ...rver Text System_Node_Id Specify physical node Id on network This is the last byte of the IP Address of the FieldServer eg If FieldServer s IP Address is 192 168 1 81 then this parameter should be set to 81 1 126 Example FieldServer Driver specific parameters FieldServer Title System_Node_Id Fins Client 81 1 07 Client Side Connection Descriptors Section Title Adapter Column Title Function Legal Va...

Page 11: ...dress Provide IP Address of PLC Eg 192 168 1 105 Node_ID Node number set at PLC The node number should correspond to the last byte of the IP address Eg 105 corresponds to the example IP address above 1 126 Protocol Specify protocol used Fins omn_fins or fins_udp Adapter Specify which port the device is connected to the FieldServer N1 N23 Net_Number Provide the network number of PLC 1 255 Example C...

Page 12: ... in Data Array section above Function Function of Client Map Descriptor RDBC WRBC WRBX 4 1 2 Driver Related Map Descriptor Parameters Column Title Function Legal Values Node_Name Name of Node to fetch data from One of the node names specified in Client Node Descriptor above Data_Type see Note 1 Appendix A 1 Data type CIO WORD WR WORD HR WORD AR WORD EM WORD Length Length of Map Descriptor 1 729 Ad...

Page 13: ...tas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com Unit_Number Unit number of CPU at PLC 0 1 2 etc 4 1 3 Timing Parameters Column Title Function Legal Values Scan_Interval Rate at which data is polled 0 001s ...

Page 14: ...MORY AREA READ 0 Command Name specifies the Main and Sub request codes to make a request to read this memory from PLC Assigning Direct MRC and SRC parameters can replace this parameter See chapter 6 to know valid MRC SRC values to read this CIO memory area This is the logical name of the target device having the parameters defined in section Client Node Descriptors One of the Data Arrays declared ...

Page 15: ... Array will be written to the PLC1 Driver will fetch consecutive 20 Length elements starting from this offset to be written at Node PLC1 Forcing the Driver to issue a write request upon updating this dedicated portion of Data Array In this case first 20 elements comes under dedicated portion for this map descriptor Note If WRBC It will Force the Driver to issue a write request for each Scan_Interv...

Page 16: ... Data_Array_Offset Function Node_Name Length Command_Name Unit_Number CMD_CLKw DA_CLKw 0 WRBX PLC1 7 CLOCK WRITE 0 Note All elements must be updated in DA_CLKw to set the clock as expected Whenever any element updates the Driver will write all seven values to the PLC along with the one updated value If all elements are updated by the upstream device in a single operation then the Driver will also ...

Page 17: ...de_name Length Command_Name Unit_Number CMD_RUN_ST DA_RUN_ST 0 WRBX PLC1 1 RUN STOP 0s The Driver will change PLC modes depending upon the value poked by the upstream device at offset 0 in this case See section Appendix B 1 for values corresponding to PLC modes 4 1 10 Map Descriptor Example 7 Read CPU Status Defining this Map Descriptor Driver reads the CPU status and stores it in the Data Array D...

Page 18: ...s the FieldServer about its interfaces and the routing of data required In order to enable the FieldServer for FINS communications the driver independent FieldServer buffers need to be declared in the Data Arrays section the FieldServer virtual node s needs to be declared in the Server Side Nodes section and the data to be provided to the clients needs to be mapped in the Server Side Map Descripto...

Page 19: ...Legal Values Node_Name Provide name for node Up to 32 alphanumeric characters Node_ID Virtual Node number of FINS server 1 126 Protocol Specify protocol used Fins omn_fins or fins_udp Server_Hold_Timeout Specifies time FieldServer will reserve server side connection while waiting for the Client side to update data in Data_Array if necessary 1 0s Net_Number Provide the network number of FINS Server...

Page 20: ...ction of Server Map Descriptor Server 5 1 2 Driver Specific Map Descriptor Parameters Column Title Function Legal Values Node_Name Name of Node to fetch data from One of the node names specified in Server Node Descriptor above Data_Type see Note1 Appendix A 1 Data type CIO WORD WR WORD HR WORD AR WORD EM WORD Length Length of Map Descriptor 1 to maximum specified in Data Array section above Addres...

Page 21: ...the Data Arrays declared in the Data_Array section Driver will serve client for CIO operations using this Data Array Starting location for data within Data Array Specify the Driver to Serve Clients This is the logical name of the server device having the parameters defined in section Server Node Descriptors Starting Address of the memory area to serve Specify the number of elements number of Words...

Page 22: ...ve the client with a Clock read request See Appendix B 1for further information Map_Descriptor_Name Data_Array_Name Data_Array_Offset Function Node_Name Length Command_Name Unit_Number SRV_CLKr DA_CLKr 0 SERVER PLC1 7 CLOCK READ 0s 5 1 6 Map Descriptor Example 4 Clock Write This Map Descriptor enables the Driver to update Clock information when the Client makes a Clock Write request See section Ap...

Page 23: ... Operating Mode See Appendix B 1 for stored values corresponding to PLC modes Map_Descriptor_Name Data_Array_Name Data_Array_Offset Function Node_Name Length Command_Name Unit_Number SRV_RUN_ST DA_RUN_ST 0 SERVER PLC1 1 RUN STOP 0 5 1 9 Map Descriptor Example 7 CPU Status This Map Descriptor enables the Driver to respond to clients requesting CPU status See Appendix B 1for further information Map_...

Page 24: ... only specify the Memory_Code The Command to be executed Specify either a The command name or b The MRC SRC Pair Memory Type Data_Type Memory_Code Command_Name MRC SRC Address MEMORY AREA READ 1 1 0 6143 CIO WORD B0 MEMORY AREA WRITE 1 2 0 6143 MEMORY AREA READ 1 1 0 511 WR WORD B1 MEMORY AREA WRITE 1 2 0 511 MEMORY AREA READ 1 1 0 511 HR WORD B2 MEMORY AREA WRITE 1 2 0 511 MEMORY AREA READ 1 1 0 ...

Page 25: ...K READ OK OK OK OK OK OK Time Data Access CLOCK WRITE OK OK OK Disabled OK OK CPU UNIT STATUS READ OK OK OK OK OK OK CS1 CJ1 Series Status Reading CYCLE TIME READ OK OK Disabled OK OK OK 5 Access Right at Other Device The Access right at other device column tells whether the CPU Unit can or cannot receive a command when another device has the access right to the CPU Unit 6 UM Read Protection The U...

Page 26: ...e lists the main codes and the sub codes which combine to form the end code response code returned for a FINS command The probable cause and corrections for each error code are also given Depending on the command the destination code will sometimes make a request of another node on a network The other node is referred to as the third Node 8 This section is a reproduction of Section 5 1 3 End Codes...

Page 27: ...mron FINS Manual Page 24 of 37 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com ...

Page 28: ...mron FINS Manual Page 25 of 37 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com ...

Page 29: ...mron FINS Manual Page 26 of 37 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com ...

Page 30: ...mron FINS Manual Page 27 of 37 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com ...

Page 31: ...mron FINS Manual Page 28 of 37 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com ...

Page 32: ...mron FINS Manual Page 29 of 37 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 9042 Toll_Free 888 509 1970 email support fieldserver com ...

Page 33: ...0 email support fieldserver com Appendix B Driver Notes Appendix B 1 Data Storage Clock Information Element Contents 1 Year 4 for 2004 12 for 2012 2 Month 3 Day of Month 4 Hours 5 Minutes 6 Seconds 7 Day of the week Sunday 0 Saturday 6 CPU Cycle Time Element Contents 1 Average Cycle Time 2 Maximum Cycle Time 3 Minimum Cycle Time PLC Mode Stored Value PLC Mode 1 STOP 2 MONITOR 3 RUN CPU Status ...

Page 34: ...10 1 0 1 Cycle Time Over 11 0 12 1 0 1 FALS Error 13 18 0 19 1 0 1 FAL Error 20 Unknown Reserved for System 21 1 0 1 Interrupt Task Error 22 1 0 1 Basic I O Unit Error 23 Unknown Reserved for System 24 1 0 1 PLC Setup Error 25 1 0 1 I O Verification Error 26 1 0 1 Inner Board Error 27 1 0 1 CPU Bus Unit Error 28 1 0 1 Special I O Unit Error 29 1 0 1 Sysmac Bus Error 30 1 0 1 Battery Error 31 1 0 1...

Page 35: ...oses certain key stats in a Data Array if required An upstream device can then monitor these stats Add the following to your configuration file to activate these stats Expose Driver Operating Stats Data_Arrays Data_Array_Name Data_Format Data_Array_Length fins stats UINT32 200 Stat Number Stats Description 0 FINS_BAD_START Number of Messages received with bad start byte 1 FINS_NET Number of Messag...

Page 36: ...r produced by multiple Map Descriptors to produce only one error message on the System Error screen The driver displays subsequent error messages on the Driver Messages screen Note In the actual message you will see that d has been replaced by an integer s by text indicating a data array name or map descriptor name and x by two hex characters Error Message Description and Action Required FINS_UDP ...

Page 37: ...gnored because mismatching for any shown parameters FINS_UDP 23 Err Message Sequence Not Matched Reqd Ext d d MRC 2X SRC 2X MD s Response from PLC ignored because of mismatching request response sequence Id FINS_UDP 24 FYI Bad Start 2X The message was ignored because the first byte was bad FINS_UDP 31 FYI Net_Number set to 1 Node s The Net_Number parameter is 0 or not specified The Driver will aut...

Page 38: ...e 4 Ensure that the Udp_port_number parameter has the correct value in the configuration file 5 Omron PLC s respond to remote FINS polls by sending UDP response messages on the ethernet network The PLC does not use the IP address of the incoming poll to determine the IP address it must respond to The PLC builds the IP address it will send the response to using 1 Its own IP address and the Node ID ...

Page 39: ...92 168 2 33 and Subnet mask 255 255 0 0 The PLC responds to 192 168 2 33 255 0 0 0 192 x x y Where x is always set to zero and y is equal to 34 The PLC obtains the node ID of 34 by inspecting the contents of the poll message Therefore the PLC responds to 192 0 0 34 which is clearly the wrong address and the FieldServer will not see the response Thus if the PLC is using Class A B IP addressing then...

Page 40: ...e wording and included Omron manual excerpts for IP address setting 4 20 04 SSS 0 00 2 Changed section 7 1 4 Value from PLC does not agree with book value Updated section 8 1 Maximum words are 729 Not 750 This is the limit for one UDP message fragment because of FINS and UDP header 4 20 04 SSS 0 00 2 Issued for Release 5 20 04 Meg Meg 0 00 3 Reformatted document Changed language and grammar Improv...

Reviews:

No comments

Brands by name

Popular brands

Load more brands