Omron 6CYCIDV6400304 RF ID Transmitter User Manual users manual

Omron Corporation RF ID Transmitter users manual

users manual

ÇÕǹÇ?Ç ëÊ 1 èÕ ëÊ 2 èÕ ëÊ 3 èÕ ëÊ 4 èÕINTRODUCTIONSECTION 1 SECTION 2 SECTION 3 SECTION 4 SECTION 5 SECTION 6IntroductionSECTION 1SECTION 2SECTION 3SECTION 4SECTION 5SECTION 6Table of Contents/Precautions on SafetyProduct OutlineInstallation and Connections/WiringPreparing for CommunicationsReading from/Writing to ID TagsTroubleshootingAppendixCIDRW SystemV640-HAM11 Amplifier UnitV640-HS61 CIDRW HeadV700-L22 CIDRW ControllerV700-L11 Link UnitUser's Manual
2222INTRODUCTIONWarranty, Limitations of Liability, Application Considerations DisclaimersCIDRW SystemUser’s ManualINTRODUCTIONWarranty, Limitations of Liability, Application Considerations DisclaimersPlease read and understand this manual before storing, installing, programming, operating, maintaining, or disposing ofthe products. Please consult your OMRON representative if you have any questions or comments.OMRON's exclusive warranty is that the products are free from defects in materials and workmanship for a period of oneyear (or other period if specified) from date of sale by OMRON.OMRON MAKES NO WARRANTY OR REPRESENTATION, EXPRESS OR IMPLIED, REGARDING NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR PARTICULAR PURPOSE OF THE PRODUCTS.  ANYBUYER OR USER ACKNOWLEDGES THAT THE BUYER OR USER ALONE HAS DETERMINED THAT THEPRODUCTS WILL SUITABLY MEET THE REQUIREMENTS OF THEIR INTENDED USE.  OMRON DISCLAIMS ALLOTHER WARRANTIES, EXPRESS OR IMPLIED.OMRON SHALL NOT BE RESPONSIBLE FOR SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES, LOSS OFPROFITS OR COMMERCIAL LOSS IN ANY WAY CONNECTED WITH THE PRODUCTS, WHETHER SUCH CLAIM ISBASED ON CONTRACT, WARRANTY, NEGLIGENCE, OR STRICT LIABILITY.In no event shall the responsibility of OMRON for any act exceed the individual price of the product on which liability isasserted.IN NO EVENT SHALL OMRON BE RESPONSIBLE FOR WARRANTY, REPAIR, OR OTHER CLAIMS REGARDING THEPRODUCTS UNLESS OMRON'S ANALYSIS CONFIRMS THAT THE PRODUCTS WERE PROPERLY HANDLED,STORED, INSTALLED, AND MAINTAINED AND NOT SUBJECT TO CONTAMINATION, ABUSE, MISUSE, ORINAPPROPRIATE MODIFICATION OR REPAIR.Read and Understand this ManualWARRANTYLIMITATIONS OF LIABILITY
3333CIDRW SystemUser’s ManualINTRODUCTIONWarranty, Limitations of Liability, Application Considerations DisclaimersINTRODUCTIONOMRON shall not be responsible for conformity with any standards, codes, or regulations that apply to the combination ofthe product in the customer's application or use of the products.At the customer's request, OMRON will provide applicable third party certification documents identifying ratings andlimitations of use that apply to the products. This information by itself is not sufficient for a complete determination of thesuitability of the products in combination with the end product, machine, system, or other application or use.The following are some examples of applications for which particular attention must be given.  This is not intended to bean exhaustive list of all possible uses of the products, nor is it intended to imply that the uses listed may be suitable for theproducts:• Outdoor use, uses involving potential chemical contamination or electrical interference, or conditions or uses notdescribed in this manual.• Nuclear energy control systems, combustion systems, railroad systems, aviation systems, medical equipment,amusement machines, vehicles, safety equipment, and installations subject to separate industry or governmentregulations.• Systems, machines, and equipment that could present a risk to life or property.Please know and observe all prohibitions of use applicable to the products.NEVER USE THE PRODUCT FOR AN APPLICATION INVOLVING SERIOUS RISK TO LIFE OR PROPERTY WITHOUTENSURING THAT THE SYSTEM AS A WHOLE HAS BEEN DESIGNED TO ADDRESS THE RISKS, AND THAT THEOMRON PRODUCTS ARE PROPERLY RATED AND INSTALLED FOR THE INTENDED USE WITHIN THE OVERALLEQUIPMENT OR SYSTEM.OMRON shall not be responsible for the user's programming of a programmable product, or any consequence thereof.SUITABILITY FOR USEPROGRAMMABLE PRODUCTS
4444INTRODUCTIONWarranty, Limitations of Liability, Application Considerations DisclaimersCIDRW SystemUser’s ManualINTRODUCTIONWarranty, Limitations of Liability, Application Considerations DisclaimersPerformance data given in this manual is provided as a guide for the user in determining suitability and does not constitutea warranty. It may represent the result of OMRON's test conditions, and the users must correlate it to actual applicationrequirements. Actual performance is subject to the OMRON Warranty and Limitations of Liability.Product specifications and accessories may be changed at any time based on improvements and other reasons.It is our practice to change model numbers when published ratings or features are changed, or when significantconstruction changes are made.  However, some specifications of the product may be changed without any notice.  Whenin doubt, special model numbers may be assigned to fix or establish key specifications for your application on yourrequest. Please consult with your OMRON representative at any time to confirm actual specifications of purchasedproduct.Dimensions and weights are nominal and are not to be used for manufacturing purposes, even when tolerances areshown.The information in this document has been carefully checked and is believed to be accurate; however, no responsibility isassumed for clerical, typographical, or proofreading errors, or omissions.PERFORMANCE DATACHANGE IN SPECIFICATIONSDIMENSIONS AND WEIGHTSERRORS AND OMISSIONS
5CIDRW SystemUser’s ManualINTRODUCTIONPrecautions for Safe UseINTRODUCTIONApplicable Standards1. FCC Rules (Federal Communications Commission)This device complies with Part 15 Subpart C of the FCC Rules.FCC ID: E4E6CYCID6400202Operation is subject to the following two conditions:(1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired oper-ation.FCC NOTICEThis equipment has been tested and found to comply with the limits for a Class B digital device, pursu-ant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection againstharmful interference in a residential installation.This equipment generates, uses and can radiate radio frequency energy and, if not installed and usedin accordance with the instructions, may cause harmful interference to radio communications. How-ever, there is no guarantee that interference will not occur in a particular installation. If this equipmentdoes cause harmful interference to radio or television reception, which can be determined by turningthe equipment off and on, the user is encouraged to try to correct the interference by one or more ofthe following measures: • Reorient or relocate the receiving antenna• Increase the separation between the equipment and receiver.• Connect the equipment into an outlet on a circuit different from that to which the receiver isconnected.• Consult the dealer or an experienced radio/TV technician for help.  FCC WARNINGChanges or modifications not expressly approved by the party responsible for compliance could voidthe user's authority to operate the equipment.Properly shielded and grounded cables and connectors must be used for connection to hostcomputer and/or peripherals in order to meet FCC emission limits.CAUTIONThis device must be professionally installed.This CIDRW Head [Model: V640-HS61 (-X)] is dedicated to Amplifier Unit [Model: V640-HAM11 (-X)]. E4E6CYCIDV6400304Do not remove the ferrite core on the cable of the CIDRW head.
7CIDRW SystemUser’s ManualINTRODUCTIONPrecautions for Safe UseINTRODUCTIONApplicable SEMI StandardsThis CIDRW system complies with the following standards.• SEMI E99 THE CARRIER ID READER/WRITER FUNCTIONAL STANDARD• SEMI E5 EQUIPMENT COMMUNICATION STANDARD 2 MESSAGE CONTENT (SECS II)• SEMI E4 EQUIPMENT COMMUNICATION STANDARD 1 MESSAGE TRANSFER (SECS I)SEMI is the acronym for Semiconductor Equipment and Materials International.SECS is the acronym for SEMI Equipment Communications Standard.
8INTRODUCTIONPrecautions for Safe UseCIDRW SystemUser’s ManualINTRODUCTIONPlease observe the following precautions for safe use of the products.• Do not insert water or wires through gaps in the case.  This could cause fire or electric shock.• In the event of a malfunction, stop using the product immediately, turn off the power, and consult yourOMRON dealer.• Dispose of this product as industrial waste.Precautions for Safe Use
9CIDRW SystemUser’s ManualINTRODUCTIONPrecautions for Safe UseINTRODUCTIONPlease observe the following precautions to prevent failure to operate, malfunctions, or undesirable effects onproduct performance.Installation SiteInstall the product at a location where:• It is not exposed to direct sunlight.• It is not exposed to corrosive gases, dust, metal chips, or salt.• The working temperature is within the range stipulated in the specifications.• There are no sudden variations in temperature (no condensation).• The relative humidity is within the range stipulated in the specifications.• No vibration or shock exceeding the values stipulated in the specifications is transmitted directly tothe body of the product.• It is not subject to splashing water, oil, or chemical substances.Mounting• This product communicates with ID Tags using the 134 kHz frequency band.  Note that some trans-ceivers, motors, monitoring equipment, and power supplies (power supply ICs) generate electricalwaves (noise) that interfere with communications with ID Tags.  If you are using the product in thevicinity of any of these devices, check the effect on communications in advance.• In order to minimize the effects of noise, ground nearby metal bodies with a grounding resistance notexceeding 100 ohms.• When mounting Amplifier Units, tighten the screws with a torque no greater than 1.2 N·m.• When mounting CIDRW Heads, tighten the screws with a torque no greater than 0.6 N·m.• When multiple CIDRW Heads are mounted next to each other, communications performance couldbe impaired by mutual interference.  Note the information in this manual on mutual interference wheninstalling multiple heads.Refer to page 115.Precautions for Correct Use
10INTRODUCTIONPrecautions for Safe UseCIDRW SystemUser’s ManualINTRODUCTIONPower and Ground Cables• Use the power supply voltage specified in this manual.• Ensure correct polarity when connecting to the +/- power supply terminals.• The ground terminals must be connected to a ground with a grounding resistance not exceeding 100ohms.Wiring Work• Always turn the power off before starting wiring work or connecting/disconnecting cables.• Do not run high-voltage lines and power lines though the same conduit.• To prevent damage by static electricity, wear a wrist strap or equivalent, and take measures to pre-vent charging, before touching terminal components or parts inside connectors.Screw Locking Adhesive• Screw locking adhesive (screw lock) may cause deterioration and cracking of resin parts: do not useit for screws in resin parts or anywhere where resin washers are used.Cleaning• Do not use organic solvents such as thinner or benzene.
11CIDRW SystemUser’s ManualINTRODUCTIONPrecautions for Safe UseINTRODUCTIONEditor’s NoteVisual AidsIndicates an explanation of a point that must be observed to ensure that the product is capable of its proper functions and perfor-mance.  Read this information carefully and follow the cautions: if the product is used incorrectly, data or the equipment itselfcould be destroyed.Indicates summaries of points of particular importance relating to product performance, e.g. points to note during operation andadvice on how to use the product.Indicates the number of a page where related information can be found.Indicates information for reference when you encounter a problem.Indicator StatusesThe following symbols are used to show the status of the indicators on the CIDRW Controller and AmplifierUnits.OFFFlashingON
12INTRODUCTIONTable of ContensCIDRW SystemUser’s ManualINTRODUCTIONTable of ContentsTable of ContentsIntroduction 3Read and Understand this Manual 2WARRANTY 2LIMITATIONS OF LIABILITY 2SUITABILITY FOR USE 3PROGRAMMABLE PRODUCTS 3PERFORMANCE DATA 4CHANGE IN SPECIFICATIONS 4DIMENSIONS AND WEIGHTS 4ERRORS AND OMISSIONS 4Applicable Standards 5Applicable SEMI Standards 7Precautions for Safe Use 8Precautions for Correct Use 9Editor’s Note 11Table of Contents 12SECTION 1 Product Outline 15What is a CIDRW System? 16Features 17System Configuration 18Component Names and Functions 19Flowchart for Getting Started 23SECTION 2 Installation and Connections/Wiring 25Installation 26Connections and Wiring 31SECTION 3 Preparing for Communications 47Set the Communications Conditions for the CIDRW Controller 48Set the Communications Conditions for Amplifier Units 61Set the Communications Conditions for Link Units 63Communications Test 65
13CIDRW SystemUser’s MaualINTRODUCTIONTable of ContentsINTRODUCTIONTable of ContentsSECTION 4 Reading from/Writing to ID Tags 69When SECS is Used 70When SECS is Not Used 81SECTION 5 Troubleshooting 91When SECS is Used 92When SECS is Not Used 98SECTION 6 Appendix 103Specifications and Dimensions 104System Configuration Examples 108Characteristic Data depending on Conditions of Use 110Data Segment Area 122Regular Inspection 123SECS Protocol Specifications 124ASCII Code Table 129Protective Construction 130Revision History 134
14INTRODUCTIONTable of ContensCIDRW SystemUser’s ManualINTRODUCTIONTable of ContentsMEMO
SECTION 1Product Outline15CIDRW SystemUser’s ManualSECTION 1Product OutlineWhat is a CIDRW System? 16Features 17System Configuration 18Component Names and Functions 19Flowchart for Getting Started 23
16SECTION 1What is a CIDRW System?CIDRW SystemUser’s ManualSECTION 1Product OutlineWhat is a CIDRW System?The CIDRW system writes data to, and reads data from, the carrier IDs (ID Tags) mounted on the carriers(FOUP) in semiconductor manufacturing processes without contacting these ID Tags.  CIDRW is theabbreviation of "Carrier ID Reader/Writer" and this abbreviation is used throughout this manual.Reading and writing information such as models, process instructions, lots, and inspection results to and fromID Tags makes it possible to manage work instruction information from a host device.Example:  Management of information in semiconductor and wafer manufacturing processesID Tag(holder is separate)CIDRW HeadReading and writing information• Model information• Process instruction information• Completion information• Lot information• Inspection resultsEtc.HostAmplifier UnitCIDRW Controller
17CIDRW SystemUser’s MaualSECTION 1FeaturesSECTION 1Product OutlineFeaturesCIDRW Systems that Conform to SEMI Standards (SEMI E99, E5, E4)List of Applicable Standards• SEMI E99 THE CARRIER ID READER/WRITER FUNCTIONAL STANDARD• SEMI E5 EQUIPMENT COMMUNICATION STANDARD 2 MESSAGE CONTENT (SECS II)• SEMI E4 EQUIPMENT COMMUNICATION STANDARD 1 MESSAGE TRANSFER (SECS I)SEMI is the acronym for Semiconductor Equipment and Materials International.SECS is the acronym for SEMI Equipment Communications Standard.HostSECS I/IICIDRW ControllerV700-L22Amplifier UnitV640-HAM11CIDRW HeadV640-HS61ID TagRI-TRP-DR2B(Made by Texas Instruments)CIDRW System Conforming to SEMI StandardsRS-232C RS-232C
18SECTION 1System ConfigurationCIDRW SystemUser’s ManualSECTION 1Product OutlineSystem ConfigurationWhen SECS is UsedCommunication with the host device is possible using the SECS protocol.When SECS is Not UsedCommunications with the host device follow the OMRON proprietary protocol.The Amplifier Units are connected directly to the host device without using a CIDRW Controller.These are antennae forreading the carrier IDsfrom the ID Tags andwriting the carrier IDs.These are units thatcontrol a CIDRW Head. This is e.g. a host,or equipment con-troller.CIDRW HeadV640-HS61Amplifier UnitV640-HAM11CIDRW ControllerV700-L22HostMultiple Amplifier Units are controlled in response to commands (SECS) from the host device.RS-232CSECS I/II RS-232CThese are antennae forreading the carrier IDsfrom the ID Tags andwriting the carrier IDs.These are units thatcontrol a CIDRW Head. This is e.g. a host,or equipment con-troller.CIDRW HeadV640-HS61Amplifier UnitV640-HAM11HostRS-232COMRON proprietary protocol
19CIDRW SystemUser’s MaualSECTION 1Component Names and FunctionsSECTION 1Product OutlineComponent Names and FunctionsCIDRW Controller  V700-L22No. Name Function1 Power indicator (green) An LED that indicates whether the power is ON or OFF. Lit while the power is ON.2 OPERATING indicator (green) Lit while the CIDRW system status model is operating.3 ALARMS indicator (green) Lit when the status of "AlamStatus" of the CIDRW system is "Alarm (1)."4 BUSY indicator (green) Lit when the status of "OparationalStatus" of the CIDRW system is "BUSY."5 ERROR indicator (red) When a processing error is detected (when SSACK is other than "NO"), this indicator is lit for 50 ms.6 24 VDC power supply termi-nals(with cover)Connect to the 24 VDC power supply.7 Frame ground terminal(with cover)The grounding wire is connected here.  (Ground to 100 Ω or less)8 MODE switch Used to select the mode of operation. Refer to page 48.0 : Normal Operation mode.  When mounting the Controller, set the switch to this posi-tion.3 : Setting mode, selected to set information such as the communication conditions.  When the switch on the bottom face of the Controller cannot be accessed, the opera-tion mode can be changed from the host device while the switch is left at the "0" set-ting.1 - 2, 4 - 7 : Setting prohibited9 RESET switch Restarts the CIDRW Controller.10 SECS port Port for connecting the host device.  Conforms to SECS I/II.11 ID port An Amplifier Unit or Link Unit is connected here.12 Maintenance port (with cover) Not used.  Do not remove the cover.45%5'%5 +& /#+06'0#00%'
20SECTION 1Component Names and FunctionsCIDRW SystemUser’s ManualSECTION 1Product OutlineAmplifier Unit  V640-HAM11No. Name Function1 Dedicated power supply con-nectorConnect to the 24 VDC power supply.2 RS-485 port When using multiple CIDRW Heads, connect this to the RS-485 port of another Amplifier Unit or to the multi-connection port of a Link Unit.3 RS-232C port Connected to a CIDRW Controller or a host device.Uses the OMRON proprietary communications protocol.4 RUN indicator (green) Turns ON when the Amplifier Unit is in normal operation.5 COMM indicator (yellow) Turns ON during communications with the host device or during communications with an ID Tag.6 NORM indicator (green) Turns ON when the communications finish with no error.7 ERROR indicator (red) Turns ON when an error occurs during communication with the host device, or during communication with an ID Tag.8 CIDRW Head connection port A CIDRW Head is connected here.9 Setting DIP switches Used to set the node number, the communications conditions, and the RS-485 terminal resistance.
21CIDRW SystemUser’s MaualSECTION 1Component Names and FunctionsSECTION 1Product OutlineCIDRW Head  V640-HS61No. Name Function1 Antenna Used to communicate with ID Tags.2 Antenna center This is the center of the communications area.3 Connector Connect to an Amplifier Unit.V640-HS61CIDRW HEAD
22SECTION 1Component Names and FunctionsCIDRW SystemUser’s ManualSECTION 1Product OutlineLink unit  V700-L11No. Name Function1 Multi-connection port(RS-485)This is the port that connects to the Amplifier Units when multiple CIDRW Heads are connected to a CIDRW Controller.  The GR (frame ground) terminal is also at this port.2 RUN indicator (green) Turns ON while the Link Unit is in normal operation.3 ID indicator (green) Turns ON during data communications with a V700 series IDRW Head.4 COMM indicator (green) Turns ON during data communications with the host device.5 ERR indicator (red) Turns ON when an error occurs during data communications with the host device or head.6 Host device connection port (RS-232C)This is a port for connecting to the CIDRW Controller via an RS-232C interface.  A dust cover is fitted on shipment from the factory.  Remove this cover before using the port.7 ID connection port This is a dedicated port for connecting a V700 series IDRW Head.  Connect either a V700-HMD13  or V700-HMD11-1 IDRW Head.8 24 V power supply terminals(inside the cover)Connect to the 24 VDC power supply.9 Setting DIP switches(inside the cover)Used to set the equipment number, the communications conditions, and the RS-485 ter-minal resistance.
23CIDRW SystemUser’s MaualSECTION 1Flowchart for Getting StartedSECTION 1Product OutlineFlowchart for Getting StartedRefer to page 26.Refer to page 31.Refer to page 48.Refer to page 61.Refer to page 65.Refer to page 66.InstallationConnection and WiringSet the Communications Conditions for the CIDRW ControllerSet the Communications Conditions for Amplifier UnitsRefer to page 63.Set the Communications Conditions for Link UnitsTest for Communications with the Host DeviceID Tag <-> CIDRW System Communications TestCheck the Surrounding EnvironmentRefer to page 28.Preparation for CommunicationsTrial Operation Installation and Connections
24SECTION 1Flowchart for Getting StartedCIDRW SystemUser’s ManualSECTION 1Product OutlineRefer to page 70.Refer to page 81.Refer to page 92. List of Error MessagesRefer to page 92. Controller IndicatorsRefer to page 93. Operation Check FlowchartRefer to page 98. List of Error MessagesRefer to page 98. Amplifier Unit IndicatorsRefer to page 99. Operation Check FlowchartWhen SECS is UsedWhen SECS is Not UsedWhen SECS is Not UsedWhen SECS is UsedWhen you Encounter a Problem...Communications
SECTION 2Installation and Connections/Wiring25CIDRW SystemUser’s MaualSECTION 2Installation and Connections/WiringInstallation 26Connections and Wiring 31
26SECTION 2InstallationCIDRW SystemUser’s ManualSECTION 2Installation and Connections/WiringInstallationCIDRW ControllerThere is a switch for selecting the operation mode (Normal Operation mode <-> Setting mode) on the bottom face of theCIDRW Controller.  Set the communications conditions in the Setting mode (switch position 3) before mounting theCIDRW Controller. Refer to page 48.Set the Controller to the Normal Operation mode (switch position 0) when mounting it.Mount the CIDRW Controller with the resin washers and four M4 screws provided as accessories.•Tighten the M4 screws with a torque not exceeding 1.2 N·m.• Do not apply organic solvents used with screw locking agents at the locations where the screws are inserted.rr /Mounting dimensions(Unit: mm)
27CIDRW SystemUser’s ManualSECTION 2InstallationSECTION 2Installation and Connections/WiringAmplifier UnitUse spring washers and flat washers with the four M4 screws when mounting the Amplifier Unit.Tighten the M4 screws with a torque not exceeding 1.2 N·m.rr/RUNCOMMNORMERRORMounting dimensions(Unit: mm)
28SECTION 2InstallationCIDRW SystemUser’s ManualSECTION 2Installation and Connections/WiringCIDRW HeadThe area for communications with ID Tags varies substantially according to the installation orientationsand the background conditions (metals, noise, etc.).  Check the communications area before decidingthe installation position.For details on actual communications distances, see Characteristic Data depending on Conditions ofUse in Appendix.Refer to page 109.Positional Relationship between the CIDRW Head and the ID TagThe communications area differs according to the positional relationship during communications.Data Reading and WritingThe communications distances for reading and writing are not the same; the distance is shorter forwriting.  Therefore, when data is to be both read and written, take the distance for writing as the refer-ence distance when installing the CIDRW Head and the ID Tag.Mountingorientation Communications area (purely illustrative) ExplanationCoaxial The maximum communications area is obtained when the centerlines of the CIDRW Head and the ID Tag coincide.Parallel The maximum communications area is obtained when the center point of the antenna on the CIDRW Controller is aligned with the centerline of the ID Tag.Vertical When the center point of the antenna on the CIDRW Head is aligned with the centerline of the ID Tag, the communications area is sub-stantially reduced.
29CIDRW SystemUser’s ManualSECTION 2InstallationSECTION 2Installation and Connections/WiringInfluence of Background Metal on ID TagMetals in the vicinity of the communications area will affect the range, making it smaller.Refer to page 115.Influence of NoiseThis CIDRW system uses a frequency of 134 kHz for communications with ID Tags.  Equipment suchas switching power supplies, inverters, servomotors, or monitors in the surrounding area will adverselyaffect communications, restricting the communications area.The noise levels in the vicinity of the CIDRW Head can be determined with the environmental noise measurement com-mand (applies only when SECS is not used).   Refer to page 89.For details on the relationship between noise and communications distance, see Appendix.   Refer to page 121.MountingUse spring washers and flat washers with the four M3 screws when mounting a CIDRW Head.Tighten the M3 screws with a torque not exceeding 0.6 N·m.Be sure to install the Amplifier Unit in a panel or metal-shielded equipment.rr/14ǾMounting dimensions(Unit: mm)Antenna center
30SECTION 2InstallationCIDRW SystemUser’s ManualSECTION 2Installation and Connections/WiringLink UnitMount Link Units with the two M4 screws and washers provided as accessories.•Tighten the M4 screws with a torque not exceeding 1.2 N·m.• Do not apply organic solvents used with screw locking agents at the locations where the screws are inserted.Mounting dimensions(Unit: mm)Two M4 or 4.2-dia. holes
31CIDRW SystemUser’s ManualSECTION 2Connections and WiringSECTION 2Installation and Connections/WiringConnections and WiringCIDRW ControllerPower Supply and Grounding WiresConnect the wires to the 24 VDC power supply terminals and frame ground terminal.• Crimp terminalsThe terminal screws on the terminal block are M3 size.  Use appropriate crimp terminals for M3 screwsas shown below.• Power supplyUse a power supply unit that satisfies the following conditions.Be sure to replace the cover after wiring.Crimp terminalsShape SizeForked Round ConditionPower supply voltage Output current24 VDC +10%, -15% 500 mA DC min.Recommended modelManufacturer ModelOMRON S82K-01524Ground to 100 Ω or less.24 VDC6 mm max.6 mm max.
32SECTION 2Connections and WiringCIDRW SystemUser’s ManualSECTION 2Installation and Connections/WiringSECS portThe method for wiring for communications with a host device via the SECS port is explained here.• ConnectorThe SECS port on the Controller is a D-SUB 9-pin connector.  The pin arrangement is shown below.Recommended modelPin No. Signal name Symbol Signal direction Remarks1 — NC — Not connected2 Receive data RD Input3 Send data SD Output4 — — Output Always OFF5 Signal ground SG —6 — — Input Use in the "open" status.7 Request send RS Input Always ON during normal operation8 — NC — Not connected9 — NC — Not connectedManufacturer ModelCable Hitachi Cable CO-MA-VV-SB 5PX28AWGConnector Socket OMRON XM2D-0901Hood XM2S-0913CIDRW Controller HostTo the RS-232 portTo the SECS port45%5'%5 +& /#+06'0#00%' The connector rim has electrical continuity with theGR (frame ground) in the 24 VDC power supply ter-minals.
33CIDRW SystemUser’s ManualSECTION 2Connections and WiringSECTION 2Installation and Connections/Wiring•WiringThe cable length should be no greater than 15 m.CIDRW ControllerV700-L22D-SUB, 9-pinSocket type  #4-40Name Pin No.NC 1RD 2SD 3NC 4SG 5NC 6RS 7NC 8NC 9PC/AT ComputerD-SUB, 9-pinSocket type  #4-40Pin No. Name1NC2RD3SD4NC5SG6NC7RS8CS9NCGround shielded wires either at the CIDRW Controller side or at the PC/AT side.
34SECTION 2Connections and WiringCIDRW SystemUser’s ManualSECTION 2Installation and Connections/WiringAmplifier UnitConnector for connecting a CIDRW Head1. Align the pin on the connector with thechannel in the cable connector and insertthe cable connector.Hold the fixed part of the connector while makingthis insertion.2. After inserting the connector fully home,turn the fixed part clockwise to lock it.Power Supply and Grounding WiresConnect the power supply and grounding wires to the dedicated power supply connector.•The grounding wire should be connected to a ground exclusive to the Amplifier Unit.  If the grounding wire is sharedwith another unit, or connected to a beam in a building, there may be adverse effects.•Make the grounding point as close as possible and the length of the grounding wire used as short as possible.24 V+24 V- GR24 VDC Ground to 100 Ω or lessConnector
35CIDRW SystemUser’s ManualSECTION 2Connections and WiringSECTION 2Installation and Connections/Wiring• Dedicated power supply connector and RS-485 port connectorPrepare a V640-A90 (can be purchased as an accessory).• Dedicated power supply cableUse an AWG20 - 24 cable.Use a dedicated tool for crimping the cable to the connector pins.• Power supply unitUse a power supply unit that satisfies the following conditions.Contents of the V640-A90 set (accessory)Name Quantity When procured individuallyManufacturer ModelPower supply connector One Tyco Electronics  1-178288-3Pins for power supply con-nectorThree 175217-3Connector for RS-485 port One Phoenix Contact MSTB2.5/2-STF-5.08Recommended crimping toolManufacturer ModelTyco Electronics  919601-1ConditionPower supply voltage Output current24 VDC +10%, -15% 300 mA DC min.Recommended productManufacturer ModelOMRON S82K-01524
36SECTION 2Connections and WiringCIDRW SystemUser’s ManualSECTION 2Installation and Connections/WiringRS-232C PortThe method for connecting a CIDRW Controller or host device via the RS-232C port is explained here.• ConnectorThe RS-232C port of the Amplifier Unit is a D-SUB, 9-pin connector.  The pin arrangement is shownbelow.Pin No. Signal name Symbol Signal direction Remarks1 — NC — Not connected2 Receive data RD Input3 Send data SD Output4 — NC — Not connected5 Signal ground SG —6 — NC — Not connected7 Request send RS Output Always ON during normal operation8 Send enable CS Input9 — NC — Not connectedHostTo ID portTo the RS-232C portAmplifier UnitTo the RS-232C portTo the RS-232C portCIDRW ControllerAmplifier UnitThe connector rim has electrical continuity with the GR (frameground) terminal in the dedicated power supply connector.
37CIDRW SystemUser’s ManualSECTION 2Connections and WiringSECTION 2Installation and Connections/Wiring• Wiring for connection to a V700-L22 CIDRW ControllerThe cable length should be no greater than 15 m.Recommended modelManufacturer ModelCable Hitachi Cable CO-MA-VV-SB 5PX28AWGConnector Host side Socket OMRON XM2D-0901Hood XM2S-0913Amplifier unit sideSocket XM2D-0901Hood XM2S-0911Amplifier unitV640-HAM11D-SUB, 9-pinSocket typeMetric screw, M2.6Name Pin No.NC 1RD 2SD 3NC 4SG 5NC 6RS 7CS 8NC 9CIDRW ControllerV700-L22D-SUB, 9-pinSocket type#4-40Pin No. Name1NC2RD3SD4NC5SG6NC7RS8CS9NCGround shielded wires either at the amplifier unit side or at theCIDRW side.
38SECTION 2Connections and WiringCIDRW SystemUser’s ManualSECTION 2Installation and Connections/Wiring• Wiring for connection to a PC/AT computer (9-pin connector specification)The cable length should be no greater than 15 m.If the CS function is to be used at the PC/AT computer side, a return wire is required.RS signal control method at the host deviceIn a 1:N connection using Link Units, the RS signals generated from the host device by normal control must be input asCS signals.  Turn the RS signals OFF within 15 ms after the completion of data transmission.  Correct communicationswill not be possible without this control.Amplifier unitV640-HAM11D-SUB, 9-pinSocket typeMetric screw, M2.6Name Pin No.NC 1RD 2SD 3NC 4SG 5NC 6RS 7CS 8NC 9PC/AT ComputerD-SUB, 9-pinSocket type#4-40Pin No. Name1NC2RD3SD4NC5SG6NC7RS8CS9NCGround shielded wires either at the CIDRW Controller side or at thePC/AT side.Amplifier unitV640-HAM11D-SUB, 9-pinSocket typeMetric screw, M2.6Name Pin No.NC 1RD 2SD 3NC 4SG 5NC 6RS 7CS 8NC 9PC/AT computerD-SUB, 9-pinSocket type#4-40Pin No. Name1NC2RD3SD4NC5SG6NC7RS8CS9NCGround shielded wires either at the CIDRW Controller side or at thePC/AT side.SD at host deviceRS at host deviceON only during data transmission from the host deviceWithin 15 ms
39CIDRW SystemUser’s ManualSECTION 2Connections and WiringSECTION 2Installation and Connections/WiringRS-485 PortThe method for connection to the RS-485 port of another Amplifier Unit when multiple CIDRW Headsare used is explained here.The maximum total length of RS-485 cable is 50 m.• ConnectorPrepare a V640-A90 (can be purchased as an accessory) as the connector for the RS-485 port on theAmplifier Unit.Refer to page 35.The pin arrangement is shown below.To the RS-485 port Amplifier UnitTo the RS-232C portCIDRW ControllerConnectorName Function- Connect to the "minus" line of another Amplifier Unit.+ Connect to the "plus" line of another Amplifier Unit.-
40SECTION 2Connections and WiringCIDRW SystemUser’s ManualSECTION 2Installation and Connections/Wiring• Notes on cables•Wiring method1. Attach crimp terminals to stripped portions of the cables.2. Insert the wires into the correct holes in the connector, bearingthe orientation of the connector in mind.3. Tighten the set screws of the connector firmly to secure thecables.The appropriate tightening torque is around 0.5 N·m.A standard, tapered screwdriver will not enter all the way into thescrew holes.  Use a small gauge flat-blade screwdriver whose shaftand tip have the same thickness.4. Having fitted the connector to the cable, connect itto an Amplifier Unit.Orient the cable connector correctly in relation to the connectoron the Amplifier Unit, and fasten the cable connector by fullytightening the retaining screws.Disconnecting the connectorFully loosen the two screws, then grip the projections on the connector and pull it straight out. If it is difficult to pull theconnector out, press down on the Amplifier Unit while pulling on the connector.Recommended modelManufacturer ModelCable RS-485 signal wire Tachii Electric Wire MVVS 2CX0.5SQCrimp terminals When one wire is connected to each terminal.Phoenix Contact AI0.5-8WHWhen two wires are con-nected to each terminal.AI-TWIN2×0.5-8WHCrimping tool CRIMPFOX UD6Small flat-blade screw-driver with no taperRecommended screwdriverManufacturer ModelOMRON XW4Z-00CSide view Face view0.6 mm 3.5 mmSet screws
41CIDRW SystemUser’s ManualSECTION 2Connections and WiringSECTION 2Installation and Connections/WiringLink Unit Power SupplyOpening the cover on the top face of the Link Unit exposes the power supply terminals.• Crimp terminalsThe terminal screws on the terminal block are M3 size. Use appropriate crimp terminals for M3 screwsas shown below.• Power supplyUse a power supply unit that satisfies the following conditions.Crimp terminalsShape SizeForked Round ConditionPower supply voltage Output current24 VDC +10%, -15% 500 mA DC min.Recommended modelManufacturer ModelOMRON S82K-0152424 VDC6 mm max.6 mm max.
42SECTION 2Connections and WiringCIDRW SystemUser’s ManualSECTION 2Installation and Connections/WiringHost Connection PortThe method for connecting to a CIDRW Controller or host device via the RS-232C port is explainedhere.• ConnectorThe host device connection port on the Link Unit is a D-SUB, 9-pin connector.  The pin arrangement isshown below.CIDRW ControllerLink UnitTo ID portTo the RS-232C portTo host device portLink UnitTo host device portHostThe connector rim does not have electricalcontinuity with the GR (frame ground) termi-nal in the multi-connection port.
43CIDRW SystemUser’s ManualSECTION 2Connections and WiringSECTION 2Installation and Connections/Wiring• Wiring for connection to a CIDRW ControllerThe cable length should be no greater than 15 m.Pin No. Signal name Symbol Signal direction Remarks1 — NC — Not connected2 Receive data RD Input3 Send data SD Output4 — NC — Not connected5 Signal ground SG —6 — NC — Not connected7 Request send RS Output Always ON during normal operation8 Send enabled CS Input9 — NC — Not connectedRecommended modelManufacturer ModelCable Hitachi Cable CO-MA-VV-SB 5PX28AWGConnector Socket OMRON XM2D-0901Hood XM2S-0913Link unitV700-L11D-SUB, 9-pin, femaleSocket type  #4-40Name Pin No.NC 1RD 2SD 3NC 4SG 5NC 6RS 7CS 8NC 9CIDRW ControllerV700-L22D-SUB, 9-pin, femaleSocket type  #4-40Pin No. Name1NC2RD3SD4NC5SG6NC7RS8CS9NCGround shielded wires at the CIDRW Controller side.
44SECTION 2Connections and WiringCIDRW SystemUser’s ManualSECTION 2Installation and Connections/Wiring• Wiring for connection to a PC/AT computerIf the CS function is to be used at the PC/AT computer side, a return wire is required.RS signal control method at the host deviceIn a 1:N system using Link Units, the RS signals generated from the host device by normal control must be input as CSsignals.  Turn the RS signals OFF within 15 ms after the completion of data transmission.  Correct communications willnot be possible without this control.Link unitV700-L11D-SUB, 9-pinSocket type  #4-40Name Pin No.NC 1RD 2SD 3NC 4SG 5NC 6RS 7CS 8NC 9PC/AT ComputerD-SUB, 9-pinSocket type  #4-40Pin No. Name1NC2RD3SD4NC5SG6NC7RS8CS9NCGround shielded wires at the PC/AT computer side.Link unitV700-L11D-SUB, 9-pinSocket type  #4-40Name Pin No.NC 1RD 2SD 3NC 4SG 5NC 6RS 7CS 8NC 9PC/AT ComputerD-SUB, 9-pinSocket type  #4-40Pin No. Name1NC2RD3SD4NC5SG6NC7RS8CS9NCGround shielded wires at the PC/AT computer side.SD at host deviceRS at host deviceON only during data transmission from the host deviceWithin 15 ms
45CIDRW SystemUser’s ManualSECTION 2Connections and WiringSECTION 2Installation and Connections/WiringMulti-connection portThe method for connecting to an Amplifier Unit is explained here.• ConnectorPin No. Name Function5 - No wiring is required.  (Short with terminal 2 within the circuit)4 + No wiring is required.  (Short with terminal 1 within the circuit)3 GR Ground to 100 Ω or less.2 - Connect to the "minus" line of the Amplifier Unit.1 + Connect to the "plus" line of the Amplifier Unit.Link UnitAmplifier UnitTo the RS-485 portTo multi-connection port
46SECTION 2Connections and WiringCIDRW SystemUser’s ManualSECTION 2Installation and Connections/Wiring•Cable•Wiring method1. Attach crimp terminals to stripped portions of the cables.2. Insert the wires into the correct holes in the connector, bearingthe orientation of the connector in mind.3. Tighten the set screws of the connector firmly to secure thecables.The appropriate tightening torque is around 0.5 N·m.A standard, tapered screwdriver will not enter all the way into thescrew holes.  Use a small gauge flat-blade screwdriver whose shaftand tip have the same thickness.4. Having fitted the connector to the cable, connectit to the Link Unit.Orient the cable connector correctly in relation to the connec-tor on the Link Unit, and fasten the cable connector by fullytightening the retaining screws.Disconnecting the connectorFully loosen the two screws, then grip the projections on the connector and pull it straight out. If it is difficult to pull theconnector out, press down on the Link Unit while pulling on the connector.Recommended ProductManufacturer ModelCable RS-485 signal wire Tachii Electric Wire MVVS 2CX0.5SQFrame ground line AWG22 - 20 cableCrimp terminals When one wire is connected to each terminal. Phoenix Contact AI0.5-8WHWhen two wires are connected to each terminal. AI-TWIN2×0.5-8WHCrimping tool CRIMPFOX UD6Small gauge flat-blade screwdriver with no taperRecommended screwdriverManufacturer ModelOMRON XW4Z-00CSide view Face view0.6 mm 3.5 mmSet screws
SECTION 3Preparing for Communications47CIDRW SystemUser’s ManualSECTION 3Preparing for CommunicationsSet the Communications Conditions for the CIDRW Controller48Set the Communications Conditions for Amplifier Units 61Set the Communications Conditions for Link Units 63Communications Test 65
48SECTION 3Set the Communications Conditions for the CIDRW ControllerCIDRW SystemUser’s ManualSECTION 3Preparing for CommunicationsSet the Communications Conditions for the CIDRW ControllerSet the communications conditions of the CIDRW Controller only when SECS is used.Switch to the Setting modeThe CIDRW Controller has two operating modes, the "Normal Operation mode" and the "Settingmode." Switch to the "Setting mode" to set the communications conditions.There are two methods for switching the mode.  Use the one that is appropriate for the circumstances.Changing the Position of the Mode Switch on the Bottom of the UnitThis is the convenient method for setting before mounting the unit.1. Turn OFF the power to the CIDRW Controller.2. Set the mode switch on the bottom of the unit to"3."1Switch to the Setting mode.2Start the terminal software.3Set the parameters for the communications conditions.4Change the Carrier ID5Change the Data segment area.6Change the response time-out time.7Set Software Revisions8Return to the Normal Operation mode.2107657321076573
49CIDRW SystemUser’s ManualSECTION 3Set the Communications Conditions for the CIDRW ControllerSECTION 3Preparing for Communications3. When all of the devices to be used are connected, turn the power ON.The system starts up in the Setting mode, and the indicators react as shown below.Sending a Switching Command from the Host DeviceThis method is convenient when the unit has already been mounted and the switch on the bottom can-not be repositioned to "3."During operation in the Normal Operation mode, a command is sent from the host device to switch tothe Setting mode.1. Send a subsystem command (S18F13 ChangeState CPVAL1 = "PS") from the host device.Refer to page page 77.CPVAL1="PS" is an expansion designation unique to V700-L22 and does not conform to SEMI standards.The system is automatically restarted and the mode switches to the Setting mode.The operation indicators react as shown below.Start the terminal softwareUse the host device's terminal software for the setting.The commands and communications conditions in the setting mode are unique to OMRON.  They do not conform to theSEMI standards.  For the terminal software, use Hyper Terminal, which is standard with Windows, or a similar program.The communications conditions for communication between the host device and CIDRW Controllerare fixed.  Make the following settings using the terminal software.OPERATING ALARMS BUSY ERROROPERATING ALARMS BUSY ERRORItem SettingBaud rate 9600 bpsData length 8 bitsParity EVENStop bit 1Communications control NoneSend code At the end of a line (when [ENTER] is input), the "line feed" characters ([LF]) are appended.Display Local echo
50SECTION 3Set the Communications Conditions for the CIDRW ControllerCIDRW SystemUser’s ManualSECTION 3Preparing for CommunicationsSet the parameters for the communications conditionsSpecify the parameters whose settings are to be changed from the terminal software of the hostdevice.  The commands, and the parameters that can be set are indicated below.The setting mode commands do not conform to SEMI standards.For the terminal software, use Hyper Terminal, which is standard with Windows, or a similar program.List of CommandsDesignation Command Input ExplanationParameter designation (Tag name) = (Set value) <CRLF> Specify the parameter value corresponding to the tag name.Parameter confirmation ::END Checks the parameter designations that have been received so far and, if there is no error, confirms the settings.Comment # (Comment) <CRLF> or CRLFThis is ignored as the comment line.Tag Name ListClassification Parameter Tag name Setting rangeDefault settingProtocol Baud Rate S_BAUD 1200, 2400, 4800, 9600, 19200, 38400, 57600,115200 bps9600 bpsDevice ID S_DEVID 0 to 32767 0Time-out between characters S_T1 0.1 to 10 s 0.5 sProtocol time-out S_T2 0.2 to 25 s 10 sResponse time-out S_T3 1 to 120 s 45 sTime-out between blocks S_T4 1 to 120 s 45 sRetry limit S_RTY 0 to 31 3Master/slave S_MS M : MasterS : SlaveMSECS Double block detection yes/no S_DB 1: The header of the block currently being received is compared with the correct block received immediately before, and double blocks are detected.0: Double block detection is not performed.1Source ID S_SRC 0 to 32767 0Single block No. S_BNO 0, 1 1Operation Baud rate for communications with Amplifier Unit/Link UnitC_BAUD 9600, 19200, 38400 bpsUse a consistent baud rate setting within the same system configuration.9600 bpsNumber of heads count pro-cessingC_HEAD 0 to 310: The number of heads is automatically detected at the start.  Any increase or decrease in the number of heads is auto-matically detected.1 to 31: The number of heads is specified.  The number of heads detected is compared with this specified number of heads.  If the number of heads changes, for exam-ple because a head fails, an error (with alarm) is detected.If a head is not connected or an error is detected with a connected head, so that the number of heads does not match the specified number, an error (with alarm) is detected.0
51CIDRW SystemUser’s ManualSECTION 3Set the Communications Conditions for the CIDRW ControllerSECTION 3Preparing for Communications1. Specify the parameters to be changed.When the first parameter is specified, the ALARMS indicator flashes.2. Confirm the parameter change.The input parameter is checked and written.When writing is completed, a message indicating the result is displayed.The ALARMS indicator lights.If writing is completed with an error, the parameters are not updated.The figure in square brackets [  ] indicates the line number where theerror was first detected.  If a parity error is detected in the received char-acters, this figure is [0].Check the sent data based on this information.A text file is created based on the data that is keyed in, as shown below, and this data can be conveniently transmittedusing the terminal's text file send function.S_BAUD=19200S_DEVID=1S_BNO=0_::END _SETUP_COMPLETE_SETUP_FAILED [2]_When writing is completed without errorWhen writing is completed with an error#Parameter Setting File for SystemA#ProtocolS_BAUD=19200S_DEVID=1#SECSS_BNO=0::ENDExample: PRM.TXT
52SECTION 3Set the Communications Conditions for the CIDRW ControllerCIDRW SystemUser’s ManualSECTION 3Preparing for Communications!Check for Correct SettingThe currently set data can be output so that you can check if it is correct.1. Send the parameter output command "::GET_PARAM"from the host device.The current communication parameter settings are displayed.Change the Carrier IDTo read the carrier ID, the CID has to be specified within the area where the carrier ID can be set (CarrierIDField) within the ID tag's memory.  This section explains the procedure for setting the "carrierID offset" (attribute name: CarrierIDOffset) and the "carrier ID size (bytes)" (attribute name: CarrierIDLength) in the memory map of the ID tag.The commands, and the parameters that can be set, are indicated below.• Settings that exceed the carrier ID area (*) cannot be made.  If such a setting is made, anerror occurs.*: (CIDOF+CIDLN) ≤ T_CIDLEN• "Carrier ID offset" and "carrier ID size (bytes)" can only be changed in the L22 mode. Theycannot be changed in the L21 mode. When you change from the L22 mode to the L21 mode,"carrier ID offset" and "carrier ID size (bytes)" are returned to their initial settings.List of CommandsDesignation Command input ExplanationParameter designation (Tag name) = (Set value) <CRLF> Specify the parameter value corresponding to the tag name.Parameter confirmation ::END Checks the parameter designations that have been received so far and, if there is no error, confirms the settings.Comment # (Comment) <CRLF> or CRLFThis is ignored as the comment line.Tag Name ListParameter Tag name Setting range Default settingCarrier ID offset CIDOF 0 -15 0Carrier ID size (bytes) CIDLN 01 - 16 16::GET_PARAMS_BAUD=19200S_DEVID=1S_T1=0.5S_T2=10.0S_T3=45S_T4=3S_RTY=3S_MS=MS_SRC=0S_BNO=0C_BAUD=9600C_HEAD=0::END_
53CIDRW SystemUser’s ManualSECTION 3Set the Communications Conditions for the CIDRW ControllerSECTION 3Preparing for Communications1. Specify the parameters to be changed.When the first parameter is specified, the ALARMS indicator flashes.2. Confirm the parameter change.The input parameter is checked and written.Check for Correct SettingThe currently set data can be output so that you can check if it is correct.1. Send the parameter output command "::GET_E99SYS"from the host device.The carrier ID settings are displayed.Do not change operation parameters other than RT, CIDOF, and CIDLN.This can cause the system to stop operating correctly.Change the data segment areaThe data segment area (memory map) must be changed to communicate with ID Tags (RI-TRP-DR2B,made by Texas Instruments).  The procedure for changing the data segment area is explained here.Data Segment Area   Refer to page 122.The commands, and the parameters that can be set, are indicated below.List of CommandsDesignation Command input ExplanationParameter designation (Tag name) = (Set value) <CRLF> Specify the parameter value corresponding to the tag name.Parameter confirmation ::END Checks the parameter designations that have been received so far and, if there is no error, confirms the settings.Comment # (Comment) <CRLF> or CRLFThis is ignored as the comment line.CIDOF=0CIDLN=16::END_::GET_E99SYSRT=10.0CT=0.1RTY=3DINST=MENT=MODEL=L22HREV=001.04CIDOF=00CIDLN=16::END_
54SECTION 3Set the Communications Conditions for the CIDRW ControllerCIDRW SystemUser’s ManualSECTION 3Preparing for Communications1. The form of the input from the host device is shown in thefigure to the right.When the first parameter is specified, the ALARMS indicator flashes.2. Confirm the parameter change.The input parameter is checked and written.When writing is completed, a message indicating the result is displayed.The ALARMS indicator lights.If writing is completed with an error, the parameters are not updated.The figure in square brackets [  ] indicates the line number where theerror was first detected.  If a parity error is detected in the received char-acters, this figure is [0].Check the sent data based on this information.Tag Name ListParameter Tag name Setting range Default settingNumber of bytes in the carrier ID T_CIDLEN 16 (fixed)The setting must maintain the following relationship(CIDOF + CIDLN) ≤ T_CIDLEN16Segment name T_SEGN "S01" to "S99" "S01" to "S28"Number of bytes in a segment T_SEGL 8 (fixed) 8T_CIDLEN=16T_SEGN=S01T_SEGL=8T_SEGN=S02T_SEGL=8T_SEGN=S03T_SEGL=8T_SEGN=S04T_SEGL=8T_SEGN=S05T_SEGL=8T_SEGN=S06T_SEGL=8T_SEGN=S07T_SEGL=8T_SEGN=S08T_SEGL=8T_SEGN=S09T_SEGL=8T_SEGN=S10T_SEGL=8T_SEGN=S11T_SEGL=8T_SEGN=S12T_SEGL=8T_SEGN=S13T_SEGL=8T_SEGN=S14T_SEGL=8T_SEGN=S15T_SEGL=8_::END _SETUP_COMPLETE_SETUP_FAILED [2]_When writing is completed without errorWhen writing is completed with an error
55CIDRW SystemUser’s ManualSECTION 3Set the Communications Conditions for the CIDRW ControllerSECTION 3Preparing for CommunicationsCheck for Correct SettingThe currently set data can be output so that you can check if it is correct.1. Send the parameter output command "::GET_SEG" fromthe host device.The data segment area is displayed.::GET_SEGT_CIDLEN=16T_SEGN=S01T_SEGL=8T_SEGN=S02T_SEGL=8T_SEGN=S03T_SEGL=8T_SEGN=S04T_SEGL=8T_SEGN=S05T_SEGL=8T_SEGN=S06T_SEGL=8T_SEGN=S07T_SEGL=8T_SEGN=S08T_SEGL=8T_SEGN=S09T_SEGL=8T_SEGN=S10T_SEGL=8T_SEGN=S11T_SEGL=8T_SEGN=S12T_SEGL=8T_SEGN=S13T_SEGL=8T_SEGN=S14T_SEGL=8T_SEGN=S15T_SEGL=8::END_
56SECTION 3Set the Communications Conditions for the CIDRW ControllerCIDRW SystemUser’s ManualSECTION 3Preparing for CommunicationsChange the response time-out timeIn the initial settings of the CIDRW Controller, when ID Tag (RI-TRP-DR2B, made by Texas Instru-ments) data is read or written, a "response time-out" may occur.  Be sure to set the response time-outtime to "10 s."The commands, and the parameters that can be set are indicated below.1. Set the response time-out time to "10.0."2. Confirm the parameter change.The input parameter is checked and written.When writing is completed, a message indicating the result is displayed.The ALARMS indicator lights.If writing is completed with an error, the parameters are not updated.The figure in square brackets [  ] indicates the line number where theerror was first detected.  If a parity error is detected in the received char-acters, this figure is [0].Check the sent data based on this information.List of CommandsDesignation Command input ExplanationParameter designation (Tag name) = (Set value) <CRLF> Specify the parameter value corresponding to the tag name.Parameter confirmation ::END Checks the parameter designations that have been received so far and, if there is no error, confirms the settings.Comment # (Comment) <CRLF> or CRLFThis is ignored as the comment line.Tag Name ListParameter Tag name Setting range Default settingResponse time-out time RT 10.0 (fixed) 2.5RT=10.0_::END _SETUP_COMPLETE_SETUP_FAILED [2]_When writing is completed without errorWhen writing is completed with an error
57CIDRW SystemUser’s ManualSECTION 3Set the Communications Conditions for the CIDRW ControllerSECTION 3Preparing for CommunicationsCheck for Correct SettingThe currently set data can be output so that you can check if it is correct.1. Send the parameter output command "::GET_E99SYS"from the host device.The current operation parameter settings are displayed.Do not change operation parameters other than RT, CIDOF, and CIDLN.This can cause the system to stop operating correctly.Set Software RevisionsThe operations of the V700-L22 can be changed to match those of the previous model, the V700-L21.The commands, and the parameters that can be set are indicated below.1. Specify the parameters to be changed.When the first parameter is specified, the ALARMS indicator flashes.List of CommandsDesignation Command input ExplanationParameter designation (Tag name) = (Set value) <CRLF> Specify the parameter value corresponding to the tag name.Parameter confirmation ::END Checks the parameter designations that have been received so far and, if there is no error, confirms the settings.Comment # (Comment) <CRLF> or CRLFThis is ignored as the comment line.Tag Name ListParameter Tag name Setting range Default settingSoftware revision RVER 2.00: in V700-L22 mode1.10: in V700-L21 mode2.00::GET_E99SYSRT=10.0CT=0.1RTY=3DINST=MENT=MODEL=L22HREV=001.04CIDOF=00CIDLN=16::END_RVER=1.10
58SECTION 3Set the Communications Conditions for the CIDRW ControllerCIDRW SystemUser’s ManualSECTION 3Preparing for Communications2. Confirm the parameter change.The input parameter is checked and written.Check for Correct SettingThe currently set data can be output so that you can check if it is correct.1. Send the parameter output command "::GET_VER" fromthe host device.The software revision settings are displayed.Return to the Normal Operation modeWhen the Mode is Selected with the Mode Switch on the Bottom of the Unit1. Turn OFF the power to the CIDRW Controller.2. Set the mode switch on the bottom of the unit tothe "0."3. When all of the devices to be used are connected, turn the power ON.Start up in the Normal Operation mode.Even if you restart with the mode switch left at the "3" position, or send a reset command "::EXIT," the Controller willstart in the Setting mode.  To switch to Normal Operation mode, you must set the mode switch to "0."When the Mode is Selected by a Command Sent from the Host Device1. Either send the reset command "::EXIT" from the hostdevice or turn the power to the CIDRW Controller OFFand then back ON.Start up in the Normal Operation mode.::END _::GET_VERRVER=1.10::END_2107657321076573::EXIT_
59CIDRW SystemUser’s ManualSECTION 3Set the Communications Conditions for the CIDRW ControllerSECTION 3Preparing for CommunicationsReference:List of CommandsDesignation Command input ExplanationParameter designation (Tag name) = (Set value) <CRLF> Specify the parameter value corresponding to the tag name.Parameter confirmation ::END Checks the parameter designations that have been received so far and, if there is no error, confirms the settings.Comment # (Comment) <CRLF> or CRLF This is ignored as the comment line.Parameter output ::GET_PARAM Outputs the set parameters (protocol, SECS, operation).::GET_SEG Outputs the set parameters (ID Tag memory map).::GET_E99SYS Outputs the set parameters (operations).::GET_VER Outputs the set parameters (software revision).RESET :EXIT Restarts the CIDRW Controller.Tag Name ListClassification Parameter Tag name Setting range Default settingProtocol Baud Rate S_BAUD 1200, 2400, 4800, 9600, 19200, 38400, 57600,115200 bps 9600 bpsDevice ID S_DEVID 0 to 32767 0Time-out between characters S_T1 0.1 to 10 s 0.5 sProtocol time-out S_T2 0.2 to 25 s 10 sResponse time-out S_T3 1 to 120 s 45 sTime-out between blocks S_T4 1 to 120 s 45 sRetry limit S_RTY 0 to 31 3Master/slave S_MS M : MasterS : Slave MSECS Double block detec-tion yes/no S_DB 1: The header of the block currently being received is compared with the correct block received immediately before, and double blocks are detected.0: Double block detection is not performed.1Source ID S_SRC 0 to 32767 0Single block No. S_BNO 0, 1 1Operation Baud rate for com-munications with Amplifier Unit/Link UnitC_BAUD 9600, 19200, 38400 bpsUse a consistent baud rate setting within the same system configuration.9600 bpsNumber of heads count processing C_HEAD 0 to 310: The number of heads is automatically detected at the start.  Any increase or decrease in the number of heads is auto-matically detected.1 to 31: The number of heads is specified.  The number of heads detected is compared with this specified number of heads.  If the number of heads changes, for example because a head fails, an error (with alarm) is detected.If a head is not connected or an error is detected with a connected head, so that the number of heads does not match the specified number, an error (with alarm) is detected.0ID Tag Number of bytes in the carrier ID T_CIDLEN 16 (fixed) 16Segment name T_SEGN "S01" - "S99" "S01" - "S28"Number of bytes in a segment T_SEGL 8 (fixed) 8
60SECTION 3Set the Communications Conditions for the CIDRW ControllerCIDRW SystemUser’s ManualSECTION 3Preparing for CommunicationsE99 Response timeout timeRT 10.0 s (fixed) 2.5 sCarrier ID offset CIDOF 00 - 15 00Carrier ID length CIDLEN 10 - 16 16Tag Name ListClassification Parameter Tag name Setting range Default setting
61CIDRW SystemUser’s ManualSECTION 3Set the Communications Conditions for Amplifier UnitsSECTION 3Preparing for CommunicationsSet the Communications Conditions for Amplifier UnitsSet the communications conditions using the DIP switches on the side face of the Amplifier Unit.After changing the DIP switch settings, restart the system.  The new settings will not become effective until thesystem is restarted. Baud rateOption DIP-SW Description6 738400 bps ON ON Use a consistent baud rate setting within the same system configuration.19200 bps OFF ON9600 bps (default setting) OFF OFF4800 bps ON OFFRS-485 terminatorOption DIP-SW Description10Invalid OFF Set "ON" at both of the end units in a multidrop system, and "OFF" at all the other units.  If there is only one unit, set "ON."If there is a possibility that one of multiple Amplifier Units in use may be used independently, turn the termi-nators of all the Amplifier Units OFF and fit external terminators close to the units at both ends.Valid ONNode No. Baud rateAlways OFF(Not used in this CIDRW system)RS-485 terminatorNode No.Node No. DIP-SW1234501 OFF OFF OFF OFF OFF02 ON OFF OFF OFF OFF03 OFF ON OFF OFF OFF04 ON ON OFF OFF OFF05 OFF OFF ON OFF OFF06 ON OFF ON OFF OFF07 OFFONONOFFOFF08 ON ON ON OFF OFF09 OFF OFF OFF ON OFF10 ON OFF OFF ON OFF11 OFF ON OFF ON OFF12 ON ON OFF ON OFF13 OFF OFF ON ON OFF14 ON OFF ON ON OFF15 OFFONONONOFF16 ON ON ON ON OFFNode No. DIP-SW1 2 3 4 517 OFFOFFOFFOFFON18 ON OFF OFF OFF ON19 OFF ON OFF OFF ON20 ON ON OFF OFF ON21 OFF OFF ON OFF ON22 ON OFF ON OFF ON23 OFF ON ON OFF ON24 ON ON ON OFF ON25 OFFOFFOFFON ON26 ON OFF OFF ON ON27 OFF ON OFF ON ON28 ON ON OFF ON ON29 OFF OFF ON ON ON30 ON OFF ON ON ON31 OFFONONONONSetting not possibleON ON ON ON ONAlways set node numbers that are unique within the system configuration. When SECS is used, the node number set here is"HeadID(E99)."
62SECTION 3Set the Communications Conditions for Amplifier UnitsCIDRW SystemUser’s ManualSECTION 3Preparing for CommunicationsCommunications conditionsItem SpecificationsStandard conformed to RS-232CCommunications con-trol protocol1:N protocol exclusive to OMRONSynchronization methodStart-stop synchronizationBaud rate Set using a DIP switchFrame composition Start bit Data bits Parity bit Stop bit Total1 8 None 1 10Error detection FCS (frame check sequence)
63CIDRW SystemUser’s ManualSECTION 3Set the Communications Conditions for Link UnitsSECTION 3Preparing for CommunicationsSet the Communications Conditions for Link UnitsSet the communications conditions by setting the DIP switches.The node numbers for Link Units are fixed.  Check that DIP switches 1to 5 are all ON.Node No. (fixed)DIP-SW12345ON ON ON ON ONBaud rateOption DIP-SW Description6 738400 bps ON ON Use a consistent baud rate setting within the same system configuration.19200 bps OFF ON9600 bps (default setting) OFF OFF4800 bps ON OFFRS-485 terminatorOption DIP-SW Description10Invalid OFF Set "ON".Valid ONNode No. Baud rateAlways OFF(Not used in this CIDRW system)RS-485 terminator
64SECTION 3Set the Communications Conditions for Link UnitsCIDRW SystemUser’s ManualSECTION 3Preparing for CommunicationsCommunications conditionsItem SpecificationsStandard conformed to RS-232CCommunications con-trol protocol1:N protocol exclusive to OMRONSynchronization methodStart-stop synchronizationBaud rate Set using a DIP switchFrame composition Start bit Data bits Parity bit Stop bit Total1 8 None 1 10Error detection FCS (frame check sequence)
65CIDRW SystemUser’s ManualSECTION 3Communications TestSECTION 3Preparing for CommunicationsCommunications TestTest for Communications with the Host DeviceCheck if the host device, CIDRW Controller, and Amplifier Units are correctly connected.When SECS is Used• Connection between host device and CIDRW ControllerSend Are You There Request message "S1, F1" from the host device.If it is correctly connected, On Line Data "S1, F2" will be sent from the CIDRW Controller.• Connection between the CIDRW Controller and Amplifier UnitThe connection between the CIDRW Controller and Amplifier Unit is checked automatically.  If they areconnected correctly, the operation indicators on the CIDRW Controller light in the manner shownbelow.When SECS is Not UsedNode No.1 is tested with the data "12345678."POWER OPERATING ALARMS BUSY ERRORSOH Node No. Command code Test data FCS CRData 1 Data 2 Data 3 Data 401h01 1 0 12345678080DhSOH Node No. Response codeTest data FCS CRData 1 Data 2 Data 3 Data 401h010012345678090DhCIDRW ControllerHost Amplifier UnitAmplifier UnitHostCommandResponse
66SECTION 3Communications TestCIDRW SystemUser’s ManualSECTION 3Preparing for CommunicationsID Tag ↔ CIDRW System Communications TestSend a command from the host device and check that normal communication with the ID Tag is possi-ble.When SECS is Used• Read IDThe host device sends a Read ID Request message to the CIDRW Controller for Head 1.  The CIDRWHead 1 reads the ID, and the CIDRW Controller returns the ID to the host device.• Read DataThe host device sends a Read Data Request message to the CIDRW Controller for Head 1, DataSegS01 and Datalength 8. The CIDRW Head 1 reads the data, and the CIDRW Controller returns the datato the host device.CIDRW Controller HostS18, F9 Read ID RequestTarget ID="01"S18, F10 Read ID DataMID="XYZ00001"CIDRW Controller HostS18, F5 Read RequestTarget ID="01"Dataseg="S01"Datalength="8"S18,F6 Read DataData="yyyyyyyy"
67CIDRW SystemUser’s ManualSECTION 3Communications TestSECTION 3Preparing for Communications• Write ID(1) The CIDRW Controller is in IDLE. The host device requests the CIDRW Controller change its oper-ational status to MAINTENANCE.(2) The CIDRW Controller changes to MAINTENANCE and replies that it has changed state.(3) The host device sends a Write ID Request message to the CIDRW Controller for Head 1. TheCIDRW Head 1 writes ID, and the CIDRW Controller returns the ID to the host devices.• Write DataThe host device sends a Write Data Request message to the CIDRW Controller for Head 1 and Data-Seg S02. The CIDRW Head 1 writes the data, and the CIDRW Controller returns the results to the hostdevice.CIDRW Controller HostS18, F13 SubSystem Command RequestTarget ID="01"CPVAL="MT"S18, F14 SubSystem Command AcknowledgeSSACK="NO"S18, F11 Write IDTarget ID="01"MID="ABC"S18, F12 Write ID DataSSACK="NO"CIDRW Controller HostS18, F7 Write ID RequestTarget ID="01"Dataseg="S02"Data="xxxxxx"S18, F8 Write Data AcknowledgeSSACK="NO"
68SECTION 3Communications TestCIDRW SystemUser’s ManualSECTION 3Preparing for CommunicationsWhen SECS is Not Used•ReadReading the page 1 and page 3 data of node No.1:•WriteWriting data to page 8 and page 10 of node No.1:The ID Tag status on normal completion is as shown below:Data content of the ID TagPage 1 12h 34h 56h 78h 90h 12h 34h 56hPage 2Page 3 11h 22h 33h 44h 55h 66h 77h 88hPage 4SOH Node No. Response code Page 1 Page 3 FCS CR01h 0 1 0 0 12345678901234561122334455667788070DhSOH Node No. Response code FCS CR01h0100010DhPage 8 11h 22h 33h 44h 55h 66h 77h 88hPage 9Page 10 01h 23h 45h 67h 89h ABh CDh EFhCommand00000000000000000000000000010100Binary notationSOH Node No. Command code Page designation FCS CR01h01010000000014050DhResponseCommand00000000000000000000101000000000SOH Node No.Command code Page designation Data of page 8 Data of page 10 FCS CR01h 0 1 0 2 0 000000A0011223344556677880123456789ABCDEF 7 4 0DhBinary notationResponse
SECTION 4Reading from/Writing to ID Tags69CIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID TagsWhen SECS is Used 70When SECS is Not Used 81
70SECTION 4When SECS is UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID TagsWhen SECS is UsedThe SEMI standards are subject to revision: you must refer to the actual standards.• SEMI E99 THE CARRIER ID READER/WRITER FUNCTIONAL STANDARD• SEMI E5 EQUIPMENT COMMUNICATION STANDARD 2 MESSAGE CONTENT (SECS II)• SEMI E4 EQUIPMENT COMMUNICATION STANDARD 1 MESSAGE TRANSFER (SECS I)SECS Protocol Specifications  Refer to page 124.Message SpecificationsList of Error Messages  Refer to page 92.List of Messages UsedClassification S F Direction SECS II names SeeGeneral purpose messages11 S,H→E,reply Are You There Request p.7212 S,H←E On Line Data p.72CIDRW system messages18 1 S,H→E,reply Read Attribute Request p.7218 2 S,H←E Read Attribute Data p.7218 3 S,H→E,reply Write Attribute Request p.7318 4 S,H←E Write Attribute Acknowledge p.7318 5 S,H→E,reply Read Request p.7418 6 S,H←E Read Data  p.7418 7 S,H→E,reply Write Request p.7518 8 S,H←E Write Acknowledge p.7518 9 S,H→E,reply Read ID Request p.7618 10 S,H←E Read ID Data  p.7618 11 S,H→E,reply Write ID Request p.7618 12 S,H←E Write ID Acknowledge p.7618 13 S,H→E,reply Subsystem Command Request p.7718 14 S,H←E Subsystem Command Acknowledge p.77Data Item DictionarySECS II data items Name Format ValueATTRID Attribute ID 20 Attribute nameATTRVAL Attribute value 20 Attribute valueMID Carrier ID MID 2016 - 7E16 (Visible ASCII)DATA Data 20 All characters 00H-0FFHDATALENGTH DataSize 52 Offset designation: 1 - 224Segment designation: Refer to Data Segment Area page 122.DATASEG DataSeg 20 Offset designation: "00", "01"..."0222", "0223"Segment designation: Refer to Data Segment Area page 122.STATUS PM information 20 "NE": Normally executed
71CIDRW SystemUser’s ManualSECTION 4When SECS is UsedSECTION 4Reading from/Writing to ID Tags*1: "PS" is an expansion command for this unit.*2: When the TARGET ID is "00" (CIDRW), this is a zero length item.*3: "EE," "HE," and "TE" are used only with S18F6, S18F8, S18F10, and S18F12.S9F7 responsesAn S9F7 response is given when a message in an illegal format is received from the host device."Illegal format" here means that there is a problem with the message composition, such as illegal attributes, or insuffi-cient or too many items.  If other problems relating to the item contents arise, the response is SSACK = "CE" (commu-nications error).SSACK Result status 20 "NO": Normal"EE": Execution error  *3"CE": Communications error"HE": Hardware error  *3"TE": Tag error *3List of STATUS Status L,41.<PMInformation>2.<AlarmStatus>3.<OperationalStatus>4.<HeadStatus> *2The STATUS values are included in the PM information.CPVAL State request  20 "OP", "MT", "PS" *1TARGETID Target ID 20 "00"-"31""00" indicates the CIDRW Controller itself.SSCMD Subsystem com-mands20 "ChangeState""GetStatus""PerformDiagnostics""Reset"Data Item DictionarySECS II data items Name Format Value
72SECTION 4When SECS is UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID TagsSpecifications for Each Stream/Function• Online  check• Get attributes S1,F1 Are You There Request S,H→E,replyHeader onlyS1,F2 On Line Data S,H←EL,21.<MDLN>2.<SOFTREV>• Set MDLN (model number).• Set SOFTREV (software revision level).S18,F1 Read Attribute Request S,H→E,replyL,21.<TARGETID> "00"-"31"2.L,n1.<ATTRID1> ⋅ n.<ATTRIDn>• The setting for reading all attributes (CIDRW Controller or heads) is n = 0.S18,F2 Read Attribute Data S,H←EL,41.<TARGETID> "00"-"31"2.<SSACK>3.L,n1.<ATTRVAL1> ⋅ n.<ATTRVALn>4.L,s1.<STATUS1> ⋅ s.<STATUSs>• The order of the attribute data corresponds to the attribute ID specified by S18, F1.When reading of all attributes is specified, unsupported attribute items (ATTRVAL) are omitted.• When the specified target is invalid:n = 0, s = 0, SSACK = "CE"  communications error• When one or more undefined attributes are included:n = 0, s = 0, SSACK = "CE"  communications error• When head attributes are specified with TARGET = "00" or CIDRW Controller attributes are specified with TARGET <> "00":n = 0, s = 0, SSACK = "CE"  communications error• If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items.
73CIDRW SystemUser’s ManualSECTION 4When SECS is UsedSECTION 4Reading from/Writing to ID Tags• Set attributesF18,F3 Write Attribute Request S,H→E,replyL,21.<TARGETID> "00" (fixed)2.L,n1.L,21.<ATTRID1>2.<ATTRVAL1>n.L,21.<ATTRIDn>2,<ATTRVALn>Since the attributes for heads are all RO in this system, the target ID is fixed as "00".S18,F4 Write Attribute Acknowledge S,H←EL,31.<TARGETID> "00" (fixed)2.<SSACK>3.L,s1.<STATUS1> ⋅ s.<STATUSs>• When the specified target is invalid:s = 0, SSACK = "CE"  communications error• When one or more undefined attributes or RO attributes are included:s = 0, SSACK = "CE"  communications error• When illegal attribute data is specified:s = 0, SSACK = "CE"  communications error• If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items.
74SECTION 4When SECS is UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID Tags• Read dataData Segment Area  Refer to page 122.S18,F5 Read Request S,H→E,replyL,31.<TARGETID> "01"-"31"2.<DATASEG>3.<DATALENGTH>• When DATASEG is specified as "0" and a character string, the size of data determined by the DATALENGTH setting is read, starting from the address indicated by the DATASEG setting.  If DATALENGTH = 0, data is read up to the end of the data area.• If DATASEG is specified as a character string, a size of data determined by DATALENGTH, starting from the address speci-fied by DATASEG, is read (segment specification).• When the data of all segments is batch read, both DATASEG and DATALENGTH are omitted (they are zero length items).• When all the data for a particular segment is read, DATALENGTH is omitted (it is a zero length item).• In a segment specification, it is not possible to specify a DATALENGTH that exceeds the maximum length of the relevant DATASEG.• In a segment specification, if a DATALENGTH that is under the set length for DATASEG is specified, only the data corre-sponding to specified DATALENGTH is read.S18,F6 Read Data  S,H→E,replyL,41.<TARGETID> "01"-"31"2.<SSACK>3.<DATA>4.L,s1.<STATUS1> ⋅ s.<STATUSs>• When the specified target is invalid:DATA item length = 0, s = 0, SSACK = "CE" communications error• In an address specification, if: (SEGMENT + DATALENGTH) ≤ total value for all segments then SSACK = "NO"• In an address specification, if: (SEGMENT + DATALENGTH) > total value for all segments then DATA item length = 0, s = 0, SSACK = "CE" communica-tions error• In a segment specification, if an undefined DATASEG is specified, or if the DATALENGTH is illegal:DATA item length = 0, s = 0, SSACK = "CE" communications error• When reading of all segment data is specified in a system where the data segment is not defined:DATA length = 0, SSACK = "NO"• If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items.
75CIDRW SystemUser’s ManualSECTION 4When SECS is UsedSECTION 4Reading from/Writing to ID Tags• Write dataData Segment Area  Refer to page 122.S18,F7 Write Request S,H→E,replyL,41.<TARGETID> "01"-"31"2.<DATASEG>3.<DATALENGTH>4.<DATA>• If DATASEG is specified as "0" and a character string, a size of data corresponding to the DATALENGTH setting and starting from the address within the data area indicated by the DATASEG setting is written (address specification).  If DATALENGTH = 0, data is written up to the end of the data area.• If DATASEG is specified as a character string, a size of data determined by DATALENGTH, starting from the address speci-fied by DATASEG, is written (segment specification).• When the data for all segments is batch written, both DATASEG and DATALENGTH are omitted (they are zero length items).• When all the data for a particular segment is written, DATALENGTH is omitted (it is a zero length item).• In a segment specification, it is not possible to specify a DATALENGTH that exceeds the maximum length of the relevant DATASEG.• In a segment specification, if a DATALENGTH that is under the set length for DATASEG is specified, only the data corre-sponding to the specified DATALENGTH is written, compressed into the smaller addresses.• The item lengths of DATASEG and DATA must be matched.• If DATASEG and DATALENGTH are both omitted (made zero length items), the length of DATA must match the total of the set lengths of all segments.S18,F8 Write Acknowledge S,H←EL,31.<TARGETID> "01"-"31"2.<SSACK>3.L,s1.<STATUS1> ⋅ s.<STATUSs>• When the specified target is invalid:s = 0, SSACK = "CE"  communications error• In an address specification, if:(SEGMENT + DATALENGTH) ≤ total value for all segments then SSACK = "NO"• In an address specification, if:(SEGMENT + DATALENGTH) > total value for all segments then DATA item length = 0, s = 0, SSACK = "CE" (communica-tions error)• In a segment specification, if DATASEG and DATALENGTH are illegal: s = 0, SSACK = "CE" communications error• If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items.
76SECTION 4When SECS is UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID Tags• Read ID Data Segment Area  Refer to page 122.• Write IDData Segment Area  Refer to page 122.S18,F9 Read ID Request S,H→E,reply1.<TARGETID> "01"-"31"S18,F10 Read ID Data  S,H←EL,41.<TARGETID> "01"-"31"2.<SSACK>3.<MID>4.L,s1.<STATUS1> ⋅ s.<STATUSs>• If the MID data contains Non-Visible ASCII code:s = 0, MID item length = 0, SSACK = "EE" execution error• When the specified target is invalid:s = 0, MID item length = 0, SSACK = "CE"  communications error• If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items.S18,F11 Write ID Request S,H→E,replyL,21.<TARGETID> "01"-"31"2.<MID>• If an MID that is under the length set for the CarrierIDlength attribute is specified, an error occurs and the MID data is not written.S18,F12 Write ID Acknowledge S,H←EL,31.<TARGETID> "01"-"31"2.<SSACK>3.L,s1.<STATUS1> ⋅ s.<STATUSs>• When the specified target is invalid:s = 0, SSACK = "CE"  communications error• When there is an MID length error:s = 0, SSACK = "CE"  communications error• If the MID data contains Non-Visible ASCII code:s = 0, SSACK = "EE" execution error• If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items.
77CIDRW SystemUser’s ManualSECTION 4When SECS is UsedSECTION 4Reading from/Writing to ID Tags• Subsystem command (ChangeState)S18,F13 Subsystem Command Request (ChangeState) S,H→E,replyL,31.<TARGETID> "00" (fixed)2.<SSCMD> "ChangeState"3.L,11.<CPVAL1> "OP", "MT" or "PS"CPVAL = "PS" is a parameter setting unique to this CIDRW Controller for switching to the Setting mode.S18,F14 Subsystem Command Acknowledge (ChangeState) S,H←EL,31.<TARGETID> "00"2.<SSACK>3.L,s1.<STATUS1> ⋅ s.<STATUSs>• When the specified target is invalid:s = 0, SSACK = "CE"  communications error• When SSCMD is invalid:s = 0, SSACK = "CE"  communications error• When OperationalStatus is BUSY:s = 0, SSACK = "EE"  execution error• If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items.
78SECTION 4When SECS is UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID Tags• Subsystem command (GetStatus)• Subsystem command (PerformDiagnostics)S18,F13 Subsystem Command Request (GetStatus) S,H→Ε,replyL,31.<TARGETID> "00"-"31"2.<SSCMD> "GetStatus"3.L,0S18,F14 Subsystem Command Acknowledge (GetStatus) S,H←EL,31.<TARGETID> "00"-"31"2.<SSACK> "GetStatus"3.L,s1.<STATUS1> ⋅ s.<STATUSs>• When the specified target is invalid:s = 0, SSACK = "CE"  communications error• When SSCMD is invalid:s = 0, SSACK = "CE"  communications error• If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items.S18,F13 Subsystem Command Request (PerformDiagnostics) S,H→E,replyL,31.<TARGETID> "00"-"31"2.<SSCMD> "PerformDiagnostics"3.L,0S18,F14 Subsystem command Acknowledge (PerformDiagnostics) S,H←EL,31.<TARGETID> "00"-"31"2.<SSACK>3.L,s1.<STATUS1> ⋅ s.<STATUSs>• When the specified target is invalid:s = 0, SSACK = "CE"  communications error• When SSCMD is invalid:s = 0, SSACK = "CE"  communications error• If the status of SSACK is other than "NO" (normal), the List of Status will comprise zero items.
79CIDRW SystemUser’s ManualSECTION 4When SECS is UsedSECTION 4Reading from/Writing to ID Tags• Subsystem command (Reset)S18,F13 Subsystem Command Request (Reset) S,H→E,replyL,31.<TARGETID> "00" (fixed)2.<SSCMD> "Reset"3.L,0S18,F14 Subsystem Command Acknowledge (Reset) S,H←EL,31.<TARGETID> "00"2.<SSACK>3.L,0• When the specified target is invalid:SSACK = "CE"  communications error• When SSCMD is invalid:SSACK = "CE"  communications error
80SECTION 4When SECS is UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID TagsOperation ConditionsThe response messages and response codes (SSACK) in each state are shown below:State Initializing Operating MaintenanceMessage Function IDLE BUSYS1,F1 OnlineRequest S1,F0 S1,F2 S1,F2 S1,F2S18,F11 WriteID S18,F0 S18,F0 S18,F0 NOS18,F7 WriteData S18,F0 NO NO S18,F0S18,F3 SetAttribute S18,F0 NO NO NOS18,F13(Reset) Reset S18,F0 NO NO NOS18,F9 ReadID S18,F0 NO NO NOS18,F5 ReadData S18,F0 NO NO S18,F0S18,F13(PerformDiagnostics) Diagnostics S18,F0 NO NO NOS18,F13(GetStatus) GetStatus S18,F0 NO NO NOS18,F1 GetAttribute S18,F0 NO NO NOS18,F13(ChangeState) ChangeState(to MT) S18,F0 NO S18,F0 S18,F0S18,F13(ChangeState) ChangeState(to OP) S18,F0 S18,F0 S18,F0 NOS18,F13(ChangeState) ChangeState(to PS) S18,F0 NO S18,F0 NO
81CIDRW SystemUser’s ManualSECTION 4When SECS is Not UsedSECTION 4Reading from/Writing to ID TagsWhen SECS is Not UsedCommand/Response FormatMeaning of FCS (frame check sequence)This is two ASCII code characters obtained by conversion from the 8-bit exclusive logical sum (EOR) of the charactersfrom the character immediately after SOH to the character immediately before FCS.Example:  Reading the data of page 1 and page 2 of node No.1:CommandSOH Node No. Command code Parameter FCS CR1 ⋅ ⋅ ⋅  n01h 0DhResponseSOH Node No. Response codeParameter FCS CR1 ⋅ ⋅ ⋅  n01h 0DhCommandCalculation range(ASCII conversion)
82SECTION 4When SECS is Not UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID TagsCommandCommand code listName Value Function SeeREAD 0100 When this command is received, the system communicates with the ID Tag, and reads the specified page(s) of data.  Any pages up to a maximum of 16 can be selected.p.83WRITE 0200 When this command is received, the system communicates with the ID Tag, and writes the specified page(s) of data.  Any pages up to a maximum of 16 can be selected.p.84Same Write 0300 When this command is received, the system communicates with the ID Tag, and writes the same data in page units to the specified pages.  Up to 17 pages, which is the maximum number of pages for an ID Tag, can be specified.p.86Byte Write 0400 When this command is received the system communicates with the ID Tag, and writes data to the area specified by a first address and number of bytes.  A maximum of 128 bytes can be specified.p.87TEST 10 Sends received data to the host device. p.88NAK 12 Sends the response made immediately before again. p.89Noise measurement 40 Measures the noise in the vicinity of the CIDRW Head. p.89RESET 7F Resets the Amplifier Unit. p.89Response code listType Response code Name DescriptionNormal end 00 Normal end Command execution is completed normally.Host communi-cations error14 Format error There is a mistake in the command format.(E.g. the command code is undefined, or the page or address spec-ification is inappropriate.)Communica-tions error70 Communications error Noise or another hindrance occurs during communication with an ID Tag, and communications cannot be completed normally.71 Verification error Correct data cannot be written to an ID Tag.72 No Tag error Either there is no ID Tag in front of the CIDRW Head, or the CIDRW Head is unable to detect the ID Tag due to environmental factors (e.g. noise).7B Outside write area error Writing is not completed normally.7E ID system error (1) The ID Tag is in a status where it cannot execute command pro-cessing.7F ID system error (2) An inapplicable ID Tag has been used.
83CIDRW SystemUser’s ManualSECTION 4When SECS is Not UsedSECTION 4Reading from/Writing to ID TagsREADReads any pages of data from the ID Tag.  The maximum number of pages that can be read at onetime is 16.Data Segment Area  Refer to page 122.The response code (when normal: 00) and the data in the specified pages are returned in ascending order ofpage numbers.Example: Reading the data of pages 1 and 3 of node No.1Parameter descriptionParameter DescriptionPage designation Pages are specified by setting the bits corresponding to pages that are to be read to "1" and setting the other bits to "0", then converting the result to a hexadecimal character string.SOH Node No. Response codeRead dataFCS CRPage n  ⋅ ⋅ ⋅  Page m (n<m)Data 1  ⋅ ⋅ ⋅ Data 8 Data 1  ⋅ ⋅ ⋅  Data 801h 0 0 0DhData content of the ID TagPage 1 12h 34h 56h 78h 90h 12h 34h 56hPage 2Page 3 11h 22h 33h 44h 55h 66h 77h 88hPage 4CommandBit 7-07-321076-1076-210PageSys-SysSys-Sys1716151413-8765-1SysSysDesignation 0* 0* 0* 0* 0* 0/1 0/1 0/1 0/1 0/1 ••• 0/1 0/1 0/1 0/1 ••• 0/1 0* 0*Value 00 00 - 07 00 - FF 00 - FC* Always specify 0.  If you specify 1 an error (Response code : 14) will occur.SOH Node No. Command code Page designation (8 characters) FCS CR01h 0100 0DhResponseCommand00000000000000000000000000010100Binary notationSOH Node No. Command code Page designation FCS CR01h01010000000014050Dh
84SECTION 4When SECS is Not UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID TagsWRITEData is written in page units to the ID Tag.  Any page(s) can be specified.  It is possible to write to amaximum of 16 pages at one time.Data Segment Area  Refer to page 122.The response code (when normal: 00) is returned.SOH Node No. Response code Page 1 Page 3 FCS CR01h 0 1 0 0 12345678901234561122334455667788070DhParameter descriptionParameter DescriptionPage designation Pages are specified by setting the bits corresponding to pages that are to be read to "1" and setting the other bits to "0", then converting the result to a hexadecimal character string.Write data The data to be written to the specified pages is specified in ascending order of page numbers.SOH Node No. Response code FCS CR01h 0 0 0DhResponseCommandBit 7-07-321076-1076-210PageSys-SysSys-Sys1716151413-8765-1SysSysDesignation 0* 0* 0* 0* 0* 0/1 0/1 0/1 0/1 0/1 ••• 0/1 0/1 0/1 0/1 ••• 0/1 0* 0*Value 00 00 - 07 00 - FF 00 - FC* Always specify 0.  If you specify 1 an error (Response code : 14) will occur.SOH Node No.Command codePage designation(8 characters)Write dataFCS CRPage n  ⋅ ⋅ ⋅  Page m (n<m)Data 1  ⋅ ⋅ ⋅  Data 8 Data 1  ⋅ ⋅ ⋅  Data 801h 0200 0DHResponse
85CIDRW SystemUser’s ManualSECTION 4When SECS is Not UsedSECTION 4Reading from/Writing to ID TagsExample:  Writing data to pages 8 and 10 of node No.1:The ID Tag status on normal completion is as shown below:SOH Node No. Response code FCS CR01h0100010DhPage 8 11h 22h 33h 44h 55h 66h 77h 88hPage 9Page 10 01h 23h 45h 67h 89h ABh CDh EFhCommand00000000000000000000101000000000SOH Node No.Command codePage designation Data of page 8 Data of page 10 FCS CR01h 0 1 0 2 0 000000A0011223344556677880123456789ABCDEF 7 4 0DhBinary notationResponse
86SECTION 4When SECS is Not UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID TagsSame WriteWrites the same data to multiple pages of an ID Tag.Any page(s) can be specified.Data Segment Area  Refer to page 122.The response code (when normal: 00) is returned.Example:  Clearing pages 1 to 17 of node No.1 to 0:Parameter descriptionParameter DescriptionPage designation Pages are specified by setting the bits corresponding to pages that are to be read to "1" and setting the other bits to "0", then converting the result to a hexadecimal character string.Write data Specify the write data.SOH Node No. Response code FCS CR01h 0 0 0DhSOH Node No. Response code FCS CR01h0100010DhCommandSOH Node No. Command code Page designation (8 characters) Write data FCS CRData 1  ⋅ ⋅ ⋅  Data 801h 0 3 0 0 0DHBit 7-07-321076-1076-210PageSys-SysSys-Sys1716151413-8765-1SysSysDesignation 0* 0* 0* 0* 0* 0/1 0/1 0/1 0/1 0/1 ••• 0/1 0/1 0/1 0/1 ••• 0/1 0* 0*Value 00 00 - 07 00 - FF 00 - FC* Always specify 0.  If you specify 1 an error (Response code : 14) will occur.ResponseCommand00000000000001111111111111111100Binary notationSOH Node No. Command code Page designation Write data FCS CR01h 0 1 03000007FFFC0000000000000000 0 0 0DhResponse
87CIDRW SystemUser’s ManualSECTION 4When SECS is Not UsedSECTION 4Reading from/Writing to ID TagsByte WriteWrites data to any specified number of bytes starting from the address specified in the ID Tag.The maximum number of bytes that can be written at one time is 128.* Data number n = number of bytes written to (2-character units)Data Segment Area  Refer to page 122.The response code (when normal: 00) is returned.Example:  Writing to two bytes starting from address 05h of node No.1:The ID Tag status on normal completion is as shown below:SOH Node No. Command code First addressWrite data FCS CRData 1 ••• Data n01h 0400 0DhParameter descriptionParameter DescriptionAddress designation Addresses can be specified in the range 00h to 87h.Write data Up to 128 bytes of write data, starting from the specified address, can be specified.SOH Node No. Response code FCS CR01h 0 0 0DhSOH Node No. Command code First address Write data FCS CRData 1 Data 201h010400051234040DhSOH Node No. Response code FCS CR01h0100010DhPage 1 12h 34hPage 2CommandResponseCommandResponse
88SECTION 4When SECS is Not UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID TagsTESTPerforms a communication test on communications between the host device and Amplifier Unit.When an Amplifier Unit receives a test command, it sends the response code and command test datato the host device as the response.* Number of data n < 136 (2-character units)The response code (when normal: 00) and the received test data are returned.Example: Testing by sending the data "12345678" to node No.1:SOH Node No. Command code Test data FCS CRData 1 ••• Data n01h 1 0 0DhParameter descriptionParameter DescriptionTest data The data to be sent in the test is specified with a hexadecimal value.  (Max. 270 characters)However, note that odd numbers of characters cannot be used.SOH Node No. Response codeTest data FCS CRData 1 ••• Data n01h 0 0 0DhSOH Node No. Command code Test data FCS CRData 1 Data 2 Data 3 Data 401h01 1 0 12345678080DhSOH Node No. Response codeTest data FCS CRData 1 Data 2 Data 3 Data 401h010012345678090DhCommandResponseCommandResponse
89CIDRW SystemUser’s ManualSECTION 4When SECS is Not UsedSECTION 4Reading from/Writing to ID TagsNAKSends the response made immediately before again.Sends the response made immediately before again.Noise measurementThe levels of noise in the vicinity of the CIDRW Head are measured and the noise level is expressednumerically in the range "00" to "99."The response code (when normal: 00) and the noise level "00" to "99" are returned.Influence of background noise on communication distance  Refer to page 121.RESETAll Amplifier Unit processing is stopped, and the initial status is re-established.There is no response to this command.SOH Node No. Command code FCS CR01h 1 2 0DhSOH Node No. Command code FCS CR01h 4 0 0DhSOH Node No. Response code Noise level FCS CR01h 0 0 0DhSOH Node No. Command code FCS CR01h 7 F 0DhCommandResponseCommandResponseCommandResponse
90SECTION 4When SECS is Not UsedCIDRW SystemUser’s ManualSECTION 4Reading from/Writing to ID TagsMEMO
SECTION 5Troubleshooting91CIDRW SystemUser’s ManualSECTION 5TroubleshootingWhen SECS is Used 92When SECS is Not Used 98
92SECTION 5When SECS is UsedCIDRW SystemUser’s ManualSECTION 5TroubleshootingWhen SECS is UsedErrors are indicated by the contents of the CIDRW Controller response messages, and by the indicators.List of Error MessagesWhen responses are made to messages sent by the CIDRW Controller, errors are expressed by thecontents of error messages and the nature of the SSACK response.Controller IndicatorsIf an error or alarm has occurred at the CIDRW Controller, the LEDs on the front of the Controller light.S F Direction SECS II names10S,H←E Abort Transaction90S,H→E Abort Transaction91S,H←E Unrecognized Device ID93S,H←E Unrecognized Stream Type95S,H←E Unrecognized Function Type97S,H←E Illegal Data99S,H←E Transaction Timer Timeout911S,H←E Data Too Long18 0 S,H←E Abort TransactionName FunctionOPERATING (green) Lit when the operation status (status model) of the CIDRW system is "operating."ALARMS (green) Lit when the status of "AlamStatus" of the CIDRW system is "Alarm (1)." BUSY (green) Lit when the status of "OparationalStatus" of the CIDRW system is "BUSY."ERROR (red) When a processing error is detected (when SSACK is other than "NO"), this indicator is lit for 50 ms.
93CIDRW SystemUser’s ManualSECTION 5When SECS is UsedSECTION 5TroubleshootingOperation Check FlowchartNormal Operation Mode• Operating normally in the Normal Operation modeIndicatorsPOWER OPERATING ALARMS BUSY ERRORResponseResponse FunctionS F— — SSACK="NO"There is aresponse to messagetransmission.(SSNAK = other than"NO")Error occurrenceAll LEDs are litor flashing.POWER-LED is off.NoYesNoYesNoAn error has occurred in the CIDRW Controller power supply.Check the power supply of the CIDRW power supply.Check the contents of the response message.When the CIDRW Controller responds to a message transmis-sion  Refer to page 94.Yes An error has occurred at the CIDRW Controller.Check the status of the indicators.When all the LEDs are lit or flashing  Refer to page 94.Check if the settings of the CIDRW Controller and Amplifier Unit are correct.When the CIDRW Controller fails to respond to messages sent to it  Refer to page 95.When an error unrelated to message transmission and responses occurs  Refer to page 95.
94SECTION 5When SECS is UsedCIDRW SystemUser’s ManualSECTION 5Troubleshooting• When the CIDRW Controller responds to a message transmissionThere is a mistake in the message sent to the CIDRW Controller or the Amplifier Unit settings.  Aftertaking the appropriate corrective action, restart the Controller and the Amplifier Unit and send the mes-sage again.• When all the LEDs are lit or flashingAn error has occurred in the CIDRW Controller.After taking the appropriate corrective action, restart the CIDRW Controller.Response Main check pointsS F— 0 Status conditions when the message was issued (e.g. a Write ID Request message (S18, F11) was sent in the operating mode, or the message was sent during initial processing)Operation Conditions  Refer to page 80.9 7 Message composition: illegal attributes, insufficient items, etc.Other than aboveAscertain the cause from the contents of the SSACK response.CE • Mistake in the details of the items in the message(The node number of an amplifier that is not set was specified as the "TARGET ID," or a segment name that is not set has been specified for "DATASEG.")• Connection of RS-485 cables between Amplifier Units (failure to detect Amplifier Units)• Amplifier Unit baud rate settings (failure to detect Amplifier Units)• Node numbers of the Amplifier Units (The same number is set for more than one unit, making detection impossible)• Cable routing between the host device and CIDRW Controller (influence of background noise)• Noise levels of the power supply line to the CIDRW ControllerEE • Installation distance/inclination between the ID Tag and CIDRW Head• Background noise levels of the CIDRW Head• Installation spacing in relation to CIDRW Heads connected in other CIDRW systems• When the ID read command is executed, the carrier ID contains non-visible ASCII code.HE • Mistake in the details of the items in the message(A segment that does not match the Amplifier Unit specifications has been set; the response time-out setting is not correct.)• Connection and wiring of cable between CIDRW Controller and Amplifier Unit• Power supply to Amplifier Units• Amplifier Unit terminal resistance settings• Routing of each cable (influence of background noise)• Node numbers of the Amplifier Units (the same number is set for more than one unit)• Amplifier Unit error (hardware error)• Noise levels of the power supply lineTE • Type/specifications of the ID Tags used• Settings of the ID Tags used (lock, etc.)• Environment of use of the ID Tags (ID Tag breakage due to use in unanticipated ways)• ID Tag overwrite lifePOWER OPERATING ALARMS BUSY ERROR Main check points• Supply of 24 VDC power• The CIDRW Controller may be damaged.• Mode switch setting (Is the setting "0"?)If the error cannot be resolved after checking, the CIDRW Controller may be damaged.• The CIDRW Controller may be damaged.
95CIDRW SystemUser’s ManualSECTION 5When SECS is UsedSECTION 5Troubleshooting• When the CIDRW Controller fails to respond to messages sent to itThere is a mistake in the CIDRW Controller or Amplifier Unit settings.After taking the appropriate corrective action, restart the CIDRW Controller and Amplifier Unit.• When an error unrelated to message transmission and responses occursThere is a mistake in the settings of the CIDRW Controller and Amplifier Unit.After taking the appropriate corrective action, restart the CIDRW Controller and Amplifier Unit.POWER OPERATING ALARMS BUSY ERROR Main check points• Mode switch setting (Is the setting "0"?)• Cable wiring between the CIDRW Controller and host device• Communications conditions for communication between the CIDRW Controller and host device (baud rate, character composition, etc.)• Cable wiring between the CIDRW Controller and host device• Node numbers of the Amplifier Units (The same number is set for more than one unit.)POWER OPERATING ALARMS BUSY ERROR Main check points• Mode switch setting (Is the setting "0"?)• Amplifier Unit baud rate settings• Node numbers of the Amplifier Units (The same number is set for more than one unit.)• Connection and wiring of cable between CIDRW Controller and Amplifier Unit• Amplifier Unit error (hardware error)• Routing of each cable (influence of back-ground noise)
96SECTION 5When SECS is UsedCIDRW SystemUser’s ManualSECTION 5TroubleshootingSetting Mode• Operating normally in the Setting modeTerminal initial screen of the host device after startup in the Setting modeTerminal screen when parameter setting has been completed without errorIndicatorsPOWER OPERATING ALARMS BUSY ERRORError occurrenceAll LEDs are litor flashing.POWER-LED is OFFNoYesNoYesAn error has occurred in the CIDRW Controller power supply.Check the power supply of the CIDRW Controller.An error has occurred at the CIDRW Controller.Check the status of the indicators.When all the LEDs are lit or flashing  Refer to page 97.Check if the CIDRW Controller settings are correct.When the CIDRW Controller fails to respond to messages sent to it  Refer to page 97.When an error unrelated to message transmission and responses occurs  Refer to page 97.SETUP_START  <L22   ><XXX.XX, YYY.YY>_Software Revision LevelModel numberHardware Revision LevelSETUP_COMPLETE_
97CIDRW SystemUser’s ManualSECTION 5When SECS is UsedSECTION 5Troubleshooting• When all the LEDs are lit or flashingAn error has occurred in the CIDRW Controller.  After taking appropriate corrective action, restart theCIDRW Controller and check the indicators.• When the CIDRW Controller responds to a message transmissionThere is a mistake in the CIDRW Controller settings or the sent parameters.  After taking appropriatecorrective action, restart the CIDRW Controller and check the indicators.• When the CIDRW Controller fails to respond to messages sent to itThere is a mistake in the CIDRW Controller settings or the sent parameters.  After taking appropriatecorrective action, restart the CIDRW Controller and check the indicators.• When an error unrelated to message transmission and responses occursThere is a mistake in the settings of the CIDRW Controller or Amplifier Unit.  After taking appropriatecorrective action, restart the CIDRW Controller and Amplifier Unit and check the indicators.POWER OPERATING ALARMS BUSY ERROR Main check points• Supply of 24 VDC power• The CIDRW Controller may be damaged.• Mode switch setting (Is the setting "3"?)If the error cannot be resolved after checking, the CIDRW Controller may be damaged.• The CIDRW Controller may be damaged.POWER OPERATING ALARMS BUSY ERROR Main check points• Sent parameters (Are the parameters cor-rect?  Are the settings correct?)Response ContentsSETUP_FAILED [ ] The parameters are not updated.  The figure in square brackets [  ] indicates the line number where the error was first detected.  If a parity error is detected in the received characters, this figure is [0].POWER OPERATING ALARMS BUSY ERROR Main check points• Transmission parameters (Are the parameters correct?)• Communications conditions for communication between the CIDRW Controller and the host device (baud rate, character composition, etc.)• Mode switch setting (Is the setting "3"?)POWER OPERATING ALARMS BUSY ERROR Main check points• Mode switch setting (Is the setting "3"?)
98SECTION 5When SECS is Not UsedCIDRW SystemUser’s ManualSECTION 5TroubleshootingWhen SECS is Not UsedErrors are indicated by the presence or absence of a response to an Amplifier Unit command, and by theindicators.List of Error MessagesAmplifier Unit IndicatorsType Response code Name DescriptionHost communi-cations error14 Format error There is a mistake in the command format.(E.g. the command portion is undefined, or the page or address speci-fication is inappropriate.)Communications error between the CIDRW Head and ID Tag70 Communications errorNoise or another hindrance has occurred during communication with an ID Tag, and communications cannot be completed normally.71 Verification error Correct data cannot be written to an ID Tag.72 No Tag error Either there is no ID Tag in front of the CIDRW Head, or the CIDRW Head is unable to detect the ID Tag due to environmental factors (e.g. noise).7B Outside write area errorThe ID Tag is at a position where reading is possible but writing is not, so writing does not complete normally.7E ID system error (1) The ID Tag is in a status where it cannot execute the command pro-cessing.7F ID system error (2) An inapplicable ID Tag has been used.Name IndicationsRUN (green) Turns ON when the Amplifier Unit is in normal operation.COMM (orange) Turns ON during communications with the host device or during communications with an ID Tag.NORM (green) Turns On when the communications finish with no error.ERROR (red) Turns ON when an error occurs during communication with the host device, or during communication with an ID Tag.
99CIDRW SystemUser’s ManualSECTION 5When SECS is Not UsedSECTION 5Troubleshooting Operation Check FlowchartFrom Installation to Trial OperationErrors are indicated by whether or not a response to the test command is received and by the status ofthe Amplifier Unit indicators.• If the test command was received normally:IndicatorsRUN COMM NORM ERRORResponse code for the responseType Response code FunctionNormal 00 The command was received normally.Error occurrenceTest command transmissionRUN-LED is OFFNoYes An error has occurred at the Amplifier Unit.Amplifier Unit error  Refer to page 100.Check if the Amplifier Unit settings are correct.If there is no response to the command:  Refer to page 100.Response received Yes Check the nature of the response.If there is a response to the command Refer to page 100.No(Lights once)
100SECTION 5When SECS is Not UsedCIDRW SystemUser’s ManualSECTION 5Troubleshooting• Amplifier Unit errorCheck the status of the indicator LEDs after transmission of the test command.After taking appropriate corrective action, restart the Amplifier Unit, send the test command again andcheck again.• If there is no response to the command:Check the status of the indicator LEDs after transmission of the test command.After taking appropriate corrective action, restart the Amplifier Unit, send the test command again andcheck again.Method using RS signal control at the host device In a 1:N connection using Link Units, the RS signals generated from the host device by normal control must be input asCS signals.  Turn the RS signals OFF within 15 ms after the completion of data transmission.  Correct communicationswill not be possible without this control.• If there is a response to the command:Check the status of the indicator LEDs after transmission of the test command.After taking appropriate corrective action, restart the Amplifier Unit, send the test command again andcheck again.RUN COMM NORM ERROR Main check points—(If RUN is OFF, the status of the other indica-tor LEDs can be ignored.)• Influence of background noise (change installation position)• Amplifier Unit power supplyIf the error cannot be resolved after checking, the Amplifier Unit may be damaged.RUN COMM NORM ERROR Main check points• Amplifier Unit baud rate settings• Node numbers of the Amplifier Units (do not match the node number in the test command)• Connection and wiring of the cable between the host device and Amplifier Unit• OFF timing of the RS signals between the host device and Amplifier Unit• Routing of each cable (influence of background noise)If the error cannot be resolved after checking, the Amplifier Unit may be damaged.• Amplifier Unit baud rate settings• Connection and wiring of the cable between the host device and Amplifier Unit• Routing of the cables (influence of background noise)• OFF timing of the RS signals between the host device and Amplifier Unit• FCS (frame check sequence) calculation methodRUN COMM NORM ERROR Main check points• Node numbers of the Amplifier Units (The same number is set for more than one unit)If the error cannot be resolved after checking, the Amplifier Unit may be damaged.There is a mistake in the command format (number of charac-ters, character code, etc.).(Lights once)SD at host deviceRS at host deviceON only during data transmission from the host deviceWithin 15 ms(Lights once)
101CIDRW SystemUser’s ManualSECTION 5When SECS is Not UsedSECTION 5TroubleshootingFrom Trial Operation to CommunicationsErrors are indicated by the status of the indicators after transmission of the write command, and by theresponse code of the response.• If the ID Tag was processed normally:If there is no response to the write command, refer to the From Installation to Trial Operation, Operation Check Flowchart.    Refer to page 99.IndicatorsRUN COMM NORM ERRORResponse code for the responseType Response code FunctionNormal 00 The ID Tag was processed normally.Error occurrenceIs the response code 1 ?NoYes Check the command format.If the response code is 1  Refer to page 102.Yes Communication with the ID Tag has failed.If the response code is 7  Refer to page 102.Write command sentRUN-LED is OFFNoYes An error has occurred at the Amplifier Unit.Amplifier Unit error  Refer to page 102.Is the response code 7 ?Communications OKNo(Lights once) (Lights once)
102SECTION 5When SECS is Not UsedCIDRW SystemUser’s ManualSECTION 5Troubleshooting• Amplifier Unit errorCheck the status of the indicator LEDs after transmission of the command.After taking appropriate corrective action, send the write command again and check again.• If the response code is 1 :There is a host device communications error.Check the status of the indicator LEDs and the response code of the response after transmission of thecommand.After taking appropriate corrective action, send the write command again and check again.• If the response code is 7 :There is a communications error in communication between the CIDRW Head and ID Tag.Check the status of the indicator LEDs and the response code of the response after transmission of thecommand.After taking appropriate corrective action, send the write command again and check again.* The ID Tag has a lock function, but the amplifier unit has no function for locking an ID Tag.RUN COMM NORM ERROR Main check points—(If RUN is OFF, the status of the other indica-tor LEDs can be ignored.)• Influence of background noise (Change installation position)• Amplifier Unit power supplyIf the error cannot be resolved by checking the two points above, the Amplifier Unit may be damaged.RUN COMM NORM ERRORResponse code Main check points14 Command format(Command code, page designation, address designation, processed data volume, etc.)RUN COMM NORM ERRORResponse code Main check points70• Background noise levels of the CIDRW Head (Check the surroundings with the environmental noise level measurement function)• Distance to another CIDRW Head• Influence of background noise (Change installation position)If the error cannot be resolved after checking, the Amplifier Unit may be damaged.71 • ID Tag overwrite life (Replace the ID Tag)• Environment of use of the ID Tags (ID Tag breakage due to use in unanticipated ways)72 • Connection to the CIDRW Head• Distance between the ID Tag and CIDRW Head• CIDRW Head background noise levels (Check the surroundings with the environmental noise level measurement function)• Distance to another CIDRW Head7B • Distance between the ID Tag and CIDRW Head• Background noise levels of the CIDRW Head (Check the surroundings with the environmental noise level measurement function)• Distance to another CIDRW Head• Influence of background noise (Change installation position)7E • Type/specifications of the ID Tags used• Settings of the ID Tags used (The ID Tag lock function is used.*)• Environment of use of the ID Tags (ID Tag breakage due to use in unanticipated ways)7F(Lights once)(Lights once) (Lights once)
SECTION 6Appendix103CIDRW SystemUser’s ManualSECTION 6AppendixSpecifications and Dimensions 104System Configuration Examples 108When SECS is Not Used 109Characteristic Data depending on Conditions of Use 110Data Segment Area 122Regular Inspection 123SECS Protocol Specifications 124ASCII Code Table 129Protective Construction 130
104SECTION 6Specifications and DimensionsCIDRW SystemUser’s ManualSECTION 6AppendixSpecifications and DimensionsControllerV700-L22Item SpecificationsPower supply voltage 24 VDC +10% -15%Current consumption 150 mA max. (inrush current: approx. 10 A max.)Ambient temperature Operating: 0 to +40°C Storage: -15 to +65°C (with no icing)Ambient humidity Operating: 10 to 85% RH  Storage: 10 to 95% RH (with no condensation)Degree of protection IP20 (IEC60529)Insulation resistance 50 MΩ min. between power supply terminals and the frame ground terminal (500 VDC M)Dielectric strength Leak current not to exceed 3.5 mA on application of 500 VAC (50/60 Hz for 1 minute) between both power supply terminals and the frame ground terminalVibration resistance Frequency: 10 to 150 Hz; double amplitude: 0.20 mm; acceleration: 15 m/s2 for8 minutes, 10 times each in X, Y, and Z directionsShock resistance Shock of 150 m/s2 in X, Y, and Z directions, 3 times each for 18 repetitionsGround Ground to 100 Ω or less.Case material SECC (coating)Weight Approx. 570 g2:rr/Ǿ(Unit: mm)Mounting dimensionsPower indicatorIndicators(mounting holes)Four, 4.5-dia. holes
CIDRW SystemUser’s ManualSECTION 6Specifications and DimensionsSECTION 6Appendix105Amplifier UnitV640-HAM11Item SpecificationsPower supply voltage 24 VDC +10% -15%Current consumption 150 mA max.Ambient temperature Operating: 0 to +40°C  Storage: -15 to +65°C (with no icing)Ambient humidity Operating/Storage: 35 to 85% RH (with no condensation)Degree of protection IP20 (IEC60529 standard)Insulation resistance 20 MΩ min. between power supply terminals and the frame ground terminal (100 VDC M)Dielectric strength Leak current not to exceed 5 mA on application of 1000 VAC (50/60 Hz for 1 minute) between both power supply terminals and the frame ground terminalVibration resistance Frequency: 10 to 150 Hz; double amplitude: 0.20 mm; acceleration: 15 m/s2 for8 minutes, 10 times each in X, Y, and Z directionsShock resistance Shock of 150 m/s2 in X, Y, and Z directions, 3 times each for 18 repetitionsGround Ground to 100 Ω or less.Case material SECC (coating)Weight Approx. 500 g㧔㧕㧔㧕㧔㧕㧔㧕㧔㧕㧔㧕㧔㧕㧔㧕㧔㧕rr Ǿ/DIP switch(Unit: mm)Mounting dimensions4 indicatorsFour, 4.5-dia. holes
106SECTION 6Specifications and DimensionsCIDRW SystemUser’s ManualSECTION 6AppendixCIDRW HeadV640-HS61Item SpecificationsTransmission frequency 134 kHzAmbient temperature Operating: 0 to +40°C  Storage: -15 to +65°C (with no icing)Ambient humidity Operating/Storage: 35 to 85% RH (with no condensation)Degree of protection IP60 (IEC60529)Insulation resistance 20 MΩ min. between all terminals and the case (100 VDC M)Dielectric strength Leak current not to exceed 5 mA on application of 1000 VAC (50/60 Hz for 1 minute) between all terminals and the caseVibration resistance Frequency: 10 to 150 Hz; double amplitude: 0.20 mm; acceleration: 15 m/s2 for8 minutes, 10 times each in X, Y, and Z directionsShock resistance Shock of 150 m/s2 in X, Y, and Z directions, 3 times each for 18 repetitionsCasing material ABS/epoxy resinStainless steel mountWeight Approx. 70 gCable length 2 mCable specification 3-mm-dia. coaxial cablerrǾ/14ǾCoaxial cable 3.0 dia., standard length 2 m(Unit: mm)ConnectorAntenna centerAntenna centerMounting dimensionsFour M3 or 3.5-dia. holesFour, 3.5-dia. holes
CIDRW SystemUser’s ManualSECTION 6Specifications and DimensionsSECTION 6Appendix107Link UnitV700-L11Item SpecificationsPower supply voltage 24 VDC +10% -15%Current consumption 250 mA max. (inrush current: approx. 10 A)Ambient temperature Operating: 0 to +40°C  Storage: -15 to +50°C (with no icing)Ambient humidity Operating/Storage: 35 to 85% RH (with no condensation)Degree of protection IP20 (IEC60529)Insulation resistance 50 MΩ min. between power supply terminals and the frame ground terminal (500 VDC M)Dielectric strength Leak current not to exceed 5 mA on application of 1000 VAC (50/60 Hz for 1 minute) between power supply terminals and the frame ground terminalVibration resistance Frequency: 10 to 150 Hz; double amplitude: 0.20 mm; acceleration: 15 m/s2 for 8 minutes, 10 times each in X, Y, and Z directionsShock resistance Shock of 150 m/s2 in X, Y, and Z directions, 3 times each for 18 repetitionsGround Ground to 100 Ω or less.Case material PC/ABS resinWeight Approx. 200 grrǾ/ޓ14ޓǾ(Unit: mm)Mounting dimensionsTwo M4 or 4.2-dia. holesTwo, 4.5-dia. holes
118SECTION 6Characteristic Data depending on Conditions of UseCIDRW SystemUser’s ManualSECTION 6AppendixCommunications TimeRegardless of whether SECS is used or not, take the time required for processing between the hostdevice and Amplifier Units into account when designing the system.Communication time calculation formula (unit: ms)Read: 150.5 × (number of pages) + 6.1For write, same writing: 468.6 × (number of pages) + 80.3Byte write: 468.6 × (number of pages/8) + 229.9TAT calculation formula (units: ms)TAT = command and response transmission time + communication timeThe command and response transmission time differs depending on the number of characterssent and the communications conditions.This calculation applies to continuous transmission in which the Controller uses no spacesbetween command characters.Example of TAT calculation:Number of command characters: A; number of response characters: BBaud rate: 9600 bps, data length: 8 bits, non parity, 1 stop bitTime DescriptionCommunications time This is the time required for communication between an ID Tag and the CIDRW Head.TAT This is the time required for processing at the Amplifier Unit, seen from the host device.HostAmplifier UnitCommand ResponseCommunications timeTATRounding upTransmission time (ms) = Number of bits per character (bits)Baud rate (bps) × total number of characters of command and responseTAT (ms) = 109600 × (A + B) + Communications time (ms)
CIDRW SystemUser’s ManualSECTION 6Characteristic Data depending on Conditions of UseSECTION 6Appendix119The graph for communications time for communication between the ID Tag and CIDRW Head, andTAT (when the baud rate is 9600 bps), is shown below.Note however that the communications time and TAT may increase substantially according to the con-ditions of use.㪇㪌㪇㪇㪈㪇㪇㪇㪈㪌㪇㪇㪉㪇㪇㪇㪉㪌㪇㪇㪊㪇㪇㪇㪊㪌㪇㪇㪈㪉㪋㪍㪏㪈㪇㪈㪉㪈㪋㪈㪍ReadNumber of pages processedCommunications timeTAT (9600 bps)Communications time (ms)Communications time (ms)Write (same writing)Number of pages processedCommunications timeTAT (9600 bps)
120SECTION 6Characteristic Data depending on Conditions of UseCIDRW SystemUser’s ManualSECTION 6Appendix        Communications time (ms)Byte WriteNumber of bytes processedCommunications timeTAT (9600 bps)
122SECTION 6Data Segment AreaCIDRW SystemUser’s ManualSECTION 6AppendixData Segment AreaThe data segment area of the RI-TRP-DR2B ID Tag is shown below.When using a CIDRW Controller, always set the data segment.Refer to page 53.• The carrier ID memory area starts from page 1 (fixed).• 00h to 87h in the table are addresses. Page 8 bytes/1 page1 00h 01h 02h 03h 04h 05h 06h 07h2 08h 09h 0Ah 0Bh 0Ch 0Dh 0Eh 0Fh3 10h 11h 12h 13h 14h 15h 16h 17h4 18h 19h 1Ah 1Bh 1Ch 1Dh 1Eh 1Fh5 20h 21h ••• ••• 27h6 28h 29h ••• ••• 2Fh7 30h 31h ••• ••• 37h89 :10 : :11 :121314 68h 69h ••• ••• 6Fh15 70h 71h ••• ••• 77h16 78h 79h ••• ••• 7Fh17 80h 81h ••• ••• 87hDATASEG LENGTHCarrierID16"S01" 8"S02" 8"S03" 8"S04" 8"S05" 8"S06" 8"S07" 8"S08" 8"S09" 8"S10" 8"S11" 8"S12" 8"S13" 8"S14" 8"S15" 8Carrier ID(16 byte)Data area(Total of 120 bytes)Data segment area  Example of datasegment settings
CIDRW SystemUser’s ManualSECTION 6Regular InspectionSECTION 6Appendix123Regular InspectionIn order to maintain optimum performance of the functions of the CIDRW system, daily and periodicinspections are necessary.Inspection item Detail Criteria Tools requiredSupply voltage fluctuation Check that the supply voltage fluctuation at the power supply terminal block is within the permissible range.To be within supply voltage rating. MultimeterCheck that there are no frequent instan-taneous power failures or radical voltage drops.To be within permissible voltage fluctua-tion range.Power supply analyzerEnvironment Ambient tem-peratureCheck that the ambient temperature and humidity are within specified range.To be within the specified range. Maximum and minimum ther-mometerHygrometerAmbient humidityVibration and shockCheck that no vibration or shock is trans-mitted from any machines.Dust Check that the system is free of dust accumulation.To be none.Corrosive gas Check that no metal part of the system is discolored or corroded.I/O power supplyVoltage fluctu-ationCheck on the I/O terminal block that the voltage fluctuation and ripple are within the permissible ranges.To be within the specified range. MultimeterOscilloscopeRippleMounting condition Check that each device is securely mounted.There must be no loose screws. —Check that each connector is securely connected.Each connector must be locked or securely tightened with screws.Check that no screw of the terminal block is loosened.There must be no loose screws.Check that no wire is broken or nearly broken.There must be no wire that is broken or nearly broken.Check if grounding to 100 Ω or less has been done.To be grounded to 100 Ω or less.
124SECTION 6SECS Protocol SpecificationsCIDRW SystemUser’s ManualSECTION 6AppendixSECS Protocol SpecificationsA summary of the SEMI standards that relate to CIDRW is provided for reference when using this product.However, since the SEMI standards are subject to revision, you should also refer to the actual standards.• SEMI E99 THE CARRIER ID READER/WRITER FUNCTIONAL STANDARD• SEMI E5 EQUIPMENT COMMUNICATION STANDARD 2 MESSAGE CONTENT (SECS II)• SEMI E4 EQUIPMENT COMMUNICATION STANDARD 1 MESSAGE TRANSFER (SECS I)Operation ModelSet the CIDRW Controller's mode switch to "0" and start the system.  When the system starts, the ini-tial processing is completed first, then the system will operate according to the status defined by E99.CIDRW status modelOperational status OPERATING Operation in progress in the operating modeIDLE Status in which no processing is in progress at any headBUSY Status when processing is in progress at any of the headsMAINTENANCE Operation in progress in the maintenance mode# Transitions according to state changes from the host deviceAlarm status No alarm Status in which there are no alarms currently in effect at the CIDRW Controller or any of the connected headsALARM Status in which an alarm has occurred• If a head in an abnormal status is detected during head detection in initial processing, or no heads are detected.  (The error will not be cleared until the system has been restarted with the heads connected correctly.)• When a head error is detected in communications with an ID Tag. (The error will be automatically reset if it is cleared in subsequent processing.)• A CIDRW Controller internal error has occurred.Initial status(INITIALIZING)This is the status during processing such as internal initialization/head detection after startup, which is maintained until the CIDRW system is capable of its proper functions.CIDRW Head status modelOperational status OPERATING Status in which the head is operating normallyIDLE Status in which no processing is in progressBUSY Status in which processing is in progressNON-OPERATING Status in which a head check (CIDRW Head, Link Unit) is necessary(The CIDRW alarm status is the ALARM status.)
CIDRW SystemUser’s ManualSECTION 6SECS Protocol SpecificationsSECTION 6Appendix125Protocol Specifications• Character compositionStart bit (1) + data bits (8) + stop bit (1)* Conforms to SEMI E4• Protocol parameters• Double block detectionThe header of the block currently being received is compared with the correct block received immedi-ately before, and double blocks are detected.  A setting in the setting mode determines whether thisfunction is used or not.•Multi-blockMulti-blocks are supported at the receiving side (maximum of 128 blocks).Multi-blocks are used at the sending side.• Message sizeThe maximum receivable message size is 32 kbytes.• InterleavingThe receiving side supports interleaving and block interleaving.The sending side uses interleaving and block interleaving.The maximum number of simultaneously open transactions is 16.  If the maximum number isexceeded, SxF0 (abort transmission) is sent.• Device IDThe number of device IDs used is 1.  Device IDs are specified in the setting mode.• Block numbersWith a single block, the block number is either 1 or 0.  For multi-block transmission, the numbers 1 to128 are used.  The block number for a single block is set in the setting mode.• Treatment of the systems byteThe system byte comprises the source ID and the transaction ID.The source ID is a fixed value and is specified in the setting mode.The initial value of the transaction ID is 1 and the maximum value is 0xFFFF.  The value is incrementedfrom the first message transmission.Sign Name Default setting Setting range Setting unitBAUD Baud Rate 9600 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200 -DEVID Device ID 0 0 to 32767 1T1 Time-out between characters 0.5 s 0.1 to 10 s 0.1 sT2 Protocol time-out 10 s 0.2 to 25 s 0.2 sT3 Response time-out 45 s 1 to 120 s 1 sT4 Time-out between blocks 45 s 1 to 120 s 1 sRTY Retry limit 3 0 to 31 1M/S Master/slave M M : MasterS : Slave-
126SECTION 6SECS Protocol SpecificationsCIDRW SystemUser’s ManualSECTION 6Appendix•StoringThe method for storing in the BUSY status, e.g. because the internal buffer is full, is to use "NAK trans-mission."• Processing for time-out detectionAt T3 and T4 time-outs, the time-out is notified by the S9F9 message.• SECS parametersItem Default setting Range Setting UnitDouble block detection yes/no 1 1: The header of the block currently being received is compared with the correct block received immediately before, and double blocks are detected.0: Double block detection is not performed.-Source ID 0 0 to 32767 1Single block No. 1 0, 1 -
CIDRW SystemUser’s ManualSECTION 6SECS Protocol SpecificationsSECTION 6Appendix127Support AttributesCIDRW attribute definitionsAttribute names Description Access Re-quest Format and mountingBasic items "Configuration" Number of CIDRW Heads RO Y 20 "00"-"31"The number of heads connected when the system power is turned ON (automatic recognition)"AlarmStatus" Substate of current CIDRW alarmsRO Y 20"0" = no alarm"0" = alarm has occurred"OperationalStatus" Substate of current CIDRW operationsRO Y 20"IDLE""BUSY""MANT""SoftwareRevisionLevel" Software revision (version) RO Y 20 6byte"VVV.RR"(VVV = version, RR = revision)CarrierIDOffset The position of the offset, referenced to the first byte of the carrier ID in the tag.RW N 20 00-15However, (CarrierIDOffset + CarrierIDLength) ≤ 16.CarrierIDlength The number of bytes in the carrier ID (if there are any non-visible ASCII charac-ters in the carrier ID, the CIDRW returns an error to the host controller.RW N 20 01-16However, (CarrierIDOffset + CarrierIDLength) ≤ 16.Option "DateInstalled Date on which the sub-system was installedRW N 20 8 bytesAll " " (space) on shipping"DeviceType" CIDR / CIDRW classifica-tionRO N 20 5 bytes"CIDRW""HardwareRevisionLevel" Hardware revision number RO N 20 6 bytes"VVV.RR"(VVV = version, RR = revision)"MaintenanceData" Supplier dependent RW N 20 80 bytesAll " " (space) on shipping"Manufacturer" Manufacturer's name or ID RO N 20 17 bytes"OMRON Corporation""ModelNumber" Model name according to the makerRO N 20 6 bytes"L22 ""SerialNumber" System serial number RO N 20  max. 20 bytes(Not supported by the CIDRW)
128SECTION 6SECS Protocol SpecificationsCIDRW SystemUser’s ManualSECTION 6AppendixReader/writer head attribute definitionAttribute names Description Access Re-quest Format and mountingBasic items "HeadStatus" Current status RO Y 20"IDLE""BUSY""NOOP""HeadID" Head number 1 to 31 RO Y(multi)20"01"-"31"("00" indicates the CIDRW itself, so cannot be used.)Option "Cycles" Number of read/write oper-ations executedRO N 54 (unsigned 4-byte integer)(Not supported by the Reader/Writer Head)"HeadCondition" Maintenance status RO N 20"NO": No alarm"NM": Status in which normal operation is not possible and maintenance is neces-sary"RW": Read/write error"RT": Read/write error rate(Not supported by the Reader/Writer Head)"NP": Status of power supply and connection errors"HeadDateInstalled" Date on which the head was installedRO N 20 "YYYYMMDD"(Not supported by the Reader/Writer Head)"HeadMaintenanceData" Supplier dependent N N 20(Not supported by the Reader/Writer Head)
CIDRW SystemUser’s ManualSECTION 6ASCII Code TableSECTION 6Appendix129ASCII Code TableLeftmostbitsRight-most bitsb8 - b50000 1001 0010 0011 0100 0101 0110 0111 1000 1101 1010 1011 1100 1101 1110 1111b4 - b1RowLine0 12345678910 11 12 13 14 150000 0NUL TC7(DLE)(SP) 0 @ P ` pUndefined Undefined Undefined0001 1TC1(SOH) DC1!1AQaq0010 2TC2(STX) DC2"2BRbr0011 3TC3(ETX) DC3#3CScs0100 4TC4(EOT) DC4$4DTdt0101 5TC5(NEQ) TC8(NAK)%5EUeu0110 6TC6(ACK) TC9(SYN)&6FVf v0111 7BEL TC10(ETB)'7GWgw1000 5FE0(BS) CAN(8HXhx1001 9FE1(HT) EM)9IYiy1010 10FE2(LF) SUB*:JZjz1011 11FE3(VT) ESC+;K[k{1100 12FE4(FF) IS4(FS),<L\ l |1101 13FE5(CR) IS3(GS)-=M]m}1110 14S0 IS2(RS).>N^nÅP1111 15S1 IS1(US)/?O_oDEL
130SECTION 6Protective ConstructionCIDRW SystemUser’s ManualSECTION 6AppendixProtective ConstructionIP-  is governed by the test methods described below.  Check in advance the seal characteristics underthe actual environment and conditions of use.IP is the abbreviation of International Protection.IEC (International Electrotechnical Commission)Standard (IEC60529: 1989-11)(A) First numeral in code: Class of protection against entry of solid foreign material(B) Second numeral of code: Class of protection against the entry of waterClass Degree of protection0 No protection1 Protected against access by solid objects with a diameter of 50 mm or greater (e.g. human hands).2 Protected against access by solid objects with a diameter of 12.5 mm or greater (e.g. fingers).3 Protected against access by wires and solid bodies with a diameter of 2.5 mm or greater.4 Protected against access by wires and solid bodies with a diameter of 1 mm or greater.5 Entry of volumes of dust that would cause difficulties in normal operation of devices or compromise safety is prevented.6 Entry of dust is prevented.Class Degree of protection Outline of test methods (tests using water)0 No special protection No protection against the entry of water. No test1 Protection against droplets of water The product suffers no ill effects from droplets of water falling vertically onto it.Water droplets are sprayed onto the product from directly above for 10 minutes by water droplet exposure test apparatus.2 Protection against droplets of water The product suffers no ill effects from droplets of water directed at it at an angle of up to 15° to vertical.The water droplet expo-sure test apparatus is set to 15° from vertical and water droplets sprayed onto the product for 10 minutes (total of 2.5 min-utes in each direction).
CIDRW SystemUser’s ManualSECTION 6Protective ConstructionSECTION 6Appendix1313 Protection against spraying water The product suffers no ill effects from a water spray directed at it at up to 60° from vertical.Using the test apparatus shown in the figure to the right, water is sprayed from both directions, onto both sides of the product, at angles up to 60° from vertical for 10 minutes.4 Protection against splashing water The product suffers no ill effects from water splashed on it from all directions.Using the test apparatus shown in the figure to the right, water is splashed onto the product from all directions for 10 minutes.5 Protection against water jets The product suffers no ill effects from a water jet aimed directly at it from all directions.Using the test apparatus shown in the figure to the right, a water jet is directed at the product from all directions for 1 minute per square meter of outer cas-ing, with a minimum total exposure of 3 minutes.6 Protection against powerful jets of water Water does not enter the product when a powerful jet of water is directed at it from all directions.Using the test apparatus shown in the figure to the right, a water jet is directed at the product from all directions for 1 minute per square meter of outer cas-ing, with a minimum total exposure of 3 minutes.7 Protection against immer-sion in water No entry of water on immersion in water at the stipulated pressure for the stipulated time.Immerse in water for 30 minutes at a depth of 1 meter (when the height of the apparatus is less than 850 mm).8 Protection against immersion in water The product can be used while continually immersed in water.Depends on arrange-ments made between the manufacturer and the user of the product.Class Degree of protection Outline of test methods (tests using water)0.07 L/min.per hole in thespray nozzle0.07 L/min.per hole in thespray nozzleDiameter of spray nozzle head: φ6.3Diameter of spray nozzle head: φ12.5
132SECTION 6IndexCIDRW SystemUser’s ManualSECTION 6AppendixIndexAAmplifier Unit 27, 34Amplifier Unit Indicators 98Amplifier Unit V640-HAM11 20ASCII Code Table 129BByte Write 87CChange the data segment area 53Change the response time-out time 56Changing the Position of the Mode Switch on the Bottom of the Unit 48Characteristic Data depending on Conditions of Use 109CIDRW Controller 26, 31CIDRW Controller V700-L21 19CIDRW Head 28CIDRW Head V640-HS61 21CIDRW Systems that Conform to SEMI Standards (SEMI E99, E5, E4) 17Coaxial Mounting 110, 111Command 82Command/Response Format 81Communications Distance Characteristics vs. Ambient Noise 121Communications Test 65Communications Time 118Component Names and Functions 19Connections and Wiring 31Connector for connecting a CIDRW Head 34Controller Indicators 92EData Reading and Writing 28Data Segment Area 122GFeatures 17Flowchart for Getting Started 23For Coaxial Installation 116For Face-to-Face Installation 116For Parallel Installation 116From Installation to Trial Operation 99From Trial Operation to Communications 101HHost Connection Port 42IID Tag ↔ CIDRW System Communications Test 66IEC (International Electrotechnical Commission) Standard (IEC605291989-11) 130Influence of Background Metal on ID Tag 29Influence of Background Metals (Reference Only) 117Influence of Noise 29Installation 26LLink Unit 30, 41Link unit V700-L11 22List of Error Messages 92, 98MMaps of Communications Areas (Reference Only) 110Message Specifications 70Mounting 29Multi-connection port 45Mutual Interference Distances (Reference Only) 116NNAK 89Noise measurement 89Normal Operation Mode 93OOperation Check Flowchart 93, 99Operation Model 124PParallel Mounting 112, 113Positional Relationship between the CIDRW Head and the ID Tag 28Power Supply 41Power Supply and Grounding Wires 31, 34Protective Construction 130Protocol Specifications 125
CIDRW SystemUser’s ManualSECTION 6IndexSECTION 6Appendix133IndexRREAD 83Regular Inspection 123RESET 89Return to the Normal Operation mode 58RS-232C Port 36RS-485 Port 39SSame Write 86SECS port 32SECS Protocol Specifications 124Sending a Switching Command from the Host Device 49Set the Communications Conditions for Amplifier Units 61Set the Communications Conditions for Link Units 63Set the Communications Conditions for the CIDRW Controller 48Set the parameters for the communications conditions 50Setting Mode 96Specifications and Dimensions 104Specifications for Each Stream/Function 72Start the terminal software 49Support Attributes 127Switch to the Setting mode 48System Configuration 18TTEST 88Test for Communications with the Host Device 65VVertical Mounting 114, 115WWhat is a CIDRW System? 16When SECS is Not Used 65, 68, 81, 98When SECS is Used 18, 65, 66, 70, 92When the Mode is Selected by a Command Sent from the Host Device 58When the Mode is Selected with the Mode Switch on the Bottom of the Unit 58WRITE 84

Navigation menu