Balluff BISM4XX07 RFID Read-only, non-contact User Manual 1 of 2

Balluff Inc RFID Read-only, non-contact 1 of 2

Contents

User Manual 1 of 2.pdf

Technical Description, User's Guide EnglishBIS M-4xx-045-00x-07-S4
www.balluff.com
www.balluff.com 3876543219BIS M-4xx IO-Link DeviceRead/Write DeviceUser instructions 51.1 Conformity and user safety 51.2 Scope of delivery 51.3 About this manual 51.4 Structure of the manual 51.5 Typographical conventions 51.6 Symbols 61.7 Abbreviations 6Safety 72.1 Intended use 72.2 General safety notes 72.3 Meaning of the warnings 7Getting started 83.1 Mechanical connection 83.2 Electrical connection 11Basic knowledge 124.1 Function principle of Identification Systems 124.2 Example 134.3 Read distance/offset 144.4 Product description 144.5 Data integrity 144.6 Autoread 154.7 Supported data carrier types 154.8 IO-Link basic knowledge 15Technical data 165.1 Electrical data 165.2 Operating conditions 165.3 BIS M-400-045-001-07-S4 165.4 BIS M-400-045-002-07-S4 175.5 BIS M-401-045-001-07-S4 185.6 BIS M-402-045-002-07-S4 195.8 BIS M-451-045-001-07-S4 215.9 Dynamic mode 22IO-Link basics 246.1 Digital point-to-point connection 246.2 Process data container 256.3 Identificationdata and device information 25Parameterizing the read/write device 267.1 Required data 267.2 Mapping of parameterization data 277.3 Storing the parameterization data 29Startup 30Device function 319.1 Functional principle 319.2 Functional principle 319.3 Process data 32
4BIS M-4xx IO-Link DeviceRead/Write Device9.4 Protocol sequence 369.5 Protocol examples 379.6 Error codes 439.7 Data transmission timing 44Appendix 47 Type designation code 47 Accessories 47 ASCII table 48
www.balluff.com 5This product was developed and manufactured in accordance with applicable European stan-dards and directives.Declaration of ConformityThis product was developed and manufactured in accordance with applicable Euro-pean standards anddirectives.NoteYou can request a Declaration of Conformity separately.For additional safety instruction, refer to Chapter "Safety“ on page 7.UL listingControl No. 3TLJFile No. E227256Included in the scope of delivery:BIS M-4xx IO-Link device –BIS software CD –Condensed manual in printed form (DE, EN) –This manual describes the read/write device of the BIS M-4xx-IO-Link Identification System and includes startup instructions for immediate operation.This manual does not describe:The start-up, function and safe operation of the host device (PC, PLC, IO-Link Master). –The installation and function of accessories and expansion devices. –The manual is organized so that the sections build on each other.Chapter 2: Basic safety information.Chapter 3: The key steps for installing the Identification System.Chapter 4: Introduction to the material.Chapter 5: Technical data for the read/write device.Chapter 6: Basics on the IO-Link communications standard.Chapter 7: User-defined settings for the read/write device.Chapter 8: Integration into a fieldbus system using Profibus as an example.Chapter 9: Processor and host system interaction.The following conventions are used in this manual. Enumerations are shown as a list with an en-dash.Entry 1, –Entry 2. –Action instructions are indicated by a preceding triangle. The result of an action is indicated by an arrow.1.1 Conformity and user safety1.2 Scope of delivery1.3 About this manual1.4 Structure of the manual1.5 Typographical conventionsEnumerationsActionsUser instructions1BIS M-4xx IO-Link DeviceRead/Write Device
6Action instruction 1. ►Action result. ⇒Action instruction 2. ►Numbers:Decimal numbers are shown without additional indicators (e.g. 123), –Hexadecimal numbers are shown with the additional indicator – hex (e.g. 00hex).Parameters:Parameters are shown in italics (e.g. CRC_16).Directory paths:References to paths in which data are stored or are to be saved are shown in small caps (e.g. Pr o j e c t :\Da t a ty P e s \Us e r De f i n e D ).Cross-references indicate where additional information on the topic can be found (see "Technical Data“ starting on page 16).Attention!This symbol indicates a safety instruction that absolutely must be followed.Note, tipThis symbol indicates general notes.BIS Balluff Identification SystemCRC Cyclic Redundancy CodeDPP Direct Parameter PageEMC Electromagnetic CompatibilityLSB Least Significant BitMSB Most Significant BitPC Personal ComputerSIO Standard IOSPDU Service Protocol Data UnitPLC Programmable Logic ControllerTCP Transmission Control ProtocolSyntaxCross-references1.6 Symbols1.7 AbbreviationsUser instructions1BIS M-4xx IO-Link DeviceRead/Write Device
www.balluff.com 7The BIS M-4xx-... read/write device, together with other components of the BIS M, form the Identification System. They may only be used for this purpose in an industrial environment corresponding to Class A of the EMC law.This description applies for the read/write devices of the BIS M-4xx-... series.Installation and startupInstallation and startup are only to be performed by trained specialists. Any damage resulting from unauthorized manipulation or improper use voids the manufacturer's guarantee and war-ranty.When connecting the read/write device to an external controller, pay attention to the choice and polarity of the connection as well as the power supply.The read/write device must only be powered using approved power supplies (see Chapter 5 "Technical data" beginning on page 16).Attention!This is a Class A device. This device may cause RF disturbances in residential areas; in such a case the operator may be required to take appropriate countermeasures.Operation and testingThe operator is responsible for ensuring that locally applicable safety regulations are observed.In the event of defects and non-correctable faults in the Identification System, take the system out of service and secure it from unauthorized use. Attention!The pictogram used with the word "Attention" warns of a possible hazardous situation affecting the health of persons or equipment damage. Failure to observe these warning notes may result in injury or damage to equipment.Always observe the described measures for preventing this danger. ►2.1 Intended use2.2 General safety notes2.3 Meaning of the warningsSafety2BIS M-4xx IO-Link DeviceRead/Write Device
83.1 Mechanical connectionBIS M-400-...-001BIS M-400-...-002Getting started3BIS M-400-045-001-07-S4 read/write device, values in mmFig.1: 1 Maximum tightening torque 40 Nm 2 Sensing surfaceBIS M-400-045-002-07-S4 read/write device, values in mmFig.2: 1 Maximum tightening torque 40 Nm 2 Sensing surfaceBIS M-4xx IO-Link DeviceRead/Write Device
www.balluff.com 9BIS M-401-...-001BIS M-402-...-002BIS M-401-045-001-07-S4 read/write device, values in mmFig.3: 1 Maximum tightening torque 3 Nm 2 Earthing connector3 Sensing surfaceBIS M-402-045-002-07-S4 read/write device, values in mmFig.4: 1 Sensing surface 2 Maximum tightening torque 25 Nm3 Cable length 0.5 m 4 Maximum tightening torque 2 Nm 0[0[AAGetting started3BIS M-4xx IO-Link DeviceRead/Write Device
10BIS M-402-045-004-07-S4 read/write device, values in mmFig.5: 1 Sensing surface 2 Maximum tightening torque 1 Nm3 Cable length 0.5 m 4 Maximum tightening torque 2 NmBIS M-451-045-001-07-S4 read/write device, values in mmFig.6: 1 Maximum tightening torque 3 Nm 2 Read/write axis3 Earthing connector 4 Sensing surface0[ AA BIS M-402-...-004BIS M-451-...-001Getting started3BIS M-4xx IO-Link DeviceRead/Write Device
www.balluff.com 11Data carrier DistanceBIS M-101-...BIS M-106-...BIS M-107-...BIS M-108-...BIS M-110-...BIS M-111-...BIS M-115-...BIS M-102-...BIS M-112-...BIS M-105-...BIS M-122-...BIS M-120-... BIS M-150-...BIS M-151-...BIS M-400-045-... > 10 cm > 15 cm > 10 cm – –BIS M-401-045-... > 20 cm > 20 cm – > 25 cm –BIS M-402-045-... > 10 cm – > 10 cm – –BIS M-451-045-... – – – – > 25 cmRead/write device Minimum distanceBIS M-400-045-0xx-... 20 cmBIS M-401-045-001-... 60 cmBIS M-402-045-001-... 20 cmBIS M-451-045-001-... 60 cmNoteWhen installing two BIS M-4xx-...on metal, there is normally no mutual interference. Unfavorable use of a metal frame can result in problems when reading a data carrier. In this case, the read distance is reduced to 80% of the maximum value.In critical applications, a pre-test is recommended.IO-Link port (M12, A-coded, female)PIN Function1 +24 V2 NC3 GND4 C/QConnect data line to IO-Link Master. ►(See Balluff IO-Link catalog for connection cable and accessories) Shielded cables are recommended in electromagnetically distorted environments.NoteFor all variants, the ground connection of the read/write device or of the function ground are, depending on the system, to be connected to ground either directly / with low impedance or via a suitable RC combination.Distance between the data carriersDistance between the read/write devices3.2 Electrical connectionGetting started3BIS M-4xx IO-Link DeviceRead/Write Device
124.1 Function principle of Identification SystemsThe BIS M-4xx-045 Identification System is a contactless read and write system. The read/write device consists of evaluation electronics with permanently connected read/write head. The system can be used to program and to read information on a data carrier. The data and current status messages are transmitted from the Identification System to the host system via a defined protocol. This protocol can also be used to transmit additional commands to the device, such as switching off the read-head antenna.The primary components of the BIS M-4xx-045 Identification System are:Read/write device, –Data carrier. –Data is transmitted to the host system via an IO-Link Master.Schematic representation of an Identification SystemFig.7: 1 Connection to the IO-Link Master 2 Read/write device3 Data carriers 4 Read/write deviceThe data carrier is an autonomous unit that is supplied with power by the read/write head. The read/write head continuously sends a carrier signal that is picked up by the data carrier from within a certain distance. As soon as the data carrier is powered up by the carrier signal, a static read operation takes place. The read/write device manages the data transfer between read/write head and data carrier, serves as a buffer storage device, and sends the data to the host controller. The data is passed to the IO-Link Master using IO-Link protocol, and the Master then passes it to the host system.Host systems may be the following:a control computer (e.g. industrial PC), –as PLC. –The main areas of application are:in production for controlling material flow (e.g. in model-specific processes, in workpiece –transport with conveying systems, for acquiring safety-relevant data),in warehousing for monitoring material movements, –transportation, and –conveying technology. –Basic knowledge 4BIS M-4xx IO-Link DeviceRead/Write Device
www.balluff.com 13Topology of a BIS M-4xx-045 Identification SystemFig.8: 1 PLC 2 PC3 Fieldbus 4 IO-Link Master5 Connection to the host system 6 BIS M-4xx-045 read/write device1345624.2 ExampleBasic knowledge4BIS M-4xx IO-Link DeviceRead/Write Device
14Basic knowledge44.3 Read distance/offset4.4 Product description4.5 Data integrityTo ensure that data carriers are detected without error and the data can be reliably read, do not exceed a maximum distance and maximum offset between the data carriers and read heads (see Chapter 5 "Technical data“, page 16). The "distance" value refers to the maximum distance from the data carrier to the sensing surface of the read/write head. The "offset" value indicates the maximum offset between the center axis of the data carrier and the center axis of the sensing surface. Data carriers can only be reliably detected and the data reliably read within the permissible read distance and offset.Data carrier detection is indicated by an LED on the device ("TP – Tag Present", see Chapter 5 "Technical data“, page 16). At the same time, the CP bit is set in the input buffer ("CP – Codetag Present“, see Chapter 9.3 "Process data“, page 32).BIS M-400-045-0xx-07-S4 read/write device:M30 threaded tube, –round connector terminations, –integrated read/write head, –the read/write head is suitable for dynamic or static operation, –data carrier is powered by the read/write head using a carrier signal. –BIS M-4x1-045-0xx-07-S4 read/write device:plastic housing, –round connector terminations, –integrated read/write head, –the read/write head is suitable for dynamic or static operation, –data carrier is powered by the read/write head using a carrier signal. –BIS M-402-045-0xx-07-S4 read/write device:metal housing, –round connector terminations, –integrated read/write head, –the read/write head is head suitable for dynamic or static operation, –data carrier is powered by the read/write head using a carrier signal. –read/write head in plastic (...-004-...) or metal housing (...-002-...). –To ensure data integrity, data transfer between the data carrier and read/write device can be monitored using a CRC_16 data check.With the CRC_16 data check, a checksum is written to the data carrier which enables the data to be checked for validity at any time.Advantages of the CRC_16 data check:Very high data integrity, even during the non-active phase (data carrier outside the read/write –head)Restrictions of the CRC_16 data check:Longer write times, as the CRC must also be written. –User bytes are lost on the data carrier – (see table on page 15).Use of CRC_16 can be parameterized by the user (see Chapter 7 "Parameterizing the read/write device“, page 26).BIS M-4xx IO-Link DeviceRead/Write Device
www.balluff.com 15Basic knowledge44.6 Autoread4.7 Supported data carrier types4.8 IO-Link basic knowledgeThe Autoread function is used to immediately read out a specific memory area of the data carrier when the data carrier enters the vicinity of the read head. The data quantity in this case is always 8 bytes; the start address can be parameterized.If a read error occurs during autoread or if the specified data area lies outside the capacity of the data carrier, no error is displayed. In this case, no data is output.MifareBalluff data carrier typeManufac-turerDescription Memory capacityUsable bytes with CRCMemory typeBIS M-1_ _-01 NXP Mifare Classic 752 bytes 658 bytes EEPROMISO15693Balluff data carrier typeManufac-turerDescription Memory capacityUsable bytes with CRCMemory typeBIS M-1_ _-02 Fujitsu MB89R118 2000 bytes 1750 bytes FRAMBIS M-1_ _-03 NXP SL2ICS20 112 bytes 98 bytes EEPROMBIS M-1_ _-04 Texas Inst. TAG-IT Plus 256 bytes 224 bytes EEPROMBIS M-1_ _-05 Infineon SRF55V02P 224 bytes 196 bytes EEPROMBIS M-1_ _-06 EM EM4135 288 bytes 252 bytes EEPROMBIS M-1_ _-07 Infineon SRF55V10P 992 bytes 868 bytes EEPROMBIS M-1_ _-08 NXP SL2IC553 160 bytes 140 bytes EEPROMBIS M-1_ _-09 NXP SL2ICS50 32 bytes 28 bytes EEPROMAdvantages of IO-Link:Uniform, simple wiring of different devices –Host system can be used to change the device parameters –Remote querying of diagnostic information is possible –Centralized data retention of the device parameters is possible –The manufacturer-specific standard IO-Link sends not only the actual process signal, but also all relevant parameter and diagnostic data on the process level over a single standard cable.Communication is based on a standard UART protocol with 24V pulse modulation; no separate power supply is required.The BIS M-4xx-045-... is an IO-Link device which uses three-conductor technology (Physics 2). The transfer rate can be configured to 4800 (COM1), 38400 (COM2) or 230400 (COM3) baud. The data quantity of the process data is 10 bytes in each direction (see Chapter 9 "Device function“, page 31).BIS M-4xx IO-Link DeviceRead/Write Device
165.1 Electrical data(valid for all device versions)5.2 Operating conditions(valid for all device versions)5.3 BIS M-400-045-001-07-S4Mechanical dataTechnical data5Operating voltage VS18...30 VDC LPS/Class 2 supplied onlyRipple 1.3 VssCurrent draw 150 mALoad current capacity in SIO mode Maximum 50 mAOutput C/Q Short-circuit protectedDevice interface IO-LinkStorage temperature -20 °C … +85 °CAmbient temperature 0 °C … +70 °CEMCEN 301 489-1/-3 –EN 61000-4-2/-3/-4/-6 –EN 300 330-1 –Class BSeverity 2A/2A/4B*/XA**Power Class 5Vibration/shock EN 60068 Part 2 6/27/29/64/32*For 230.4 kBaud, use shielded cable.**Verified with shielded cable.BIS M-400-045-001-07-S4 read/write deviceFig.9: 1 LED 2 Maximum tightening torque 40 NmHousing material Nickel-plated brassConnection M12, 4-pin plug connectionEnclosure rating IP 67Weight 100 gBIS M-4xx IO-Link DeviceRead/Write Device
www.balluff.com 17LED Status FunctionLED 1 Green PowerLED 1 Yellow Data carrier detectedLED 1 Green flashing (1 s on / 100 ms off)IO-Link connection activeBIS M-400-045-002-07-S4 read/write deviceFig.10: 1 LED 2 Maximum tightening torque 40 NmHousing material Nickel-plated brassWiring M12, 4-pin plug connectionEnclosure rating IP 67Weight 100 gLED Status FunctionLED 1 and LED 2 Green PowerLED 1 and LED 2 Yellow Data carrier detectedLED 1 and LED 2 Green flashing (1 s on / 100 ms off)IO-Link connection active$/('/('/('/('$LED5.4 BIS M-400-045-002-07-S4Mechanical dataLEDTechnical data5BIS M-4xx IO-Link DeviceRead/Write Device
18Technical data55.5 BIS M-401-045-001-07-S4Mechanical dataLEDBIS M-401-045-001-07-S4 read/write deviceFig.11: 1 Maximum tightening torque 3 Nm 2 Earthing connector3 Sensing surfaceHousing material PBTConnection M12, 4-pin plug connectionEnclosure rating IP 67Weight 190 gLED Status FunctionLED 1 Green PowerLED 2 Yellow Data carrier detectedLED 1 Green flashing (1 s on / 100 ms off)IO-Link connection activeBIS M-4xx IO-Link DeviceRead/Write Device
www.balluff.com 19BIS M-402-045-002-07-S4 read/write device, values in mmFig.12: 1 Maximum tightening torque 25 Nm 2 Maximum tightening torque 2 Nm3 LEDHousing material AlMGSIO5Read/write head housing material Nickel-plated brassConnection M12, 4-pin plug connectionEnclosure rating IP 67Weight 220 gLED Status FunctionLED 1 Green PowerLED 1 Yellow Data carrier detectedLED 1 Green flashing (1 s on / 100 ms off)IO-Link connection active5.6 BIS M-402-045-002-07-S4Mechanical dataLEDTechnical data5BIS M-4xx IO-Link DeviceRead/Write Device
20BIS M-402-045-004-07-S4 read/write deviceFig.13: 1 Sensing surface 2 Maximum tightening torque 1 Nm3 LEDHousing material AlMGSIO5Read/write head housing material ABS-GF16Connection M12, 4-pin plug connectionEnclosure rating IP 67Weight 220 gLED Status FunctionLED 1 Green PowerLED 1 Yellow Data carrier detectedLED 1 Green flashing (1 s on / 100 ms off)IO-Link connection active.5.7 BIS M-402-045-004-07-S4Mechanical dataLEDTechnical data5BIS M-4xx IO-Link DeviceRead/Write Device
www.balluff.com 21BIS M-451-045-001-07-S4 read/write deviceFig.14: 1 Maximum tightening torque 3 Nm 2 Read/write axis3 Earthing connectorHousing material PBTConnection M12, 4-pin plug connectionEnclosure rating IP 67Weight 360 gLED Status FunctionLED 1 Green PowerLED 2 Yellow Data carrier detectedLED 1 Green flashing (1 s on / 100 ms off)IO-Link connection active5.8 BIS M-451-045-001-07-S4Mechanical dataLEDTechnical data5BIS M-4xx IO-Link DeviceRead/Write Device
22The read/write device can read or write each individual byte on the data carrier. But since the data carrier is divided into 16-byte memory blocks, the actual writing can only be performed in blocks. Our processor electronics convert this time accordingly.To calculate the read/write times, the block read or write time must, therefore, always be estima-ted.Data-carrier detection time [mm]Parameter "Used data carrier type“All BIS M1xx-01 BIS M1xx-02BIS M1xx-02 data carrier ≤ 40 - ≤ 27BIS M1xx-01 data carrier ≤ 30 ≤ 18 -Data carrier with 16 byte blocks BIS M-1xx-01 BIS M-1xx-02First block to be read ≤ 20 ≤ 35Other started 16 bytes ≤ 10 ≤ 25Data carrier with 16 bytes per block BIS M-1xx-01 BIS M-1xx-02First block to be read ≤ 40 ≤ 65Other started 16 bytes ≤ 30 ≤ 55NoteFluctuations in the ms range are possible. Electrical noise effects may increase the read/write time.To calculate the permissible speed at which the data carrier and head may move relative to one another, the static distance values are used (see Chapter 5 "Technical data“, pages 16 to 23).The permissible speed is:Vmax. perm..Path 2 * |offset value|= =Time Processing timeThe offset value is dependent on the read/write distance actually used in the system.Processing time = Data-carrier detection time +Read/write time of first block to be read+ n1XRead/write time for other started blocks1 Number of started blocksTechnical data55.9 Dynamic modeMemory accessData carrier detection timeRead timesWrite timesMaximum speedBIS M-4xx IO-Link DeviceRead/Write Device
www.balluff.com 23Technical data5Example calculation NoteThe texts, such as "Read time of first block to be read", can also be represented as variables: tL1.Read and write 44 bytes starting with address 15 of a BIS M-102-01/L data carrier with EEPROM memory and parameter setting of ALL for "Used data carrier type" using the BIS M-400-045-001-07-S4 read/write deviceThe distance from the sensing surface of the read/write head to the data carrier is 12 mm. A maximum clear zone is assumed, i.e. installation completely in plastic frame.Address 15 is in block 1 (15/16 = 0.94  block 1)Address 58 is in block 4 (58/16 = 3.63  block 4)Therefore, a total of 4 blocks will be processed, where the first block always has a slightly longer read or write time.Calculation of read/write time:Total read time = 30 ms + 20 ms + 3 x 10 ms = 80 msTotal write time = 30 ms + 40 ms + 3 x 30 ms = 160 msFor the specified values, this yields an offset of ± 20 mm.Calculation of maximum speed:Vmax.perm.read = 40 mm/80 ms = 0.5 m/sVmax.perm.write = 40 mm/160 ms = 0.25 m/sNoteFluctuations in the ms range are possible. Electrical noise effects may increase the read/write time.BIS M-4xx IO-Link DeviceRead/Write Device
246.1 Digital point-to-point connectionThree-conductor physicsCommunication modeInterleave modeIO-Link integrates conventional and intelligent actuators and sensors into automation systems. Mixed use of traditional and intelligent devices is possible with no additional expense. IO-Link is intended as a communications standard below the traditional fieldbus level. Fieldbus-neutral IO-Link transmission uses existing communications systems (fieldbuses or Ethernet-based systems).The actuators and sensors are connected in point-to-point connection using conventional unshielded cables. IO-Link devices can send application-specific parameters and data (e.g. diagnostics data) using a serial communication procedure. Flexible telegrams are possible for sending larger quantities of data. Communication is based on a standard UART protocol with 24V pulse modulation. Only one data line is used for communication. This carries both the controller telegram as well as the device telegram. This means that conventional 3-conductor physics is possible.IO-Link supports both communication mode as well as standard IO mode (SIO). Standard IO provides a switching signal on the communication line, as is used by normal binary switching sensors. This mode is only possible with devices using 3-conductor connection technology. Three-conductor physics of the IO-LinkFig.15: The BIS M-4xx-045... supports both modes. In SIO mode, the "Data carrier in range" (24 V) or "No data carrier in range" (0 V) signal is made available to the host system as a switching signal.If the BIS M-4xx-045… is not used with an IO-Link Master and without triggering IO-Link com-munication, it works in SIO mode and can be operated on a digital input.The BIS M-4xx-045-... works in communication mode with Frame Type 1. In this transmission type, 2 bytes of process data or required data are sent per frame (data block). This can take place either from the IO-Link Master to the device or vice-versa.Process data are the application-specific data; required data may contain parameters, service or diagnostic data.So-called "Interleave Mode" makes it possible to send larger quantities of data. There, multiple type 1 frames must be combined into a sequence. One frame with process data and one with required data are sent in alternation. With the BIS M-4xx-045-..., a sequence consists of 20 individual frames. 10 bytes of process data are sent in each direction per sequence. This process data is described in greater detail in Section 9.3 "Process data“ on page 32.IO-Link basics6BIS M-4xx IO-Link DeviceRead/Write Device
www.balluff.com 256.2 Process data container6.3 Identification data and device informationThe IO-Link protocol provides a process data container 32 bytes in size. Addressing occurs in the command byte, which is sent by the IO-Link Master. When process data is sent, addressing is directly to the subindices 00hex … 1Fhex.The BIS M-4xx-045-... processes 10 bytes of input and 10 bytes of output data (input buffer/output buffer). The process data is mapped to the first 10 bytes of the process data container (subindices 00hex…09hex).IO-Link protocolSubaddressBIS M-4xx IO-Link deviceSubaddress00hex ⇒00hex.........09hex ⇒09hex0Ahex...1FhexVia the Service-PDu, in addition to the application-specific parameters, information stored on the device can also be read.SPDU Object name Length InformationIndex SubindexIdentification data0hex 89101112Vendor ID 2 bytes Balluff Vendor ID = 0378hexDevice ID 3 bytes Balluff Device ID = 0602xxhex10hex 0 Vendor name 7 bytes Balluff11hex 0 Vendor text 15 byteswww.balluff.com12hex 0 Product name 23 bytesDevice designation13hex 0 Product ID 7 bytes Order code14hex 0 Product text 27 bytesIO-Link RFID read-write head16hex 0 Hardware revision 5 bytes Hardware version17hex 0 Firmware revision 5 bytes Firmware versionIO-Link basics6BIS M-4xx IO-Link DeviceRead/Write Device
267.1 Required data The device-specific parameters of the Identification System can be parameterized via the SPDU. The parameterization data of the BIS M-4xx-045-... is described in the following in greater detail.Access Description Data widthValue range Factory settingSPDUIndex SubindexParameterization data40hex 1hex CRC yes/no 1 byte 0 = without CRC1 = with CRC040hex 2hex Dynamic mode - yes/no1 byte 0 = no1 = yes040hex 3hex Action if tag present1 byte 0 = no action1 = serial number and tag type7 = automatically read 8 bytes of data beginning at a set start address after subindex 4 and 5140hex 4hex Low byte of start address for autoread2 bytes Observe data-carrier specifications. 040hex 5hex High byte of start address for autoread40hex 6hex Used data-carrier type1 byte See Chapter 7.2 "Mapping of parameterization data“, page 2700hex=ALLFEhex=BIS M1xx-01FFhex=BIS M1xx-02041hex 1hex Baud rate 1 byte 00hex = 4800 baud01hex = 38400 baud02hex = 230400 baud1NoteAn entire index can be addressed via subindex 0 . For example, with index 40hex/subindex 1hex, only the "CRCCheck" parameter is accessed. With index 40hex/subin-dex 0, on the other hand, all parameters from "RCCheck" to "Used data carrier type" can be addressed. The parameters are then arranged in byte blocks.Parameterizing the read/write device7BIS M-4xx IO-Link DeviceRead/Write Device
www.balluff.com 277.2 Mapping of parameterization dataCRC_16Data checkDynamic modeTo ensure data integrity, data transfer between the data carrier and read/write device can be monitored using a CRC_16 data check.With the CRC_16 data check, a checksum is written to the data carrier which enables the data to be checked for validity at any time.Advantages of the CRC_16 data check:Very high data integrity, even during the non-active phase (data carrier outside the read/write –head)Restrictions of the CRC_16 data check:Longer write times, as the CRC must also be written. –User data capacity is sacrificed. – (see table on page 15).NoteThe CRC_16 data check can only be used in combination with data carriers that have been appropriately initialized. If a data carrier is not initialized and this parameter is nevertheless set, CRC errors occur during reading and writing (see Chapter 9.6 "Error codes" page 43).The data carriers can be initialized for using CRC16 with command designator 12 hex. The checksum is written on the data carrier as 2 bytes (per block) of information. Thus, 2 bytes of user data is lost per block.The following figure applies for this parameter:Index 40hex, subindex 1hex - 1 byte7-MSB 6 5 4 3 2 1 0-LSBnot relevant 1/0** 0 = CRC_16 data check is not used (default setting). 1 = CRC_16 data check is used.If dynamic mode is activated, a job can be sent even if no data carrier is located in the read/write range of the read/write head, which would result in errors without dynamic mode. The job is then stored and is executed as soon as a data carrier is detected.The following figure applies for this parameter:Index 40hex, subindex 2hex - 1 byte7-MSB 6 5 4 3 2 1 0-LSBnot relevant 1/0** 0 = dynamic mode not activated (default setting). 1 = dynamic mode activated.Parameterizing the read/write device7BIS M-4xx IO-Link DeviceRead/Write Device
28Action if tag presentStart address for autoreadData carrierBaud rateThe "Action on tag present" parameter specifies how the read/write device is to react if a new data carrier is detected in the field. The default setting is to send the UID (serial number). In addition, it is possible to set that nothing or a selected range of 8 bytes is to be sent immediately as read data. The following values are permissible:Index 40hex, subindex 3hex - 1 byte0hex No action1hex Send UID immediately7hex Immediately send 8 bytes of data beginning at a set address (parameter "Autoread start address“)This parameter is only valid if "Autoread“ was selected as the action on tag present. The start address can be set via subindices 4hex (low byte) and 5hex (high byte). The value range is depen-dent on the specification of the data carrier; take this into account. An incorrect setting prevents autoread from functioning; no data is output.This parameter offers the possibility of specifying certain data carrier models that are to be detected. All models, all BIS M1xx-01 models or all BIS M1xx-02 models can be selected. The data carriers are detected more quickly if only those that are used are parameterized. The fol-lowing values are permissible:Index 40hex, subindex 6hex - 1 byte0hex All data carrier models supported by BalluffFEhex All BIS M1xx-01 model data carriersFEhex All BIS M1xx-02 model data carriersThe Baud Rate parameter can be used to set the used transfer rate. The Min Cycle Time, i.e. the time intervals at which the device may be queried by the IO-Link Master, is dependent on the setting of this parameter. The following table applies:Index 41hex, subindex 1hex - 1 byteIO Link designationBaud Rate [baud]Parameter settingMin Cycle TimeCOM1 4800 00hex 60hex = 12.8 msCOM2 38400 01hex 35hex = 5.3 msCOM3 230400 02hex 20hex = 3.2 msNoteNot all IO-Link Masters support COM3. This must absolutely be checked before parameterizing! After the speed has been parameterized once, the device is only parameterized for this speed and can only be reparameterized using a COM3-capa-ble IO-Link Master. The Balluff-USB-Master is recommended for this purpose. Please contact Balluff Sales for further information.After saving the parameter, the M-4xx-045-... performs a reset. During this process, IO Link communication is interrupted and errors can be displayed in the controller. Only after this reset does the device restart with the newly set baud rate.Parameterizing the read/write device7BIS M-4xx IO-Link DeviceRead/Write Device
www.balluff.com 297.3 Storing the parameterization dataThe set parameters are stored in the EEPROM memory of the BIS M-4xx-045-... On restart, the most recently used parameters are used.NoteShould it be necessary to exchange a BIS M-400-045-... in the system, make certain that the correct parameter settings are programmed in the new device.Parameterizing the read/write device7BIS M-4xx IO-Link DeviceRead/Write Device
30For information on starting up, please read the instructions for your IO-Link Master. BIS M4-xx IO-Link devices use a process buffer of 10 bytes for both the input and the output.Startup8BIS M-4xx IO-Link DeviceRead/Write Device
www.balluff.com 319.1 Functional principle9.2 Functional principleThe BIS M-4xx-045 Identification System is a contactless read and write system. The read/write device consists of evaluation electronics with permanently connected read/write head.The primary components of the BIS M-4xx-045 Identification System are:Read/write device, –Data carrier. –Schematic representation of an Identification SystemFig.16: 1 Connection to the IO-Link Master 2 Read/write device3 Data carriers 4 Read/write deviceThe data carrier is an autonomous unit which is supplied with power by the read/write head. The read/write head continuously sends a carrier signal which is picked up by the data carrier from within a certain distance. Once the data carrier is powered, a static read operation takes place. The processor manages the data transfer between read/write head and data carrier, serves as a buffer storage device, and sends the data to the controller. The data is passed to the IO-Link Master using IO-Link protocol, and the Master then passes it to the host system.Host systems may be the following:A control computer (e.g. industrial PC), –A PLC. –The BIS M-4xx-045 supports cyclical data exchange via IO-Link protocol and standard IO mode. Detection of a data carrier (Codetag Present, 24 V) or no data carrier present (0 V) is sent on data line C/Q as a digital switching signal.With cyclical data exchange, read data from the BIS M-4xx-045 are cyclically exchanged with the controller. It is also possible to read or enter parameter data in this operating mode.Device function9BIS M-4xx IO-Link DeviceRead/Write Device
329.3 Process dataOutput/Input bufferData exchange occurs via the process data, which, depending on the control system that is used, is mapped in the input and output buffer or in a memory field. The BIS M-4xx-045 uses 10 bytes of input data and 10 bytes of output data; the assignments are described in the following. Subaddress 00hex corresponds to the respective start address in the corresponding data field.To transfer commands and data between the BIS M-4xx-045 read/write device and the host sys-tem, the BIS M-4xx-045 provides two fields: – Output buffer – Input buffer These fields are embedded in process data transmission via the IO-Link Master. As already described, 10 bytes of process data are sent in each direction.The mapping of this process data is described in the following:Output buffer: Bit-No.Subaddress7654321000hex - 1st bit header TI KA GR AV01hex Command designator or data02hex Start address (low byte) or data03hex Start address (high byte) or data04hex Number of bytes (low byte) or data05hex Number of bytes (high byte) or data06hex Data07hex Data08hex Data09hex - 2nd bit headerTI KA GR AVExplanations for output buffer:Subaddress Bit nameMeaning Function description00hex 1st bit headerTI Toggle bit A state change during a job indicates that the controller is ready to receive additional data made available by the read/write device.KA Head on/off 1 = Head off (read/write head switched off)0 = Head on (read/write head in operation)GR Ground state 1 = Software reset - causes the BIS to switch to the ground state0 = Normal operationAV Job 1 = New job pending0 = No new job or job no longer pendingDevice function9BIS M-4xx IO-Link DeviceRead/Write Device
www.balluff.com 33Subaddress Bit nameMeaning Function description01hex Command designator00hex = No command01hex = Read data carrier02hex = Write data carrier12hex = Initialize the CRC_16 data check on the data carrier32hex = Write a constant value on the data carrieror data Data that is to be written on the data carrier02hex Start addressLow byteLow byte of the start address on the data carrier for the current jobor data Data that is to be written on the data carrier03hex Start addressHigh byteHigh byte of the start address on the data carrier for the current jobor data Data that is to be written on the data carrier04hex No. of bytesLow byteLow byte of the data length for the current jobor data Data that is to be written on the data carrier05hex No. of bytesHigh byteHigh byte of the data length for the current jobor data Data that is to be written on the data carrier06hex Data Data that is to be written on the data carrier07hex Data Data that is to be written on the data carrier08hex Data Data that is to be written on the data carrier09hex 2nd bit headerTI, KA, GR, AVIf 1st and 2nd bit headers agree, valid commands or data are present.NoteTo specify the start address and the number of bytes, the specifications of the used data carrier and the maximum job size of 256 bytes are to be observed!Device function9BIS M-4xx IO-Link DeviceRead/Write Device
34Input buffer: Bit-No.Subaddress7654321000hex - 1st bit header BB HF TO AF AE AA CP01hex Error code or data or high-byte version02hex Data or low-byte version03hex Data04hex Data05hex Data06hex Data07hex Data08he Data09hex - 2nd bit headerBB HF TO AF AE AA CPExplanations for input buffer:Subaddress Bit nameMeaning Function description00hex 1st bit headerBB Power 1 = Device is ready0 = Device is in ground stateHF Head Failure 1 = Head is turned off0 = Head is turned onTO Toggle Bit A state change during a job indicates that the read/write device is ready to transfer other dataAF Job Error 1 = Job incorrectly processed0 = Job processed without errorsAE Job End 1 = Job processed without errors0 = No job or job runningAA Job accepted 1 = The job was detected and accepted. Is being processed.0 = No job activeCP Codetag Present Data carrier is in the read range of the read/write headNo data carrier in read rangeDevice function9BIS M-4xx IO-Link DeviceRead/Write Device
www.balluff.com 35Subaddress Bit nameMeaning Function description01hex Error code Error number is entered if the job was incorrectly processed or canceled. Only valid with AF bit!00hex = No error01hex = No data carrier in read/write range02hex = Error during reading03hex = Data carrier was removed from the read range of the head during reading04hex = Error during writing05hex = Data carrier was removed from the write range of the read/write head during writing.07hex = AV-bit is set but command designator is invalid or missing. Or: number of bytes is 00hex.0Ehex = The CRC on the data carrier does not agree with the calculated CRC for the read data.0Fhex = 1st and 2nd bit header of the output buffer do not agree.20hex = Addressing of the job lies outside of the memory range of the data carrier21hex = Calls up a function that is not possible with the current data carrier.or data Data which was read from the data carrieror SW version High byte of the software version02hex Data Data which was read from the data carrieror SW version Low byte of the software version03hex Data Data which was read from the data carrier04hex Data Data which was read from the data carrier05hex Data Data which was read from the data carrier06hex Data Data which was read from the data carrier07hex Data Data which was read from the data carrier08hex Data Data which was read from the data carrier09hex 2nd bit headerBB, HF, TO, AF, AE, AA, CPIf 1st and 2nd bit headers agree, there is valid data presentDevice function9BIS M-4xx IO-Link DeviceRead/Write Device
36NoteThe 1st and 2nd headers must be compared by the user (host system) in order to query the validity of the sent data.When communication is initiated by the IO-Link Master, transmission of the current process data begins.As long as no data carrier was detected after start-up of the device, the firmware version of the device is displayed in the first two user bytes (see Chapter 9.5 "Protocol examples“, page 37).If a data carrier is detected, the "Reaction to Tag Present" set in the parameterization is execu-ted. If, for example, display serial number is set here, the serial number of the currently detected data carrier is displayed in index 01hex...08hex.The bit headers of the output buffer can be used to control the device. For example, a device restart can be triggered by setting the GR bit or a new job can be passed by setting the AV bit. Furthermore, the write data can be passed to the device here.The state of the device is displayed in the input buffer. Here, for example, the AF bit indicates an error in the current job and the HF bit indicates that the head is currently switched off. In addi-tion, the input buffer is used to pass read data and status codes. If no data carrier is present, the most recent data is displayed in the input buffer. The deleted CP bit indicates that no data carrier is in the field.By means of this method, all functions of the read/write device can be used. This includesreading, –writing, –dynamic reading, –dynamic writing, –writing a constant value, –initializing CRC16 on the data carrier. –NoteNote here that a job is limited to a maximum of 256 bytes. If more than 256 bytes are to be processed, multiple, individual jobs must be started.Functions can only be executed if a data carrier is in the read/write range. If a command is to be sent that is not to be executed until the next tag is encountered, the device must be paramete-rized for dynamic mode (see Chapter 7 "Parameterizing the read/write device“, page 26).9.4 Protocol sequenceDevice function9BIS M-4xx IO-Link DeviceRead/Write Device
www.balluff.com 37The following examples show the protocol sequence in various situations.Start the device, still no data in the output buffer:Command from controller BIS M-4xx-045-... reaction1. Process output buffer: 2. Process input buffer:00hex GR, KA, AV = 0 00hex Set BB09hex GR, KA, AV = 0 01hex e.g. 10hex = V 1.0002hex e.g. 10hex09hex Set BBReaction to Tag Present = no and new data carrier in the read range:Command from controller BIS M-4xx-045-... reaction1. Process output buffer: 2. Process input buffer:00hex GR, KA, AV = 0 00hex Set CP09hex GR, KA, AV = 0 09hex Set CPReaction to Tag Present = serial number and new data carrier in the read range:Command from controller BIS M-4xx-045-... reaction1. Process output buffer: 2. Process input buffer:00hex GR, KA, AV = 0 00hex Set CP09hex GR, KA, AV = 0 01 ... 08hex UID09hex Set CPReaction to TagPresent = read (start address 5) and data carrier in the read range:Command from controller BIS M-4xx-045-... reaction1. Process output buffer: 2. Process input buffer:00hex GR, KA, AV = 0 00hex Set CP09hex GR, KA, AV = 0 01hex Address 5 read data... Address 12 read data01 ... 08hex UID09hex Set CP9.5 Protocol examples1st example2nd example3rd example4th exampleDevice function9BIS M-4xx IO-Link DeviceRead/Write Device
385th example6th exampleDevice function9BIS M-4xx IO-Link DeviceRead/Write DeviceData carrier no longer in detection range of the read/write head:Command from controller BIS M-4xx-045-... reaction1. Process output buffer: 2. Process input buffer:00hex GR, KA, AV = 0 00hex Delete CP09hex GR, KA, AV = 0 09hex Delete CPInitialization of the CRC_16 data check on the data carrier (256 bytes beginning with address 0):Command from controller BIS M-4xx-045-... reaction1. Process subaddresses in the order shown:2. Process input buffer:01hex Command designator 12hex 00hex/09hex Set AA02hex Start address 00hex03hex Start address 00hex04hex No. of bytes 00hex05hex No. of bytes 01hex00hex/09hex Set AV3. Process subaddresses: 4. Copy received data, process subaddres-ses of the input buffer:01hex... 08hex Enter the first 8 bytes of data 00hex/09hex Invert TO00hex... 07hex Invert TI5. Process subaddresses: 6. Copy received data, process subaddres-ses of the input buffer:01hex... 08hex Enter the second 8 bytes of data00hex/09hex Invert TO00hex... 09hex Invert TI65. Process subaddresses: 66. Copy received data, process sub-addresses of the input buffer:01hex... 08hex Enter the last 8 bytes of data 00hex/09hex Set AE00hex... 09hex Invert TI67. Process subaddresses: 68. Process subaddresses:00hex/09hex Delete AV 00hex/09hex Delete AA and AENoteRepeat the process with the new addresses until the entire memory range of the data carrier is initialized.
www.balluff.com 397th exampleDevice function9BIS M-4xx IO-Link DeviceRead/Write DeviceRead 17 bytes starting at data carrier address 10:Command from controller BIS M-4xx-045-... reaction1. Process subaddresses in the order shown:2. Process input buffer:01hex Command designator 01hex 00hex/09hex Set AA02hex Start address 0Ahex 01hex... 08hex Enter the first 8 bytes of data03hex Start address 00hex04hex No. of bytes 11hex05hex No. of bytes 00hex00hex/09hex Set AV3. Copy received data, process subaddres-ses of the input buffer:4. Process subaddresses of the input buffer:00hex... 09hex Invert TI 01hex... 08hex Enter second 8 bytes of data00hex/09hex Invert TO5. Copy received data, process subaddres-ses of the input buffer:6. Process subaddresses of the input buffer:00hex... 09hex Invert TI 01hex Enter last byte of data02hex... 08hex 0x00 (empty)00hex/09hex Invert TO, set AE7. Copy received bytes, process sub-addresses of the input buffer:8. Process subaddresses of the input buffer:00hex... 09hex Delete AV 00hex/09hex Delete AF and AA
408th example Read 30 bytes starting at address 10 with read error:Command from controller BIS M-4xx-045-... reaction1. Process subaddresses in the order shown:2. Process input buffer:01hex Command designator 01hex *Error occurred immediately*02hex Start address 0Ahex 00hex/09hex Set AA03hex Start address 00hex 01hex Enter error number04hex No. of bytes 1Ehex 00hex/09hex Set AF05hex No. of bytes 00hex00hex/09hex Set AV3. Evaluate error number and process subaddresses of the output buffer:4. Process subaddresses of the input buffer:00hex... 09hex Delete AV 00hex/09hex Delete AF and AADevice function9BIS M-4xx IO-Link DeviceRead/Write Device
www.balluff.com 419th example Write 18 bytes starting at data carrier address 20Command from controller BIS M-4xx-045-... reaction1. Process subaddresses in the order shown:2. Process input buffer:01hex Command designator 02hex 00hex/09hex Set AA02hex Start address 14hex03hex Start address 00hex04hex No. of bytes 12hex05hex No. of bytes 00hex00hex/09hex Set AV3. Process subaddresses: 4. Copy received data, process subaddres-ses of the input buffer:01hex... 08hex Enter the first 8 bytes of data 00hex/09hex Invert TO00hex... 07hex Invert TI5. Process subaddresses: 6. Copy received data, process subaddres-ses of the input buffer:01hex... 08hex Enter the second 8 bytes of data00hex/09hex Invert TO00hex... 09hex Invert TI7. Process subaddresses: 8. Copy received data, process subaddres-ses of the input buffer:01hex... 02hex Enter the remaining 2 bytes of data00hex/09hex Set AE00hex... 09hex Invert TI9. Process subaddresses: 10. Process subaddresses:00hex/09hex Delete AV 00hex/09hex Delete AA and AEDevice function9BIS M-4xx IO-Link DeviceRead/Write Device
4210th example11th example12th exampleWrite constant data. 20 bytes, value 5Ahex, starting at address 0:Command from controller BIS M-4xx-045-... reaction1. Process subaddresses in the order shown:2. Process input buffer:01hex Command designator 32hex 00hex/09hex Set AA02hex Start address 00hex03hex Start address 00hex04hex No. of bytes 14hex05hex No. of bytes 00hex06hex Value 5Ahex00hex/09hex Set AV3. Data is written 00hex/09hex Set AE4. Process subaddresses: 5. Process subaddresses:00hex/09hex Delete AV 00hex/09hex Delete AA and AEMove read/write device to ground state:Command from controller BIS M-4xx-045-... reaction1. Process subaddresses: 2. Process input buffer:00hex/09hex Set GR 01...08hex 00hex (empty)00hex/09hex Delete BB3. Process subaddresses: 4. Process input buffer:00hex/09hex Delete GR 00hex/09hex Set BBPerform head shutdown:Command from controller BIS M-4xx-045-... reaction1. Process subaddresses: 2. Process input buffer:00hex/09hex Set KA 00hex/09hex Set HF, delete CP New data carriers are not detected, antenna is shut down.3. Process subaddresses: 4. Process input buffer:00hex/09hex Delete KA 00hex/09hex Set HF New data carriers are now detected again.Device function9BIS M-4xx IO-Link DeviceRead/Write Device
www.balluff.com 439.6 Error codes Error codeMeaning Remedy01hex No data carrier in read/write range Data carriers must already be in the read/write range when a command is sent; otherwise dynamic mode must be parameterized.02hex Read error Repeat job.03hex Data carrier was removed from the read range of the head during reading.04hex Write error Repeat job.05hex Data carrier was removed from the write range of the read/write head during writing.07hex AV is set, but the command designator is invalid or missing. Or: number of bytes is 00hex.Please check and correct.0Ehex CRC error Data carrier was not successfully read.Possible causes:Data carrier defective –Transmission failed –Data carrier not CRC capable –0Fhex Bit header error The two headers in the output buffer and in the host system do not agree.The headers must be matched (see "Output buffer“, page 32).20hex Addressing of the job lies outside of the memory range of the data carrier.Please correct addressing, taking into account the used data carrier.21hex Calls up a function that is not possible with the current data carrier.Observe permissible commands for the current data carrier.NoteIf an error occurs, a new command cannot be executed until the AV has first been deleted, i.e. the faulty job has been completed in full.Device function9BIS M-4xx IO-Link DeviceRead/Write Device
449.7 Data transmission timingThe sequence of the IO-Link communication is shown in the following diagram. Exchange alter-nates between the input buffer and the output buffer. As soon as current data is pending in one of the buffers, it is exchanged on the next in or out data cycle. The problem arises here that the transmission times can vary greatly. If data is updated shortly before the start of the respective exchange cycle, the transfer lasts just over 10 x cycle time (e.g. t2). If, however, data is updated shortly after the start of an exchange cycle, it lasts a maximum of 3 x 10 x cycle time (e.g. t3). The processing sequence of a command is shown on the next page using a read job of 9…16 bytes (2 x input buffer for read data) as an example.IO-Link transmission sequenceFig.17: t1 Cycle time In-Data: Input datat2 Polling time Out-Data: Output datat3 Cycle time Process Data Cycle: Process data cycleByte a+b: Process datax: Required dataCycle time t1: Time until the data of a data carrier that enters the read range is read. The read time is 70 ms x number of parameterized data comparison counts, default = 2 (see Chapter 7.2 "Mapping of parameterization data“, page 27).Polling time t2: Time until it is recognized that the data carrier is no longer in the read range (polling time). The polling time is xx ms.Cycle time t3: Time between the sending of two frames. The cycle time is dependent on the set baud rate and on the respective Master.Device function9BIS M-4xx IO-Link DeviceRead/Write Device
www.balluff.com 45In-Data/Out-Data: Sending of the input data and output data. 10 frames of 2 bytes each are sent, alternating between process data and required data (x).Process Data Cycle: A process data cycle consists of the complete sending of the input and output data. At the beginning of each process data cycle, the current data are polled and immediately sent.IO-Link transmission sequenceFig.18: 1 The command is passed on to the IO-Link Master by the controller via a bus system.2 After the synchronization time t1, the command is passed on to the BIS M-400-045-… via IO-Link. The duration is dependent on the bus system, the Master, the cycle time and the current state of the IO-Link communication (see problem described above).3 The processing time begins with the arrival of the command at the M-400-045-…This is composed of the time for the command processing t2, the time for the actual read operation t3 and the evaluation time for the read data t4. A flat value of max. 3 ms can be estimated for t2 and t3. The pure read time is calculated as described (see Chapter 5.9 "Dynamic mode", page 22). Please note: If the data carrier that is to be read was already detected by the device, the time for data carrier detection is eliminated.4 The pure time for data carrier processing is shown here.5 Following another synchronization time t5, the first data is passed on to the IO-Link Master with the next In-Data cycle. In addition, the AE-bit is set in the bit header. The time for this is t7 = 10 x cycle time.6 The data is only passed on to the controller via the host bus system. The latency period t6 is dependent on the bus system and the IO-Link Master.7 After the first data arrives at the controller, the toggle-bit in the output buffer must be inverted (see Chapter 9 "Device function“, page 31). In the example, it is assumed that the this occurs immediately and that the transfer to the IO-Link Master happens fast enough that the BIS M-400-045-… receives the new data on the next Out-Data cycle.Device function9BIS M-4xx IO-Link DeviceRead/Write Device
468 Now, the device places the next and, thus, the last bytes of the read data in the input buffer and inverts the toggle bit.9 The controller retrieves the data and deletes the AV bit.10 The re-updated output buffer is sent to the BIS M-400-045-….11 The device ends the read command and deletes the bits in the bit header in the input buffer that belong to the job .NoteThe sequence for a write command occurs analogously. Here, the data is transfered via IO-Link and the actual writing on the data carrier is interchanged.A maximum command processing time can be approximated as follows:Ttotproc.max = 40 x tcyc + read/write speed + 5 ms + 30 x tcyc + 20 x tcyc x n1 = 5 ms + tread/write speed2 + tcyc3 x (70 + 20 x n)1 Number of bytes/8 (rounded to the next whole number)2 Calculated time for data carrier processing (see Chapter 5.9 "Dynamic mode“, page 22)3 Master Cycle Time.NoteThe actual required time may be considerably less than the maximum processing duration.NotePrerequisite for calculating the maximum command processing time is that no delays occur in the host bus system and in the controller.Device function9BIS M-4xx IO-Link DeviceRead/Write Device
www.balluff.com 47 Type designation code Accessories (optional, not included)AppendixBIS M-4xx IO-Link DeviceRead/Write DeviceBIS M – 4xx – 045 – 0xx –07– S4Balluff Identification SystemSeries M = Read and write system, 13.56 MHz Hardware type4xx = Read/write deviceSoftware type045 = Software number, IO-LinkVersion001 = Standard002 = Taperedinterface 0 7 = IO-Linkmodule S4 = M12 4-pin maleAccessories for the BIS M-4xx-... can be found in the Balluff IO-Link catalog.The catalog can be downloaded on the Internet at "www.balluff.de".
48Decimal Hex Control codeASCII Decimal Hex ASCII Decimal Hex ASCII0 00 Ctrl @ NUL 43 2B + 86 56 V1 01 Ctrl A SOH 44 2C , 87 57 W2 02 Ctrl B STX 45 2D - 88 58 X3 03 Ctrl C ETX 46 2E . 89 59 Y4 04 Ctrl D EOT 47 2F / 90 5 A Z5 05 Ctrl E ENQ 48 30 0 91 5B [6 06 Ctrl F ACK 49 31 1 92 5C \7 07 Ctrl G BEL 50 32 2 93 5D [8 08 Ctrl H BS 51 33 3 94 5E ^9 09 Ctrl I HT 52 34 4 95 5F _10 0 A Ctrl J LF 53 35 5 96 60 `11 0B Ctrl K VT 54 36 6 97 61 A12 0C Ctrl L FF 55 37 7 98 62 B13 0D Ctrl M CR 56 38 8 99 63 c14 0E Ctrl N SO 57 39 9 100 64 d15 0F Ctrl O SI 58 3 A : 101 65 e16 10 Ctrl P DLE 59 3B ; 102 66 f17 11 Ctrl Q DC1 60 3C < 103 67 g18 12 Ctrl R DC2 61 3D = 104 68 h19 13 Ctrl S DC3 62 3E > 105 69 i20 14 Ctrl T DC4 63 3F ? 106 6 A j21 15 Ctrl U NAK 64 40 @ 107 6B k22 16 Ctrl V SYN 65 41 A 108 6C L23 17 Ctrl W ETB 66 42 B 109 6D m24 18 Ctrl X CAN 67 43 C 110 6E n25 19 Ctrl Y EM 68 44 D 111 6F o26 1 A Ctrl Z SUB 69 45 E 112 70 p27 1B Ctrl [ ESC 70 46 F 113 71 q28 1C Ctrl \ FS 71 47 G 114 72 r29 1D Ctrl ] GS 72 48 H 115 73 s30 1E Ctrl ^ RS 73 49 I 116 74 t31 1F Ctrl _ US 74 4 A J 117 75 u32 20 SP 75 4B K 118 76 V33 21 ! 76 4C L 119 77 W34 22 " 77 4D M 120 78 X35 23 # 78 4E N 121 79 Y36 24 $ 79 4F O 122 7 A Z37 25 % 80 50 P 123 7B {38 26 & 81 51 Q 124 7C |39 27 ‘ 82 52 R 125 7D }40 28 ( 83 53 S 126 7E ~41 29 ) 84 54 T 127 7F DEL42 2 A * 85 55 U ASCII tableAppendixBIS M-4xx IO-Link DeviceRead/Write Device
www.balluff.com 49ADimensions 16, 18, 19, 21, 22Distancebetween the data carriers 11between the read/write devices 11Sensing surface 8, 9, 10, 16, 17, 18, 20ASCII table 48Output buffer 25, 32, 37, 43, 44, 45, 46BBaud rate 26, 28, 44Intended use 7Operating conditions 16CCRC checkError message 31DData carrierISO 15693 15, 26Mifare 15, 22, 26Data transfer 12, 14, 27, 31Data transmission 12EInput buffer 14, 25, 32, 34, 36, 38, 39, 40, 41, 42, 44, 46Electrical data 17Ground 11Earthing connector 9, 10, 18, 21FClear zone 23Function indicators 20Functional principle 12IStartup 5, 7Installation 5, 7KCable length 9, 10, 19, 20Characteristic data in combination with data carriers 22, 23Communications standard 5, 24LRead distance 11, 14, 22MMechanical data 16, 17, 18, 19, 20, 21PProtocol examples 36Process data 14, 15, 24, 25, 32, 36, 44, 45SSafety 7Operation 7Startup 7Installation 7 Safety regulations 7TTechnical dataOperating conditions 16Electrical data 17Function indicators 20Characteristic data in combination with data carriers 22, 23Mechanical data 16, 17, 18, 19, 20, 21Type designation code 47ZAccessories 47AppendixBIS M-4xx IO-Link DeviceRead/Write Device
Balluff GmbH Schurwaldstraße 973765 Neuhausen a.d.F.GermanyTel. +49 7158 173-0Fax +49 7158 5010balluff@balluff.deNo. 870554 E . Edition 1005; Subject to modifications.www.balluff.comwww.balluff.com

Navigation menu