Emsa HS500E manual

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82

Go to page of

A good user manual

The rules should oblige the seller to give the purchaser an operating instrucion of Emsa HS500E, along with an item. The lack of an instruction or false information given to customer shall constitute grounds to apply for a complaint because of nonconformity of goods with the contract. In accordance with the law, a customer can receive an instruction in non-paper form; lately graphic and electronic forms of the manuals, as well as instructional videos have been majorly used. A necessary precondition for this is the unmistakable, legible character of an instruction.

What is an instruction?

The term originates from the Latin word „instructio”, which means organizing. Therefore, in an instruction of Emsa HS500E one could find a process description. An instruction's purpose is to teach, to ease the start-up and an item's use or performance of certain activities. An instruction is a compilation of information about an item/a service, it is a clue.

Unfortunately, only a few customers devote their time to read an instruction of Emsa HS500E. A good user manual introduces us to a number of additional functionalities of the purchased item, and also helps us to avoid the formation of most of the defects.

What should a perfect user manual contain?

First and foremost, an user manual of Emsa HS500E should contain:
- informations concerning technical data of Emsa HS500E
- name of the manufacturer and a year of construction of the Emsa HS500E item
- rules of operation, control and maintenance of the Emsa HS500E item
- safety signs and mark certificates which confirm compatibility with appropriate standards

Why don't we read the manuals?

Usually it results from the lack of time and certainty about functionalities of purchased items. Unfortunately, networking and start-up of Emsa HS500E alone are not enough. An instruction contains a number of clues concerning respective functionalities, safety rules, maintenance methods (what means should be used), eventual defects of Emsa HS500E, and methods of problem resolution. Eventually, when one still can't find the answer to his problems, he will be directed to the Emsa service. Lately animated manuals and instructional videos are quite popular among customers. These kinds of user manuals are effective; they assure that a customer will familiarize himself with the whole material, and won't skip complicated, technical information of Emsa HS500E.

Why one should read the manuals?

It is mostly in the manuals where we will find the details concerning construction and possibility of the Emsa HS500E item, and its use of respective accessory, as well as information concerning all the functions and facilities.

After a successful purchase of an item one should find a moment and get to know with every part of an instruction. Currently the manuals are carefully prearranged and translated, so they could be fully understood by its users. The manuals will serve as an informational aid.

