Balluff BIS M-62 Series Manual
  1. Manuals
  2. Brands
  3. Balluff Manuals
  4. Computer Hardware
  5. BIS M-62 Series
  6. Manual
Balluff BIS M-62 Series Manual

Balluff BIS M-62 Series Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Advertisement

Table of Contents
loading

Related Manuals for Balluff BIS M-62 Series

Summary of Contents for Balluff BIS M-62 Series

  • Page 4: Table Of Contents

    About this Manual ..................... 11 1.3.1 Who Should Read This Manual? ................12 1.3.2 HEX Notation ......................12 Models and Accessories ................... 12 Balluff RFID Tags ..................... 13 INSTALLATION ......................15 Mechanical Dimensions .................... 15 2.1.1 BIS M-620-068-A01-00-_ _ Serial RS232 Models ............. 15 2.1.2 BIS M-620-067-A01-04-_ _ Subnet16 Models ............
  • Page 5 4.1.1 Node ID Configuration Using Configuration Tags ............61 Configuration Tools ....................62 4.2.1 Configuration Using Balluff Dashboard™ ..............63 4.2.2 Software Upgrades Using Balluff Dashboard™ ............65 4.2.3 Creating and Using RFID Macros with C-Macro Builder™ ........65 Command Protocols....................69 Industrial Ethernet (IND) INTERFACE ..............
  • Page 6 Standard TCP/IP Overview ..................104 Standard TCP/IP - IP Configuration via HTTP Server ..........104 Standard TCP/IP - Command & Response Examples ..........107 7.3.1 Standard TCP/IP - Command Structure Example ........... 108 7.3.2 Standard TCP/IP - Response Structure Example ............ 108 DEVICENET INTERFACE ..................

  • Page 8: References

    The documentation related to the BIS M-62_ Processor Unit management is available on the specific product page at the website: www.balluff.com SERVICES AND SUPPORT Balluff provides several services as well as technical support through its website. Log on to www.balluff.com and click on the l inks indicated for further information including: ...

  • Page 9: Regulatory And Compliance Notices

    REGULATORY AND COMPLIANCE NOTICES This product is intended to be installed by Qualified Personnel only. This product must not be used in explosive environments. Only connect Ethernet and data port connections to a network which has routing only within the plant or building and no routing outside the plant or building. POWER SUPPLY This product is intended to be installed by Qualified Personnel only.

  • Page 10: General View

    GENERAL VIEW RS232 Models Figure A HF Antenna Connector COM LED Ready LED Mounting Bracket RF LED Host (RS232) and Power Connector...
  • Page 11 RS485 Models Figure B COM LED HF Antenna Connector Ready LED Mounting Bracket RF LED Host (RS485) and Power Connector Node ID LEDs...
  • Page 12 IND Models Figure C Mounting Bracket HF Antenna Connector Ready LED Power Connector RF LED Host (Ethernet) Connector COM LED IP Address Status LEDs...
  • Page 13 DNT Models Figure D Mounting Bracket HF Antenna Connector Ready LED RS232 Configuration Connector RF LED Host (DeviceNet) and Power Connector COM LED DeviceNet Status LED...
  • Page 14 PBS Models Figure E RS232 Configuration Connector HF Antenna Connector Ready LED Power Connector RF LED Host (Profibus Out) Connector COM LED Host (Profibus In) Connector Mounting Bracket 10 Profibus Status LEDs...
  • Page 15 PNT Models Figure F RS232 Configuration Connector HF Antenna Connector Ready LED Power Connector RF LED Profinet 2 Connector COM LED Profinet 1 Connector Mounting Bracket 10 Profinet Status LEDs...
  • Page 16 BIS M-371-000-A01 BIS M-372-000-A01 BIS M-373-000-A01 BIS M-370-000-A02 Figure G...

  • Page 18: Overview

    Profinet • Reads/Writes ISO 14443A and ISO 15693 compliant RFID tags • Compatible with BIS M-1xx Series RFID tags from Balluff • Supports Balluff's ABx Fast & CBx RFID command protocols • Operates at the internationally recognized ISM frequency of 13.56 MHz •...

  • Page 19: Who Should Read This Manual

    Listed here are the products and accessories relative to the HF-Series processor units. For a complete list of products and accessories relative to the Subnet16™ Gateway see the Gateway Processor manual. To purchase any of the Balluff products listed below contact your Balluff distributor or visit our Web site: http://www.balluff.com. Order...

  • Page 20: Balluff Rfid Tags

    T Connector: 7/8-16/5P M/F/F (ThickNet to ThickNet) 1.5 BALLUFF RFID TAGS Balluff designs and manufactures several lines of RFID tags. BIS M-13_ passive read/write RFID tags are especially suited for Balluff HF RFID Processor. Tag Mounting Kits are also available.
  • Page 21 BIS M-62_ MANUAL...

  • Page 22: Installation

    INSTALLATION 2 INSTALLATION 2.1 MECHANICAL DIMENSIONS 2.1.1 BIS M-620-068-A01-00-_ _ Serial RS232 Models [4.41] [1.50] [2.13] [0.21] * Digital I/O (-12 models only) Ø5.3 [Ø0.21] [3.86] Figure 1 - BIS M-620-068-A01-00-_ _ Dimensions...

  • Page 23: Bis M-620-067-A01-04

    BIS M-62_ MANUAL 2.1.2 BIS M-620-067-A01-04-_ _ Subnet16 Models [4.41] [1.50] [2.13] [3.86] [0.21] * Digital I/O (-12 models only) Ø5.3 [Ø0.21] [3.86] Figure 2 - BIS M-620-067-A01-04-_ _ Dimensions...

  • Page 24: Bis M-626

    INSTALLATION BIS M-626-_ _ Industrial Ethernet (IND) Models 2.1.3 [4.41] [1.50] [2.13] [2.48] [0.21] * Digital I/O (-12 models only) Ø5.3 [Ø0.21] [3.86] Figure 3 - BIS M-626-_ _ Dimensions...

  • Page 25: Bis M-623

    BIS M-62_ MANUAL 2.1.4 BIS M-623-_ _ DeviceNet Models [4.41] [1.50] [0.98] [0.21] Ø5.3 [Ø0.21] [3.86] Figure 4 - M-623-_ _ Dimensions...

  • Page 26: Bis M-622

    INSTALLATION 2.1.5 BIS M-622-_ _ Profibus Models [4.41] [0.79] [1.69] [1.50] [2.13] [0.21] Ø5.3 [Ø0.21] Figure 5 - BIS M-622-_ _ Dimensions...

  • Page 27: Bis M-628

    BIS M-62_ MANUAL 2.1.6 BIS M-628-_ _ PROFINET Models [4.41] 43.0 [1.69] 54.0 [2.13] Figure 6 - BIS M-628-_ _ Dimensions...
  • Page 28 INSTALLATION BIS M-371-000-A01 [0.24] [3.94] Ø5.1 [Ø0.20] [3.86] 113.4 [4.47] [2.56] Figure 7 - BIS M-371-000-A01...
  • Page 29 BIS M-62_ MANUAL BIS M-372-000-A01 [7.87] [0.24] 47.4 [1.87] 16.4 Ø5.1 [0.64] [1.18] [Ø0.20] 20.5 [0.81] [3.86] 113.4 [4.47] Ø3 [Ø0.12] [2.56] 89.3 [3.52] Figure 8 - BIS M-372-000-A01...
  • Page 30 INSTALLATION BIS M-373-000-A01 [0.24] [11.81] 47.4 [1.87] 16.4 Ø5.1 [0.64] [1.18] [Ø0.20] [3.98] [3.86] 20.6 [0.81] 113.4 [4.47] Ø5.1 [Ø0.20] [2.56] 89.3 [3.51] Figure 9 - BIS M-373-000-A01...
  • Page 31 BIS M-62_ MANUAL BIS M-370-000-A02 [1.59] [2.98] 13.1 [0.52] [2.76] [1.50] [1.02] Ø5.4 [Ø0.21] Figure 10 - BIS M-370-000-A02...

  • Page 32: Bis M-37_ Antenna Mounting

    INSTALLATION 2.2 BIS M-37_ ANTENNA MOUNTING 2.2.1 Direct Antenna Mounting Only -371, -372, and -373 Antenna models Antenna Mounting Screws (M5 x 20 mm) and Washers (M5) included in BIS M-62_ package. Figure 11 - Direct Antenna Mounting The BIS M-37_RFID antennas (except BIS M-370-000-A02) are designed to be connected directly to the BIS M-62_ Processor units using the hardware included in the Processor unit package.

  • Page 33: Remote Antenna Mounting

    BIS M-62_ MANUAL 2.2.2 Remote Antenna Mounting Using BIS M-500-PVC-07-A01/02 Extension Cable Figure 12 - Remote Antenna Mounting All BIS M-37_RFID antennas can be connected remotely to the BIS M-62_ processor units through the BIS M-500-PVC-07-A01/02 Extension Cable. You can use the 4 mm hex key wrench supplied with each Processor unit to tighten all screws to 1.7 Nm or 15 lbs per inch ±...

  • Page 34: Minimum Mounting Distance Between Adjacent Antennas

    INSTALLATION 1. Mount the processor unit Adapter to the top of the processor unit using the two 20 mm M5 screws and washers provided with each BIS M-62_ Processor unit. 2. Mount the Antenna Adapter to the bottom of the antenna as follows: 3.

  • Page 35: Antenna To Tag Range

    The tag ranges below are provided for design purposes only. Testing should be performed in the actual environment for more precise range results. Typical Antenna-to-Tag Ranges for some of Balluff Tags Tag range values are listed in mm / inches. BIS M-62_ _ -Series RFID Antenna [HF-ANT]...

  • Page 36: Electrical Connectors

    INSTALLATION 2.3 ELECTRICAL CONNECTORS 2.3.1 RS232 The RS232 Connector (M12 8-pin, Male) is used for a point-to-point serial connection between a host computer and the BIS M-62_ processor unit. Figure 13 - RS232 Interface M12 8-pin Male Connector Name Function Input Power Power Ground Reserved...

  • Page 37: Rs485

    BIS M-62_ MANUAL 2.3.2 RS485 The Subnet16™ RS485 Connector (M12 5-pin, Male) is used for connecting the BIS M-62_ processor units to a Subnet16™ network. These models are powered from the Subnet16™ network power. PIN 4: PIN 5: TX/RX+ TX/RX- PIN 3: PIN 1: SIGNAL...

  • Page 38: Industrial Ethernet (Ind)

    INSTALLATION Industrial Ethernet (IND) 2.3.3 The Ethernet Connector (M12 4-pin D-coded, Female) is used for connecting the BIS M-62_ processor unit to an Ethernet network. PIN 4: PIN 1: PIN 3: PIN 2: Figure 15 - M12 4-pin D-Coded Female Connector (for Ethernet) Name Function Transmit Data positive...

  • Page 39: Devicenet

    BIS M-62_ MANUAL 2.3.4 DeviceNet The DeviceNet Connector (M12 5-pin, Male) is used for connecting the BIS M-62_ processor unit to a DeviceNet network. These models are powered from the DeviceNet network power supply PIN 4: PIN 5: CAN_H CAN_L PIN 3: PIN 1: SHIELD...
  • Page 40 INSTALLATION The RS232 Connector (M12 8-pin, Male) on the DeviceNet models is used for connecting the BIS M-62_ processor unit to a portable PC for configuration. Figure 18 - M12 8-pin Male Connector (RS232) Name Function Receive Data Transmit Data SGND Signal Ground...

  • Page 41: Profibus

    BIS M-62_ MANUAL 2.3.5 Profibus The Profibus IN Connector (M12 5-pin B-coded, Male) is used for connecting the BIS M-62_ processor unit to a Profibus network. PIN 4: PIN 5: B Line (+) SHIELD PIN 3: PIN 1: +5 Vdc PIN 2: A Line (-) Figure 19 - M12 5-pin B-Coded Male Connector (Profibus-IN)
  • Page 42 INSTALLATION The Profibus models are ONLY powered through their VDC power connector (M12 5-pin, Male). PIN 4: PIN 5: PIN 3: PIN 1: PIN 2: Figure 21 - M12 5-pin Male Connector (Power Supply) Name Function Input Power Power Ground The RS232 Connector (M12 8-pin, Male) on the Profibus models is used for connecting the Processor unit to a portable PC for configuration.

  • Page 43: Profinet

    BIS M-62_ MANUAL 2.3.6 Profinet The PNT1 and PNT2 PROFINET Connectors (M12 4-pin D-coded, Female) are used for connecting the processor unit to a PROFINET network. PIN 4: PIN 1: PIN 3: PIN 2: Figure 23 - M12 4-pin D-Coded Female Connector (for Profinet) Name Function Transmit Data positive...
  • Page 44 INSTALLATION The RS232 Connector (M12 8-pin, Male) on the PROFINET models is used for connecting the processor unit to a portable PC for configuration. Figure 25 - M12 8-pin Male Connector (RS232) Name Function Receive Data Transmit Data SGND Signal Ground...

  • Page 45: Digital I/O (-12 Models)

    BIS M-62_ MANUAL 2.3.7 Digital I/O (-12 models) The Digital I/O Connector (M12 8-pin Female Connector) is used for connecting the processor unit to optional external digital input/output devices. See par. 2.7 for further details. Figure 26 - M12 8-pin Female Connector (Digital I/O) Name Function Power from the Processor unit to the I/O device...

  • Page 46: Power & Wiring

    INSTALLATION 2.4 POWER & WIRING The information presented below is provided to assist the installer in determining the amount of power that will be required by the Processor unit depending on the application. 2.4.1 Power Requirements The HF-Series Processor unit requires an electrical supply voltage of 12 to 30 Vdc. Use a regulated power supply that is capable of delivering the requirements listed in the Technical Features.

  • Page 47: Cable Voltage Drop

    24 Vdc - 7.10/2 = 20.45 Vdc at processor unit number 4 of each branch 2.4.4 Current Rating for Cables The maximum current rating for the Subnet16™ network using Balluff cables and accessories (BCCxxxx), is 4.0 A. The resistance calculation must include both wires (Vdc and GND).

  • Page 48: Installation Guidelines

    Adequate length cabling, connectors and terminators  Sufficient power capable of powering all the RFID components  Balluff RFID data carrier or labels: BIS M-1xx or BIS U-1xx 2.5.2 Installation Precautions  RF performance and read/write range can be negatively impacted by the proximity of metallic objects and liquids.

  • Page 49: Typical Layouts And Installation Procedures

    To verify operations, download the Balluff Dashboard™ Configuration Tool from www.balluff.com. The Balluff Dashboard™ Configuration Tool allows users to configure and control their BIS M-620-068-A01-00-S_ processor units and send RFID commands for testing purposes. See the Dashboard™ Manual for details.

  • Page 50: Installing The Bis M-620-067-A1-04-S_ Rs485

    INSTALLATION 2.6.2 Installing the BIS M-620-067-A1-04-S_ RS485 BCC07WR BCC07WR BCC07WR BCC07WR BCC07WR BCC0ET0 BCC0ET0 BCC0ET0 BCC0ET0 BCC06ZF BCC07WR Gateway Vdc GND Configuration PC Host BIS M-620-067-_ w antenna to Power Supply BIS M-620-067-_ w antenna Figure 28 - RS485 Typical Layouts See Gateway or Hub Reference Manual for further connection details.

  • Page 51: Installing The Bis M-626-069-A01-06_ Industrial Ethernet (Ind)

    Default or Custom. To verify operations, download the Balluff Dashboard™ Configuration Tool from www.balluff.com. The Balluff Dashboard™ Configuration Tool allows users to configure and control their BIS M-626-069_ processor units and send RFID commands for testing purposes. See the Dashboard™ Manual for details.

  • Page 52: Installing The Bis M-623-071-A01-03-S_ Devicenet (Dnt)

    To configure and control the BIS M-623-071 processor unit and send RFID commands for testing purposes, download and install the Balluff Dashboard™ Configuration Tool from www.balluff.com. The Dashboard™ Configuration Tool uses the PC RS232 serial port to communicate to the processor unit’s RS232 serial port. To enable communication: 1.

  • Page 53: Installing The Bis M-622-070-A01-03-St33 Profibus (Pbs)

    BIS M-62_ MANUAL 2.6.5 Installing the BIS M-622-070-A01-03-ST33 Profibus (PBS) BCC06ZF BCC06ZF to Configuration PC to Configuration PC to Configuration PC to Power Supply PBS OUT PBS IN PBS IN PBS OUT PBS IN PBS OUT PBS IN Profibus Terminator Figure 31 - PBS Typical Layouts The BIS M-622-070-A01-03-ST33 Processor unit is designed for Profibus RFID applications, where the processor unit is connected as a slave node in a Profibus (DP) network via...
  • Page 54 To configure and control the BIS M-622-070_ processor unit and send RFID commands for testing purposes, download and install the Balluff Dashboard™ Configuration Tool from www.balluff.com. The Dashboard™ Configuration Tool uses the PC RS232 serial port to communicate to the processor unit’s RS232 serial port. To enable communication: 1.

  • Page 55: Installing The Bis M-628-075-A01-03-St34 Profinet (Pnt)

    BIS M-62_ MANUAL 2.6.6 Installing the BIS M-628-075-A01-03-ST34 PROFINET (PNT) BCC06ZF BCC06ZF PNT 1 PNT 1 PNT 1 to Configuration PC to Configuration PC to Configuration PC to Power Supply PNT 2 PNT 2 to Profinet Master Figure 32 - PNT Typical Layouts The BIS M-628-075-A01-03-ST34 Processor unit is designed for PROFINET RFID applications, where the processor unit is connected as a slave node in a PROFINET IO network via compatible cables directly to a PROFINET Master (host).
  • Page 56 To configure and control the BIS M-628-075-A01-03-ST34 processor unit and send RFID commands for testing purposes, download and install the Balluff Dashboard™ Configuration Tool from www.balluff.com. The Dashboard Configuration Tool uses the PC RS232 serial port to communicate to the processor unit’s RS232 serial port. To enable communication: 1.

  • Page 57: Digital I/O (-12 Models)

    BIS M-62_ MANUAL 2.7 DIGITAL I/O (-12 MODELS) 2.7.1 Input There is one optocoupled polarity insensitive input available on the Processor units with the I/O option. See par. 2.3.7 for pinout. “Polarity Insensitive” means that, in the applications examples shown below, the user can exchange I1A with I1B without affecting the system behaviour.
  • Page 58 INSTALLATION Input Connections Using Processor unit Power Figure 33 - PNP External Trigger Using Processor unit Power Figure 34 - NPN External Trigger Using Processor unit Power Input Connections Using External Power Figure 35 - PNP External Trigger Using External Power...

  • Page 59: Outputs

    BIS M-62_ MANUAL Figure 36 - NPN External Trigger Using External Power 2.7.2 Outputs Two general purpose optocoupled outputs are available on the Processor units with the I/O option. See par. 2.3.7 for pinout. The user can activate/deactivate the two outputs through specific commands (see par. 2.7.3 for the specific Command Protocol Reference Manual according to your Processor unit model).
  • Page 60 INSTALLATION...
  • Page 61 BIS M-62_ MANUAL The following connection diagrams show examples involving only Output1; the same principles are valid and applicable also to Output2. Output Connections Using Processor unit Power Figure 37 - Open Emitter (Sourcing) Output Using Processor unit Power Figure 38 - Open Collector (Sinking) Output Using Processor unit Power...
  • Page 62 INSTALLATION Output Connections Using External Power Figure 39 - Open Emitter (Sourcing) Output Using External Power Figure 40 - Open Collector (Sinking) Output Using External Power...

  • Page 63: Digital I/O Command Control

    To handle the Input and Outputs, a set of CBx and ABx commands are available for the user. These commands include getting the status and setting/clearing the Input/Outputs. For more details, refer to the Balluff CBx Command Protocol Reference Manual, and the Balluff ABx Fast Command Protocol Reference Manual, both available on the Balluff web site in the download section of the product page.

  • Page 64: Led Indicators

    LED INDICATORS 3 LED INDICATORS 3.1 FRONT PANEL LEDS 3.1.1 BIS M-620-068-A01-00_ RS232 Models LED Name LED Color LED Description The READY LED is ON after the power up READY GREEN sequence has completed. The RF LED illuminates when RF power is being AMBER transmitted by the antenna.

  • Page 65: Bis M-626-069-A01-06_ Industrial Models

    HF-SERIES REFERENCE MANUAL 3.1.3 BIS M-626-069-A01-06_ INDUSTRIAL Models LED Name LED Color LED Description The READY LED is ON after the power up READY GREEN sequence has completed. The RF LED illuminates when RF power is being AMBER transmitted by the antenna. The COM (communications) LED flashes ON and OFF when data is being transmitted between the antenna and a tag.

  • Page 66: Bis M-622-070-A01-03-St33 Profibus Models

    LED INDICATORS 3.1.5 BIS M-622-070-A01-03-ST33 PROFIBUS Models LED Name LED Color LED Description The READY LED is ON after the power up READY GREEN sequence has completed. The RF LED illuminates when RF power is AMBER being transmitted by the antenna. The COM (communications) LED flashes ON and OFF when data is being transmitted between the antenna and a tag.

  • Page 67: Bis M-628-075-A01-03-St34 Profinet Models

    HF-SERIES REFERENCE MANUAL 3.1.6 BIS M-628-075-A01-03-ST34 PROFINET Models LED Name LED Color LED Description The READY LED is ON after the power up READY GREEN sequence has completed. The RF LED illuminates when RF power is AMBER being transmitted by the antenna. The COM (communications) LED flashes ON and OFF when data is being transmitted between the antenna and a tag.

  • Page 68: Configuration Methods

    There are several configuration methods available for your processor unit depending on the interface type and application:  Configuration Tag  Configuration Tools: Balluff Dashboard™ and C-Macro Builder™  Command Protocol 4.1 CONFIGURATION TAG A configuration tag is included with your BIS M-62_ processor unit. This can be used to reset all BIS M-62_ processor units to their factory default configuration settings.

  • Page 69: Configuration Tools

    BIS M-62_ MANUAL All Balluff RS485-based processor units’ ship with their Node ID value set to 0. NOTE When a powered processor unit (that is set to Node ID 0) is connected to the Subnet, it will not initially be recognized by the Gateway until the Configuration Tag is placed in the antenna’s RF field.

  • Page 70: Configuration Using Balluff Dashboard

    Configuration Using Balluff Dashboard™ 4.2.1 The Balluff Dashboard™ Configuration Tool is a software application that allows users to view, modify, save and update the configuration settings of their BIS M-62_ processor units. Follow the instructions below to operate the Balluff Dashboard™ Configuration Tool and to set the BIS M-62_ device’s configuration.
  • Page 71 The Dashboard should send some commands to retrieve device and configuration information from the device. If communications are set up correctly, the device configuration area within the Balluff Dashboard™ should now look something like this: Figure 45 - Balluff Dashboard™ HF RS232 Processor unit Configuration...

  • Page 72: Software Upgrades Using Balluff Dashboard

    Creating and Using RFID Macros with C-Macro Builder™ 4.2.3 What are RFID Command Macros? RFID Command Macros are a powerful feature of Balluff BIS M-62_ Processor units. Macros are simple programs that direct a processor unit to execute multiple pre-programmed instructions.
  • Page 73 Triggers can be configured, for example, to activate a macro when a tag enters or leaves a processor unit’s RF field. Balluff RFID processor units can store up to eight separate triggers in addition to the eight macros they can also house. Any trigger can activate any of the eight stored macros.
  • Page 74 How can I learn more about the Dashboard and C-Macro Builder? More information regarding macros, triggers, uploading, downloading, configuring and monitoring Balluff RFID equipment is available in the respective User’s Manuals for these products, which are available on the Balluff website at:...
  • Page 75 BIS M-62_ MANUAL C-Macro Builder™ is an easy to use GUI-driven Configuration Tool for Windows that allows users to create powerful RFID command macro programs. Figure 46 - C-Macro Builder™ For specific information regarding the configuration and use of either of these utilities, please see the accompanying documentation included when downloading each software application.

  • Page 76: Command Protocols

    CONFIGURATION METHODS 4.3 COMMAND PROTOCOLS HF-Series processor units can be directly programmed using a proprietary command protocol over the specific host interface. This is useful for processor units connected to a PLC over a Fieldbus network (i.e. DeviceNet, Profibus, Industrial Ethernet (IND), Profinet, etc.).
  • Page 77 BIS M-62_ MANUAL...

  • Page 78: Industrial Ethernet (Ind) Interface

    (via Industrial Ethernet (IND)) with a ControlLogix Programmable Logic Controller (PLC). Also in this chapter are descriptions of the Balluff HTTP Server and OnDemand Utilities, as well as systematic instructions to help configure the BIS M-626 Industrial RFID Controller for Industrial Ethernet (IND) environments.

  • Page 79: Industrial Ethernet (Ind) Configuration Overview

     Verify PLC and BIS M-626_ Subnet Node connectivity 5.2 HTTP SERVER & ONDEMAND PLC SUPPORT Below is a partial list of the programmable logic controllers that are supported by the Balluff HTTP Server and OnDemand Utilities:  ControlLogix – OnDemand supports all current versions ...

  • Page 80: Http Server And Ondemand Utilities

    Within each controller tag, information is stored in two-byte segments, known as registers or “words.” NOTE OnDemand is the Balluff approach to adding Change of State messaging to ControlLogix and legacy support for RA PLC5E and RA SCL5/05 programmable logic controllers.

  • Page 81: Ip Configuration Via Http Server

    BIS M-62_ MANUAL 5.4 IP CONFIGURATION VIA HTTP SERVER To configure the BIS M-626 for Ethernet communications, begin by assigning the controller a locally compatible IP address. Through a standard Web browser, you can utilize the BIS M-626’s HTTP Server to access an embedded suite of controller configuration tools, called the “OnDemand Utilities.”...
  • Page 82 Industrial Ethernet (IND) INTERFACE 4. Click the button labeled “EDIT”, located below “Network Settings.” The IP Configuration Page will be displayed. IP Configuration Page The IP Configuration Page is used to modify and save changes to the IP Address, Subnet Mask and (Network) Gateway IP Address.

  • Page 83: Ondemand Configuration For Industrial Ethernet (Ind)

    BIS M-62_ MANUAL 5.5 ONDEMAND CONFIGURATION FOR Industrial Ethernet (IND) Now that you have configured the BIS M-626’s IP address, you will need to use the embedded HTTP Server to access the BIS M-626’s OnDemand Configuration Page. Through the use of the OnDemand Configuration Page, the BIS M-626 can be configured to communicate with a ControlLogix PLC.
  • Page 84 Industrial Ethernet (IND) INTERFACE OnDemand Configuration Page The OnDemand Configuration Page allows you to modify the settings of the BIS M-626’s Node. Figure 49 - The OnDemand Configuration Page 3. In the upper portion of the OnDemand Configuration Page, select a PLC Type from the drop-down menu.
  • Page 85 BIS M-62_ MANUAL 5. For the PLC Slot Number, enter a value between 0 and 255. The PLC Slot Number indicates the location in your PLC rack where the controller module is installed (normally slot 0 for ControlLogix). 6. In the Read Delay field, enter a value between 0 and 6000. This number specifies (in 10ms “ticks”) how frequently the BIS M-626 will poll the PLC for the presence of new data.

  • Page 86: Configuring Plc Controller Tags

    Industrial Ethernet (IND) INTERFACE The OnDemand Status Page will be displayed. 13. At the OnDemand Status Page, click the link labeled “Main Page” to return to the HTTP Server – Main Page. 5.6 CONFIGURING PLC CONTROLLER TAGS After you have configured the BIS M-626’s Node via the OnDemand Configuration Page, open your PLC program (i.e.
  • Page 87 BIS M-62_ MANUAL The BIS M-626 should already be linked to the proper Write Tag and Read Tag via the OnDemand Utilities - OnDemand Configuration Page). NOTE After creating and defining a Write Tag and a Read Tag for the BIS M-626, return to the BIS M-626’s HTTP Server –...

  • Page 88: Checking Ondemand Status

    Industrial Ethernet (IND) INTERFACE 5.7 CHECKING ONDEMAND STATUS Now that you have configured the BIS M-626’s Node and defined corresponding Write and Read Tags in the PLC, the last step is to check the communication status between the BIS M-626 and the PLC. Return to the BIS M-626’s HTTP Server - Main Page and click the link labeled “OnDemand Status.”...

  • Page 89: Industrial Ethernet (Ind) Handshaking

    BIS M-62_ MANUAL 5.8 VERIFYING DATA EXCHANGE WITH RSLOGIX 5000 At this point, communication between the BIS M-626 and the PLC should be properly configured and a connection established. You can verify the exchange of information between devices using RSLogix 5000. Figure 52 - RSLogix 5000 Industrial Ethernet (IND) Handshaking 5.8.1...

  • Page 90: Industrial Ethernet (Ind) Handshaking Example

    Industrial Ethernet (IND) INTERFACE Industrial Ethernet (IND) Handshaking Example 5.8.2 In the example below, EMS_READ1 is the name of the Read Tag and EMS_WRITE1 is the name of the Write Tag. [0] indicates the first word, [1] indicates the second word in a controller tag. NOTE 1.

  • Page 91: Industrial Ethernet (Ind): Object Model

    BIS M-62_ MANUAL 5. The data will then be cleared from EMS_WRITE1. After which the BIS M-626 will be ready to receive another command. 5.9 Industrial Ethernet (IND): OBJECT MODEL The Object Model is the logical organization of attributes (parameters) within classes (objects) and services supported by each device.

  • Page 92: Industrial Ethernet (Ind) Required Objects

    Industrial Ethernet (IND) INTERFACE Industrial Ethernet (IND) Required Objects 5.9.1 Under Industrial Ethernet (IND), there are six Required Objects:  Identity Object (0x01)  Message Router Object (0x02)  Assembly Object (0x04)  Connection Manager Object (0x06)  TCP Object (0xF5) ...
  • Page 93 BIS M-62_ MANUAL Message Router Object (0x02) This object has no supported attributes. Assembly Object (0x04 - 3 Instances) Class Attributes Default Data Access Attribute ID Name / Description Data Type Rule Value Revision UINT Max Instance UINT Instance 0x64 Attributes (Input Instance) Default Data Access...
  • Page 94 Industrial Ethernet (IND) INTERFACE Instance 0x66 Attributes (Input Instance 3) Default Attribute Access Name / Description Data Type Data Rule Value Serial Produce Data: Consume Data Seq. Number UINT Handshake Produce Data Sequence Number UINT Node ID (1-32) UINT Node Serial Produce Data Size UINT All 0’s Node Serial Produce Data...
  • Page 95 BIS M-62_ MANUAL Connection Manager Object (0x06) This object has no attributes. TCP Object (0xF5 - 1 Instance) Class Attributes Default Data Attribute ID Name / Description Data Access Rule Type Value Revision UINT Instance Attributes Default Data Attribute ID Name / Description Data Access Rule...

  • Page 96: Industrial Ethernet (Ind): Vendor Specific Objects

    Industrial Ethernet (IND) INTERFACE Ethernet Link Object (0xF6 - 1 Instance) Class Attributes Default Access Attribute ID Name / Description Data Type Data Rule Value Revision UINT Instance Attributes Default Access Attribute ID Name / Description Data Type Data Rule Value Interface Speed* UDINT...
  • Page 97 BIS M-62_ MANUAL Instance Attributes (Instances 1-32) Default Attribute Access Name / Description Data Type Data Rule Value Consume Data Size (in words) UINT Get / Set Consume Data [0-249] UINT Get / Set Consume Data [250-499] UINT Get / Set Consume Data [500-749] UINT Get / Set...
  • Page 98 Industrial Ethernet (IND) INTERFACE BIS M-626 Produce Data Object (0x65 - 32 Instances) Class Attributes (Instance 0) Default Attribute Access Name / Description Data Type Data Rule Value Revision UINT Maximum Produce Data Buffer Size (in UINT 32768 words) Bitmap of Produce Instances with Data DINT Bit 0: Instance 1 …...

  • Page 99: Application Object (0X67 10 Instances)

    BIS M-62_ MANUAL Common Services Service Implementation Service Name Code Class Level Instance Level 0x05 Reset* 0x0E Get Attribute Single 0x10 Set Attribute Single *This Service Code is used to flush all attributes to zero. 5.9.3 Application Object (0x67 10 Instances) –...
  • Page 100 Industrial Ethernet (IND) INTERFACE Attribute Default Data Access Name / Description Data Type Value Rule Read File Number (SLC/PLC Only) UINT NX:0 - Where “X” is the File Number Read File Offset (SLC/PLC Only) UINT N7:Y - Where “Y” is the File Offset Read Poll Rate Measured in 10ms “ticks”...
  • Page 101 BIS M-62_ MANUAL...

  • Page 102: Modbus Tcp Interface

    MODBUS TCP INTERFACE 6 MODBUS TCP INTERFACE For BIS M-626-069-A01-06_ models. NOTE One of the most popular and well-proven industrial automation protocols in use today is Modbus. Modbus is an open client/server application protocol. Modbus TCP allows the Modbus protocol to be carried over standard Ethernet networks. Modbus TCP is managed by the Modbus-IDA User Organization.
  • Page 103 BIS M-62_ MANUAL The HTTP Server - Main Page will be displayed.
  • Page 104 MODBUS TCP INTERFACE HTTP Server – Main Page Figure 53 - The HTTP Server - Main Page The HTTP Server - Main Page lists the network settings (including the IP address) currently stored on the BIS M-626_. 4. Click the button labeled “EDIT”, located below “Network Settings.” The IP Configuration Page will be displayed.
  • Page 105 BIS M-62_ MANUAL IP Configuration Page The IP Configuration Page is used to modify and save changes to the IP Address, Subnet Mask and (Network) Gateway IP Address. Figure 54 - The IP Configuration Page 5. In the fields provided, enter your new IP configuration values for the BIS M-626_. 6.

  • Page 106: Modbus Tcp - Command Packet Structure

    MODBUS TCP INTERFACE 6.2.1 Modbus TCP - Command Packet Structure Consume Registers hold data that is destined for the BIS M-626_. Modbus TCP commands must be placed in the holding registers, starting at address 40001, of Device ID 01 (Node Input Page 01).

  • Page 107: Modbus Tcp - Mapping For Node 33

    BIS M-62_ MANUAL 6.2.3 Modbus TCP - Mapping for Node 33 Modbus Read / Write Address Register Description Privilege (4xxxx) IP Address 1 (MSB) Example: 192 IP Address 2 Example: 168 IP Address 3 Example: 000 IP Address 4 (LSB) Example: 100 Subnet Mask 1 (MSB) Example: 255 Subnet Mask 2 Example: 255 Subnet Mask 3 Example: 255...

  • Page 108: Modbus Tcp - Handshaking

    MODBUS TCP INTERFACE 6.3 MODBUS TCP - HANDSHAKING Due to the process with which commands and responses are passed between the BIS M- 626_ and the host, a handshaking procedure is used to notify the host that returning data is available for retrieval.

  • Page 109: Modbus Tcp - Host/Bis M-626_ Handshaking

    BIS M-62_ MANUAL Page will be reset to zero (0x00), indicating that the host has received and processed its pending data. 6.3.1 Modbus TCP - Host/BIS M-626_ Handshaking When the host issues a command, it must first write the entire command to the Node Input Page, leaving the Overall Length value to be written last.
  • Page 110 MODBUS TCP INTERFACE NOTE: when the Node Input Page’s value at register 40001 is returned to 0x0000, the host can assume that the command was at least received and execution was attempted. The host can also assume that it is OK to clear the remaining holding registers and write another command to the Device ID NOTE (Node Input Page).

  • Page 111: Standard Tcp/Ip Interface

    BIS M-62_ MANUAL 7 STANDARD TCP/IP INTERFACE For BIS M-626-069-A01-06-ST3_ models. NOTE 7.1 STANDARD TCP/IP OVERVIEW Another means of communicating with the BIS M-626 is through the standard TCP/IP protocol. For this manual, the protocol is referred to as Standard TCP/IP to distinguish it from other industrial protocols.
  • Page 112 STANDARD TCP/IP INTERFACE Setting the BIS M-626 IP Address To set the BIS M-626’s IP address using the HTTP Server, follow the steps below: 1. Open a Web browser on the PC. 2. In the URL address field, enter the BIS M-626’s IP address (192.168.253.110 = factory default).
  • Page 113 BIS M-62_ MANUAL IP Configuration Page The IP Configuration Page is used to modify and save changes to the IP Address, Subnet Mask and (Network) Gateway IP Address. Figure 56 - The IP Configuration Page 5. In the fields provided, enter your new IP configuration values for the BIS M-626. 6.

  • Page 114: Standard Tcp/Ip - Command & Response Examples

    STANDARD TCP/IP INTERFACE 7.3 STANDARD TCP/IP - COMMAND & RESPONSE EXAMPLES In standard TCP/IP, RFID commands issued by the host resemble Modbus TCP commands. The BIS M-626 handles all handshaking tasks. Moreover, the command & response packets need an additional word at the beginning of the string: Protocol Header 0xFF in MSB,<...

  • Page 115: Standard Tcp/Ip - Command Structure Example

    BIS M-62_ MANUAL 7.3.1 Standard TCP/IP - Command Structure Example In the following example, a 12-byte command has been issued to the BIS M-626, instructing the controller to read six bytes from a tag within RF range. A Timeout Value of five seconds has been set for the completion of the command.

  • Page 116: Devicenet Interface

    NOTE The .EDS file (filename: “DeviceNet EDS.zip”) for the BIS M-623-071-A01- 03-ST30 is available from the technical support area of the Balluff website. 1. Download the .EDS file to the computer running your network’s Rockwell Automation software (i.e. the host computer).

  • Page 117: Configuring Controller And Plc Devicenet Communications

    BIS M-62_ MANUAL 8.2.2 Configuring Controller and PLC DeviceNet Communications After importing the .EDS file and rebooting the host computer (or after restarting your Rockwell Automation software), follow the steps below to continue configuring DeviceNet network communications between the Controller and a ControlLogix PLC. 1.
  • Page 118 DEVICENET INTERFACE The Scanner Configuration Applet in RSNetWorx will begin scanning the specified network. This procedure may take some time depending on the speed of the bus and the number of devices connected. Node addresses are scanned from zero to 63. The default node address for the Controller is 63.
  • Page 119 BIS M-62_ MANUAL The 1756-DNB/A is a Series A DeviceNet Bridge / Scanner Module. After updating the software, the Controller should be recognized on the network and the device name, “63, Cobalt DN Controller”, should be displayed under “Available Devices.” NOTE 4.
  • Page 120 DEVICENET INTERFACE Figure 61 - Editing the Controller’s DeviceNet I/O Parameters The following images display the Input and Output properties tabs (in RSNetWorx for DeviceNet) for the 1756-DNB/A DeviceNet Bridge / Scanner Module after running the Scanner Configuration Applet for a second time. The scanner module, in this case, only identified one node, the Controller, at node address 63.
  • Page 121 BIS M-62_ MANUAL 7. Next, verify the mapping of the address where the PLC will retrieve output data from the Controller. In the image below, output data is mapped to start at 1:O.Data (0).0 on the PLC. Figure 63 - 1756-DNB/A Output Properties Tab 8.

  • Page 122: Configuring Data Rate And Node Address

    To change the data rate or node address, use either the "Node Commissioning" tool in RSNetWorx for DeviceNet or the “Balluff Dashboard™” utility running on a host computer that is connected to the RS232 port on the Controller. The Balluff Dashboard™ utility is available on the Balluff Web site (www.balluff.com).

  • Page 123: Devicenet - Exchanging Data And Handshaking

    After the Controller has been properly configured for your DeviceNet network, it will be possible to send the Controller commands using the Balluff CBx Command Protocol. For reference, the CBx Command Protocol Reference Manual is available on the Balluff Web site (www.balluff.com).

  • Page 124: Devicenet - Handshaking Example

    DEVICENET INTERFACE 8.2.5 DeviceNet - Handshaking Example This example describes the sequence of events for a simple command and response. All data is written in 2-byte WORD format and stored in 2-byte “registers.” The Output Controller Tag holds command data written by the PLC. The Input Controller Tag holds response data generated by the Controller.
  • Page 125 Local:2:I.Data [3] First WORD of Produce Data (Response from Controller) Local:2:I.Data [xxx] xxx WORD of Produce Data NOTE: A ladder logic example illustrating the implementation of this handshaking strategy can be downloaded from the technical support area of the Balluff website.
  • Page 126 DEVICENET INTERFACE...

  • Page 127: Profibus Interface

    BIS M-62_ MANUAL 9 PROFIBUS INTERFACE For BIS M-622-070-A01-03-ST33 models. NOTE 9.1 PROFIBUS OVERVIEW Profibus was created under German Government leadership in co-operation with automation manufacturers (Siemens) in 1989. Today it is commonly found in Process Control, large assembly and material handling machines. Just a single-cable which is able to wire multi- input sensor blocks, pneumatic valves, complex intelligent devices, smaller sub-networks, operator interfaces and many other devices.

  • Page 128: Data Exchange

    PROFIBUS INTERFACE 9.3 DATA EXCHANGE The Master Profibus is usually a PLC (Siemens S7 or others) but it could be a PC based device as well. The Profibus Processor unit is always Slave in the Profibus network. Profibus Master Profibus Network Profibus Slaves Profibus Slaves RFID...

  • Page 129: Protocol Implementation

    Processor unit to the Master station is about 30 ms plus the intrinsic PROFIBUS DP delay and the Master delay. This product implements the Balluff AnyBus Protocol which is a layer that is built upon the intrinsic fieldbus data exchange mechanism. The Driver is needed to add features such as flow control and fragmentation.

  • Page 130: Control Field

    PROFIBUS INTERFACE Figure 68 - Exchange Area Buffer Structure 9.4.2 Control Field The Input field structure reserves IN[0] for handshake purposes: bit 0 and bit 1 are used for this. Bit 6 is set to 1 in order to specify the messaging protocol number 1 is in use. The Output field structure is symmetrical, and reserves bit 0 and 1 for handshake purposes.
  • Page 131 BIS M-62_ MANUAL function of the OUT[0] byte: OUT[0].bit0 = TxBufferEmpty, toggles when transmitted data block has been read from master. OUT[0].bit1 = RxBufferFull, toggles when new data block is available from master. OUT[0].bit2 = Resync Request, set to 1 for 1 second to resynchronize a slave. After resynchronization, all 4 handshake bits are set to 0 and next toggle brings them to 1.
  • Page 132 PROFIBUS INTERFACE Data Transmission Slave → Master The transmission state machine is shown to understand how a single block is transmitted and received. This protocol guarantees a basic flow control mechanism from slave to master. Figure 70 - Slave to Master Transmission State Machine Data Transmission Master →...

  • Page 133: Sap Field

    The Application layer uses all or a part of the remaining bytes of the Exchange Area buffers that are not used by the Balluff AnyBus Protocol. The Length Field is introduced to keep the information of how many bytes are really used by the Application Layer. A fragment that is not the last one of a fragmentation sequence must fill this field with Max(In/Out)Bytes-3, depending on whether it is an INPUT/OUTPUT fragment.

  • Page 134: Application Data Buffer

    PROFIBUS INTERFACE 9.4.5 Application Data Buffer The Application data buffer holds the CBx commands described in the CBx Command Protocol Reference Manual. 9.5 EXAMPLES OF PROFIBUS COMMAND/RESPONSE MECHANISM As seen in par. 9.3, there are two buffers – an OUTPUT Buffer that is controlled by the MASTER, and an INPUT Buffer that is controlled by the slave (the Processor unit).
  • Page 135 BIS M-62_ MANUAL Bit 7 is always 1, to conform to Balluff’s proprietary Protocol. Byte 1: is always 0. Byte 2: contains the length of the packet in bytes (CBx Command or Command Fragment) to be sent to the Processor unit. This can be the length of an entire CBx command, or the length of a fragment of a command, if the CBx command is larger than the space allowed to send it in a single fragment.

  • Page 136: Example 1: Normal Command/Response Sequence

    Slave. Bit 7 is set to 1 as soon as the Slave has been successfully initialized at power-up, and remains at 1, to conform to Balluff’s proprietary Protocol. Byte 1: is always 0. Byte 2: contains the length of the packet in bytes (CBx response or response fragment) to be sent back to the Master.
  • Page 137 BIS M-62_ MANUAL (See the Green changes below) Output Buffer Input Buffer Byte # Value Byte # Value Output Buffer Control Byte Input Buffer Control Byte (OBCB) (IBCB) [1] [0] [0] [0] [0] [0] [0] [0] [1] [0] [0] [0] [0] [0] [0] [0] (Always 0) (Packet length in bytes) (CBx Command word length MSB)
  • Page 138 PROFIBUS INTERFACE (See the Green changes below) Output Buffer Input Buffer Byte # Value Byte # Value Output Buffer Control Byte Input Buffer Control Byte (OBCB) (IBCB) [1] [0] [0] [0] [0] [0] [1] [0] [0] [0] [0] [0] [0] [0] (Always 0) (Packet length in bytes) (CBx Command word length MSB)
  • Page 139 BIS M-62_ MANUAL (See the Green changes below) Output Buffer Input Buffer Byte # Value Byte # Value Output Buffer Control Byte Input Buffer Control Byte (OBCB) (IBCB) [1] [0] [0] [0] [0] [0] [1] [0] [1] [0] [0] [0] [0] [0] (Always 0) (Packet length in bytes) (CBx Command word length MSB)
  • Page 140 PROFIBUS INTERFACE (See the Green changes below) Output Buffer Input Buffer Byte # Value Byte # Value Output Buffer Control Byte Input Buffer Control Byte (OBCB) (IBCB) [1] [0] [0] [0] [0] [0] [1] [0] [1] [0] [0] [0] [0] [0] [1] [1] (Always 0) (Always 0)
  • Page 141 BIS M-62_ MANUAL The Master now toggles Bit 0 of the OBCB & OBDCB to acknowledge that it has received the response. (See the Green changes below) Output Buffer Input Buffer Byte # Value Byte # Value Output Buffer Control Byte Input Buffer Control Byte (OBCB) (IBCB)
  • Page 142 PROFIBUS INTERFACE If we now place a tag on the processor unit’s antenna, we can reissue the same command by toggling Bit 1 of the OBCB & OBDCB again. (See the Green changes below) Output Buffer Input Buffer Byte # Value Byte # Value...
  • Page 143 BIS M-62_ MANUAL (See the Green changes below) Output Buffer Input Buffer Byte # Value Byte # Value Output Buffer Control Byte Input Buffer Control Byte (OBCB) (IBCB) [1] [0] [0] [0] [0] [0] [0] [1] [1] [0] [0] [0] [0] [0] (Always 0) (Always 0) (Packet length in bytes)
  • Page 144 PROFIBUS INTERFACE (See the Green changes below) Output Buffer Input Buffer Byte # Value Byte # Value Output Buffer Control Byte Input Buffer Control Byte (OBCB) (IBCB) [1] [0] [0] [0] [0] [0] [0] [1] [1] [0] [0] [0] [0] [0] [0] (Always 0) (Always 0) (Packet length in bytes)
  • Page 145 BIS M-62_ MANUAL The Master now toggles Bit 0 of the OBCB & OBDCB to acknowledge that it has received the response. (See the Green changes below) Output Buffer Input Buffer Byte # Value Byte # Value Output Buffer Control Byte Input Buffer Control Byte (OBCB) (IBCB)

  • Page 146: Example 2: Unsolicited Responses (Continuous Read Mode)

    PROFIBUS INTERFACE 9.5.2 Example 2: Unsolicited Responses (Continuous Read Mode) In some modes (such as Continuous Read Mode) the slave can generate unsolicited responses. If the Slave generates an unsolicited response, it will place the response in the Input Buffer, as long as the Master has acknowledged receiving the previous response. If the Master does not perform the handshake to acknowledge the previous response, the responses will accumulate in the internal memory buffer of the Slave (The RFID processor unit has an internal 2K buffer for responses) and the responses will remain until the...
  • Page 147 BIS M-62_ MANUAL The Master can see that Bit 0 of the IBCB & IBDCB has been toggled, so it knows that a new response in the Input Buffer is ready (even though it hasn’t issued a command). Since Bit 2 is not set to 1, it knows that the response is complete (not a fragment). The Master now toggles Bit 0 of the OBCB &...
  • Page 148 PROFIBUS INTERFACE (See the Green changes below) Output Buffer Input Buffer Byte # Value Byte # Value Output Buffer Control Byte Input Buffer Control Byte (OBCB) (IBCB) [1] [0] [0] [0] [0] [0] [0] [1] [1] [0] [0] [0] [0] [0] [0] (Always 0) (Always 0) (Packet length in bytes)
  • Page 149 BIS M-62_ MANUAL The Master now toggles Bit 0 of the OBCB & OBDCB to acknowledge that it has received the response. (See the Green changes below) Output Buffer Input Buffer Byte # Value Byte # Value Output Buffer Control Byte Input Buffer Control Byte (OBCB) (IBCB)

  • Page 150: Example 3: Fragmentation Of Responses

    PROFIBUS INTERFACE 9.5.3 Example 3: Fragmentation of Responses For this example, the Master will send a CBx “Read Tag Data” command to the Slave (the Processor unit) to read 50 bytes from a tag. We will assume for this example that the both the input and output buffers have been configured to 32 bytes each.
  • Page 151 BIS M-62_ MANUAL Now that the command is in the Output Buffer, The Master alerts the Slave that the command is ready. It does this by toggling Bit 1 of the Output Buffer Control Byte (the OBCB) and then also toggling the same bit in the Output Buffer Data Consistence Byte (the OBDCB) This bit is a toggle.
  • Page 152 PROFIBUS INTERFACE When the Slave sees Bit 1 of the OBCB & OBDBC toggle, it grabs the command from the Output Buffer. The Slave then acknowledges the command by toggling Bit 1 of the Input Buffer Control Byte (the IBCB) and also the same bit of the Input Buffer Data Consistency Byte (the IBDCB).
  • Page 153 BIS M-62_ MANUAL The Slave writes the first fragment of the response into the Input Buffer, and toggles Bit 0 of the IBCB to indicate that there is a response fragment ready for the master, and sets Bit 3 of the IBCB to 1 to indicate that this is a fragment of a longer response (i.e.
  • Page 154 PROFIBUS INTERFACE The Master now toggles Bit 0 of the OBCB & OBDCB to acknowledge that it has received the response fragment. (See the Green changes below) Output Buffer Input Buffer Byte # Value Byte # Value Output Buffer Control Byte Input Buffer Control Byte (OBCB) (IBCB)
  • Page 155 BIS M-62_ MANUAL After the Master acknowledges that it has received the fragment, the Slave places the next fragment in the Input Buffer and toggles Bit 0 of the IBCB & IBDCB. Since this is still not the last fragment, the Save leaves Bit 3 set to 1 in the IBCB & IBDCB (See the Green changes below)
  • Page 156 PROFIBUS INTERFACE Now the Master acknowledges this fragment by toggling Bit 0 of the OBCB & OBDCB. It knows that this is still not the last fragment of the response, since Bit 3 of the IBCB & IBDCB is still set to 1. (See the Green changes below)
  • Page 157 BIS M-62_ MANUAL Now the Slave places the final fragment into the Input Buffer and toggles Bit 0 of the IBCB & IBDCB to indicate the new fragment is ready. Since it is the final fragment, the Slave also now clears Bit 3 of the IBCB & IBDCB: (See the Green changes below)
  • Page 158 PROFIBUS INTERFACE And lastly, the Master acknowledges receipt of the final fragment by toggling Bit 0 of its OBCB & OBDCB: (See the Green changes below) Output Buffer Input Buffer Byte # Value Byte # Value Output Buffer Control Byte Input Buffer Control Byte (OBCB) (IBCB)

  • Page 159: Example 4: Fragmentation Of Commands

    BIS M-62_ MANUAL 9.5.4 Example 4: Fragmentation of Commands For this example, the Master will send a CBx “Write Tag Data” command to the Slave (the BIS M-622 Processor unit) to write 50 bytes to a tag. We will assume for this example that the both the input and output buffers have been configured to 32 bytes each.
  • Page 160 PROFIBUS INTERFACE Now that the first command fragment is in the Output Buffer, the Master alerts the Slave that the command fragment is ready. It does this by toggling Bit 1 of the OBCB & OBDCB. Since there are more command fragments to follow to complete the command, the Master also sets Bit 3 of the OBCB &...
  • Page 161 BIS M-62_ MANUAL When the Slave sees Bit 1 of the OBCB & OBDBC toggle, it grabs the command fragment from the Output Buffer. The Slave then acknowledges the command fragment by toggling Bit 1 of the IBCB & IBDCB. (See the Green changes below)
  • Page 162 PROFIBUS INTERFACE Now that the Slave has acknowledged receiving the command fragment, the Master writes the next command fragment into the Output Buffer: (See the Green changes below) Output Buffer Input Buffer Byte # Value Byte # Value Output Buffer Control Byte Input Buffer Control Byte (OBCB) (IBCB)
  • Page 163 BIS M-62_ MANUAL Next, the Master signals that this fragment is ready, by toggling Bit 1 of the OBCB & OBDCB. Since this is still not the final fragment, the Master leaves Bit 3 set to 1. (See the Green changes below) Output Buffer Input Buffer...
  • Page 164 PROFIBUS INTERFACE When the Slave sees Bit 1 of the OBCB & OBDBC toggle, it grabs this command fragment from the Output Buffer. The Slave then acknowledges the command fragment by toggling Bit 1 of the IBCB & IBDCB. (See the Green changes below) Output Buffer...
  • Page 165 BIS M-62_ MANUAL Now that the Slave has acknowledged receiving the command fragment, the Master writes the next (and final) command fragment into the Output Buffer: (See the Green changes below) Output Buffer Input Buffer Byte # Value Byte # Value Output Buffer Control Byte Input Buffer Control Byte...
  • Page 166 PROFIBUS INTERFACE Next, the Master signals that this fragment is ready, by toggling Bit 1 of the OBCB & OBDCB. Since this is the final fragment, the Master clears Bit 3 to 0. (See the Green changes below) Output Buffer Input Buffer Byte # Value...
  • Page 167 BIS M-62_ MANUAL When the Slave sees Bit 1 of the OBCB & OBDBC toggle, it grabs this command fragment from the Output Buffer. The Slave then acknowledges the command fragment by toggling Bit 1 of the IBCB & IBDCB. (See the Green changes below)
  • Page 168 PROFIBUS INTERFACE The Slave, at this point, after acknowledging the final fragment, knows it has the complete CBx command, so it processes the command. Assuming the command is successful, the Slave will write the response (in this case a “Tag Write Successful”...
  • Page 169 BIS M-62_ MANUAL The Master now toggles Bit 0 of the OBCB & OBDCB to acknowledge that it has received the response. (See the Green changes below) Output Buffer Input Buffer Byte # Value Byte # Value Output Buffer Control Byte Input Buffer Control Byte (OBCB) (IBCB)

  • Page 170: Example 5: Resynchronization

    PROFIBUS INTERFACE 9.5.5 Example 5: Resynchronization For this example we will assume the same conditions as the previous example, that the input buffer and output buffer are 32 bytes each. It does not matter what data is currently in the two buffers, other than the control bytes and data consistency bytes –...
  • Page 171 BIS M-62_ MANUAL If the Master believes that the handshaking has gotten out of synch, it can request a resynchronization, by setting Bit 2 of the Output Buffer Control Byte (the OBCB) and then also setting the same bit in the Output Buffer Data Consistency Byte (the OBDCB). Bit 2 is not a toggle –...
  • Page 172 PROFIBUS INTERFACE When the slave sees Bit 2 In the OBCB & OBDCB set, it knows it needs to resynchronize its handshaking bits in the IBCB & IBDCB. So the Slave will acknowledge the resynchronization request by setting Bit 2, and will clear Bit 1 and Bit 0 in the IBCB &...
  • Page 173 BIS M-62_ MANUAL When the Master sees Bit 2 of the IBCB & IBDCB set, it clears Bit 2 of the OBCB & OBDCB to acknowledge that the Slave has resynchronized. (See the Green changes below) Output Buffer Input Buffer Byte # Value Byte #...
  • Page 174 PROFIBUS INTERFACE And lastly, when the Slave sees the Master clear Bit 2 of the OBCD & OBCDB, it clears Bit 2 of the IBCB & IBDCB to complete the resynchronization process. (See the Green changes below) Output Buffer Input Buffer Byte # Value Byte #...

  • Page 175: Profinet Interface

    BIS M-62_ MANUAL 10 PROFINET INTERFACE For BIS M-628-075-A01-03-ST34 models. NOTE 10.1 PROFINET OVERVIEW Profinet is the open industrial Ethernet standard of PROFIBUS & PROFINET International (PI) for automation. Profinet uses TCP/IP and IT standards, and is, in effect, real-time Ethernet.

  • Page 176: Data Exchange

    PROFINET INTERFACE 10.3 DATA EXCHANGE The Master Profinet is usually a PLC (Siemens S7 or others) but it could be a PC based device as well. The Profinet Controller is always Slave in the Profinet network. Profinet Master Profinet Network Profinet Slaves Profinet Slaves RFID...

  • Page 177: Protocol Implementation

    Controller to the Master station is about 30 ms plus the intrinsic PROFINET IO delay and the Master delay. This product implements the Balluff AnyBus Protocol which is a layer that is built upon the intrinsic fieldbus data exchange mechanism. The Driver is needed to add features such as flow control and fragmentation.

  • Page 178: Control Field

    PROFINET INTERFACE Figure 75 - Exchange Area Buffer Structure 10.4.2 Control Field The Input field structure reserves IN[0] for handshake purposes: bit 0 and bit 1 are used for this. Bit 6 is set to 1 in order to specify the messaging protocol number 1 is in use. The Output field structure is symmetrical, and reserves bit 0 and 1 for handshake purposes.
  • Page 179 BIS M-62_ MANUAL function of the OUT[0] byte: OUT[0].bit0 = TxBufferEmpty, toggles when transmitted data block has been read from master. OUT[0].bit1 = RxBufferFull, toggles when new data block is available from master. OUT[0].bit2 = Resync Request, set to 1 for 1 second to resynchronize a slave. After resynchronization, all 4 handshake bits are set to 0 and next toggle brings them to 1.
  • Page 180 PROFINET INTERFACE Data Transmission Slave → Master The transmission state machine is shown to understand how a single block is transmitted and received. This protocol guarantees a basic flow control mechanism from slave to master. Figure 77 - Slave to Master Transmission State Machine Data Transmission Master →...

  • Page 181: Sap Field

    The Application layer uses all or a part of the remaining bytes of the Exchange Area buffers that are not used by the Balluff AnyBus Protocol. The Length Field is introduced to keep the information of how many bytes are really used by the Application Layer. A fragment that is not the last one of a fragmentation sequence must fill this field with Max(In/Out)Bytes-3, depending on whether it is an INPUT/OUTPUT fragment.

  • Page 182: Application Data Buffer

    PROFINET INTERFACE 10.4.5 Application Data Buffer The Application data buffer holds the CBx commands described in the CBx Command Protocol Manual. 10.5 EXAMPLES OF PROFNET COMMAND/RESPONSE MECHANISM As seen in par. 10.3, there are two buffers – an OUTPUT Buffer that is controlled by the MASTER, and an INPUT Buffer that is controlled by the slave (the Controller).
  • Page 183 BIS M-62_ MANUAL Bit 7 is always 1, to conform to Balluff’s proprietary Protocol. Byte 1: is always 0. Byte 2: contains the length of the packet in bytes (CBx Command or Command Fragment) to be sent to the RFID Controller. This can be the length of an entire CBx command, or the length of a fragment of a command, if the CBx command is larger than the space allowed to send it in a single fragment.
  • Page 184 Slave. Bit 7 is set to 1 as soon as the Slave has been successfully initialized at power-up, and remains at 1, to conform to Balluff’s proprietary Protocol. Byte 1: is always 0. Byte 2: contains the length of the packet in bytes (CBx response or response fragment) to be sent back to the Master.
  • Page 185 BIS M-62_ MANUAL...

  • Page 186: Technical Features

    RFID OPERATING PRINCIPLES 11 TECHNICAL FEATURES 11.1 BIS M-62_ PROCESSOR UNITS ELECTRICAL FEATURES Supply Voltage 12 to 30 Vdc DC Input Current max. 500 to 300 mA Host Communication Interface: RS232 RS232 Subnet16™ (RS485) RS485 Industrial Ethernet (IND), TCP/IP, MODBUS TCP DeviceNet 125 Profibus –DP Profinet IO...

  • Page 187: Bis M-37_ Antennas

    BIS M-62_ REFERENCE MANUAL 11.2 BIS M-37_ ANTENNAS RADIO FEATURES Frequency 13.56 MHz Input Impedance 50 ohms Gain: BIS M-370-000-A02 -37.8 dBi BIS M-371-000-A01 -36.6 dBi BIS M-372-000-A01 -26.3 dBi BIS M-373-000-A01 -22.9 dBi Conducted Input Power ENVIRONMENTAL FEATURES Operating Temperature -20°...
  • Page 188 RFID OPERATING PRINCIPLES...

  • Page 189: Rfid Operating Principles

    BIS M REFERENCE MANUAL RFID OPERATING PRINCIPLES RFID OVERVIEW BIS M products are designed for use with passive RFID tags, which do not require batteries or contain an internal power supply. Through a process called inductive coupling, passive RFID tags obtain power from the RFID antenna. When a passive tag comes in contact with the RF field from an RFID antenna, the incoming radio frequency signal generates a small, but sufficient, electrical current that powers the passive tag’s integrated circuit (IC) and antenna.
  • Page 190 Z-HB-004 IND) or Subnet16 TCP/IP Hub (BIS Z-HB-004-TCP). Subnet16 Hubs possess four independent controller ports, four digital inputs and four digital outputs. BALLUFF RFID TAGS As of this publication, Balluff tags containing the RFID integrated circuits (ICs) listed below are compatible with BIS M Controllers. BIS M-1xx-10 RFID Tags...
  • Page 191 For this reason there are many security authentication measures taken within the air protocol between the RFID device and the tag. Balluff was the...
  • Page 192 “features,” an ISO 14443 tag made by one manufacturer may not necessarily be readable by a BIS M Controller and, likewise, a Balluff ISO 14443 compliant tag might not be readable by another manufacturer’s RFID controller. The BIS M Controllers support Balluff security keys for use on NXP Mifare ISO 14443A tags.
  • Page 193 Molded tags, which are PCB tags that have been protected with a durable resin over molding, are the most rugged and reliable type of tag offered by Balluff. These tags are designed for closed loop applications where the tag is reused; thereby the cost of the tag can be amortized over the life of the production line.
  • Page 194 High temperature (HT) tags, using patented processes and specialized materials, allow tags to survive elevated temperatures, such as those found in automotive paint and plating applications. Balluff offers a wide variety of molded tags that have been developed over the years for real world applications.
  • Page 195 BIS M REFERENCE MANUAL Optimizing Tag Memory Data is stored in tag memory in binary format (1’s and 0’s). Binary numbers are notated using the hexadecimal numbering system (otherwise, users would be forced to interpret long strings of 1’s and 0’s). Below is an example of how hexadecimal notation simplifies the expressing of byte values for the decimal number 52,882.
  • Page 196 RFID OPERATING PRINCIPLES Konformitätserklärung Declaration of Conformity Dokumentnr. · Documentno. 895203 QEP 000 01 / ON0200 Hersteller · Manufacturer Balluff GmbH Adresse · Address Schurwaldstraße 9 73765 Neuhausen a.d.F. Germany Telefon · Phone +49 7158 173-0 +49 7158 5010 E-Mail balluff@balluff.de...
  • Page 197 BIS M REFERENCE MANUAL Neuhausen a. d. F., den Norbert Popp Geschäftsbereichsleiter, Geschäftsbereich Identifikation Vice President, Business Unit Identification...
  • Page 198 RFID OPERATING PRINCIPLES...

This manual is also suitable for:

Bis m-620-068-a01-00 seriesBis m-620-067-a01-04 seriesBis m-623 seriesBis m-622 seriesBis m-628 seriesBis m-371-000-a01 ... Show all

Table of Contents