CONTENTS REFERENCES ......................vi Conventions......................... vi Reference Documentation ................... vi Services and Support ....................vi SAFETY AND COMPLIANCE NOTICES..............vii FCC Compliance ......................vii Power Supply.......................vii CE Compliance......................vii GENERAL VIEW ....................... viii GETTING STARTED....................1 Introduction ........................1 1.1.1 The Subnet16™ Gateway .................... 1 Subnet16 Profibus Gateway Features................
Page 4
5.5.4 Example 4: Fragmentation of Commands ..............71 5.5.5 Example 5: Resynchronization ................... 82 TECHNICAL FEATURES................... 87 MODELS AND ACCESSORIES ................88 Datalogic Automation RFID Tags ................89 EXAMPLE NETWORK LAYOUTS................90 Subnet16™ Gateway –ThickNet Network Layout ............90 Subnet16™ Gateway –ThinNet Network Layout ............91...
“You” refers to the System Administrator or Technical Support person using this manual to install, mount, operate, maintain or troubleshoot a GWY-01-PBS-01. Throughout this manual, the GWY-01-PBS-01 is referred to as the “Subnet16 Gateway” or simply “the Gateway”. Cobalt C-Series, HF-Series and UHF-Series RFID Controllers are referred to as Cobalt Controllers, or just “the Controller”.
FCC COMPLIANCE Modifications or changes to this equipment without the expressed written approval of Datalogic could void the authority to use the equipment. This device complies with PART 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference which may cause undesired operation.
GENERAL VIEW GWY-01-PBS-01 Figure A Profibus Mode LED Mounting Bracket Power On LED Subnet16 BUS LED Profibus Status LED USB Connector Subnet16 Connector Configuration Error LED Profibus Connector viii...
GETTING STARTED 1 GETTING STARTED 1.1 INTRODUCTION Welcome to the GWY-01-PBS-01 Reference Manual. This manual will assist you in the installation, configuration and operation of Datalogic Automation Subnet16™ Profibus Gateway Interface Module. The Profibus Gateway can control up to 16 passive ultra-high or high frequency read/write Radio-Frequency Identification (RFID) controllers.
1.3 ABOUT THIS MANUAL This manual provides guidelines and instructions for installing, configuring and operating Datalogic Automation's Subnet16 Profibus Gateway Interface Module (GWY-01-PBS-01). This document does NOT include explicit details regarding each of the Gateway’s RFID commands. Specific RFID command related information is available in the CBx Command Protocol –...
Sufficient power, supplied via Subnet16 network cabling, capable of powering the Gateway and its RFID controllers Datalogic Automation RFID series tags: HMS, LRP, T/Gamma, I, or UHF-G2-525 1.5.2 Installation Precautions Do not route cables near unshielded cables or near wiring carrying high voltage or high current.
GETTING STARTED 1.5.4 Maximum Supported Trunk and Drop Cable Lengths ThickNet trunk length up to 300 m. ThinNet trunk length up to 20 m. ThinNet drop cable length up to 2 m. 1.6 INSTALLING THE GATEWAY The numbered steps in the following procedure are also indicated in the SubNet16 networks example layouts shown in Appendix B.
To modify the Gateway’s internal configuration for application specific requirements: 1. Install the USB Driver onto the configuration PC, see par. 1.8. 2. Download the Cobalt Dashboard™ utility from www.automation.datalogic.com and install the software on your configuration computer. Use the Dashboard utility to connect, via USB, to the Gateway.
GETTING STARTED 1.8 USB DRIVER INSTALLATION This paragraph contains instructions for installing the Windows 2000/XP USB driver for Datalogic Automation RFID devices. Complete the following steps before installing the RFID USB driver. Download the RFID USB driver package from www.automation.datalogic.com.
Page 16
GWY-01-PBS-01 Select “Install from a list or specific location” and then click Next. Check the box labeled: “Include this location in the search” and then click the Browse button. Figure 4: Found New Hardware Wizard – Include this Location Browse to the folder containing the extracted RFID USB driver files and then click OK.
Page 17
GETTING STARTED Click Next to install the USB driver. Figure 6: Found New Hardware Wizard – Ready to Install Please wait while the Found New Hardware Wizard installs the USB driver. Figure 7: Installing the USB Driver...
Page 18
GWY-01-PBS-01 After the USB driver has been installed, click Finish. Figure 8: USB Driver Installation Complete Immediately after you click Finish, the Found New Hardware Wizard will close and then automatically restart, prompting you to repeat the USB driver installation. This occurs because Windows requires a second trip through...
GETTING STARTED 1.9 GATEWAY PROFIBUS CONFIGURATION USING COBALT DASHBOARD™ The Cobalt Dashboard™ Utility is a software application that allows users to view, modify, save and update the configuration settings of their Cobalt controllers. Follow the instructions below to operate the Cobalt Dashboard Utility and to set the Cobalt device’s configuration. 1.
Page 20
GWY-01-PBS-01 The Dashboard should send some commands to retrieve device and configuration information from the device. If serial communications are set up correctly, the device configuration area within the Cobalt Dashboard should now look like this: Figure 12: Cobalt Dashboard™ Gateway Profibus Device Configuration Area The default Profibus ID is 63, and the default Input and Output Buffer sizes are 64 bytes each.
2.1.1 Subnet16™ Subnet16™ is an advanced feature-rich network protocol that supports a subset of the Datalogic Automation MUX32 legacy protocol. The advanced features implemented in the Subnet16 protocol allow the Gateway to assign individual Node ID values automatically to each RFID controller connected on the Subnet bus. Subnet16 also allows the Gateway to detect when a new controller is connected to the Subnet or when a controller “falls off the...
GWY-01-PBS-01 2.2 LED INDICATORS 2.2.1 Front Panel LEDs LED Name LED Color LED Description The POWER LED is ON whenever power POWER GREEN is applied to the Gateway. The BUS LED will flash ON and OFF to indicate that data is being transmitted...
GATEWAY OVERVIEW 2.3.1 Profibus The Gateway Profibus Connector is used for Profibus Slave Node connection to the Profibus network. Figure 14: Profibus DB9F Interface Connector Name Function B Line (+) Positive RxD/TxD (RS485 level) Request To Send Bus Ground (isolated) +5 Vdc Bus Power A Line (-)
GWY-01-PBS-01 2.3.3 Subnet16™ RS485 The Gateway Subnet16™ RS485 Connector (M12 5PF) is used for connecting to the Subnet16 network and RFID controllers. Figure 16: M12 5PF Subnet16™ RS485 Interface Connector Name Function Shield Cable shield Power supply input voltage +...
Total System Current Consumption = [Max Gateway Current + (Max Controller Current x Number of Controllers)] Example A Subnet16™ network powered at 24 Vdc is composed of a GWY-01-PBS-01 connecting eight C0405-485 RFID Controllers. Total System Current Consumption = [0.133 A + (0.087 A X 8)] = 0.829 A 2.4.3 Cable Voltage Drop...
Gateway, as it will experience the greatest voltage drop. 2.4.4 Current Rating for Cables The maximum current rating for the Subnet16™ network using Datalogic Automation's cables and accessories (CBL-xxxx), is 4.0 A. 2.5 NODE ID CONFIGURATION & MANAGEMENT Only RS485-based RFID controllers can be connected to a Gateway’s Subnet network and...
GATEWAY OVERVIEW Avoid that the configuration tag is simultaneously read by more than one controller, especially for UHF controllers. NOTE 2.6 GATEWAY AND SUBNET NODE NAMING The Gateway can store a 64-byte ASCII string for each of the 16 Subnet Nodes and one 64- byte ASCII string for the Gateway itself.
The Cobalt Dashboard™ is a Windows-based software application that provides users with complete control over their Datalogic Automation RFID Solution. Users can monitor their entire RFID system, from the tag level, to the RFID controller, to the Gateway, and to the host.
GATEWAY OVERVIEW Supports Ethernet, Profibus, DeviceNet, RS232, and USB models 2.7.2 C-Macro Builder™ C-Macro Builder™ is an easy to use GUI-driven utility for Windows that allows users to create powerful RFID command macro programs. Figure 18: C-Macro Builder™ When used in conjunction with the Cobalt Dashboard™, users can easily download, erase, backup and manage multiple RFID command macros and macro triggers for each Subnet Node.
Triggers can be configured, for example, to activate a macro when a tag enters or leaves a controller’s RF field. Datalogic Automation RFID controllers 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...
RFID COMMAND MACROS 3.5 HOW ARE MACROS CREATED? Macros are created using the powerful, yet simple, C-Macro Builder™ utility from Datalogic Automation. The easy to use GUI allows the user to create powerful RFID macro programs quickly and easily. When used with Datalogic Automation Cobalt Dashboard™ utility, users can effortlessly download, erase, and manage their macros and triggers, as well as set the operational configurations of their RFID controllers and Subnet16™...
In order to execute RFID commands properly, the RFID device and host computer must be able to communicate using the same language. The language that is used to communicate is referred to as the Command Protocol. The command protocol used by GWY-01-PBS-01 is called "CBx".
COMMAND PROTOCOL 4.2 CBX - COMMAND PACKET STRUCTURE Below is the packet structure of a standard CBx command. Word # Command Packet Element Overall Length: 2-byte value indicating 0x00 0x06 + (number the number of “words” in the command of any additional packet.
GWY-01-PBS-01 4.3 CBX - RESPONSE PACKET STRUCTURE After performing a command, the Gateway or RFID controller will issue a host-bound response packet. Below is the packet structure of a standard CBx response message. Word # Response Packet Element Overall Length: 2-byte integer indicating...
COMMAND PROTOCOL 4.4 CBX COMMANDS TABLE The table below lists the CBx protocol RFID commands supported by the Gateway and RFID Controllers. Command ID Command Name Description RFID Tag Commands Lock Memory Block Write protects a block of tag memory 0x02 Writes a specified data byte value to all 0x04...
Page 36
GWY-01-PBS-01 Command ID Command Name Description Retrieves the baud rate of the Subnet 0x1C Get Subnet Baud Rate network Writes to flash memory, a user-defined Set Gateway Name 0x21 “friendly” name for the Gateway Used customize modify 0x24 Set Notification Mask Gateway’s 16-bit Notification Mask...
COMMAND PROTOCOL Command ID Command Name Description Deletes pending buffered 0x79 Clear Pending Response responses in the Gateway and resets all Instance Counters to zero Multi-Tag RFID Commands 0x92 Retrieves the tag ID number and a Multi-Tag Read ID and Data All contiguous segment of data from all RFID tags in range 0x95...
GWY-01-PBS-01 4.5.2 CBx - Controller Response Example Below is a controller’s response after successfully completing the Read Data command (as issued in the previous example). Word # Packet Element Overall Length of Response (in "words") 0x00 0x08 0xAA in MSB...
COMMAND PROTOCOL 4.5.4 CBx - Gateway Response Example Below is the Gateway response to the command “Get Node Status List” (as issued in the previous example). Word # Packet Element Overall Length of Response (in “words,” 0x00 0x0E not including the previous 2-bytes – CBx Header and Node ID Echo) 0xAA in MSB 0xAA...
GWY-01-PBS-01 4.6 NODE STATUS BYTE DEFINITION TABLE Node Status Node Status Status Description Byte CONTROLLER The controller at this node has not responded to a INACTIVE poll for at least 40 seconds. If a controller does eventually respond at this Node ID, its status will be changed to “0x04 -...
COMMAND PROTOCOL 4.7 CBX ERROR RESPONSE PACKET STRUCTURE Below is the packet structure of a CBx error response. Note that the one-byte Error Code value is returned in the MSB of the seventh data word. Error Response Element Overall Length: 2-byte value indicating the number 0x00 0x07 of “words”...
GWY-01-PBS-01 4.8 CBX ERROR CODE TABLE Error Code Error Description 0x04 FILL TAG FAILED Fill Tag Command Failed 0x05 READ DATA FAILED Read Data Command Failed 0x06 WRITE DATA FAILED Write Data Command Failed 0x07 READ TAG ID FAILED /...
GWY-01-PBS-01 4.10 NOTIFICATION MESSAGES Notification Messages are small host-bound informational packets of data that are issued by the Gateway when a specified Notification Event (or series of events) occurs within the Gateway or on the Subnet network. For example, the Gateway can be configured to send the host a Notification Message when a controller is attached, or removed, or experiences a problem.
COMMAND PROTOCOL 4.10.1 Notification Message Table The following table contains a listing of the nine possible Notification Messages. Notification Message Event Description CONTROLLER IS HEALTHY Sent whenever the status of a controller changes to ‘Healthy’ CONTROLLER HAS Sent whenever a controller is marked ‘Has PROBLEM Problem’...
GWY-01-PBS-01 4.10.3 Notification Message Packet Structure Description Overall Length of Notification Message (in words) 0x00 0x06 0xFE in MSB = Notification Message Flag 0xFE <Notification Event> Notification Event in LSB Instance Counter in MSB (a Notification Message is <IC> 0x04 considered a response;...
PROFIBUS INTERFACE 5 PROFIBUS INTERFACE 5.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.
GWY-01-PBS-01 5.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 Gateway Profibus is always Slave in the Profibus network. Profibus Master Profibus Network GWY-01-PBS-01 Profibus Slave Subnet16™...
INPUT Area is the Exchange buffer from Gateway Profibus to the Master while OUTPUT Area is the exchange buffer from the Master to the Gateway Profibus. Only the first three bytes are used by the Datalogic AnyBus Driver layer in both buffers for the extended protocol.
GWY-01-PBS-01 Figure 21: Exchange Area Buffer Structure 5.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 51
PROFIBUS INTERFACE 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 52
GWY-01-PBS-01 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 23: Slave to Master Transmission State Machine Data Transmission Master →...
The Application layer uses all or a part of the remaining bytes of the Exchange Area buffers that are not used by the Datalogic AnyBus Driver. 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.
GWY-01-PBS-01 5.4.5 Application Data Buffer The Application data buffer holds the CBx commands with the syntax explained in chapter 4. 5.5 EXAMPLES OF PROFIBUS COMMAND/RESPONSE MECHANISM As seen in par. 5.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 Gateway).
Page 55
– and so the Master can know when all the fragments of a response have been returned from the Slave. Bit 7 is always 1, to conform to Datalogic’s proprietary “DAD” Protocol. Byte 1: is always 0.
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 Datalogic’s proprietary “DAD” Protocol. Byte 1: is always 0.
Page 57
PROFIBUS INTERFACE We will assume for this example that both the Input and Output Buffers have been configured to 32 bytes each. This means that the controllers response (for this command) can fit entirely in the input buffer, and no fragmentation is required. Sending the command: In Byte 2 of the output buffer the Master places the length (in bytes) of the data packet (CBx Command) we are sending.
Page 58
GWY-01-PBS-01 (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]...
Page 59
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] [1] [0] (Always 0) (Packet length in bytes) (CBx Command word length MSB)
Page 60
GWY-01-PBS-01 (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] [1] [1] [0] [0] [0] [0] [0] [1] [0]...
Page 61
PROFIBUS INTERFACE 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 62
GWY-01-PBS-01 If we now place a tag on the controller’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 #...
Page 63
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] [1] (Always 0) (Always 0) (Packet length in bytes)
Page 64
GWY-01-PBS-01 (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] [0] [0] [0] [0] [0] [0] [1]...
Page 65
PROFIBUS INTERFACE 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)
GWY-01-PBS-01 5.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...
Page 67
PROFIBUS INTERFACE 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 68
GWY-01-PBS-01 (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] [0] [0] [0] [0] [0] [0] [1]...
Page 69
PROFIBUS INTERFACE 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)
GWY-01-PBS-01 5.5.3 Example 3: Fragmentation of Responses For this example, the Master will send a CBx “Read Tag Data” command to the Slave (the RFID Controller) 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 71
PROFIBUS INTERFACE 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 72
GWY-01-PBS-01 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 73
PROFIBUS INTERFACE 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. there is more data remaining) The Slave also simultaneously makes the same changes to the IBDCB.
Page 74
GWY-01-PBS-01 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...
Page 75
PROFIBUS INTERFACE 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 76
GWY-01-PBS-01 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.
Page 77
PROFIBUS INTERFACE 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 78
GWY-01-PBS-01 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...
PROFIBUS INTERFACE 5.5.4 Example 4: Fragmentation of Commands For this example, the Master will send a CBx “Write Tag Data” command to the Slave (the RFID Controller) 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 80
GWY-01-PBS-01 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 81
PROFIBUS INTERFACE 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) Output Buffer...
Page 82
GWY-01-PBS-01 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...
Page 83
PROFIBUS INTERFACE 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 Byte #...
Page 84
GWY-01-PBS-01 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...
Page 85
PROFIBUS INTERFACE 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 (OBCB)
Page 86
GWY-01-PBS-01 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...
Page 87
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 88
GWY-01-PBS-01 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” response) into the Input buffer, and then toggle Bit 0 of the IBCB &...
Page 89
PROFIBUS INTERFACE 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)
GWY-01-PBS-01 5.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 91
PROFIBUS INTERFACE 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 92
GWY-01-PBS-01 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 93
PROFIBUS INTERFACE 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 # Value...
Page 94
GWY-01-PBS-01 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...
TECHNICAL FEATURES 6 TECHNICAL FEATURES ELECTRICAL FEATURES Supply Voltage 12 to 30 Vdc DC Input Current max. 200 – 100 mA Communication Interfaces: Host Profibus RFID Multidrop Readers Subnet16™ (uses RS485 physical layer) Configuration Subnet16™ Baud Rate 9600 (default), 19.2k, 38.4k, 57.6k, 115.2k ENVIRONMENTAL FEATURES Operating Temperature -20°...
RFID tags and the cables needed to make it all work. This portion of the manual lists the products and accessories available for the Subnet16™ Gateway product family. To purchase any of the Datalogic Automation products listed below contact your...
DATALOGIC AUTOMATION RFID TAGS Datalogic Automation designs and manufactures several lines of RFID tags. LRP, HMS and T-Series passive read/write RFID tags are specially suited for Datalogic Automation HF RFID Controllers. Several G2-Series Standard and High Temperature tags are available for UHF RFID Controllers.