Table of contents for the manual

  • Page 1

    [...]

  • Page 2

    ESCORT MEMORY SYSTEMS HS500E Industrial Ethernet Antenna Operator’s Manual P/N: 17-1305 REV 02 (12/05) Copyright © 2005 Escort Memory Systems, All rights reserved. Escort Memory Systems reserv es the right to make modifications or improvements to its products and/or docu mentation without prior notification. Escort Memory Systems shall not be li[...]

  • Page 3

    HS500E Read/Write Industria l Ethernet Antenna O PERATOR’S M ANUAL How to Install, Configure and Operate Escort Memory Systems’ HS500E Industrial Ethernet Antenna[...]

  • Page 4

    FCC C OMPLIANCE N OTICE FCC Part 15 This equipment has been tested a nd found to comply with the limits for a Class A digital device, pursuant to part 15 of t he FCC Rules. These limits are desi gned to provide reasonable protection against harmful interfer ence in a residential installation. This equipment use s, generates, and can radiate radi o [...]

  • Page 5

    TA B LE OF CONTENTS T ABLE OF C ONTENTS FCC COMPLIANCE NOTICE 4 TABLE OF CONTENTS 5 CHAPTER 1: GETTING STARTED 8 1.1 Introduction 8 1.1.1 Company Background 8 1.1.2 RFID Over view 8 1.2 About this Manual 9 1.2.1 Who Should Read this Manual? 9 1.2.2 HEX Notation 9 1.3 Dimensions & Diagrams 10 1.3.1 Dimensions – Top View 10 1.3.2 Dimensions –[...]

  • Page 6

    TA B LE OF CONTENTS Command F2: Start/Stop Repetitive Command 33 Command F3: Write IP Address 35 Command F4: Reset Battery Counter 37 CHAPTER 4: ERROR CODES 38 4.1 Error Types 38 4.1.1 Syntax Errors 38 4.1.2 RF Response Errors 38 CHAPTER 5: ETHERNET/IP PROTOCOL 39 5.1 Steps to Configure the HS500E 40 5.1.1 HTML Server and OnDemand Overview 40 5.2 H[...]

  • Page 7

    TA B LE OF CONTENTS APPENDIX B: ASCII CHART 61 APPENDIX C: ETHERNET/IP - OBJECT MODEL 63 C.1 Ethernet/IP - Required Objects 64 C.1.1 Identity Object (0x01- 1 Instance) 64 C.1.2 Message Router Object (0 x02) 66 C.1.3 Assembly Object (0x04 – 3 Instances) 66 C.1.4 Connection Manag er Object (0x06) 70 C.1.5 TCP Object (0 xF5 - 1 Instance ) 70 C.1.6 E[...]

  • Page 8

    CHA PTER 1 : GETTING ST ARTED CHAPTER 1: G ETTING S T A R TED 1.1 I NTRODUCTION Welcome to the HS500E Industrial Ethernet An tenna - Operator’s M anual . This manual will assist you in the installation, configuratio n and operation of Escort Memory Systems’ HS500E Industrial Eth e rnet Antenna. The HS500E Ethernet Antenna is a complete rea d/wr[...]

  • Page 9

    CHA PTER 1 : GETTING ST ARTED 1.2 A BOUT THIS M ANUAL This document provides guideline s and in structions on how to install, configure and operate the HS500E Industrial Ethernet Ant enna. Descriptions of the RFID command set are also included, a s are instructions detailing ho w to issue commands from a Host computer to the HS500E. 1 . 2 . 1 Who S[...]

  • Page 10

    CHA PTER 1 : GETTING ST ARTED 1.3 D IMENSIONS & D IAGRAMS 1.3.1 Di m e n s i o n s – T o p V i e w Dimensions – Top View HS500E – OPERA TOR’S MAN UA L P/N: 17-1 305 REV02 (12-05) PA GE 10 O F 82[...]

  • Page 11

    CHA PTER 1 : GETTING ST ARTED 1.3.2 Di m e n s i o n s – S i d e V i e w Dimensions – Side View HS500E – OPERA TOR’S MAN UA L P/N: 17-1 305 REV02 (12-05) PA GE 11 O F 82[...]

  • Page 12

    CHA PTER 1 : GETTING ST ARTED 1 . 3 . 3 Dimensions – Rear V iew (Power & Ethernet) Dimensions – Rear View (Power & E thernet) HS500E – OPERA TOR’S MAN UA L P/N: 17-1 305 REV02 (12-05) PA GE 12 O F 82[...]

  • Page 13

    CHA PTER 1 : GETTING ST ARTED 1.3.4 L E D D e s c r i p t i o n s LED Descriptions HS500E – OPERA TOR’S MAN UA L P/N: 17-1 305 REV02 (12-05) PA GE 13 O F 82[...]

  • Page 14

    CHA PTER 1 : GETTING ST ARTED 1.3.5 A n t e n n a R e a d R a n g e - F r o n t Vi e w NOTE: The range listed above wa s defined in free air. However, proximity to metal, water and RF interference can affect range perfor mance and results. All RFID a pplications should be tested to ensure adequate RF performance can be achieved. HS500E – OPERA TO[...]

  • Page 15

    CHA PTER 1 : GETTING ST ARTED 1.3.6 An t e n n a R e a d R a n g e - S i d e V i e w NOTE : The range listed above wa s defined in free air. However, proximity to metal, water and RF interference can affect range perfor mance and results. All RFID a pplications should be tested to ensure adequate RF performance can be achieved. HS500E – OPERA TOR[...]

  • Page 16

    CHA PTER 1 : GETTING ST ARTED 1.4 I NST ALLA TION & S ETUP 1.4.1 I n s t a l l a t i o n P r e c a u t i o n s Mounting Guidelines  Avoid mounting the HS500E or its RFID controllers near sources of EMI (electro-magnetic interfe r ence) or near devices that generate high ESD (electro-static disc harge) levels.  Do not route cables near u n[...]

  • Page 17

    CHA PTER 1 : GETTING ST ARTED 1.4.2 I n s t a l l i n g t h e H S 5 0 0 E 1 Unpack and inspect the HS500E hardw are and acce ssories. If an item appears to be damaged, notify your EMS distributor immediately. 2 Securely mount the HS500E to your chosen locatio n using four (4) #10 [M5] screws and matching locking wa shers and nuts. The HS500E may be[...]

  • Page 18

    CHA PTER 2: IP CONFIGUR ATION CHAPTER 2: IP C ONFIGURA TION 2.1 T HE HTML S ER VER Built into the HS500E is an embedded HTML Server which provides a Website-like user interface with all of the tools necessary to configu re the unit. The first step in configuring the HS500E is to set its IP address. This particular chapter describes the IP configura[...]

  • Page 19

    CHA PTER 2: IP CONFIGUR ATION Click the link: IP Configuration The HTML Server- Main Page 4 At the HTML Server - Main Page, click the link labeled IP Configuration . The IP Configuration Page will be displayed. You will a rrive at a page similar to the one displayed below. The HTML Server - IP Configuration Page 5 Enter new IP address values in the[...]

  • Page 20

    CHA PTER 2: IP CONFIGUR ATION 6 Click the “ Save Settings” button to store the config uration changes to the HS500E’s non-volatile flash memory. 7 Manually cycle power to the HS500E. It takes 15 – 30 seconds for the HS500E to reboot, at which time your IP configuration changes wil l be implemented. 8 After the HS500E has completely restart [...]

  • Page 21

    CHA PTER 3 : RFID COMM ANDS CHAPTER 3: RFID C OMMANDS 3.1 C OMMAND S TRUCTURE RFID commands a re Host-generated packets of data that contain i nstructions intended for the HS500E. In general, RFID commands adhere to a 6-word minimum packet stru cture, where each word within a packet is com prised of 2-bytes ; a Most Significant Byte ( MSB ) and a L[...]

  • Page 22

    CHA PTER 3 : RFID COMM ANDS 3 . 1 . 1 Command Packet Structure T able Word # MSB LSB Description 01 00 06 (+ number of additional data words, if any) OVERALL LENGTH: The first word in a command packet is the Overall Length . This 2-byte value indicates the total number of words in the comm and (including this - the Overall Length field). This value[...]

  • Page 23

    CHA PTER 3 : RFID COMM ANDS 3 . 1 . 2 Response Packet Structure T able Word # MSB LSB Description 01 00 06 (+ number of returned data words, if any) OVERALL LENGTH: The first word in a response packet is the Overall Length . This 2-byte value indicates the total number of words in the respon se (including this - the Overall Length field). Length wi[...]

  • Page 24

    CHA PTER 3 : RFID COMM ANDS Word MSB # LSB Description 05 (RF Retry) (Reser ved) 0x00 RF RETRY COUNTER: The fifth word contains the RF Retry Counter in the MSB. This counter indicates the number of packets that required re-transmi ssion to successfully compl ete the given command. RESERVED: LSB: 0x00 06 (TT1) (TT2) TOTAL TIME: The sixth word in a r[...]

  • Page 25

    CHA PTER 3 : RFID COMM ANDS 3.2 RFID C OMMANDS The HS500E uses a 2-byte Command ID number to specify the type of operation to perform. Commands 02, 03 and 05 must include the comm and prefix “ AB ” (0xAB), as in AB03 (for Command 03) .These thre e com mands instruct the HS500E to perform standard RFID ope rations such as rea ding from and writi[...]

  • Page 26

    CHA PTER 3 : RFID COMM ANDS C OMMAND 02: R EAD D ATA DESCRIPTION Command 02 instru cts the H500E to retrieve a specified number of bytes from a contiguous (sequential) are a of an RFID tag’s memory. The Read Data command consists of the Overall Length (OAL), the Comm and ID Number, Node ID value, Timeout Value, Start Address and Read Length. The [...]

  • Page 27

    CHA PTER 3 : RFID COMM ANDS Command 02: Read Data – Response Structure Field Name MSB LSB Word Value Overall Length (in word s) 00 08 0008 MSB =RF Error Counter LSB = Command ID Echo 00 02 0002 MSB = Instance Counter LSB = Node ID Echo 01 01 0101 RF Time RFT1 RFT2 XXXX MSB = RF Retry Counter LSB = Reserved 01 00 0100 Total Time TT TT TTTT Returne[...]

  • Page 28

    CHA PTER 3 : RFID COMM ANDS C OMMAND 03: W RITE D ATA DESCRIPTION Command 03 instru cts the HS500E to write segments of data to contiguou s addresses of an RFID tag’s memory. The Write Data comm and consists of an Overall Length, the Command ID, a Timeout Value, Start Address and Write Length, and the Data Byte Value(s) to be written to the tag. [...]

  • Page 29

    CHA PTER 3 : RFID COMM ANDS Command 03: Write Data – Respo nse Structure Field Name MSB LSB Word Value Overall Length 00 06 0006 MSB =RF Error Counter LSB = Command ID Echo 00 03 0003 MSB = Instance Counter LSB = Node ID Echo 01 01 0101 RF Time XX XX XXXX MSB = RF Retry Counter LSB = Reserved 01 00 0100 Total Time TT TT TTTT HS500E – OPERA TOR?[...]

  • Page 30

    CHA PTER 3 : RFID COMM ANDS C OMMAND 05: F ILL T AG DESCRIPTION Command 05 is used to instruct the HS5 00E to write a particular data byte value to all specified contiguous areas of tag memory begi nning at the Start Address. EXAMPLE In this example, the HS500E will write the ASCII character “D” (0x4 4) to 8-bytes of tag memory starting at addr[...]

  • Page 31

    CHA PTER 3 : RFID COMM ANDS C OMMAND F1: T EST LED S / G ET I NFO DESCRIPTION Command F1 tests the HS500E’s LE Ds and re trieves the unit’s currently installed software version number. This comman d causes the HS500E’s LE Ds to flash a coded diagnostic pattern while also retri eving the version number of the installed software. EXAMPLE In thi[...]

  • Page 32

    CHA PTER 3 : RFID COMM ANDS Command F1: Test LEDs / Read Info – Resp onse Structure Field Name MSB LSB Word Value Overall Length 00 06 0006 MSB =RF Error Counter LSB = Command ID Echo 00 F1 00F1 MSB = Instance Counter LSB = Node ID Echo 01 01 0101 Response Data (first word ) 31 2E 312E Response Data (secon d word) 30 41 3041 Response Data (third [...]

  • Page 33

    CHA PTER 3 : RFID COMM ANDS C OMMAND F2: S TART /S TOP R EPETITIVE C OMMAND DESCRIPTION Command F2 is used to instruct the HS500E to continuously repe at a specified RFID command. Note that only Commands 02, 03 and 05 are repeatable. To begin repeating a command, set the Overall Len gth to a value of 0x0006 or greater. To stop this command, ch ange[...]

  • Page 34

    CHA PTER 3 : RFID COMM ANDS Command F2: Repeat Command (Re ad Data) – Response Structure Word # Field Name MSB LSB Word Value 1 Overall Length (in word s) 00 08 0008 2 MSB =RF Error Counter LSB = Command ID Echo 00 02 0002 3 MSB = Instance Counter LSB = Node ID Echo 01 01 0101 4 RF Time XX XX XXXX 5 MSB = RF Retry Counter LSB = Reserved YY 00 YY,[...]

  • Page 35

    CHA PTER 3 : RFID COMM ANDS C OMMAND F3: W RITE IP A DDRESS DESCRIPTION Command F3 is used to modify and st ore the IP address of the HS500E. NOTE: The unit’s IP address can also b e changed using the built-in HTML Server. See Chapter 2 for instructions. Follow the steps below to conf igure the unit’s IP address. S ETTING THE IP A DDRESS OF THE[...]

  • Page 36

    CHA PTER 3 : RFID COMM ANDS R ESPONSE FROM HS500E There is no response for Comm and F3 because as soon as the I P address is changed on the HS500E, the existing TCP /IP connection with the Ho st will be terminated. To reset the IP address of the HS500E to factory default settings see: Appendix A: IP Address Reset . HS500E Factory Default IP Address[...]

  • Page 37

    CHA PTER 3 : RFID COMM ANDS C OMMAND F4: R ESET B ATTERY C OUNTER DESCRIPTION Command F4 resets the value of a tag’s Battery Count er to zero (0x00). This command is intended to be used when replacing the batteries in an active RFI D tag and will reset the value of the Battery Counter to zero (0x00). Located at tag address 0x0000, the Battery Cou[...]

  • Page 38

    CHA PTER 4: ERROR CODE S CHAPTER 4: E RROR C ODES The HS500E will generate an error re sponse if it is unable to complete an operation. When an error occurs, the LSB of the se con d word in a response (the Command Echo word) will be replaced by a 1-byte error code that indicates the actual error that was experienced. 4.1 E RROR T YPES There are bas[...]

  • Page 39

    CHA PTER 5: ETHERNET/IP PROTOCO L CHAPTER 5: ETHERNET/IP PROT OCOL The HS500E is designed to support ma ny common Industrial Ethernet protocols and can be implemented in a wide variety of existing Ho st / PLC Industrial Ethernet applications. One such popular protocol that can be u sed to transfer data over Ethernet to and from the unit is Ethernet[...]

  • Page 40

    CHA PTER 5: ETHERNET/IP PROTOCO L 5.1 S TEPS TO C ONFIGURE THE HS500E See Chapter 2 for instructions o n conf iguring the IP addres s of the HS500E. Sections 5.2 through 5.4 in this chapter will help you accomplish the following:  Configure the HS500E via OnDemand Node Configuration  Create “Controller Tags” in the PLC  Verify PLC and [...]

  • Page 41

    CHA PTER 5: ETHERNET/IP PROTOCO L The OnDemand Co nfiguration Page 3 At the HS500E’s OnDemand Co nfiguration Page , select Node 01 from the drop-down list (Node 01 is sele cted in the image above). 4 Click Submit. The OnDemand Node 01 Configuratio n Page will be displayed. HS500E – OPERA TOR’S MAN UA L P/N: 17-1 305 REV02 (12-05) PA GE 41 O F[...]

  • Page 42

    CHA PTER 5: ETHERNET/IP PROTOCO L 5 . 2 . 2 OnDemand Node 01 Configuration Page The OnDemand No de 01 Configuration Page Use this page to modify the settings for Node 01. Controller Settings 5 Select the Controller Type from the drop-down menu. The Controller Type (in this case) specifies the type of PLC that will be communicating wi th the HS500E.[...]

  • Page 43

    CHA PTER 5: ETHERNET/IP PROTOCO L 9 Write Tag Name / Write File Address: a. For ControlLogix : Specify a Write Ta g Name that is 40 characters or less. The Write Tag Name refers to the name of the Controller Tag in the PLC where the HS 500E will write PLC-bou nd data for Node 01 (example: EMS_WRITE1). Note: this is not to be confused with writing t[...]

  • Page 44

    CHA PTER 5: ETHERNET/IP PROTOCO L 5 . 2 . 3 OnDemand Configuration Page (Summar y) OnDemand Configuration Page When you return to the OnDemand Con figuration Page , you will notice a brief summary (similar to the image above) that displays the current details of the Node configuration settings for the HS500E. HS500E – OPERA TOR’S MAN UA L P/N: [...]

  • Page 45

    CHA PTER 5: ETHERNET/IP PROTOCO L 5.3 C ONFIGURING PLC C ONTROLLER T AGS After you have configured Node 01 via OnDemand Node Configu r ation , open y our PLC control software (RSLogix 5000 for ControlLogix) and define two Controller Tags (a Write Tag and a Read Tag ). Be sure to use the same Write Tag Name and Read Tag Name specified in the OnDeman[...]

  • Page 46

    CHA PTER 5: ETHERNET/IP PROTOCO L 5.4 C HECKING O N D EMAND S TAT U S Now that you have configured Node 01 f or the HS500E and defined corresponding Write and Read Tags in the PLC, the last step is to check the communication status between the HS500E and the PLC.  On the HS500E’s HTML Server - Main Page , click the link labeled: “ OnDemand S[...]

  • Page 47

    CHA PTER 5: ETHERNET/IP PROTOCO L 5.5 U SING THE HS500E WITH RSL OGIX 5000 At this point, communication between t he PLC and the HS500E should be properly configured and a connectio n established. You can verify the exchange of informat ion between devices using RS Logix 5000. Note that under the Ethernet/IP protocol, the HS500E acts as the client [...]

  • Page 48

    CHA PTER 5: ETHERNET/IP PROTOCO L 5.5.1 E t h e r n e t / I P H a n d s h a k i n g To ensure that messages to and from the HS500E are properly delivered and received, a handshaking mech anism has been implemented that uses a pair of dedicated words in the ex change. The first two words in each Cont roller Tag are dedicated to handsh aking. When ne[...]

  • Page 49

    CHA PTER 5: ETHERNET/IP PROTOCO L 3 After executing the command, the HS500E writes the response in the Write Tag and then increment s the counter in EMS_WRITE1 [1]. This signals that there is new information for the PL C (the HS500E g enerated response). 4 After the PLC has processed the response information, it copies the cou n ter from EMS_WRITE1[...]

  • Page 50

    CHA PTER 5: ETHERNET/IP PROTOCO L Write Tag (where responses are w ritten by the HS500E) EMS_Write1 [0] = (2) the counter is copied here by the HS500E to ACK EMS_Write1 [1] = (3) the HS500E increments this count er to signal a respon se is available EMS_Write1 [2] = Data Size EMS_Write1 [3-102] = Data Read Tag (where commands are retri eved by the [...]

  • Page 51

    CHA PTER 5: ETHERNET/IP PROTOCO L 5.6 HTML S ER VER AND O N D EMAND PLC S UPPOR T Below is a partial list of the programmab le logic controllers that are supported by EMS’ HTML Server and OnDemand Utility .  ControlLogix – OnDemand supp orts all current versions  RA’s PLC5E releases: • Series C, Revision N.1 • Series D, Revision E.1[...]

  • Page 52

    CHA PTER 6 : MOD BUS TCP PROTOCO L CHAPTER 6: MODBUS TCP PROT OCOL One of the most popular and well -proven i ndustrial automation protocol s in use today is Modbus. Modbus TCP al lows the Modbus protocol to be carri ed over standard Ethernet networks. 6.1 M ODBUS TCP O VER VIEW Under the Modbus TCP protocol, the HS500E acts as a Modb us Server and[...]

  • Page 53

    CHA PTER 6 : MOD BUS TCP PROTOCO L 4 R/W 2-byte Timeout Value (0-65535) measured in milliseconds 5 R/W 2-byte Read/Write Start Addres s (0-65535) 6 R/W 2-byte Read/Write Data Le ngth (0-65535) 7 – 32774 R/W HS500E Consume Data (when applicable) 32775 – 65536 R/W Reserved Modbus TCP Comm and Structu r e Node 01 Memory Map (Consum e Regi sters) H[...]

  • Page 54

    CHA PTER 6 : MOD BUS TCP PROTOCO L 6 . 1 . 2 Modbus TCP Respon se Structure M APPING N ODE 33 (P RODUCE R EGISTERS ) Produce Registers hold data that is destined for the Host. ModBus Address (4xxxx / 3xxxx) Read / Write Priv ilege Register Description (40001) 1 R/W HS500E Produce Data Overall Length (> 0 indicates that data is available; Modbus [...]

  • Page 55

    CHA PTER 6 : MOD BUS TCP PROTOCO L 6.2 M ODBUS TCP H ANDSHAKING Modbus TCP handshakin g is governed by the changin g of the “ Overall Length ” value within a data packet. The Overall Length value is typically the first 2-bytes of a command or response and indicate s the total number of data words in the packet (including one word for the Overal[...]

  • Page 56

    CHA PTER 6 : MOD BUS TCP PROTOCO L 6 . 2 . 2 Modbus TCP Comman d, Respon se & Handshaking Exam ple 1 The Host issues an RFID comman d to the HS500E, writing the command string to the holding registers for Devi ce ID 1. An Overall Length val ue of 0x06 is written last to holding register 40001. 2 The HS500E recognizes that the Over all Length va[...]

  • Page 57

    CHA PTER 7 : RA W TCP/IP PROTOCOL CHAPTER 7: RA W TCP/IP PROT OCOL 7.1 RA W TCP/IP O VERV IEW Another means of communicating with t he HS500E is through the standard TCP/IP protocol. For this manual, the protocol is referred to a s RAW TCP/IP to distinguish it from the other industrial protocol s. In the RAW TCP/IP environment, the HS500E acts as t[...]

  • Page 58

    CHA PTER 7 : RA W TCP/IP PROTOCOL 7.2 RA W TCP/IP C OMMAND & R ESPONSE E XAMPLES In RAW TCP/IP, RFID commands issued by the Host resemble Modbus TCP commands; howeve r RAW TCP/IP commands re quire an additional tw o-b yt e header (which includ es 0xFF in the MSB, and 0x01 - the Node ID of the HS500E - in the LSB). These two bytes are inserted i[...]

  • Page 59

    CHA PTER 7 : RA W TCP/IP PROTOCOL 7 . 2 . 2 RA W TCP/IP Response Example The following is the respon se to the Read Da ta command issued in the previous example: Word MSB LSB Description 01 FF 01 “Raw TCP/IP” 2-byte Response Header : MSB = 0xFF LSB = Node ID Echo (0x01 for the HS500E) 02 00 09 Ov erall Length of response packet (not including t[...]

  • Page 60

    AP PENDIX A: IP A DDRE SS RES ET A PPENDIX A: IP A DDRESS R ESET To reset the IP address of the HS500E to factory default values, follow the steps below: 1. Disconnect the power supply and remove the Etherne t cable. 2. With a blunt toothpick (or similar non-m etallic object), gently press and hol d the small blue-colored button located within the [...]

  • Page 61

    AP PENDIX B: ASCII CHA RT A PPENDIX B: ASCII C HAR T HS500E – OPERA TOR’S MAN UA L P/N: 17-1 305 REV02 (12-05) PA GE 61 O F 82[...]

  • Page 62

    AP PENDIX B: ASCII CHA RT HS500E – OPERA TOR’S MAN UA L P/N: 17-1 305 REV02 (12-05) PA GE 62 O F 82[...]

  • Page 63

    AP PENDIX C: ETHERNET/IP – O B JECT MODE L A PPENDIX C: E THERNET /IP - O BJECT M ODEL The Object Model is the logical organization of attributes (parameters) withi n classes (objects) and services supp orted by each device. Objects are broken down i nto three categories: Requi red Objec t s , Vendor Specific Objects and Application Objects . [...]

  • Page 64

    AP PENDIX C: ETHERNET/IP – O B JECT MODE L C.1 E THERNET /IP - R EQUIRED O BJECTS Under Ethernet/IP, the HS500E has six Required Objects : Required Objects:  Identity Object (0x01)  Message Router Object (0x02)  Assembly Object (0x04)  Connection Manager Obj e ct (0x06)  TCP Object (0xF5)  Ethernet Link Object (0xF6) C.1.1 Ident[...]

  • Page 65

    AP PENDIX C: ETHERNET/IP – O B JECT MODE L 7 Product Name Structure of: Product Name Size Product Name String USINT USINT[26] 11 “HS500E” Get Status Word Bit Bit = 0 Bit = 1 0 No I/O Connection I/O Connectio n Allocated 1 – 15 Unus ed Unused Common Services Implemented for Service Code Class Level Instance Lev el Service Name 0E HEX Yes Yes[...]

  • Page 66

    AP PENDIX C: ETHERNET/IP – O B JECT MODE L C.1.2 Message Router Object (0x02) This object has no sup ported attributes. C.1.3 A ssembly Object (0x04 – 3 Inst ances) Class Attributes Attribute ID Name Data Typ e Data Value Access Rule 1 Revision UINT 1 Get 2 Max Instance UINT 81 Get Instance 0x64 Attributes (Input Instan ce) Attribute ID Name Da[...]

  • Page 67

    AP PENDIX C: ETHERNET/IP – O B JECT MODE L Instance 0x65 Attributes (Input Instan ce 2) Attribute ID Name Data Ty pe Def ault Data Value Access Rule 3 Serial Produce Data Structure of: Consume Data Seq. Numb er Handshake Produce Data Sequence Numbe r Node 1 Serial Produce Data Size Node 1 Serial Produce Data UINT UINT UINT WORD[100] 0 0 0 All 0?[...]

  • Page 68

    AP PENDIX C: ETHERNET/IP – O B JECT MODE L Instance 0x70 Attributes (Output Ins tance 1) Attribute ID Name Data Ty pe Def ault Data Value Access Rule 3 Serial Consume Data Structure of: Produce Da ta Seq. Number Handshake Consume Data Sequen ce Number Node 1 Serial Consume Da ta Size Node 1 Serial Consume Da ta UINT UINT UINT WORD[100] 0 0 0 All [...]

  • Page 69

    AP PENDIX C: ETHERNET/IP – O B JECT MODE L Instance 0x71 Attributes (Output Ins tance 2) Attribute ID Name Data Ty pe Def ault Data Value Access Rule 3 Serial Consume Data Structure of: Produce Da ta Seq. Number Handshake Consume Data Sequen ce Number Node ID (1-32) Node Serial Consume Dat a Size Node Serial Consume Dat a UINT UINT UINT UINT WORD[...]

  • Page 70

    AP PENDIX C: ETHERNET/IP – O B JECT MODE L C.1.4 Connection Mana ger Object (0x06) This object has no attributes. C.1.5 TCP O bject (0xF5 - 1 Instance) Class Attributes Attribute ID Name Data Typ e Data Value Access Rule 1 Revision UINT 1 Get Instance Attributes Attribute ID Name Data Ty pe Default Data Value Access Rule 1 Status 1 DWORD 1 Get 2 [...]

  • Page 71

    AP PENDIX C: ETHERNET/IP – O B JECT MODE L 5 Interface Configuration 5 Structure of: IP Address Network Mask Gateway Address Name Server Name Server 2 Domain Name Size Domain Name UDINT UDINT UDINT UDINT UDINT UINT STRING 0 0 0 0 0 0 0 Get 6 Host Name 6 Structure of: Host Name Size Host Name UINT STRING 0 0 Get Common Services Implemented for Ser[...]

  • Page 72

    AP PENDIX C: ETHERNET/IP – O B JECT MODE L C.1.6 Ethernet Link Object (0xF6 - 1 Inst ance) Class Attributes Attribute ID Name Data Typ e Data Value Access Rule 1 Revision UINT 1 Get Instance Attributes Attribute ID Name Dat a Type Default Data Value Access Rule 1 Interface Speed 7 UDINT 100 Get 2 Interface Flags 8 DWORD 3 Get 3 Physical Address 9[...]

  • Page 73

    AP PENDIX C: ETHERNET/IP – O B JECT MODE L C.2 V ENDOR S PECIFIC O BJECTS C.21 HS500E Consume Dat a Object (0x64 - 32 Inst ances) Class Attributes (Instance 0) Attribute ID Name Data Ty pe Default Data Value Access Rule 1 Revision UINT 1 Get 2 Maximum Consume Data Buffer Size (in words) UINT 32768 Get 3 Bitmap of Consume Instance s with Data Bit [...]

  • Page 74

    AP PENDIX C: ETHERNET/IP – O B JECT MODE L … … … … … 34 Consume Data [8,000-8,24 9] UINT 0 Get / Set … … … … … 38 Consume Data [9,000-9,24 9] UINT 0 Get / Set … … … … … 42 Consume Data [10,000-10,249] UINT 0 Get / Set … … … … … 82 Consume Data [20,000-20,249] UINT 0 Get / Set … … … … … 122 Consume[...]

  • Page 75

    AP PENDIX C: ETHERNET/IP – O B JECT MODE L Common Services Implemented for Service Code Class Level Instance Lev el Service Name 05 HEX No Yes Reset 10 0E HEX Yes Yes Get Attribute Single 10 HEX No Yes Set Attribute Single 10 This Service Code is used to flush all attributes to zero. HS500E – OPERA TOR’S MAN UA L P/N: 17-1 305 REV02 (12-05) P[...]

  • Page 76

    AP PENDIX C: ETHERNET/IP – O B JECT MODE L C.22 HS500E Produce Dat a Object (0x65 - 32 Inst ances) Class Attributes (Instance 0) Attribute ID Name Data Ty pe Default Data Value Access Rule 1 Revision UINT 1 Get 2 Maximum Produce Data Buffer Size (in words) UINT 32768 Get 3 Bitmap of Produce Instances with Data Bit 0: Instance 1 … Bit 31: Instan[...]

  • Page 77

    AP PENDIX C: ETHERNET/IP – O B JECT MODE L … … … … … 38 Produce Data [9,000-9,249] UINT 0 Get … … … … … 42 Produce Data [10,000-10,249] UINT 0 Get … … … … … 82 Produce Data [20,000-20,249] UINT 0 Get … … … … … 122 Produce Data [30,000-30,249] UINT 0 Get … … … … … 126 Produce Data [31,000-31,249] U[...]

  • Page 78

    AP PENDIX C: ETHERNET/IP – O B JECT MODE L Common Services Implemented for Service Code Class Level Instance Lev el Service Name 05 HEX No Yes Reset 11 0E HEX Yes Yes Get Attribute Single 10 HEX No Yes Set Attribute Single 11 This Service Code is used to flush all attributes to zero. HS500E – OPERA TOR’S MAN UA L P/N: 17-1 305 REV02 (12-05) P[...]

  • Page 79

    AP PENDIX C: ETHERNET/IP – O B JECT MODE L C.23 OnDemand Object (0x67 - 10 Inst ances) Class Attributes (Instance 0) Attribute ID Name Data Ty pe Default Data Value Access Rule 1 Revision UINT 1 Get Instance Attributes (Insta nces 1-32) Attribute ID Name Data Ty pe Default Data Value Access Rule 1 Instance Type (0-3) 0 - Disable 1 – ControlLogi[...]

  • Page 80

    AP PENDIX C: ETHERNET/IP – O B JECT MODE L 14 Write File Offset (SLC/PLC Only) N7:Y where Y is the File Offset UINT 0 Get 15 Write Heartbeat Timeout: 0 = disabled 5-60000 ticks = enable (10ms Resolution) UINT 100 Get 21 Max Read Size in Words 0 – Disable 1 – 100 Words UINT 0 Get 22 Read Tag Name (ControlLogix Only) SHORT STRING 0 Get 23 Read [...]

  • Page 81

    AP PENDIX C: ETHERNET/IP – O B JECT MODE L Common Services Implemented for Service Code Class Level Instance Lev el Service Name 0E HEX Yes Yes Get Attribute Single HS500E – OPERA TOR’S MAN UA L P/N: 17-1 305 REV02 (12-05) PA GE 81 O F 82[...]

  • Page 82

    EMS WAR RANTY EMS W ARRANTY Escort Memory Systems warrants that all products of its own manufacturing conform to Escort Memory Systems’ specifications and are free fr om defects in material and workmanship when used under normal operatin g conditions and within the servi ce conditions for which they were furnished. The obligation of E scort Memor[...]