Home

BIS M-62_ Processor Unit

1. Figure 65 Controller I O Controller Tags in RSLogix 5000 115 oO BIS M 62_ MANUAL 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 Handshaking is implemented using the first two words Words 0 and 1 in both Input Controller Tag and Output Controller Tags The PLC writes a command to the Output Controller Tag starting with the 2 byte Consume Data Size value at Local 2 0 Data 2 which is the third register of the Output Controller Tag The remainder of the command packet is then written 2 byte per register to the Output Controller Tag starting at the fourth register Local 2 0 Data 3 After writing the command packet data to the appropriate registers the PLC increments the counter value stored at Local 2 0 Data 1 the second register in the Outout Controller Tag The counter at Local 2 0 Data 1 is copied by the Controller to Local 2 l Data 0 the first register of the Input Controller Tag which signals the PLC that the command has been received by the Controller Following execution of the command the Controller writes its response to the Input Controller Tag starting with the 2 byte Produce Data Size at Local
2. 12 BIS M 626 069 A01 06 ST32 BIS M 62 Processor units Industrial Ethernet w I O ISOOZA OVERVIEW gt Name Description BCC M415 MA15 9A 390 PSBENG 003 C BCC M415 M415 6A 330 PS85N6 002 Cable M12 5 pin Male Male ThinNet 0 2 m BCCOET2 Gateway to Drop T BCC M415 M415 6A 330 PS85N6 010 able M12 5 pin Male Male ThinNet 1 m BCCOET3 Gateway to Drop T BCC A315 A315 30 330 PS85N4 020 Cable 7 8 16 5 pin Male Female ThickNet 2 m BCCO95A Cable M12 5 pin Male Male ThinNet 2 m BCC M415 M415 6A 330 PS85N6 020 Gateway to Drop T BCCOET4 BCC M415 0000 1A 030 PS85N6 020 Cable M12 5 pin Female Bare Wires ThinNet 2 m BCCOETA BCC M415 0000 1A 030 PS85N6 050 Cable M12 5 pin Female Bare Wires ThinNet 5 m BCCOETC BCC A315 0000 10 030 PS85N6 050 Cable M12 5 pin Male Bare Wires ThinNet 2M BCCO8WT BCC M414 E834 8G 672 ES64N8 050 Industrial Ethernet Cable M12 RJ45 5m BCCOCT 1 Subnet16 Ts Terminators i Connectors Drop T Connector 5 pin 7 8 16 F M12 F 7 8 16 M BDN T DTE AD 01 ThickNet to ThinNat BCCO7WZ BCC M435 0000 1A 000 41X575 000 Field Mountable Connector M12 5 pin Female Straight BOCO6ZF BCC A315 0000 2A R04 Termination Resistor Plug 7 8 16 5 pin Male ThickNet BCCOAO9 BCC M438 0000 1A 000 51X850 000 RS232 Connector M12 8 pin Female BCCOA03 BCC A315 0000 10 030 PS85N4 050 Cable 7 8 16 5 pin Female Bare Wires 5M BCCO96Y BCC A315 0000 1A R04 Plug Termination
3. 4 47 I mm in N N GH GH sg NY Y oc O gt Y 65 2 56 Figure 7 BIS M 371 000 A01 21 O BIS M 62 MANUAL BIS M 372 000 A01 200 6 2 0 24 i et N nN 00 Tr So ei Y 30 95 1 164 1 18 90 20 Ae 98 B8 7 0 81 gt 3 113 4 _ SE 4 47 23 y mm in AS 65 Ei 2 56 90 12 89 3 Dan Figure 8 BIS M 372 000 A01 22 INSTALLATION gt BIS M 373 000 A01 300 11 81 No E 47 4 1 87 SC So Mm A N co LO T o oo kel St Sei A p 30 951 1 18 u 101 98 8 90 20 3 98 3 86 113 4 R 4 47 Q E r N oon 95 1 Sibt 2 65 90 20 2 56 89 3 3 51 Figure 9 BIS M 373 000 A01 16 4 0 64 206 0 81 2 42 23 lt gt BIS M 62 MANUAL BIS
4. BIS M 62_ MANUAL And lastly when the Slave sees the Master clear Bit 2 of the OBCD amp OBCDB it clears Bit 2 of the IBCB IBDCB to complete the resynchronization process See the Green changes below Output Buffer Input Buffer EIERE Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 7 6 5 4 EGEN RR for foo Always0 Jon fo CL 02 oe Packet length in byte Ja 00 mm 03 00 03 00 30 Ste 180 Data Consistency Byte OBDCB 31 80 Data Consistency Byte IBDCB The Resynchronization process is complete The Slave is now in a known state with the handshake bits set to zero and internally in a state of waiting for a new command 166 PROFINET INTERFACE lt gt 10 PROFINET INTERFACE d For BIS M 628 075 A01 03 ST34 models NOTE 10 1 PROFINET OVERVIEW Profinet is the open industrial Ethernet standard of PROFIBUS amp PROFINET International Pl for automation Profinet uses TCP IP and IT standards and is in effect real time Ethernet The Profinet concept features a modular structure so that users can select the cascading functions themselves They differ essentially because of the type of data exchange to fulfill the partly very high requirements of speed Profinet is defined by PROFIBUS amp PROFINET International Pl and backed by the INTERBUS Club and since 2003 is part of the IEC 61158 and IEC 61784 standards 10 2 PROFINET IO In conjunction wit
5. Bit 0 is toggled by the Master to acknowledge a packet response from the Processor unit Bit 1 is toggled by the Master when it has a packet command ready for the Processor unit Bit 2 is set when the Master wishes to initiate a Resynchronization with the Slave and then cleared when it sees the corresponding handshake from the Slave indicating that the resynchronization is complete Bit 3 is set by the Slave when the total CBx response being returned to the Master is larger than the space available in the Input Buffer or that the packet being returned is a fragment and that there are more fragments to follow This bit is cleared for the final fragment of a fragmented response and so the Master can know when all the fragments of a response have been returned from the Slave 126 PROFIBUS INTERFACE O 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 Byte 3 through Byte N 2 are used for the actual CBx Command or Command Fragment to be sent Byte N 1 the final byte of the Output Buffer is the Data Consistency Byte It is a copy of the Ouptut Buffer Control Byte When changes to the Control Byt
6. STANDARD TCP IP INTERFACE 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 Word Description IMSB ILSB Protocol Header in MSB OxFF Node ID in LSB default value for Cobalt IND is OxFF 0x01 one 0x01 Overall Length 2 byte integer indicating number of 0x00 0x06 words in the command packet MSB 0xAA LSB Command ID example 0x05 Read Data Timeout Value 2 byte integer measured in 10 1 10 second increments 0x00 0x32 0x0032 50 x 10 or 5 seconds Start Address 2 byte integer identifies tag address 0x00 0x01 where read will begin Block Size 2 byte integer indicates number of 0x00 0x06 bytes to retrieve 7 3 2 Standard TCP IP Response Structure Example MSB 0x00 LSB Node ID default value for Cobalt IND is one 0x00 0x01 0x01 The following resembles a typical response to the command issued in the previous example Description IMSB ILSB Protocol Header in MSB OxFF Node ID in LSB default value for Cobalt IND is OxFF 0x01 one 0x01 Overall Length 2 byte integer indicating number of 0x00 0x09 words in the response packet MSB OxAA LSB Command Echo 0x05 Read Data Time Stamp Month Day March 19 Time Stamp Hour Minute 8 15 a m MSB
7. 3 Aller the LED stop blinking remove the Configuration Tag from the antenna s RF field and then power down Factory default values have been restored Figure 42 BIS M Series Configuration Tag 4 1 1 Node ID Configuration Using Configuration Tags Only RS485 based RFID processor units can be connected to a Gateway s Subnet network and each must be assigned a unique Node ID value between 1 and 16 When an RFID processor unit is connected to the Gateway s Subnet network the Gateway will query the new processor unit to obtain certain configuration values specifically the Node ID number If the Gateway does not detect a Node ID conflict it will allow the RFID processor unit onto the Subnet network By using the BIS M Series Configuration Tag that is included with each RS485 based BIS M 62 processor unit the Node ID value can be dynamically assigned by the Gateway or can be manually assigned by the user For the Gateway to dynamically assign a Node ID value to a processor unit the processor unit must first be initialized with the Node ID value of zero This is the equivalent of having no Node ID assigned 61 lt D BIS M 62_ MANUAL d 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 f
8. Data length 1 byte the Error Code CBx Response Data Byte 1 Error Code 7 Tag Not Found CBx Response byte not used SE 81 Data Consistency Byte OBDCB Data Consistency Byte IBDCB The processor unit will toggle Bit 1 of the IBCB amp IBDCB to indicate it has received the command 134 PROFIBUS INTERFACE See the Green changes below Output Input Buffer mere ere Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 81 6 5 4 3 81 7 6 5 4 3 2 1 0 ARCA IS He ON EOI DAD ey or 189 Always 0 __________ A Aways 0 _______ Command word on MSB er Response word an MSB Command word length LSB CBx Response word length LSB Command Type Minimum of 6 words Command Opcode Response Type FF Error Command byte not used Response Opcode FF Error Command Node ID Response Instance Counter Command Timeout MSB Response Node ID Command Timeout LSB Response Timestamp Month Command Not Used Response Timestamp Day Command Not Used Response Timestamp Hour Command Not Used Response Timestamp Minute Command Not Used Response Timestamp Second Response Data length 1 byte the Error Code CBx Response Data Byte 1 Error Code 7 Tag Not Found CBx Response byte not used Jer Data Consistency Byte OBDCB 31 81 Data Consistency Byte IBDCB We will assume that the Slave successfully reads the RFID tag The Slave writes the response in
9. Description Data Type Data Rule Value 1 Interface Speed UDINT 2 Interface Flags DWORD a USINT See section 5 4 2 2 1 5 4 2 2 3 of Volume 2 EtherNet IP Adaptation of CIP from ODVA for more details on this attribute Common Services Service Implementation Service Name Code Class Level Instance Level 0x0E Yes Yes Get Attribute Single 5 9 2 EtherNet IP Vendor Specific Objects The BIS M 626 has two Vendor Specific Objects Vendor Specific Objects BIS M 626 Consume Data Object 0x64 BIS M 626 Produce Data Object 0x65 BIS M 626 CONSUME DATA OBJECT 0X64 32 INSTANCES Class Attributes Instance 0 Default ern Name Description Data Type Data SOSE Value UINT Maximum Consume Data Buffer UINT 32768 Cet Size in words 2 Bitmap of Consume Instances with Data Bit 0 Instance 1 Bit 31 Instance P NT 32 89 BIS M 62 MANUAL Instance Attributes Instances 1 32 Attribute Access Rule PP in _ PP a 1 PN be 1 e E Name Description Data Type Data Consume Data Size in words UINT Value Default UINT UINT UINT UINT A UINT FO Consume Data 8 000 8 249 Fr C Z INT Consume Data 9 000 9 249 INT a Consume Data 10 000 10 249 UINT H J Consume Data 20 000 20 249 UINT FA Consume Data 30 000 30 249 UINT ke Consume Data 31 000 31 249 ve Consume Data 32 000 32 249 UINT UINT Consume Data 32 250 32
10. Response Data length CBx Command Length LSB 50 bytes total Tag Data 50 bytes Response Data Byte Response Data Byte Response Data Byte Response Data Byte Response Data Byte Response Data Byte Response Data Byte Response Data Byte Response Data Byte Response Data Byte Response Data Byte Response Data Byte Response Data Byte Response Data Byte Response Data Byte Response Data Byte 31 183 Data Consistency Byte OBDCB Data Consistency Byte IBDCB 146 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 amp IBDCB Since this is still not the last fragment the Save leaves Bit 3 set to 1 in the IBCB amp IBDCB See the Green changes below Output Buffer Input Buffer nn ee Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 5 4 3 7 6 5 4 KO 0 E 0 a Command word an MSB Response CBx Command word length LSB Response Minimum of 6 words Response CBx Command Type Always AA Response CBx Command Opcode Response 0x05 Read Tag Data Response CBx Command byte not used E Response CBx Command Node 1D Response CBx Command Timeout MSB Response CBx Command Timeout LSB Response OxE8 1000 ms timeout Response CBx Command Start Address MSB Response CBx Command Start Address LSB Response address 0 Response CBx Comm
11. Sync finish ack 0 0 D C Figure 79 Resynchronization State Machine 10 4 3 SAP Field SAP Service Access Point is an identifier that is used to share the same communication channel between processes of two remote stations This allows splitting the single service into different services SAP 0 is actually used by the slave to transfer acquisition information it should also be used to transfer application data from Master to Slave SAP 2 is currently reserved SAP 255 is currently reserved Only SAP 255 and 2 are reserved All other SAPs are free and may be used by new application programs 10 4 4 Length 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 Otherwise this field is filled with a number that is less than or equal to Max In Qut Bytes 3 173 gt BIS M 62_ MANUAL 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 MAST
12. blink used for node identification SOLID RED exception error STATUS GREEN RED FLASHING RED 1 FLASH configuration FLASHING RED 2 FLASHES IP address error FLASHING RED 3 FLASH Station Name error FLASHING RED 4 FLASHES Internal error SOLID GREEN IO Controller connected in NET RUN STATUS FLASHING GREEN IO Controller connected in STOP LINK 1 ime anser SOLID AMBER Profinet link established 60 CONFIGURATION METHODS o 4 CONFIGURATION METHODS There are several configuration methods available for your processor unit depending on the interface type and application e Configuration Tag e Configuration Tools Balluff Dashboard and C Macro Builder e 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 For Subneti6 models BIS M 62 RS485 models this tag can also be used to set the Node ID of each processor unit in the network BIS M Configuration Tag INSTRUCTIONS This tag can be used to restore factory defaults lest RFID controllers and assign Subnet15 Node ID addresses See the product Reference Manual fur further details BUI EE To Restore Factory Defaults 1 Place this Configuration Tag in the antenna s RF field 2 Cycle power to the controller or issue the lt lt Reset Controlier gt gt command the controller LEDs blink
13. red Power Supply GND black Figure 27 RS232 Typical Layouts The BIS M 620 068 A01 00 S_ Processor unit is designed for point to point RFID applications where the distance from host to processor unit is less than 15 meters 50 feet The processor unit connects directly to a serial communications port on a host computer via an RS232 compatible serial interface cable 1 Select a suitable location for the BIS M 62_ Processor unit Antenna 2 Mount the BIS M 37_ antenna to the BIS M 62_ Processor unit either directly or remotely as described in par 1 2 3 Mount the processor unit and antenna to your mounting fixture using M5 or 10 diameter screws not included and secure them with appropriate washers and nuts Tighten screws to 1 7 Nm or 15 Ibs per inch 10 d Connect the BCCOETJ M12 8 pin female connector to the M12 8 pin male interface connector on the BIS M 62_ Connect the BCCOETJ 9 pin female D sub connector to an RS232 COM port on the host computer Tighten the cable s two locking thumbscrews 5 Connect the power supply to the VDC red and GND black wires on the BCCOETJ cable 6 Apply power to the processor unit after all cable connections have been made The LEDs on the unit will flash The READY LED is ON after the power up sequence has completed 7 Onthe host computer set the COM port parameters to 9600 baud 8 data bits 1 stop bit no parity and no handshaking To verify operations download the
14. we will still call this a response See the Green changes below Output Buffer Input Buffer amg E Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 7 6 5 4 7 6 5 4 Elke RE EEN Elie EEN EEN 1 01 00 Always 0 01 00 always o foo foo Packet Tengen In bytes oa 12 Packet length in bytes CBx Response word length MSB CBx Response word length LSB Minimum of 6 words CBx Response Type AA Normal Response CBx Response Opcode OD Continuous Read Response CBx Response Instance Counter CBx Response Node ID CBx Response Timestamp Month CBx Response Timestamp Day CBx Response Timestamp Hour CBx Response Timestamp Minute CBx Response Timestamp Second CBx Response Data length 6 bytes the Tag ID CBx Response Data Byte 1 Tag ID Byte I CBx Response Data Byte 2 Tag ID Byte 2 CBx Response Data Byte 3 Tag 1D Byte 3 CBx Response Data Byte 4 Tag ID Byte 4 CBx Response Data Byte 5 Tag 1D Byte 5 CBx Response Data Byte 6 Tag ID Byte 6 30 00 31 180 Data Consistency Byte OBDCB Data Consistency Byte IBDCB 138 PROFIBUS INTERFACE The Master can see that Bit 0 of the IBCB amp 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
15. 0 21 PA Le Oi L ts ra lt no mm e RE wei O COM RS232IVDG Jo Digital 1 O 12 models only Se Y 05 3 98 90 21 3 86 Figure 1 BIS M 620 068 A01 00 Dimensions 15 O BIS M 62 MANUAL 2 1 2 BIS M 620 067 A01 04 Subnet16 Models 2 112 E 4 41 co Si co rm NN po E E E Zu om e I T E a Y ue BS T rT e ODE ID Lot READY O In O rr Je Be EG ei S r LO a F COM O O Lot ascas une JO Digital I O 12 models only D lt A d 5 3 L 98 8 90 21 3 86 Figure 2 BIS M 620 067 A01 04 Dimensions 16 INSTALLATION gt 2 1 3 BIS M 626 Ethernet IP Models 3 112 a 4 41 qa Ns ie aS 1 50 2 13 63 2 48 3 2 48
16. 5 3 ve 0 21 I Ge i p E rT e BOIATALOOI COBALT FF mm READY in ed RF ei A TO P ADDRESS COLEG DEFAULT Lo custom ETHERNET voe lO Digital I O 12 models only _ 05 3 8 13 86 90 21 Figure 3 BIS M 626 Dimensions oO BIS M 62 MANUAL 2 1 4 BIS M 623 _ DeviceNet Models 112 4 41 4 0 16 rr et 2 DEVICENET READY os 2 a L HET STATUS e 10 wi m OM DNT RS232 Y 5 3 98 90 21 3 86 8 Figure 4 M 623 _ Dimensions 18 INSTALLATION O 2 1 5 BIS M 622 Profibus Models 112 4 p 4 41 00 20 y iit 43 0 79 1 69 hu 54 1 5
17. M 370 000 A02 40 1 59 ga 76 s E LO T 2 98 W m E 13 1 i x2 e 0 52 70 SO Br a 2 76 e DO 38 i gt 1 50 e Io 2 Sv 9 0 Es gt Ny M ee _ 26 1 02 05 4 T O 00 O LO E TN No O0 a dhr Ze SE Se e Bu Ei ki eg wend O s E mm in U U on Figure 10 BIS M 370 000 A02 24 INSTALLATION oO 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 1 Connect the BIS M 37_ antenna to the BIS M 62_ processor unit by inserting the RCA antenna plug into the RF port RCA jack on the processor unit as shown above 2 Secure the antenna to the processor unit using the two 20 mm M5 screws and washers provided with each BIS M 62 processor unit You can use the 4 mm hex key wrench supplied with e
18. Model 371 371 371 371 Environment BISM 135 267 105 38171150 4061160 120 48 Free Air BIS M 136 __ 254 10 0 1381 15 0 1432 17 0 127 5 0 Attached to Metal with spacers BIS M 184 03 L 216 8 5 292 11 5 343 13 5 82 3 25 BIS M 132 _ 64 2 5 64 2 5 Not Advised Not Advised isms 15 45 155 61 een ans BIS M 183 07 L 85 34 05 27 NotAdvised Not Advised d For further information regarding the Antenna to Tag Ranges please refer to the specific Tag s Datasheet NOTE 28 INSTALLATION gt 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 PIN 5 PIN 8 N C SIGNAL GND PIN 4 PIN 1 RESERVED VDC PIN 3 GND RESERVED N C Not Connected Figure 13 RS232 Interface M12 8 pin Male Connector Function Input Power Power Ground Reserved Reserved RS232 Receive Data RS232 Transmit Data Signal Ground Pi 1 2 3 4 5 6 D 8 29 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 5 TX RX PIN 1 SIGNAL GND Figure 14 RS485 Subnet16 Interface M12 5 pin Male Connector Function SGND Signal Ground Vdc Subnet16 M Bus Power GND Su
19. Resistor M12 5 pin Female ThinNet BCCOADA BCC A315 A315 30 330 P585N4 050 Cable 7 8 16 5 pin Male Female ThickNet 5 m BCCO95F Plug Termination Resistor 7 8 16 5 pin Female BCC M415 0000 1A R04 ThickNet BCCOA08 BCC A335 0000 10 000 61X5A5 000 Field Mountable Connector 7 8 16 5 pin Female Straight BCCO7OF BDN T DTE AA 01 T Connector 7 8 16 5P M F F ThickNet to ThickNet BCCO7WP BCC M415 0000 2A R04 Termination Resistor Plug M12 5 pin Male ThinNet BCCO9MR BDN T DTN DD 01 Drop T Connector M12 5 pin F F M ThinNet to ThinNet BCCO7WR 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 13 lt D BIS M 62 MANUAL 14 INSTALLATION gt 2 INSTALLATION 2 1 MECHANICAL DIMENSIONS 2 1 1 137 BIS M 620 068 A01 00 Serial RS232 Models 112 4 41 co CG 00 2 3 3 msk Q e i 3 T m e a te 5 3
20. Tag ID Byte 1 CBx Response Data Byte Tag ID Byte 2 CBx Response Data Byte Tag ID Byte 3 CBx Response Data Byte Tag ID Byte 4 CBx Response Data Byte Tag 1D Byte 5 CBx Response Data Byte Tag ID Byte 6 CBx Response Data Byte Tag ID Byte 7 CBx Response Data Byte Tag 1D Byte 8 131 180 Data Consistency Byte OBDCB SETE FG Data Consistency Byte IBDCB The command response sequence has completed command has been issued and the response received in this case a successful read of the RFID Tag ID and the response has been acknowledged 137 O BIS M 62_ MANUAL 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 lf 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 handshakes are performed for each response For this example the processor unit automatically reads a tag 6 bytes of data and places the response in the Input Buffer and toggles Bit 0 to indicate that a response Is waiting Although no command was issued by the Master
21. The BIS M 626 069 A01 06 Processor unit is designed for Industrial Ethernet IP RFID applications where the processor unit is connected in an Ethernet IP TCP IP network via compatible cables through a hub or directly to an Ethernet IP host 1 Select a suitable location for the BIS M 626 Processor unit Antenna 2 Mount the BIS M 37 antenna to the BIS M 626 Processor unit either directly or remotely as described in par 2 2 3 Mount the processor unit and antenna to your mounting fixture using M5 or 10 diameter screws not included and secure them with appropriate washers and nuts Tighten screws to 1 7 Nm or 15 Ibs per inch 10 4 Connect the BCCOCT1 M12 4 pin male connector to the M12 4 pin female interface connector on the BIS M 626 Connect the BCCOCT1 RJ45 male connector to the LAN hub switch lf connecting directly to the host computer you will need to use an additional crossover cable 5 Build a power supply cable using the BCC06ZF M12 5 pin female connector Use minimum 24 AWG wires for connection to the power supply lines according to the Vdc connector pinout Connect the BCCO6ZF M12 5 pin female connector to the M12 5 pin male connector on the processor unit Connect the other end of the cable wires or user supplied connectors to the power supply 6 Apply power to the processor unit after all cable connections have been made The LEDs on the unit will flash The READY LED is ON after the power up sequence has complete
22. Time Stamp Seconds LSB Number of Additional Bytes Retrieved 6 Retrieved Bytes 1 amp 2 Retrieved Bytes 3 8 4 Retrieved Bytes 5 8 6 MSB Instance Counter oo LSB Node ID 0x01 04 m 08 oo 107 oO BIS M 62_ MANUAL 8 DEVICENET INTERFACE d For BIS M 623 071 A01 03 ST30 models NOTE 8 1 DEVICENET OVERVIEW DeviceNet is a digital multi drop network based on the CAN Controller Area Network specification which permits easy connectivity between industrial controllers and I O devices When the Controller is connected to a DeviceNet network it is considered an individual node for which a unique Node Address number between 1 and 63 is assigned The DeviceNet Controller conforms to the standards set by the Open DeviceNet Vendor Association ODVA 8 2 DEVICENET CONFIGURATION 8 2 1 Importing the Controller EDS File After making all necessary hardware connections the next step in configuring the BIS M 623 071 A01 03 ST30 for DeviceNet is to import the EDS file Electronic Data Sheets EDS are basic text files that are utilized by network configuration tools to identify and configure hardware devices for DeviceNet networks A typical EDS file contains a description of the product its device type hardware version and configurable parameters The EDS file filename DeviceNet EDS zip for the BIS M 623 071 A01 03 5130 is available from the technical support area of the Balluff website 1 Do
23. a suitable location for the BIS M 62_ Processor unit Antenna 2 Mount the BIS M 37_ antenna to the BIS M 62_ Processor unit either directly or remotely as described in par 2 2 3 Mount the processor unit and antenna to your mounting fixture using M5 or 10 diameter screws not included and secure them with appropriate washers and nuts Tighten screws to 1 7 Nm or 15 Ibs per inch 10 4 Attach a Subnet16 compatible cable i e BCCOETO to the M12 5 pin male Subneti16 connector on the processor unit Connect the other end of this cable to your Subnet16 network 5 To complete the Subnet16 M network installation including power supply wiring trunk wiring network termination Gateway Hub wiring and for a complete list of compatible accessory cables and Subnet16 M network layout examples see the Subnet16 M Gateway or Subnet16 Hub Reference Manuals After installation the Subnet16 network can be configured through the Subnet16 M Gateway Hub using the Dashboard Configuration Tool See the Dashboard Manual for details 43 oO BIS M 62 MANUAL 2 6 3 Installing the BIS M 626 069 A01 06 Industrial Ethernet IND BCCO6ZF Vdc to Power Supply BIS M 626 069 w antenna E BCCOCT 1 H mm mm EE ET H mmm EEE EE EE Ethernet Router Peewee EEE EEE EEE EEE es Ik Figure 29 IND Typical Layouts
24. below Output Buffer Input Buffer gr Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 82 7 6 5 4 7 6 5 4 3 2 1 0 HEI GJ ee ee Kap FEE OE el or 100 Always 0 EFE Jupe 4 Always 0 Packet length in bytes Packet length in bytes CBx Command word length MSB CBx Response word length MSB CBx Command word length LSB CBx Response word length LSB Minimum of 6 words Minimum of 6 words CBx Command Type Always AA CBx Response Type CBx Command Opcode AA Normal Response 0x05 Read Tag Data CBx Response Opcode CBx Command byte not used 05 Continuous Read Response CBx Command CBx Command CBx Command OxE8 1000 CBx Command CBx Command address 0 CBx Command Node 1D Timeout MSB Timeout LSB ms timeout Start Address MSB Start Address LSB Length MSB CBx CBx CBx CBx CBx CBx CBx CBx Response Response Response Response Response Response Response Response Instance Counter Node ID Timestamp Month Timestamp Day Timestamp Hour Timestamp Minute Timestamp Second Data length CBx Command Length LSB 50 bytes total Tag Data 50 bytes d CBx Response Data Byte CBx Response Data Byte CBx Response Data Byte CBx Response Data Byte CBx Response Data Byte CBx Response Data Byte CBx Response Data Byte CBx Response Data Byte CBx Response Data Byte CBx Response Data Byte CBx Response Data Byte CB
25. device Power Ground Output 1 positive Output 1 negative Output 2 positive Output 2 negative Input 1A optocoupled polarity insensitive Input 1B optocoupled polarity insensitive CON OOF WD processor unit They can only be used to optionally supply the I O device AN The Vdc and Ground pins on this connector must not be used to power the within the limits specified in par 2 7 and in the Technical Features CAUTION 38 INSTALLATION gt 2 4 POWER amp 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 For point to point or individually powered slave nodes the calculation is straight forward The calculation becomes more complex for network power sources The following information is provided to assist you in determining the power requirements of an RFID network application in particular a Subnet16 network through drop cables to the Gateway and RFID Processor units By positioning the power supply near the middle of the network you can limit NOTE voltage drop at the ends see par 2 6 2 for network layout diagrams d Power is applied directly to the Subne
26. each Controller Tag are dedicated to handshaking When new information is generated the producing device Data Producer will increment a counter in one of the Controller Tags After identifying the new data the consuming device Data Consumer will copy that same counter value to a different Controller Tag location which lets the Data Producer know that the information has been processed by the Data Consumer WRITE TAG where responses are written by the Cobalt EMS Write1 0 2 the Cobalt copies counter here to ACK EMS Write1 1 3 the Cobalt increments this counter to signal response available EMS _Write1 2 Data Size EMS Write1 8 102 Data READ TAG where commands are retrieved by the Cobalt EMS Read1 0 4 PLC copies the counter here to ACK the response EMS Readti 1 1 PLC increments this counter after writing a command EMS Head 2 Data Size EMS Head 3 102 Data 82 ETHERNET IP INTERFACE O 5 8 2 Ethernet IP Handshaking Example 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 1 The PLC writes the command to the Read Tag EMS_READ1 and then increments the counter in EMS READ1 1 2 The counter in EMS READ1 1 is copied by the BIS M 626 to EMS_WRITE1 0 which acknowledges that the command has been received Controller Tags SAMPLE_435NBA
27. for o 02 os Packet lengtn in bytes oz oc Packet length im bytes ____ Command CBx Response word length MSB Command CBx Response word length LSB Command Minimum of 6 words Command CBx Response Type Command AA Normal Response Command d CBx Response Opcode 06 echo of Tag Write CBx Response Instance Counter CBx Response Node ID CBx Response Timestamp Month CBx Response Timestamp Day CBx Response Timestamp Hour CBx Response Timestamp Minute CBx Response Timestamp Second CBx Response Not Used Data Consistency Byte OBDCB Data Consistency Byte IBDCB 160 PROFIBUS INTERFACE The Master now toggles Bit 0 of the OBCB amp OBDCB to acknowledge that it has received the response See the Green changes below Output Buffer Input Buffer EIERE Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 83 7 6 5 4 83 OOA JG 1 01 00 Always 0 ST 02 poe trasket engen da Bybee 102 oo Tracker Tenth Im ees Command or Response word Er MSB Command CBx Response word length LSB Command Minimum of 6 words Command gt CBx Response Type Command AA Normal Response Command CBx Response Opcode 06 echo of Tag Write Response Instance Counter Response Node ID Response Timestamp Month Response Timestamp Day Response Timestamp Hour Response Timestamp Minute Response Timestamp Second Response Not Used Data Consistency Byte OBD
28. 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 In this case the CBx command we are sending is 12 bytes This length is the length of the command bytes we are interested in sending not the full size of the buffer The length also does not include the Data Consistency Byte at the end of the buffer That is just a mirror of the Control Byte In Byte 3 through Byte 14 the Master places the 12 bytes of this particular CBx command Some CBx commands are larger but all will be at least 12 bytes even if some of those 12 bytes are not actually used 128 PROFIBUS INTERFACE See the Green changes below Output Buffer Input Buffer mere er vare Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 7 6 5 4 5 ee KS h 192 foc Packet length in bytes om fo lt CBx Command word length MSB CBx Command word length LSB Minimum of 6 words CBx Command Type Always AA CBx Command Opcode 0x07 Read Tag ID CBx Command byte not used CBx Command Node ID CBx Command Timeout MSB CBx Command Timeout LSB OxE8 1000 ms timeout CBx Command Not Used CBx Command Not Used CBx Command Not Used CBx Command Not Used 30 31 180 Data Consistency Byte OBDCB 31 80 Data Consistency Byte IBDCB Now tha
29. 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 Byte 3 through Byte N 2 are used for the actual CBx Command or Command Fragment to be sent Byte N 1 the final byte of the Output Buffer is the Data Consistency Byte It is a copy of the Ouptut Buffer Control Byte When changes to the Control Byte are made the same changes must also be made in the Data Consistency Byte before the changes take effect This is to guarantee the validity of the data between the two bytes The INPUT Buffer is controlled by the Slave RFID Controller and is mapped the same way except for the packet bytes containing a response or response fragment from the controller Input Buffer 00 INPUT BUFFER CONTROL BYTE IBCB Always 0 Packet Length in Bytes BEE Packet Bytes Response Byte 0 is the Input Buffer Control Byte The Slave uses the lowest four bits of this byte for handshaking to acknowledge receiving a command from the master Bit 1 and to signal that a response Is ready for the master Bit 0 INPUT BUFFER CONTROL BYTE 7 6 5 4 3 2 1 0 1 0 0 0 0 0 0 0 Bit 0 is toggled by the Slave when it has a new packet response or response fragment ready for the Maste
30. technical support area of the Balluff website 117 E BIS M 62 MANUAL 118 PROFIBUS INTERFACE O 9 PROFIBUS INTERFACE d 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 9 2 PROFIBUS DP Basically Profibus is available in three different versions Profibus DP Decentralized Periphery Multiple masters are possible with Profibus DP in which case each slave device is assigned to one master This means that multiple masters can read inputs from the device but only one master can write outputs to that device Profibus FMS It is a peer to peer messaging format which allows masters to communicate with one another Just as in Profibus DP up to 126 nodes are available and all can be masters if desired FMS messages consume more overhead than DP messages Profibus PA PA protocol is the same as the latest Profibus DP except that voltage and current levels are reduced to meet the requirements of intrinsic safety Class div II for the process industry The Profibus Processor unit supports Profibus DP only since
31. 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 1 Install the Processor unit as described in the relevant sub paragraph in 2 6 2 Connect the Processor unit to your PG power up and wait for the boot procedure to finish 3 Run the Balluff Dashboard 4 From the Connection screen choose your processor unit from the list Dashboard Configuration Tool BALLUFF sensors worldwide COBALT DASHBOARD Industrial Identification RFID Connect To Device Type RFID Controller BIS M 620 Serial RFID Gateway BIS Z GW 001 IND Version 4 0 0 RFID Gateway BIS Z GW 001 TCP Copyright C 2013 RFID Gateway BIS Z GW 001 R5232 RFID Gateway BIS Z GW 001 DNT Balluff GmbH RFID Gateway BIS 2 GW 001 PBS RFID Hub BIS Z HB 004 IND RFID Hub E ies E RFID Controller BIS M 620 Serial bh eg RFID Controller BIS M 623 DeviceNet DP mager BIS M 622 Prof Dashboard Configuration Tool RFID Controller BIS M 410 Serial RFID Controller HF CNTL Profinet RFID Controller HF 0405 Serial RFID Controller C62 Serial RFID Controller HF_CNTL UHF Industrial RFID Controller HF_CNTL UHF Serial Figure 43 Balluff Dashboard HF RS232 Processor unit Selection 5 Choose the appropriate COM port and Baudrate or IP Address for Ethernet mod
32. to the examples in par 9 5 Profibus Interface 176 PROFINET INTERFACE lt gt 177 BIS M 62 REFERENCE MANUAL 11 TECHNICAL FEATURES 11 1 BIS M 62 PROCESSOR UNITS ELECTRICAL FEATURES Supply Voltage DC Input Current max Host Communication Interface RS232 RS232 RS485 Subnet16 RS485 Ethernet IP TCP IP MODBUS TCP DeviceNet 125 Profibus DP Profinet lO One optocoupled polarity insensitive digital input Voltage Range 6 to 30 Vdc DC Input Current max 28 mA Digital Outputs 12 models Two optocoupled digital outputs Voltage Range 6 to 30 Vdc external power 500 mA per output processor units power 300 mA total for both outputs 12 to 30 Vdc 500 to 300 mA vyj w Z 0 Z Digital Input 12 models DC Output Current max RADIO FEATURES Frequency Air Protocols Conducted Output Power ENVIRONMENTAL FEATURES Operating Temperature 20 to 50 C 4 to 122 F Storage Temperature 20 to 70 C 4 to 158 F Humidity max 90 non condensing Protection Class EN 60529 IP65 PHYSICAL FEATURES Dimensions RS232 RS485 IND DNT PBS PNT Weight RS232 RS485 IND 440 g 15 5 oz DNT PBS PNT 560 g 19 8 oz USER INTERFACE LED Indicators RS232 RS485 13 56 MHz ISO 14443A ISO 15693 137 x 112 x 48 mm 5 40 x 4 41 x 1 88 in 164 x 112 x 48 mm 6 48 x 4 41 x 1 88 in READY RF COM READY RF COM NODE ID READY RF COM DEFAULT IP CUSTOM IP READY RF COM DEVICENET READY RF C
33. 0 2 13 _ PROFIBUS q 00 STATUS READY o ae ge mone BE o 19 a ne com in PBSIN PBS OUT voc RS282 9 S d 05 3 _ 98 7 90 21 3 86 Figure 5 BIS M 622 Dimensions gt BIS M 62 MANUAL 2 1 6 BISM 628 _ PROFINET Models a 112 4 41 22 6 0 89 20 0 AR 43 0 0 79 38 0 u 1 69 54 0 1 50 2 13 53 0 21 SE ION SE I PROFINET q co gt MOD STATUS READY G os st 2 NEL STATUS BE D a O LINK 4 en O LINK 2 PNT1 PNT2 VDE RS232 tl 3 q Y 5 3 98 0 20 21 3 86 20 Figure 6 BIS M 628 Dimensions INSTALLATION gt BIS M 371 000 A01 100 6 2 3 94 T 0 24 J N S 3 Te No rs az kal og ON es at Y Y T 85 1 98 p 113 4 A
34. 0 of the OBCB amp OBDCB to acknowledge that it has received the response See the Green changes below Output Input Buffer A EE Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 81 7 6 5 4 3 7 6 5 4 3 GO A A ESA PRO ee Ve KT ee foi 00 Always 0 Im fame 02 oo tracker Length In bytes 109 112 Packet length In bytes a Response word oo MSB CBx Response word length LSB Minimum of 6 words CBx Response Type AA Normal Response CBx Response Opcode OD Continuous Read Response Response Instance Counter Response Node ID Response Timestamp Month Response Timestamp Day Response Timestamp Hour Response Timestamp Minute Response Timestamp Second Response Data length 6 bytes the Tag ID CBx Response Data Byte 1 Tag ID Byte 1 CBx Response Data Byte 2 Tag ID Byte 2 CBx Response Data Byte Tag 1D Byte 3 CBx Response Data Byte Tag ID Byte 4 CBx Response Data Byte Tag ID Byte 5 CBx Response Data Byte Tag ID Byte 6 30 00 Data Consistency Byte OBDCB Data Consistency Byte IBDCB The response has been acknowledged a read of 6 bytes 11 22 33 44 55 66 The reader then reads another tag puts another response in the Input Buffer and toggles Bit 0 again in the IBCB IBDCB 139 BIS M 62_ MANUAL See the Green changes below Output Input Buffer mere ere Output Buffer Control Byte Input Buffer Control By
35. 001 connecting eight BIS M 620 067 A01 04 Processor units 366 mA each 24 Vdc A total of 20 meters of ThinNet cables are used to connect the devices which have Cable Resistance 0 058 Ohms per meter per wire The network power is 24 Vdc The voltage drop calculation must be conducted on the processor unit that is farthest from the Power Supply as it will experience the greatest voltage drop It is always recommended to power the network from the middle T configuration to reduce total voltage drop at the ends In the example below this allows the fourth processor unit and not the eighth to be the furthest from the power supply Voltage Drop 0 133 A GWY 0 366 A x 8 Processor units x 0 058 x 2 x 20 meters 7 10 Vdc total voltage drop for 8 Processor units 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 Subneti6 network using Balluff cables and accessories BCCxxxx is 4 0 A The resistance calculation must include both wires Vde and GND 40 INSTALLATION gt 2 5 2 5 1 INSTALLATION GUIDELINES Hardware Requirements The following is a list of minimum components required to create an RFID reading system Other components may be required depending on the processor unit model see the specific installation procedure for your model 2 5 2 Host computer with specific interface Serial Subnet16 M or Fi
36. 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 Commands utilize at least six registers double byte values or words Modbus Address 4xxxx 3XXXX Read Write Privilege Register Description Im lm 2 byte Consume Data Overall Length 40001 1 R W gt 0 indicates data is available BIS M 626 _ clears to 0 after data is processed MSB Reader Type 2 Jam 1 57 77 LSB Node ID 0x01 for the BIS M 626_ OE e 0 65535 measured in milliseconds ee 0 65535 C e 0 65535 bytes 6 2 2 Modbus TCP Response Packet Structure Produce Registers hold data that is destined for the host or PLC Modbus Address Read Write 4xxxx 3XXXx IEEE 2 byte Produce Data Overall Length 40001 1 R W gt 0 indicates data is available Modbus Client clears to 0 after data is processed EE LSB Command Echo Register Description 8 JRO Node ID Number 33 for the BISM 626_ 4 JRO Timeout Value 0 65535 ________ 5 JRO Read Write Start Address 0 65535 _ 6 JRO Read Block Size 0 65535 bytes _ 7 32774 RO BIS M 626_ Produce Data when applicable 32775 65536_ RO__________ Reseved___________z 98 MODBUS TCP INTERFACE O 6 2 3 Modbus TCP Mapping for Node 33 Modbus Read Write Privilege 1 RW IP Address 1 MS
37. 10 diameter screws not included and secure them with appropriate washers and nuts Tighten screws to 1 7 Nm or 15 Ibs per inch 10 4 Attach a DeviceNet compatible cable to the 5 pin male M12 interface connector on the Connect the other end of this cable to your DeviceNet network 5 Turn your DeviceNet power supply ON After a while the Devicenet LED will briefly flash alternatively Red and Green The READY LED will be ON when the processor unit s startup procedure has completed 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 M Configuration Tool uses the PC RS232 serial port to communicate to the processor unit s RS232 serial port To enable communication 1 To connect the processor units RS232 serial port to the PC you have two choices the first one is the quickest a Connect the BCCOETJ M12 8 pin female connector to the M12 8 pin male interface connector on the BIS M 623 Connect the BCCOETJ 9 pin female D sub connector to an RS232 COM port on the host computer or b Build your own communication cable using the BCCOAO3 connector M12 8 pin female connector and follow the schematic shown in par 1 3 4 2 On the host computer set COM port parameters to 9600 baud 8 data bits 1 stop bit no parity and no handshaking 3 Run the Dashboard M Configuration Tool 45 BI
38. 2 Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 7 6 5 4 7 6 5 4 BE IO ea es eee u e ES Im Tem o a Command word SE MSB CBx Response CBx Command word length LSB CBx Response Minimum of 6 words CBx Response CBx Command Type Always AA CBx Response CBx Command Opcode CBx Response 0x05 Read Tag Data CBx Response CBx Command byte not used CBx Command Node 1D CBx Command Timeout MSB CBx Command Timeout LSB OxE8 1000 ms timeout CBx Command Start Address MSB CBx Command Start Address LSB address 0 CBx Command Length MSB CBx Command Length LSB 50 bytes Sis 183 Data Consistency Byte OBDCB Data Consistency Byte IBDCB The command response sequence has completed A command has been issued and the response received and all fragments of a response have been retrieved and acknowledged 150 PROFIBUS INTERFACE oO 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 This means that the command itself cannot completely fit in the output buffer and therefore needs to be sent in fragments Long Tag writes that exceed the buffer size can be separated into multiple writes with each write addressed
39. 2 1 Data 2 and the actual data beginning at Local 2 l Data 3 It then increments the counter value at Local 2 l Data 1 This alerts the PLC to the new data available the Controller generated response in this case After processing the response information the PLC copies the counter from Local 2 1 Data 1 to Local 2 0 Data 0 which signals to the Controller that the PLC has retrieved the response data OUTPUT CONTROLLER TAG Controller Tag Location and Data Description 4 The PLC copies the value at 2 1 Data 1 here to acknowledge Local 2 0 Data 0 receipt of the response 1 The PLC increments this counter value after copying a command in Consume Data Local 2 0 Data 2 Consume Data Size Local 2 0 Data 3 First WORD of Consume Data Command from PLC Local 2 0 Data xxx xxx WORD of Consume Data Local 2 0 Data 1 116 DEVICENET INTERFACE O INPUT CONTROLLER TAG Controller Tag Location and Data Local 2 1 Data 0 2 The value at 2 0 Data 1 is copied here by the Controller to acknowledge receipt of a command Description 3 The Controller increments this counter to signal that a response Local 2 1 Data 1 S A 9 p Local 2 1 Data 2 Produce Data Size Local 2 1 Data 3 First WORD of Produce Data Response from Controllen Local 2 1 Data xxx xxx WORD of Produce Data NOTE A ladder logic example illustrating the implementation of this handshaking strategy can be downloaded from the
40. 249 UINT Consume Data 32 500 32 249 UINT Consume Data 32 750 32 767 UINT ID A 2 gt So 4 gt 5 gt e fee 10 gt Pr 34 fees 38 fees A2 fees 82 fees 122 gt fees 126 gt fees 130 gt 131 gt 132 133 gt Common Services Service Implementation oo P Service Name Class Level Instance Level Get Attribute Single Set Attribute Single This Service Code is used to flush all attributes to zero 90 ETHERNET IP INTERFACE BIS M 626 Produce Data Object 0x65 32 Instances Class Attributes Instance 0 Default lan Name Description Data Type Data SOSE Value Revision UINT Maximum Produce Data Buffer Size in UINT 32768 Get words et Rule Bitmap of Produce Instances with Data DINT G Bit 0 Instance 1 Bit 31 Instance 32 Instance Attributes Instances 1 32 Default Name Description Data Type Data Access Rule Value Produce Data Size in words UINT ME UNT 10 gt o Attribute ID Produce Data 0 249 UINT Produce Data 250 499 Produce Data 500 749 JUINT O Get Produce Data 750 9 JUINT 0 Get Produce Data 1 000 1 249 ___ UINT ___ O0 Get F FR EA AO AA 0 Produce Data 2 000 2 249 UINT o Get PA PP a Pr 34 Produce Data 8 000 8 249 UINT Oo Get 38 Produce Data 9 000 9 249 UINT 0 Get 42 Produce Data 10 000 10 249 UINT Oo Get 82 Produce Data 20 000 20 249 UINT 0 Get 122 Produce Data 30 000 30 249 UINT 0 Ge
41. 6 000a EMS_READ1 3 16 aa07 Hex INT EMS WRITE1 3 16 aa07 EMS_READ1 4 16 0001 Hex INT EMS_WRITE1 4 16 0601 EMS_READ1 5 1680700 Hex INT EMS_WRITE1 5 16 0204 EMS_READ1 6 1640000 Hex INT EMS_WRITE1 6 1640009 EMS READ1 8 16 0000 Hex INT EMS_WRITE1 8 16 e004 EMS_READ1 9 16 0000 Hex EMS WRITE1 9 16 0100 EMS READ1 10 1640000 Hex EMS_WRITE1 10 16 000f EMS READ1 11 16 0000 Hex EMS_WRITE1 11 164 0 0 EMS READ1 12 16 0000 Hex EMS_WRITE1 12 1640000 EMS_READ1 13 1640000 Hex EMS WRITE1 13 1640000 I m E ES E u EMS_READ1 7 16 0000 Hex INT EMS_WRITE1 16 3408 Ei E zi Ei 4 After the PLC has processed the response information it copies the counter from EMS WRITE1 1 to EMS READ1 0 which signals to the BIS M 626 that the PLC has retrieved the response data 83 gt BIS M 62 MANUAL EE Hler LERS DnE RE NACH EEE er 4 Contraller Tags 5 wm Mara Controller Tags SAMPLE_435MBA controller Serge SAMPLE 35NBA KE Siga Show Al WEI E SAMPLE_ASNBA Shou Show ai sl Sot Tag Name Tag Hana e Valve Foca Mask Tag Hane Male Force Mask Ende EMS READ Br Cava Hen F EMS WRITE el LG Bei EMS READ TO EMS M ITE TD 1640005 be EMS READ 1640005 EMS WFITE1 1 En Hs EMS READ TE 1640006 E EMS MESTIEII EMS READS 164sa0 lo HEMS WRITES EMS_READ1 4 1640001 EMrswallEld 160000 EMS READ 1840740 HL mesur
42. APs are free and may be used by new application programs 9 4 4 Length 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 Otherwise this field is filled with a number that is less than or equal to Max In Qut Bytes 3 125 gt BIS M 62_ MANUAL 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 1 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 The OUTPUT Buffer is mapped the following way Output Buffer OUTPUT BUFFER CONTROL BYTE 0BCB Always 0 Packet Length in Bytes Packet Bytes Command AN Byte 0 is the Output Buffer Control Byte The Master uses the lowest two bits of this byte for handshaking to signal that a command is ready for the slave Bit 1 and to acknowledge receiving a response from the slave Bit 0 OUTPUT BUFFER CONTROL BYTE 7 6 5 4 3 2 1 0 1 0 0 0 0 0 0 0
43. B Example 192 2 RW IPAddress2Example 168 gt 3 CT RW IPAddress3Example 000 __ 4 JRW IPAddress4 LSB Example 100 5 RW 1SubnetMask1 MSB Example 255 gt 6 RW SubnetMask2Example 255 0 8 RW Subnet Mask 4 LSB Example 000 9 RW Gateway Address 1 MSB Example 192 10 RW GatewayAddress2Example 1688 11 RW Gateway Address 3 Example 000 12 LD GatewayAddress4 LSB Example 004 13 RO MAC Address 1 MSB Example 000 14 RO MAGAddress2Example 0x40 0 15 JRO MACAddress3 Example 09D 16 JRO MACAddress4Example 0x12_ Z 17 JRO MACAddress5Example 0x34_ 18 JRO MAC Address 6 LSB Example 0x56 Link Status 0 No Link 1 Link is OK 20 RO Ethernet Speed 10M or 100M bits Link Duplex 0 Half Duplex 1 Full Duplex 22 JRO Revision Major Minor 23 1000 RW Reserved _ S 1001 JRO Input Data Ready Mask Nodes 1 16 gt 1002 JRO Input Data Ready Mask Nodes17 32 gt 1003 JRO Output Data Ready Mask Nodes 33 48 74 1004 JRO Output Data Ready Mask Nodes49 64 gt FO FO PUN 13100 13199 13200 13299 13300 65536 Address 4xxxx Register Description 99 Te BIS M 62_ MANUAL 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 Overall Length The handshaking process is gov
44. BALLUFF sensors worldwide BIS M 62 Processor Unit Technical Description Manual www balluff com CONTENTS mb N OkRWWWh 2 1 211 2 1 2 2 143 2 1 4 2 18 2 1 6 2 2 2 2 1 2 2 2 2 2 8 2 2 4 2 3 1 2 3 2 2 3 3 2 3 4 2 3 0 2 3 6 2 3 2 4 1 2 4 2 2 4 3 2 4 4 2 9 1 2 9 2 2 6 1 2 6 2 REFERENCES Lun 1 CONVENIO ET 1 Reference Documentation a dt 1 SEIVICES and SUNN 1 REGULATORY AND COMPLIANCE NOTICES ennennnnnrnnnnennnnnnnnnennnnnnnnnnennnnennnnnennnner 2 POWER SU PR 2 GENERAL VIE Na 3 OVERVIEW sea area 11 ic o A O ea en eee nen 11 FIF Serles EE 11 ABOUT SS e sees Le es 11 Who Should Read This Manual 12 A 12 Models and ACCESSONES a ai 12 Ballot REID 1440 sa 13 INSTALLATION a ne des l nsi datan best Sons S r F rs ON 15 Mechanical DIMENSIONS Vitro 15 BIS M 620 068 A01 00 Serial RS232 Models ooccococccccccccccccocccnnconcnccononcnncnnnos 15 BIS M 620 067 AO1 04 _ _ Subnet16 Models ee 16 BIS WI 626 Heel EELER ageet ee 17 BIS 1623 DeviceNet Models mannen ee ee 18 BIS M 622 Profibus Models utorrent 19 BIS M 628 PROFINET Models iieri i 20 BIS MES7 Antenna MOUNT 25 Berg Antenna MOI ee 25 Remote Antenna Mounting ccoocccoccconcconcocncncnoncnonononcnonononnncnnnnanonnnnnanonancnnncnnncnons 26 Minimum Mounting Distance Between Adjacent Antennas 27 Antenna 10 149 Ranges aussen aa ea 28 Elcano o es da Load 29 SG EE EE MR tens
45. 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 42 INSTALLATION gt 2 6 2 Installing the BIS M 620 067 A1 04 S_ RS485 BCCO7WR BCCO7WR nn BCCOETO A n Im al St Sch BCCOETO lt O LLI O oO O O m o O O E E ca LLI LLI O o LL Oo E E O O LLI LU O O O O a O O m O O m m DATALOGIC SDATALOGIC SDATALOGIE SDATALOGIC Les COBALT HF COBALT HF Kg COBALT HF N COBALT HF E JE z so mo Kl Im Vdc GND 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 The BIS M 620 067 A1 04 5 Processor unit is designed for Subnet16 RFID applications where the processor unit is connected in an RS485 network via Subnet16 M compatible cables to the host through a Gateway or Hub 1 Select
46. CB Data Consistency Byte IBDCB The command response sequence has completed A command has been issued over 3 fragments and processed and the response received and the response has been acknowledged 161 BIS M 62_ MANUAL 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 resynchronization only resets the handshaking to a known state For this example we will assume a starting state as follows Output Input Buffer Ae ee Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 7 6 5 4 ee EEN CONC E A A OG 02 oe Packet length in bytes 19 o mm 0 3 00 03 00 ELO Er Data Consistency Byte OBDCB Data Consistency Byte IBDCB 162 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 It is always set to 1 to begin a resynchronization process and cleared later to acknowledge that the process is complete NOTE See the Green changes below Output Buffer Input Buffer Bee 7 AE Output Buf
47. Configuring Controller for DeviceNet Going Online Browse for network Select communications path to the desired network w Autobrowse Refresh El Workstation KLASON e Linx Gateways Ethernet A1 e ALL NTWKS Ethernet Jamin Ethernet a 192 100 100 107 ATI CR Master DR Master 192 100 100 3 1756 ENBT 4 1756 ENET 23 Backplane 1756 41374 00 1756 L1 4 LOGIKS550 CL DI G DNP DeviceNet Scanne 47 1551 C18 DC 2 59 3 Select the appropriate DeviceNet network and then click OK 109 lt gt BIS M 62 MANUAL 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 1755 DNEYA 1747 50N Scanner Modulo oo DI Browsing network E Hol loud Dees sihen DA Fi ee Dodge FJ Rekl fusta imbibe Er Roco hubarin ips Seder Controls Corporation Zeche inctrurentaion Linknosn Fender 10 971 H bk M Gasph rasche b nats Love Conbguratarn A Disg Jl rf NEESS Mode George Pha onire paih b LAO rn 152 100 100 MBacipine TA Figure 59 Scanning Node Addresses on a DeviceNet Network 4 When the scan operation has completed click UPLOAD in the Scanner Configuration Applet dialog box to update the configuration of the
48. D CONFIGURATION FOR ETHERNET IP 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 To configure the BIS M 626 s OnDemand Configuration settings follow the steps below 1 Open a Web browser on the host and enter the BIS M 626 s new IP address in the URL field The HTTP Server Main Page will be displayed 2 Atthe HTTP Server Main Page click the button labeled OnDemand Config 1 we A wm MT Get Ae A at Ce A wn 4 A d ee mm Fa eg wi HF CNTL IND v1 0 4 Industrial Ethernet RFID Control OnDemand ina OnDemand Status Serial Config EMS Web Page AA AA AAA ARA AA ATA AAA de Bn ni The OnDemand Configuration Page will be displayed 76 ETHERNET IP INTERFACE O OnDemand Configuration Page The OnDemand Configuration Page allows you to modify the settings of the BIS M 626 s Node OnDemand Configuration PLC Type Disable OnDemand PLC IP Address 0 0 0 0 PLC Slot Number pg Read Delay 0 10ms ticks 0 6000 Writes transfer data from the FxLink to the PLC Reads transfer data from the PLC to the FxLink Write Size and Read Size Range is 0 100 words 0 disables Write Tag Name and Read Tag Name are the Tag Names 1 e Taga for the ControlLogqgix
49. Devices Scanlist 163 Cobalt DN Gateway A i Automap on Add Electronic Key Upload from Scanner _ nella Vet Download to Scanner UK Lancel Apply Help 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 4 Highlight the Controller in the Available Devices list and add it to the Scanlist field on the right hand side of the dialogue box Click Apply and then OK The Controller will be added to the list of DeviceNet hardware in RSNetWorx 5 Next select the Controller from the list of DeviceNet hardware and edit its LC Parameters Set the Input Size and Output Size parameters according to your application requirements then click OK In the example below 30 input bytes and 30 output bytes will be scanned per polling cycle d Strobed mode is not supported by the BIS M 623 071 A01 03 ST30 111 lt gt BIS M 62 MANUAL Edit HO Parameters 63 Cobalt DH Gateway Strobed Change of State Cyclic Input Size Butes 3 e Input Size mw Polled Output Size Input Size 20 71 Bytes Heartbeat Rate Output Size 20 Bytes Poll Rate Every Scan Cancel Restore lO Sizes Figure 61 Editing the Controller s DeviceNet I O Parameters The follo
50. ER and an INPUT Buffer that is controlled by the slave the Controller The OUTPUT Buffer is mapped the following way Output Buffer OUTPUT BUFFER CONTROL BYTE 0BCB Always 0 Packet Length in Bytes Packet Bytes Command AN Byte 0 is the Output Buffer Control Byte The Master uses the lowest two bits of this byte for handshaking to signal that a command is ready for the slave Bit 1 and to acknowledge receiving a response from the slave Bit 0 OUTPUT BUFFER CONTROL BYTE 7 6 5 4 3 2 1 0 1 0 0 0 0 0 0 0 Bit 0 is toggled by the Master to acknowledge a packet response from the RFID Controller Bit 1 is toggled by the Master when it has a packet command ready for the RFID Controller Bit 2 is set when the Master wishes to initiate a Resynchronization with the Slave and then cleared when it sees the corresponding handshake from the Slave indicating that the resynchronization is complete Bit 3 is set by the Slave when the total CBx response being returned to the Master is larger than the space available in the Input Buffer or that the packet being returned is a fragment and that there are more fragments to follow This bit is cleared for the final fragment of a fragmented response and so the Master can know when all the fragments of a response have been returned from the Slave 174 PROFINET INTERFACE lt gt Bit 7 is always 1 to conform to Balluff s proprietary Protocol Byte 1
51. Input Only This instance allows clients to monitor input data without providing output data Common Services Service Implementation Service Name Code Class Level Instance Level 0x0E Yes Yes Let Attribute Single 0x10 No es Set Attribute Single 87 O BIS M 62_ MANUAL Connection Manager Object 0x06 This object has no attributes TCP Object OxF5 1 Instance Class Attributes Data Default Access Rule Type Attribute ID Name Description Data Default Attribute ID Name Description T ype 2 Configuration Capability DWORD Configuration Control DWORD Physical Link Object Structure of Ser Se Array Of 0x20F6 WORD 0x2401 a gt Interface Configuration Structure of IP Address UDINT Network Mask UDINT Gateway Address UDINT Name Server UDINT Name Server 2 UDINT Domain Name Size UINT Domain Name STRING Host Name Structure of Host Name Size UINT Host Name STRING See section 5 3 2 2 1 5 3 2 2 6 of Volume 2 EtherNet IP Adaptation of CIP from ODVA for more information regarding these attributes Common Services Service Implementation Service Name Code Class Level Instance Level Get Attribute Single 88 ETHERNET IP INTERFACE O Ethernet Link Object 0xF6 1 Instance Class Attributes Default Attribute ID Name Description Data Type Data Access Rule Value 1 Revision SINT Instance Attributes Default en Attribute ID Name
52. OM STATUS OP MODE READY RF COM NET STATUS MODE STATUS LINK 1 LINK 2 JE lf u AN 0 Z The features given are typical at a 25 C ambient temperature if not otherwise indicated h 78 11 2 BIS M 37 ANTENNAS RADIO FEATURES Frequency Input Impedance Gain A BIS M 370 000 A02 BIS M 371 000 A01 BIS M 372 000 A01 BIS M 373 000 A01 Conducted Input Power ENVIRONMENTAL FEATURES Operating Temperature 20 to 50 C 4 to 122 F Storage Temperature 20 to 70 C 4 to 158 F Humidity max 90 non condensing Protection Class EN 60529 IP65 when correctly mounted PHYSICAL FEATURES BISM 370 000 A02 S BISM 371 000 A S BISM 372 000 A S BISM 373 000 A1 S AA ESAS The BIS M 62_ Processor units and its antenna are intended for indoor use only 179 E uuww balluff com Balluff GmbH SchurwaldstraBe 9 13765 Neuhausen a d F Germany Phone 49 7158 173 0 Fax 49 7158 5010 balluff balluff de E www balluff com Nr 896 712 E Edition 1307 Subject to modification
53. Overall Length holding register of Device ID 01 Node Input Page 01 setting it back the default value of zero 0x0000 101 O BIS M 62_ MANUAL 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 Node Input Page 4 After the BIS M 626 executes its given command instructions it will write the command response to the holding registers for Device ID 33 Node Output Page 33 Again the Overall Length value is written last to holding register 40001 Host bound data is always written to Device ID 33 Node Output Page 33 5 With holding register 40001 of Device ID 33 Node Output Page 33 now containing a non zero length value the BIS M 626 will enable change from zero to 1 the first bit in the Output Data Ready Mask The first bit is allocated to Node Output Page 33 6 Once bit 01 in the Output Data Ready Mask becomes enabled the host retrieves the data string stored in the holding register area for Device ID 33 Node Output Page 33 7 After importing the data from Device ID 33 Node Output Page 33 the host clears sets back to 0x0000 the Overall Length value at holding register 40001 of Device ID 33 Node Output Page 33 In doing so bit 01 in the Output Data Ready Mask is also c
54. RSNetWorx software File Edit View Network Device Diagnostics Tools Help aS H amp g h QIER Fr NER x 1756 DNB A ang DeviceNet HU Category General Module Scanlist Input Output ADR Summary J AC Drive TJ Barcode Scanner CT Communication Adapter 9 1756 DNB A FJ DPI to DeviceNet 00 ae mn FJ DSI to DeviceNet ame DeviceNet Safety Scanner CT DeviceNet to SCANport Scanner Configuration Applet Dodge EZLINK j 7 General Purpose Discrete I O e y Do you want to upload the configuration from the device updating the software s configuration or download the software s configuration to G ic Devi 5 z pe er Ben the device updating the device FJ Human Machine Interface TT Inductive Proximity Switch For more information press F1 T 1 Limit Switch TJ Motor Overload 5 dejos Po Upload Download otoelectric Sensor FJ PointBus Motor Starter J Residual Gas Analyzer Device 1756 DNB A 14 FJ Rockwell Automation miscellan CT SCANport Adapter Catalog N 736 DNB A TJ Safety Discrete UO Device Revision 6 002 FJ Smart MCC C Specialty I O OK Cancel Help FJ ATI Industrial Automation Carcel f J AquaSensors d d i D A S D Figure 60 Updating Configuration in RSNetWorx 110 DEVICENET INTERFACE Le 29 1756 DNB A ak General Module Scanlist Input Output ADR Summary Available
55. Response Data Response Data Response Data Response Data 31 82 Data Consistency Byte OBDCB Data Consistency Byte IBDCB 148 PROFIBUS INTERFACE Now the Slave places the final fragment into the Input Buffer and toggles Bit 0 of the IBCB 4 IBDCB to indicate the new fragment is ready Since it is the final fragment the Slave also now clears Bit 3 of the IBCB amp IBDCB See the Green changes below Output Buffer Input Buffer nn KO Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 82 7 6 5 4 3 83 7 6 5 4 3 2 1 0 EO ONO MR RR NE Si JG A UP LG NAT I 02 100 1 Packet length in bytes 02 196 1 Packet length in bytes _ a Command word an MSB Response CBx Command word length LSB Response Minimum of 6 words Response CBx Command Type Always AA Response CBx Command Opcode Response 0x05 Read Tag Data Response CBx Command byte not used CBx Command Node 1D CBx Command Timeout MSB CBx Command Timeout LSB OxE8 1000 ms timeout CBx Command Start Address MSB CBx Command Start Address LSB address 0 CBx Command Length MSB CBx Command Length LSB 50 bytes 31 182 Data Consistency Byte OBDCB Data Consistency Byte IBDCB 149 BIS M 62 MANUAL And lastly the Master acknowledges receipt of the final fragment by toggling Bit 0 of its OBCB amp OBDCB See the Green changes below Output Buffer Input Buffer Be
56. S M 62 MANUAL 2 6 5 Installing the BIS M 622 070 A01 03 ST33 Profibus PBS ES IM es 8 U LO BIS M 622 070 w antenna O a a BCCO6ZF s Setz wm ew w 3 T O O to Configuration PC to Configuration PC to Configuration PC 2 to Power Supply PBS IN PBS OUT PBS IN PBS OUT PBS IN PBS OUT PBS IN Profibus Terminator Cap to Profibus Master 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 compatible cables directly to a Profibus Master host The default Node ID is 63 1 2 46 Select a suitable location for the BIS M 622 Processor unit Antenna Mount the BIS M 37 antenna to the BIS M 622 Processor unit either directly or remotely as described in par 2 2 Mount the processor unit and antenna to your mounting fixture using M5 or 10 diameter screws not included and secure them with appropriate washers and nuts Tighten screws to 1 7 Nm or 15 Ibs per inch 10 Attach Profibus compatible data cables to the 5 pin B Coded reverse keyed male and female M12 interface connectors on the BIS M 622_ Connect the other end of the cables to your Profibus network Build a power supply cable using the BCCO6ZF M12 5 pin female connector Use minimum 24 AWG wires for connection to the power supply lines according to the Vdc connecto
57. TL IND v1 0 A En Industrial Ethernet RFID Control Network Status MAC Address 00 40 9D 26 D9 70 OnDemand Status Revision 1 27 Link Duplex FULL Link Speed 100 MBPS OnDemand Config Figure 55 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 A web we P tn TT A A A A tt RR TT RA LT TT A AE af wf RR eT A an Metwork Settings IP Address 192 168 253 110 Subnet Mask 255 255 255 0 Gateway IP Address 0 000 ee NT HE u The IP Configuration Page will be displayed 104 STANDARD TCP IP INTERFACE O 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 IP Configuration IF Address 92 168 253 110 Subnet Wlask 255 955 255 0 rateway IP Address 0 0 0 0 save Settings Cancel Changes The unit resets automatically when seffings are modified Man Page Figure 56 The IP Configuration Page In the fields provided enter your new IP configuration values for the BIS M 626 Click the Save Settings button to store your new IP configuration The BIS M 626 will completely reset and your IP changes will be implemented 7 After the BIS M 626 has restarted verify the new IP configuration by opening a Web browser and manually ent
58. Tag Name Hame Le 7e _ Mol fico Bb EMS WRITE WRITE _ foo Jee EMS READ READ PA Write Size Enter a value between 1 and 100 yee O to aia for the Write Size The Write Size represents the maximum number of 2 byte words that the BIS M 626 will attempt to write to PLC memory during a single write cycle Note to accommodate message handshaking overhead the actual data size required by the PLC is three words larger than the value specified in this field Write Tag Name For Contro Logix systems specify a Write Tag Name that is 40 characters or less for example EMS WRITE1 for Node 01 The Write Tag Name is a user defined description or title for the area of memory in the PLC where host bound data will be written for the BIS M 626 Note the Write Tag Name is not to be confused with writing to an RFID transponder which IS often referred to as writing to a tag OR Write Tag Name For PLC5E SLC5 05 and MicroLogix systems enter the PCCC File Number and Offset for example N7 0 in the Write Tag Name field Together these values identify the location in the PLC s Status File where host bound data will be written for the BIS M 626 Read Size Enter a value between 1 and 100 or 0 to disable for the Read Size The Read Size represents the maximum number of 2 byte words that the BIS M 626 will attempt to retrieve from PLC memory during a single read cycle Note to accommodate message handshaking overhe
59. ability to write time stamps to RFID tags e The ability to filter command responses to only those of interest to the host such as when an error occurs or when a tag has arrived in the FF field e The ability to harness powerful logic and triggering capabilities such as read write start stop continuous read data compare branch transmit custom string and set outputs 65 o BIS M 62 MANUAL What is a macro trigger Macros are initiated by triggers Triggers can be configured in numerous ways simple command from the host such as execute macro number three can be considered a trigger 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 How are macros created Macros are created using the powerful yet simple C Macro Builder M Configuration Tool from Balluff The easy to use GUI allows the user to create powerful RFID macro programs quickly and easily When used with Balluff Dashboard Configuration Tool users can effortlessly download erase and manage their macros and triggers as well as set the operational configurations of their RFID processor units and Subnet16 Gateways 66 CONFIGURATION METHODS O Which communication interfaces support the use of macro
60. ach Processor unit to tighten the screws to 1 7 Nm or 15 los per inch 10 3 Fasten the combined processor unit and antenna to your mounting fixture using M5 or 10 diameter screws not included Pass the screws through the antenna s mounting holes and the processor unit bracket and secure them with appropriate washers and nuts Tighten screws to 1 7 Nm or 15 lbs per inch 10 To complete the installation refer to the specific procedure for your Processor unit under par 2 6 25 lt gt BIS M 62 MANUAL 2 2 2 Remote Antenna Mounting Using BIS M 500 PVC 07 A01 02 Extension Cable Processor unit Adapter Mounting Screws M5 x 20 mm and Washers M5 included in BIS M 62 packaae Antenna Adapter Mounting Screws M5 x 35 mm included in BIS M 370_ package Antenna Adapter Mounting Washers and Nuts M5 included in Extension Antenna Adapter Mounting Screws M5 x 25 mm are include in the Extension Cable Cable package 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 d You can use the 4 mm hex key wrench supplied with each Processor unit to tighten all screws to 1 7 Nm or 15 Ibs per inch 10 NOTE 26 INSTALLATION gt 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 u
61. acro BuilderTM For specific information regarding the configuration and use of elther of these utilities please see the accompanying documentation included when NOTE downloading each software application 68 CONFIGURATION METHODS O 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 Ethernet IP Profinet etc To determine which command protocol to utilize please refer to the list below for the different BIS M 62_ devices CBx Protocol e BIS M 62_ Fieldbus and Non Fieldbus models Industrial Ethernet BIS M 626 IND DeviceNet BIS M 623 DNT Profibus BIS M 622 PBS Profinet BIS M 628 PNT ABx Protocol Fast and Standard e BIS M 620_ Serial models RS232 All RS485 based RFID processor units are used in conjunction with Subnet16 Gateway and Subnet16 Hub interface modules which all use NOTE the CBx Command Protocol Refer to the specific Command Protocol Reference Manual for details 69 gt BIS M 62 MANUAL 70 ETHERNET IP INTERFACE O 5 ETHERNET IP INTERFACE d For BIS M 626 069 A01 06 ST3 models NOTE e Users of the Balluff Dashboard Configuration Tool should exit the application before attempting communications between the Industrial BIS M 626 and an EtherNet IP host Programmable Log
62. ad the actual data size required by the PLC is three words larger than the value specified in this field Read Tag Name For Contro Logix systems specify a Read Tag Name that is 40 characters or less for example EMS READ1 for Node 01 The Read Tag Name is a user defined description or title for the area of memory in the PLC from which the BIS M 626 will retrieve data OR Read Tag Name For PLC5E SLC5 05 and MicroLogix systems enter the PCCC File Number and Offset in the Read Tag Name field Together these values indicate the location in the PLC s Status File from which the BIS M 626 will retrieve data After entering the proper information for Node 01 click the Save Settings button located at the bottom of the page ETHERNET IP INTERFACE O DEWE Setipas Cancel Changes Man Page 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 OnDemand Status Man Page PLC Read TCP Status Disconnected PLC Write TCP Status Disconnected NODE READCOUNTS READSTATUS WRITE COUNTS WRITE STATUS oo OO OOOO O Ir Tun lc o e aer cl ri A A A ae ee MA eee A TE gee oe AAA A PS ee ne he E E 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 RSLogix 5000 and if you have not already done so define two C
63. and CompactLogix and the PCCE File Number and offset i e N7 C0 for the PLCSE SLCS 05 and MicroLogix Enable Node Hode WEE Size mtr Tag Name E Size ae Taq Name Bes e E de e ee e ap 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 OnDemand Configuration ees en el PLC Type PLC IP address MERHIG NEUENS Lontrollogi PLC Slot Number 5LC5 05 or MicroLogix PLESE Read Delay 0 ll0ms ticks 0 6000 E A TN TT TT mm TA on E en aen Ae EE E TT vn rn ME ms n EE NE NE AAA gt Figure 50 The OnDemand Configuration Page 4 Enter the PLC s IP address 77 O BIS M 62 MANUAL 78 5 10 11 12 NE me ET me menn A 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 O for ControlLogix 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 Note a value of 6000 60 seconds zero disable In the column labeled Enable Node place a check in the box for Node 01 Other Nodes listed on this en are not ern Dy the BIS M 626 IND i Taia A A eil ee an et tn MER Hode dee Size 1 tL Write Tag Name CE Size Read Read
64. and Data Byte CBx Command Data Byte CBx Command Data Byte CBx Command Data Byte CBx Command Data Byte CBx Command Data Byte CBx Command Data Byte ee ee Data Consistency Byte OBDCB 31 180 Data Consistency Byte IBDCB 151 BIS M 62_ MANUAL 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 amp OBDCB to 1 This bit is what tells the Slave to wait for further fragments before processing the command See the Green changes below Output Buffer Input Buffer mn ae te Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 7 6 5 4 3 2 il 0 AO KE KM CI o2 ic tracker Length in bytes v r fo Command word Tenth MSB CBx Command word length LSB CBx Command Type Always AA CBx Command Opcode 0x06 Write Tag Data CBx Command byte not used CBx Command Node ID CBx Command Timeout MSB CBx Command Timeout LSB OxE8 1000 ms timeout CBx Command Start Address MSB CBx Command Start Address LSB address 0 CBx Command Length MSB CBx Command Length LSB 50 bytes Command Data Byte Command Data Byte Command Data Byte Command Data Byte Command Data Byte Command Data Byte Command Data Byte Command Data Byte Com
65. and Length MSB Response CBx Command Length LSB Response 50 bytes Response Response Response Response Response Response Response Response Response Response Response Response 31 183 Data Consistency Byte OBDCB Er hen Data Consistency Byte IBDCB 147 BIS M 62 MANUAL Now the Master acknowledges this fragment by toggling Bit 0 of the OBCB amp OBDCB It knows that this is still not the last fragment of the response since Bit 3 of the IBCB amp IBDCB is still set to 1 See the Green changes below Output Buffer Input Buffer EIERE Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 5 4 3 2 5 4 3 KO SS Command word an MSB Response Data CBx Command word length LSB gt Response Data Minimum of 6 words Response Data CBx Command Type Always AA Response Data CBx Command Opcode Response Data 0x05 Read Tag Data E Response Data CBx Command byte not used Response Data CBx Command Node ID Response Data CBx Command Timeout MSB Response Data CBx Command Timeout LSB Response Data OxE8 1000 ms timeout Response Data CBx Command Start Address MSB Response Data CBx Command Start Address LSB d Response Data address 0 Response Data CBx Command Length MSB Response Data CBx Command Length LSB Response Data 50 bytes Response Data Response Data Response Data Response Data Response Data Response Data Response Data Response Data
66. ata Signal Ground o JO OD P OD AR 35 gt 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 na RX PIN 1 TX PIN 3 TX PIN 2 RX Figure 23 M12 4 pin D Coded Female Connector for Profinet Function Transmit Data positive Receive Data positive Transmit Data negative Receive Data negative The Profinet models are powered through their VDC power connector M12 5 pin Male PIN 4 PIN 5 N C PIN 2 VDC N C Not Connected Figure 24 M12 5 pin Male Connector for Power Supply Function Input Power Power Ground 36 INSTALLATION gt The RS232 Connector M12 8 pin Male on the PROFINET models is used for connecting the processor unit to a portable PC for configuration PIN 5 N C PIN 4 N C PIN 3 N C N C N C Not Connected Figure 25 M12 8 pin Male Connector RS232 Function 3 Receive Data Transmit Data Signal Ground o JO MB WII 37 gt BIS M 62_ MANUAL 2 3 7 Digital I O 12 models The Digital 1 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 PIN 6 PIN 7 PIN 2 O1 GND Figure 26 M12 8 pin Female Connector Digital I O H 5 Function Power from the Processor unit to the I O
67. bnet16 Bus Ground TX RX Receive Transmit Data positive TX RX Receive Transmit Data negative 30 INSTALLATION gt 2 3 3 Industrial Ethernet IP 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 RX PIN 1 TX PIN 3 TX PIN 2 RX Figure 15 M12 4 pin D Coded Female Connector for Ethernet Function Transmit Data positive Receive Data positive Transmit Data negative Receive Data negative The Industrial Ethernet models are powered through their VDC power connector M12 5 pin Male N C Not Connected Figure 16 M12 5 pin Male Connector for Power Supply Function Input Power Power Ground 31 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 5 CAN L PIN 3 V PIN 1 SHIELD PIN 2 Function DeviceNet Bus Shield DeviceNet Bus Power DeviceNet Bus Ground Data positive Data negative 32 INSTALLATION gt 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 00 NOORA ON fv 5 PIN 5 N C PIN 4 N C PIN 3 N C N C N C Not Connected Figure 18 M12 8 pin Male Connector RS232 F
68. can exchange I1A with 11B without affecting the system behaviour The user can handle the input through specific commands see par 2 7 3 for the specific Command Protocol Reference Manual according to your processor unit model The electrical features of the input are Maximum voltage 30 Vdc Minimum voltage 6 Vdc Maximum current 28 mA The input is optocoupled and can be driven by both an NPN and PNP type command 50 INSTALLATION gt Input Connections Using Processor unit Power Controller Controller Figure 34 NPN External Trigger Using Processor unit Power Input Connections Using External Power Vuser 6 30 Vdc 4 GNDuser Controller Figure 35 PNP External Trigger Using External Power 51 lt gt BIS M 62 MANUAL Vuser Controller GNDuser 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 When connected to an external circuit the current must enter in 01 02 and exit from O1 02 The electrical features of the outputs are Voltage Range 6 30 Vdc Maximum Current If externally powered by the user 500 mA If powered by the Proc
69. ce 0x65 Attributes Input Instance 2 Attribute Default Data Access ID Name Description Data Type Value Rule Serial Produce Data Consume Data Seq Number Handshake aul Produce Data Sequence UINT Number Node 1 Serial Produce Data UINT Size Node 1 Serial Produce Data WORDI100 All O s 86 ETHERNET IP INTERFACE Instance 0x66 Attributes Input Instance 3 Default Name Description Data Type Data Value Attribute Access Rule Serial Produce Data Consume Data Seq Number Handshake en o Produce Data Sequence Number UINT 10 Geet Node Serial Produce Data Size UINT ___0O Instance 0x70 Attributes Output Instance 1 Attribute Default Name Description Data Type Data Serial Consume Data Produce Data Seq Number UINT e Handshake Get Set Consume Data Sequence Number UINT HO Node 1 Serial Consume Data Size UINT o Node 1 Serial Consume Data WORD 100 All O s Instance 0x71 Attributes Output Instance 2 une Default Name Description Data Type Data Serial Consume Data 0 Consume Data a er CJ Handshake Consume Data Sequence Number UINT O Get Set Node ID 1 32 JUN 4 gt Node Serial Consume Data Size UNI 10 gt Instance 0x80 Attributes Configuration Instance Most I O clients include a configuration path when opening an I O connection to a server There is no configuration data needed Instance 0x81 Attributes Heartbeat Instance
70. ce Level 0x0E Yes Ves Get Attribute Single 0x05 No ie Reset 85 BIS M 62_ MANUAL Message Router Object 0x02 This object has no supported attributes Assembly Object 0x04 3 Instances Class Attributes Data DIEU Access Attribute ID Name Description Data Type Value Rule EEE 20 UINT UINT Instance 0x64 Attributes Input Instance 0 Default er Data Access Attribute ID Name Description Type ata Rule Status Information Bitmap of Consume Instances with Data DINT O Get Bitmap of Produce Instances with Data DINT 0 User Datagram Protocol UDP I O Sequence Number Handshaking The data producing device increments the data sequence number by one with the transmission of each new serial data packet Valid sequence numbers are 1 65535 After the consuming device has processed the data it must echo the sequence number in the handshake to allow the producing device to remove the data from the queue This is required for I O communications because UDP is not guaranteed to arrive in order If the Node ID number is passed as part of the I O message the message is stored to the appropriate location in the Modbus RTU table Because communications are asynchronous the Node ID number is also stored as part of the output data lt is the responsibility of the PLC programmer to make sure the proper request lines up with the proper response if the BIS M 626 is used as a request response device Instan
71. cesl rer ren rr ror r norra 92 MODBUS TCP INTERFACE inisi ainiai aa aiaa aaa era aa aani a 95 MOADUS TOP NENNE 95 Modbus TCP Configuration via HTTP Gener rer rrr nr rr nr nns 95 Modbus TCP Command Packet Structure ooccccocccccccnccncnncnoncnoncnonannnonnnnnonencnnnnonos 98 Modbus TCP Response Packet Giruchure ren r rr ror n na 98 Modbus TCP Mapping for Node 272 99 Modbus TCP Handshaking sosossrssressessrssresrerreorrerrenrrrrrrnrrrr rar rrrr rer rank rn rr rn R KR RAR K nan nn 100 Modbus TCP Host BIS M 626 Handshaking n nnnennnennnsnnnennnennnrnserreerrrerrresnnne 101 Modbus TCP Handshaking Example ccooccccccccocccccnccncnconcccncncnncononnnonnnnncnonanonos 101 STANDARD TCP IP INTERFACE u u u une a 103 8 2 5 10 4 1 10 4 2 10 4 3 10 4 4 10 4 5 10 5 11 11 1 11 2 Standard TCP IP Overview ranrararsnnrannoransenonennnnrnrnnvevnnnnnennvennnnenevevnensnenevennenenennven 103 Standard TCP IP IP Configuration via HTTP Gener reor nro rna 103 Standard TCP IP Command Response Evamples sssmrrssrersrerrrerrrrerrrrnrrnrrrnrr norra 106 Standard TCP IP Command Structure Example oocccoccccccnccccncocncocnnoncnccnnncncnnnnos 107 Standard TCP IP Response Structure Evample ssmsmssssssresserrresrrrrrrerrrrrinr rer rrn reor nana 107 DEVIGENET INTERFACE cuina 108 DeviceNet Ove Me eben 108 DEVICENE GON GUAN are 108 Importing the Controller EDS Files nireti a a 108 Configuring Controlle
72. controller SE Controller Tags SAMPLE_435NBA controller Scope SAMPLE_435NBA c D Show Show All y Sort Tag Name D Scope SAMPLE 435NBA c x Show Show All y Sort Tag Name Tag Name H Value Force Mask Style Type ForceMask amp __ EMS_READI TE Hex INTI2 TWA LI 5000 Hes A 16 0004 MS READ 16 0004 EMS_WRITE1 1 16 0005 EMS_READ1 2 1640006 EMS WRITE1 2 1640000 EMS_READ1 3 16 2a07 EMS_WRITE1 3 16 0000 EMS_READ1 4 16 0001 EMS_WRITE1 4 16 0000 EMS_READ1 5 16 07d0 EMS_WRITE1 5 16 0000 EMS_READ1 6 16 0000 EMS_WRITE1 6 1640000 EMS_READ1 7 1640000 EMS_WRITE1 7 1640000 EMS Bang 1640000 EMS_WRITE1 8 1640000 3 Following execution of the command the BIS M 626 copies the response to EMS WRITE1 the Write Tag and increments the counter in EMS_WRITE1 1 This signals that there is new data for the PLC the BIS M 626 generated response in this case Controller Tags SAMPLE_435NBA controller AE _ Controller Tags SAMPLE_435NBA controller Scope SAMPLE 435NBA c y Show Show All y Sort Tag Name y Scope SAMPLE 435NBA c D Show Show All Sort Tag Name Tag Name e Value Force Mask Style Type Force Mask EMS_READ1 SE Hex nt gt EMS WRITE1 l E EMS_READ1 0 16 0005 Hex INT EMS_WRITE1 0 16 0005 D EMS READ1 1 1640005 Hex INT EMS_WRITE1 1 EMS_READ1 2 1640006 Hex INT EMS WRITE1 2 1
73. d Then one of the Ethernet IP Address LEDs will remain on either Default or Custom To verify operations download the Balluff Dashboard Configuration Tool from www balluff com The Balluff Dashboard M 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 44 INSTALLATION gt 2 6 4 Installing the BIS M 623 071 A01 03 5 DeviceNet DNT BIS M 623 071 w antenna BIS M 623 071 w antenna 5 2 gt a e Vdc GND E a a e to Power 2 g 9 Supply 5 2 w D 2 a 5 E 5 2 E O O O O gt 3 it 2 BCCO7WR iT 2 Se ge 3 gt 3 IESSE TI O D m Oo m gt zZ LL m gt BCCO6ZF a D ODO TACA e E O SIS E gt JE O Si JE Q 7 m I zur 2 BCCOETO 8 BCCOETO Wl lin Teneste S fr BCCO7WR BCCO7WR BCCO7WR Figure 30 DNT Typical Layouts The BIS M 623 071 A01 03 5 Processor unit is designed for DeviceNet RFID applications where the processor unit is connected as a slave node in a DeviceNet network via compatible cables directly to a DeviceNet Master Scanner host The default Node ID is 63 1 Select a suitable location for the BIS M 623_ Processor unit Antenna 2 Mount the BIS M 37 antenna to the BIS M 623 Processor unit either directly or remotely as described in par 2 2 3 Mount the processor unit and antenna to your mounting fixture using M5 or
74. d by the Balluff HTTP Server and OnDemand Utilities e ControlLogix OnDemand supports all current versions e RA s PLC5E releases e Series C Revision N 1 e Series D Revision E 1 e Series E Revision Di e PLC5 Sidecar Module Series B Revision A with EIP support e SLC5 05 releases e Series A with firmware revision OS501 FRN5 e All Series B and Series C PLC Controllers 72 ETHERNET IP INTERFACE O 5 3 HTTP SERVER AND ONDEMAND UTILITIES Embedded in the BIS M 626 069 A01 06 ST31 is an HTTP Server which provides a Website like interface and a suite of configuration tools Through the use of the BIS M 626 s HTTP Server users can access modify and save changes to the unit s Industrial Ethernet configuration IP address and OnDemand mode settings The OnDemand Utilities will be used later in this chapter to link the BIS M 626 to specific Controller Tags as defined in Rockwell Automation s RA ControlLogix PLC computer Firewalls can potentially block communications between the BIS AN Disable any firewall services affecting or running locally on the host M 626 and the host and or PLC CAUTION In ControlLogix a Controller Tag is a small block of internal memory that is used to hold outgoing command and incoming response data Within each controller tag information is stored in two byte segments known as registers or words OnDemand is the Balluff approach to adding Change of State messagi
75. d configuration using a PC It provides Serial RS232 or USB and Ethernet interface configuration C Macro Builder an easy to use GUl driven utility for Windows This software tool allows users with minimal programming experience to build their own macro programs which are stored internally on and executed directly by RFID Processors 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 ce POWER SUPPLY This product is intended to be installed by Qualified Personnel only This device is intended to be supplied by a UL Listed or CSA Certified Power Unit with Class 2 or LPS power source GENERAL VIEW RS232 Models Figure A HF Antenna Connector 4 COM LED 2 Ready LED 5 Mounting Bracket 3 RF LED 6 Host RS232 and Power Connector RS485 Models 4 Figure B HF Antenna Connector 4 COM LED 2 Ready LED 5 Mounting Bracket 3 RF LED 6 Host RS485 and Power Connector 7 Node ID LEDs IND Models Figure C ao HF Antenna Connector 5 Mounting Bracket 2 Ready LED 6 Power Connector 3 RF LED 7 Host Ethernet Connector 4 COM LED IP Address Status LEDs DNT Models Figure D 1 HF Antenna Co
76. dels LED Name LED Color LED Description READY E READY LED is ON after the power sequence has completed O Gar o u STATUS e GREEN RED OP MODE GREEN RED The RF LED illuminates when RF power is being transmitted by the antenna The COM communications LED flashes ON and OFF when data is being transmitted between the antenna and a tag When in Continuous Read mode the COM LED will remain ON and will turn OFF briefly only while data is being read from or written to a tag SOLID GREEN initialized FLASHING GREEN initialized diagnostic event s present SOLID RED exception error SOLID GREEN on line data exchange FLASHING GREEN on line but idle FLASHING RED 1 FLASH parametrization error FLASHING RED 2 FLASHES Profibus configuration error 59 HF SERIES REFERENCE MANUAL 3 1 6 BIS M 628 075 A01 03 ST34 PROFINET Models LED Name LED Color LED Description READY The READY LED is ON after the power up sequence has completed AMBER The RF LED illuminates when RF power is being transmitted by the antenna The COM communications LED flashes ON and OFF when data is being transmitted between the antenna and a tag een When in Continuous Read mode the COM LED will remain ON and will turn OFF briefly only while data is being read from or written to a tag SOLID GREEN initialized Normal Operation FLASHING GREEN 1 FLASH diagnostic event s present FLASHING GREEN 2 FLASHES
77. displays an example of the data contained in the two I O Controller Tags for the Controller f RSLogix 5000 CL in Combined Diet EIP Demo ACD 1756 L1 File Edit View Search Logic Communications Tools Window Help ajaja S eje gt gt I 3ss amp je f a SA No Forces gt ee OK tt K en lan ln NoEdts A non al Bleu EA KOR KG H 4 gt Favorites ABR Timer Counter deit Compare 3 3 Controller CL Controller Tags CL controller 8 fa x Controller Tags Scope Cu controller y Show Show All T Sort E Name I Controller Fault Handler CO Power Up Handler nme Value Force Mack JSwe Lues JDesciprel 5 6 Tasks wea A e 23 Maintask EE EE es EER MainProgram KE SES mmm 16 004 _0050 Hex ONT Unscheduled Programs Hex INT E Trends Her a OJ Eiloost2idatste 168000 Hex E Ep Predefined Controller SS CL controller i D x Or Module Defined 5 6 10 Configuration 2 EEE B 1 1756 ENGTIA ENST A A es e B t211756 008 Devicenet fa A Jais TA Th rner Y EEE PA I Ei I Fardal en He num El ied bnag EAT Her DINT Local 2 0 Data 1 l aa05 0006 Hex DINT H Local 2 0 Data 2 16 0352_0001 Hex DINT FH Locat 2 0 Data 3 16 000a_0000 Hex DINT Local 2 0 Data 4 16 0000 0000 Hex DINT Local 2 0 Data 5 16 0000 0000 Hex DINT Local 2 0 Data 6 16 0000 0000 Hex DINT H Local 2 0 Dataf 7 16 0000 0000 Hex DINT
78. e OnDemand Status 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 Metwork Settings IP Address 192 168 253 110 Subnet Mask 255 259 255 0 Gateway IP Address 0 000 A A EM TA A AA A AAA The IP Configuration Page will be displayed 96 MODBUS TCP INTERFACE O IP Configuration Page The P Configuration Page is used to modify and save changes to the IP Address Subnet Mask and Network Gateway IP Address IP Configuration IP Address 92 168 253 110 Subnet Wlask 255 955 255 0 rateway IP Address 0 0 0 0 save Settings Cancel Changes The unit resets automatically when seffings are modified Man Page Figure 54 The IP Configuration Page 5 Inthe fields provided enter your new IP configuration values for the BIS M 626_ 6 Click the Save Settings button to store your new IP configuration then cycle power to the controller to store the changes in the main memory The Ethernet module will reset and your IP changes will be implemented 7 After the BIS M 626_ has restarted verify the new IP configuration by opening a Web browser and manually entering the BIS M 626_ s new IP address in the URL field If successful you should arrive back at the HTTP Server Main Page 97 BIS M 62_ MANUAL 6 2
79. e TED EMS READE 1 E40000 IT z EMS WRITE TE l snond EMS READ 1640000 EMS WFITE1 7 EMS READS 1640000 EMS WFITE1 8 EMS READS 1640000 EMS WRITES I EMS READ celal EMS WRITE TiO 140000 EMS READIN 16 e H EMS El 1E40000 EMS READ 16400 o i EMS WRITE 11 1840000 H Fal H Al H 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 ETHERNET IP OBJECT MODEL The Object Model is the logical organization of attributes parameters within classes objects and services supported by each device Objects are broken down into three categories Required Objects Vendor Specific Objects and Application Objects e Required Objects are classes that must be supported by all devices on EtherNet IP The BIS M 626 has six Required Objects e Vendor Specific Objects are classes that add attributes and services that do not fit into the Required Objects or Application Objects categories The BIS M 626 has two Vendor Specific Objects e Application Objects are classes that must be supported by all devices using the same profile An example of a profile is a Discrete I O device or an AC Drive This ensures that all devices with the same profile have a common look on the network Data Type Definition Table EtherNet IP was designed by the Open Device Vendors Association ODVA as an open protocol The following table conta
80. e Timestamp Month Command Not Used Response Timestamp Day Command Not Used Response Timestamp Hour Command Not Used Response Timestamp Minute Command Not Used Response Timestamp Second Response Data length 1 byte the Error Code CBx Response Data Byte 1 Error Code 7 Tag Not Found CBx Response byte not used 31 183 Data Consistency Byte OBDCB Data Consistency Byte IBDCB The command response sequence has completed A command has been issued and the response received in this case a Tag Not Found error and the response has been acknowledged 133 BIS M 62_ MANUAL 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 amp OBDCB again See the Green changes below Output Buffer Input Buffer eee m Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB Command word SE MSB a Response word an MSB Command word length LSB CBx Response word length LSB Command Type Minimum of 6 words Command Opcode Response Type FF Error Command byte not used Response Opcode FF Error Command Node 1D Response Instance Counter Command Timeout MSB Response Node ID Command Timeout LSB Response Timestamp Month Command Not Used Response Timestamp Day Command Not Used Response Timestamp Hour Command Not Used Response Timestamp Minute Command Not Used Response Timestamp Second Response
81. e are made the same changes must also be made in the Data Consistency Byte before the changes take effect This Is to guarantee the validity of the data between the two bytes The INPUT Buffer is controlled by the Slave BIS M 622 RFID Processor unit and is mapped the same way except for the packet bytes containing a response or response fragment from the processor unit Input Buffer 00 INPUT BUFFER CONTROL BYTE IRGB Always 0 Packet Length in Bytes Packet Bytes Response Byte 0 is the Input Buffer Control Byte The Slave uses the lowest four bits of this byte for handshaking to acknowledge receiving a command from the master Bit 1 and to signal that a response is ready for the master Bit 0 INPUT BUFFER CONTROL BYTE 7 6 5 4 3 2 1 0 1 0 0 0 0 0 0 0 Bit 0 is toggled by the Slave when it has a new packet response or response fragment ready for the Master Bit 1 is toggled by the Slave to acknowledge a packet command or command fragment from the Master 127 O BIS M 62 MANUAL Bit 2 is set by the Slave after it completes resynchronization and then cleared once the Master has acknowledged that resynchronization is complete Bit 3 is set by the Slave when the total CBx response being returned to the Master is larger than the space available in the Input Buffer or that the packet being returned is a fragment and that there are more fragments to follow This bit is cleared f
82. e at www balluff com 11 gt BIS M 62_ MANUAL 1 3 1 Who Should Read This Manual This manual should be read by those who will be installing configuring and operating the Processor units This may include the following people e Hardware Installers e System Integrators e Project Managers e IT Personnel e System and Database Administrators e Software Application Engineers e Service and Maintenance Engineers 1 3 2 HEX Notation Throughout this manual numbers expressed in Hexadecimal notation are prefaced with Ox For example the number 10 in decimal is expressed as 0x0A in hexadecimal 1 4 MODELS AND ACCESSORIES Balluff designs manufactures and distributes a wide range of RFID equipment including Processor units network interface modules Gateways and Hubs RFID tags and the cables needed to make it all work 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 Subneti6 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 Name Description BISM 62_Processorunits S00ZK BIS M 623 071 A01 03 ST30 BIS M 62_ Processor units DeviceNet B BIS M 622 070 A01 03 ST33 BIS M 62 Processor units Profibus B BIS M 628 075 A01 03 ST34 BIS M 62 Processor units Profinet HF Series antennas
83. e data packet into pre defined holding registers within the Node Output Page Note that a single holding register stores 2 bytes or one word of data The 2 byte Overall Length value for example is written to the first holding register which is location 40001 of the Node Output Page Then as the BIS M 626_ finishes writing host bound data to the Node Output Page the Overall Length value stored at holding register 40001 will change from its default value of 0x00 to reflect the number of data words within the newly written host bound data packet This change to the Overall Length value i e register 40001 within the Node Output Page triggers the BIS M 626_ to enable change from zero to one bit one in the Output Data Ready Mask It is when bit one in the Output Data Ready Mask has become enabled that the host will recognize the pending data Finally after the host has retrieved its pending data the enabled bit in the Output Data Ready Mask and the Overall Length value at holding register 40001 of the Node Output 100 MODBUS TCP INTERFACE gt 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 For example for the host to issue the 6 word command Read Data it must first write
84. eldbus Programmable Logic Processor unit PLC or PC RFID processor unit s BIS M 41x BIS M 62x or BIS U 62x Series Processors 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 Installation Precautions RF performance and read write range can be negatively impacted by the proximity of metallic objects and liquids Avoid mounting the antenna within 15 cm 6 inches of any metallic object or wet surface Do not route cables near other unshielded cables or near wiring carrying high voltage or high current Cross cables at perpendicular intersections and avoid routing cables near motors and solenoids Avoid mounting the processor unit near sources of EMI electro magnetic interference or near devices that generate high ESD electro static discharge levels Always use adequate ESD prevention measures to dissipate potentially high voltages If electrical interference is encountered as indicated by a significant reduction in read write performance relocate the processor unit to an area free from potential sources of interference 41 BIS M 62_ MANUAL 2 6 TYPICAL LAYOUTS AND INSTALLATION PROCEDURES 2 6 1 Installing the BIS M 620 068 A01 00 S_ RS232 BIS M 620 068 w antenna BCCOETJ SDATALGGIC COBALT HF meg 0 o VDC
85. els then click Connect 63 oO BIS M 62 MANUAL COBALT DASHBOARD Industrial Identification RFID Connect To Device Type Dashboard Configuration Tool Version 4 0 0 Copyright Ci 2013 Balluff GmbH Figure 44 Balluff Dashboard COM Port and Baudrate Selection 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 M should now look something like this HH Cobalt Dashboard Device Network gt File Connect Options Tools View Help RFID Controller at Com2 9600 Baud Cobalt HF mm Configuration Read write Macros Triggers Multi T ag co Node Configuration Tag Type LAP S Series Me Continuous Start D Read on Reset fo 0 0 Tag Presence Detect I Include Tag IDs in Continuous Reads I Send Tag IDs LSB First I Use Legacy Error Code for Tag Search I Send Reduced Tag IDs I Multiple HMS LRP LAP S Mode I Serial Baud 9600 y Ready Wal a Figure 45 Balluff Dashboard HF RS232 Processor unit Configuration See the Balluff Dashboard M User s Manual for more configuration details 64 CONFIGURATION METHODS lt gt 4 2 2 Software Upgrades Using Balluff Dashboard The Balluff Dashboard Configuration Tool also allows for processor unit software upgrades For the BIS M 62_ Processor units software upgrades downg
86. els RS232 All RS485 based RFID Processor units are used in conjunction with Subnet16 Gateway and Subnet16 Hub interface modules which all use NOTE the CBx Command Protocol 56 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 READY READY LED is ON after the power E sequence has completed AMBER The RF LED illuminates when RF power is being transmitted by the antenna The COM communications LED flashes ON and OFF when data is being transmitted between the antenna and a tag AMBER When in Continuous Read mode the COM LED will remain ON and will turn OFF briefly only while data is being read from or written to a tag 3 1 2 BIS M 620 067 A01 04 RS485 Models LED Name LED Color LED Description READY h READY LED is ON after the power sequence has completed AMBER The RF LED illuminates when RF power is being transmitted by the antenna The COM communications LED flashes ON and OFF when data is being transmitted between the antenna and a tag AMBER When in Continuous Read mode the COM LED will remain ON and will turn OFF briefly only while data is being read from or written to a tag The five Node ID LEDs indicate in Binary from AMBER top to bottom the current Node ID value assigned to the controller 57 HF SERIES REFERENCE MANUAL 3 1 3 BIS M 626 069 A01 06 INDUSTRIAL Models LED Name LED Co
87. ering the BIS M 626 s new IP address in the URL field If successful you should arrive back at the HTTP Server Main Page 105 o BIS M 62_ MANUAL 7 3 STANDARD TCP IP COMMAND amp 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 amp response packets need an additional word at the beginning of the string Protocol Header OxFF in MSB Node ID gt in LSB Please notice that these two bytes are not considered part of the CBx command packet and should not be counted in the Overall Length Below is the structure of the additional word required named as Word 00 Word Command Packet Element MSB LSB Protocol Header in MSB OxFF And similarly for the response Word Response PACKET ELEMENT MSB LSB Protocol Header in MSB OxFF oo Node ID Echo in LSB lt Node ID Echo gt d These first two bytes will not be returned in the response packet for commands executed by Node 01 NOTE Therefore the command packet structure for Standard TCP IP applications is TCP IP Applications Command Packet Structure EE sr 2 e y Prof Header Additional Node ID Data Fun B A 7 3 Block Size Overall Read Write Length Length AA AR k A OxAA amp Start Command 1D Address Figure 57 Standard TCP IP Protocol Command Packet Structure 106
88. erned by the changing of the Overall Length value within a data packet The Overall Length value is typically the first word 2 bytes of a command or response and indicates the total number of data words in the packet Node Input and Node Output Pages Under the Modbus TCP protocol host generated data is written to a pre defined region of the BIS M 626_ s own memory known as the Node Input Page Host bound data generated by the BIS M 626_ is written to a separate region of the BIS M 626_ s memory known as the Node Output Page in Modbus TCP these regions of memory are called Device IDs Node Input and Node Output Pages are used to temporarily hold incoming controller bound and outgoing host bound data Output Data Ready Mask To notify the host that new data is waiting to be retrieved from the Node Output Page the BIS M 626 utilizes a separate 32 bit block of internal memory called the Output Data Ready Mask The first bit of the 32 bit Output Data Ready Mask represents the status of the Node Output Page For example the first or lowest bit bit 01 represents Node Output Page 33 which holds output data from Node 01 The BIS M 626 itself is assigned Node 01 and thus its corresponding Node Output Page is 33 As noted Node Output Page 33 is represented by the first bit b t 07 in the Output Data Ready Mask Holding Registers When writing host bound data to Node Output Page 33 the BIS M 626 actually places each byte of th
89. esareesteece 29 AND NN 30 HAUSTA BENENE aar 31 A en ehe 32 Erol 34 A EE 36 Digital OEM nee Male 38 Beie arc n 39 Power Heouirements ense rr rensar rr KKR RAR RAR RAR KKR KKR KKR KKR KKR KKR KKR KKR KKR KKR rna 39 Total System Current Consumption s sssnessressrrsrrrsrresrrerrresrren narr rss rr rr rr rr rr rr rr rr rn RR KORR none 39 Gable Voltage EE ebe ee ie 40 Curent die e Berl 40 INST lla leie eat 41 Hardware Requirements cooccoccoconoconoconoconocononononcnnonnnonononnnnnnnnnnnnnnnnnnnnnenanenanenanenanes 41 Installation Ge de cag rasende 41 Typical Layouts and Installation Procedures rrrrrrnnrrnnnrvnnvrnnnrrnnvrennrennrrnnnrernerennrenne 42 Installing the BIS M 620 068 A01 00 5 HG 42 Installing the BIS M 620 067 A1 04 5 HA 43 Installing the BIS M 626 069 A01 06 Industrial Ethernet IND 44 Installing the BIS M 623 071 A01 03 S_ DeviceNet ONT 45 Installing the BIS M 622 070 A01 03 ST33 Profibus DD 46 Installing the BIS M 628 075 A01 03 ST34 PROFINET PNT u u 48 Digital O12 models aar 50 Ile DE 50 AA een 52 Digtal VO Command CONO osas laos 56 EEDINDICATORS aaa ada 57 ROPE A er en 57 BIS M 620 068 A01 00 RS232 Models oocccccoccccccccnnococonoccncnnononcncnnnnncnnncnnnnonencnnns 57 BIS M 620 067 A01 04 RS485 Models oocccccoccccccccnnccoccncconcnnononcnononononnncnnnnonenonnos 57 BIS M 626 069 A01 06 INDUSTRIAL Model ornsrresssresssassarersarerrr
90. essor unit pins 1 and 2 of the I O connector max 300 mA This is the maximum value of current computed as the sum of both the Outputs In fact the output current supplied by the Processor unit is limited In other words if only one output is active the maximum current value is 300 mA but if both the outputs are active then each Output current must decrease for example max 150 mA for each Output Notes It should be noted that if the power supply for the I O is supplied by the Processor unit pins 1 and 2 the opto isolation feature for the Input and Output sections will be lost because the ground reference of the I O and the Processor unit power supply is the same A device that operates at 200 mA may damage the Digital Output due to inrush current if a current limiting device is not used and the current exceeds 500 mA e g an incandescent light The inductive kick that occurs when a relay is released back EMF from a collapsing magnetic field can impose a voltage higher than 30 Vdc that may damage the output transistor To avoid this potential issue employ a diode D1 to clamp the back EMF D1 should be a 1N4001 or equivalent 52 INSTALLATION gt 53 gt 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 Controller Figure 37 Open Emitter Sou
91. etwork type 120 PROFIBUS INTERFACE O 9 4 PROTOCOL IMPLEMENTATION 9 4 1 Definitions In the protocol description we ll use the following definitions e Input field is the set of master inputs that can be modified by the specific slave e Output field is the set of master outputs that can be read by the specific slave e MaxinBytes is the number of input bytes shared by the master and the specific slave e MaxOutBytes is the number of output bytes shared by the master and the specific slave e IN Nin represent the input byte number Nin where numbering starts from O to MaxInBytes 1 e OUT Nout represent the output byte number Nout where numbering starts from 0 to MaxOutBytes 1 Obviously MaxInBytes and MaxOutBytes are respectively the configured INPUT and OUTPUT AREA sizes The I O Exchange Areas are actually updated and read every 30 ms at the Profibus Processor unit side So after an RFID tag is read the worst delivery time from the Profibus 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 In order to implement the flow controlled version of the driver I O Exchange Areas must be congruently compiled in both directions INPUT Area is the Exchange bu
92. fer Control Byte Input Buffer Control Byte OBCB IBCB 7 6 5 4 3 2 EIA BEE CEIM CE ITA ERES SE 02 oe Packet length in bytes o 00 79 0 3 gt 00 03 00 30 30 00 31 84 Data Consistency Byte OBDCB Data Consistency Byte IBDCB 163 BIS M 62_ MANUAL When the slave sees Bit 2 In the OBCB 8 OBDCB set it knows it needs to resynchronize its handshaking bits in the IBCB amp IBDCB So the Slave will acknowledge the resynchronization request by setting Bit 2 and will clear Bit 1 and Bit 0 in the IBCB amp IBDCB Note that whatever values Bit 1 or Bit 0 had they will be set to 0 This process forces the handshaking into a known state See the Green changes below Output Input Buffer Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 6 5 4 3 2 1 0 KOMM 0 AEST 0 0 IC EC Always 0 Facket length in bytes OS 00 Data Consistency Byte OBDCB ee Data Consistency Byte IBDCB 164 PROFIBUS INTERFACE When the Master sees Bit 2 of the IBCB IBDCB set it clears Bit 2 of the OBCB 4 OBDCEB to acknowledge that the Slave has resynchronized See the Green changes below Output Buffer Input Buffer Be ee en Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 7 6 5 4 3 2 PA A A CIRCUS ESAS TER ETA E 02 06 Packet length in byte 10 00 mm 0 3 00 03 00 a eo Data Consistency Byte OBDCB Data Consistency Byte IBDCB 165
93. fers to anyone using a BIS M 62 Processor Device refers to the BIS M 62 Processor You refers to the System Administrator or Technical Support person using this manual to install mount operate maintain or troubleshoot a BIS M 62 Processor BIS M 41 BIS M 62_ and BIS U 62 RFID Processors are referred to as Processors or just the Processor In addition the terms Subnet Node Number Node ID and Processor ID are used interchangeably BIS M 620 068 _ correspond to the old name HF CNTL 232 unit BIS M 620 067_ correspond to the old name HF CNTL 485 unit BIS M 622 068 correspond to the old name HF CNTL PBS unit BIS M 623 071 correspond to the old name HF CNTL DNT unit BIS M 626 069 correspond to the old name HF CNTL IND unit BIS M 628 075 correspond to the old name HF CNTL PNT unit REFERENGE DOCUMENTATION 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 links indicated for further information including e PRODUCTS Search through the links to arrive at your product page which describes specific Info Features Applications Models Accessories and Downloads including Dashboard a Windows based utility program which allows system testing monitoring an
94. ffer 169 lt gt BIS M 62 MANUAL Exchange Area buffer Max In Out Bytes Application Data Butter Length Bytes byte 2 Length Field byte 1 SAP Field byte 0 Control Field Figure 75 Exchange Area Buffer Structure 10 4 2 Control Field The Input field structure reserves IN 0 for handshake purposes bit O 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 Bit 6 is set to 1 in order to specify the messaging protocol number 1 is in use Bit 2 of the Output buffer is used to request a clear of the synchronization numbers bit O and bit 1 of both Input and Output buffers This is called a resynchronization request and it is always initiated by the Master Station The Slave must acknowledge the request using bit 2 of the Input buffer Bit 3 is used to control a fragmentation sequence in both directions More precisely function of the IN O byte IN 0 bit0 TxBufferFull toggles when new data is available on IN 1 IN Nin input area IN O bit1 RxBufferEmpty toggles when rx block has been read on OUT 1 OUT Nout IN 0 bit2 Resync Acknowledge set to 1 as an acknowledge to a resync request IN 0 bit3 More Bit it must be set to 1 when this is not the last piece of a fragmentation sequence lt must be set to O when this is the last piece of a fragme
95. ffer Control Byte Input Buffer Control Byte OBCB IBCB 6 5 4 3 2 1 0 COC We ee ee CER EUA CT EEE 02 106 Packet length in bytes 102 190 2 Command Command Command Command Command Command EX eae Data Consistency Byte OBDCB 31 180 Data Consistency Byte IBDCB 158 PROFIBUS INTERFACE When the Slave sees Bit 1 of the OBCB amp 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 amp IBDCB See the Green changes below Output Input Buffer nee BE rgges Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 6 5 4 3 2 il 0 BE TOI TOI MAA RO ror oo Always o foo ozs foe racket 1ength in bytes oa fo Command Command Command Command Command Command Data Consistency Byte OBDCB 31 182 Data Consistency Byte IBDCB 159 BIS M 62_ MANUAL 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 O of the IBCB 4 IBDCB See the Green changes below Output Input Buffer SET ge tee Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 6 5 4 3 i 0 EIERE Fe DA 1 1 ror 00 always o
96. ffer from Profibus Processor unit to the Master while OUTPUT Area is the exchange buffer from the Master to the Profibus Processor unit Only the first three bytes are used by the Balluff AnyBus Protocol layer in both buffers for the extended protocol These are byte 0 Control Field used to issue and control the Balluff AnyBus Protocol primitives such as flowcontrol fragmentation and resynchronization byte 1 Service Access Point Field used to distinguish among different services but also to provide future expandability Since this SAP definition is introduced by the Balluff AnyBus Protocol it must not be confused with the AnyBus SAP that is defined by the international standard byte 2 Length Field that contains the number of bytes used by the application layer This number must always be less than or equal to MaxInBytes 3 for the IN buffer and less than or equal to MaxOutBytes 3 for the OUT buffer 121 O BIS M 62 MANUAL Exchange Area buffer Max In Out Bytes Application Data Butter Length Bytes byte 2 Length Field byte 1 SAP Field byte 0 Control Field 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 Bit 6 is se
97. h PROFINET the two perspectives PROFINET CBA and PROFINET IO exist PROFINET CBA Suitable for component based communication via TCP IP and real time communication for real time requirements in modular systems engineering PROFINET IO Developed for real time RT and isochronous real time IRT communication with decentral periphery The designations RT and IRT merely describe the real time properties for the communication within PROFINET IO The Profinet Controller supports Profinet lO MAIN FEATURES e Complies to conformance class B e Device characteristics stored in a GSD file used by PROFINET engineering tools when setting up the network configuration e 100Mbps full duplex with auto negotiation enabled as default e Up to 248 bytes of IO Data 167 gt BIS M 62_ MANUAL 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 PLC Profinet Network Profinet Slaves Profinet Slaves RFID RFID RFID RFID RFID Controller Controller Controller Controller Controller Figure 73 Profinet IO Network Diagram Basically two shared memory areas Exchange Areas are used to exchange information between the SLAVE and the MASTER both devices provide information to each other Figure 74 Profinet Communication Data Exchange Areas Diagram Input and Output areas always refe
98. hanism from slave to master First bit shown in transition IN 0 0 TX BUFFER FULL data written by slave Second bit shown in transition gt OUT 0 1 0 TX BUFFER EMPTY data read by master 0 0 master read tx buff slave write tx buff NZ 0 1 1 0 B slave write tx N 1 1 Se Figure 77 Slave to Master Transmission State Machine Data Transmission Master Slave The receive state machine is shown to understand how a single block is transmitted by the master and received by a slave This protocol guarantees a basic flow control mechanism from master to slave First bit shown in transition gt OUT 0 1 RX BUFFER FULL data written by master Second bit shown in transition IN 0 1 EX BUFFER EMPTY data read by slave vi 0 0 A slave read tx buff master write tx butt d 1 0 D master wnte tx buff 1 1 slave read tx buff Figure 78 Master to Slave Reception State Machine 172 PROFINET INTERFACE Resynchronization Protocol Resynchronization may be used at the master startup both to detect if a slave is on line or not or to restart the messaging protocol from a predefined state lt is also used during normal operations in case of errors requiring a protocol reset procedure to be started Bits order OUT 0 bit Sync request IN 0 bit2 Sync acknowledge Sync request UNSYNCRONIZED Sync acknowledge 1 1 IN 0 IN 1 OUT 0 OUT 1 reset EEN Sync request finish 0 1
99. he 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 The OnDemand Status Page will be displayed ExLink OnDemand Status Microsoft Internet Explorer File Edit View Favorites Tools Help Q sa Ke EN aA A JO search 57 Favorites Es ur OnDemand Status Main Page PLC Read TCP Status Connected 4 times PLC Write TCP Status Connected 4 times READ STATUS WRITE COUNTS WRITE STATUS Success 27 Success Figure 51 The OnDemand Status Page The OnDemand Status Page provides statistical information regarding the connection status of the BIS M 626 This information can be used to verify that read and write connections between the BIS M 626 and the PLC have been established successfully e Read Counts this value indicates the number of times the BIS M 626 has checked the PLC for new data e Write Counts this value indicates the number of times the BIS M 626 has provided data to the PLC That under Ethernet IP the host and or PLC acts as the server However additional messaging instructions are not required on the part of the host because the BIS M 626 will automatically poll the Read Tag in the PLC at the interval specified by the Read Delay value set via the OnDemand Configuration Utility There is no delay parameter when writing data to the PLC as the BIS M 626 delivers all PLC b
100. ic Controller PLC e When installing the Controller for communication over EtherNet IP the ODVA Guidelines for EtherNet IP Media System installation should be followed refer to www odva org ODVA PUB00148R0 Pub 148 EtherNet IP Media Planning and Installation Manual 2006 ODVA e Follow ODVA recommendations for switching and wiring Ethernet IP e l the Ethernet IP network enables I O Messaging for remote I O etc or if other UDP traffic is present then the Controller must be protected by a switch that incorporates IGMP Snooping or a VLAN The BIS M 626 069 A01 06 ST3_ model is designed to support many common Industrial Ethernet protocols and can be implemented in a wide variety of existing host PLC applications One such popular Ethernet protocol is Ethernet IP EIP This chapter focuses on the process of setting up the BIS M 626 Industrial RFID Controller to communicate via Ethernet IP 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 Ethernet IP environments This manual assumes that users are already familiar with Ethernet IP industrial Ethernet communications protocols and programmable logic controller technologies For specific information regarding the protocol used by your particular RFID application please refer to the a
101. ield After a few seconds the processor unit will display its new assigned Node ID value in binary code from right to left or top to bottom using the five amber Node LEDs on the processor unit see Figure B 7 When dynamically assigning a Node ID value for a new processor unit the Gateway will either assign the next available Node ID value or the value that the Gateway recognizes as offline or missing that is a Node ID value that previously existed but has since disappeared from the network Because the Gateway stores a backup of each Subnet Node s configuration should an RFID processor unit ever fail a replacement processor unit can be installed quickly and easily The new processor unit will be automatically assigned the same Node ID value and configuration as the replaced processor unit provided the Configuration Tag is introduced to the antenna field after startup and then removed d Avoid that the configuration tag IS simultaneously read by more than one processor unit NOTE 4 2 CONFIGURATION TOOLS Balluffoffers the following powerful RFID configuration utilities for Microsoft Windows 2000 XP Vista and 7 systems e Balluff Dashboard e C Macro Builder These configuration tools can be downloaded from the Balluff website www balluff com 62 CONFIGURATION METHODS O 4 2 1 Configuration Using Balluff Dashboard The Balluff Dashboard Configuration Tool is a software application that allows users
102. igure 63 1756 DNB A Output Properties Tab 8 Lastly click Apply and select YES to download the configuration and mapping settings from RSNetWorx to the PLC si General Module Scanlist Input Output ADR Summary E 63 Co Polled 30 1 0 Data 0 0 Scanner Configuration Applet he 2 Do vou wank to download these changes to the device ke ze I 1 0 Datafel 68 Cobalt DN Gateway 1 0 Datal8l OF Cancel Apply Help Figure 64 1756 DNB A Output Properties Tab 113 oO BIS M 62_ MANUAL 8 2 3 Configuring Data Rate and Node Address As noted each device computer and controller on a DeviceNet network is considered an individual node for which a unique Node Address number between 0 and 63 is assigned The node address provides a means of numerically identifying each device on a DeviceNet network Prior to operating the BIS M 623 071 A01 03 ST30 you must verify that it has been configured for the same Data Rate as your network and that it has been assigned a suitable node address value The Controller supports data rates of 125Kb default 250Kb and 500Kb and supports node addresses 1 63 default 63 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 a
103. ins a description of the data types used by ODVA that are also found in this chapter Data Type Description USINT Unsigned Short Integer 8 bit UINT Unsigned Integer 16 bit UDINT Unsigned Double Integer 32 bit Character String 1 byte per character Bit String 8 bits Bit String 16 bits Bit String 32 bits 84 ETHERNET IP INTERFACE O 5 9 1 Ethernet IP Required Objects Under Ethernet IP there are six Required Objects e Identity Object 0x01 e Message Router Object 0x02 e Assembly Object 0x04 e Connection Manager Object 0x06 e TCP Object 0xF5 e Ethernet Link Object OxF6 Identity Object 0x01 1 Instance Class Attributes Attribute a Default Data Access ID Name Description Data Type Value Rule 1 Revisin_______ LUNT Instance Attributes Ee Default Data Access Name Description Data Type Value Rule Ca Vendor Number UINT 50 DEC 2 Device Type UINT 3 Product Code Number UINT 6102 DEC Product Major Revision USINT 01 Get Product Minor Revision USINT 25 Status Word see below for WORD See Below Get definition cue 6 Serial Number 000 Number um um Y cue Value a fest Name HF CNTL IND x2 7 Product Name Size USINT 06 Get Product Name String USINT 26 Cobalt Status Word Bit Bit 0 Bit 1 0 Nol OComnection I O Connection Allocated 1 15 Unused oo fUnused Common Services Service Implementation Service Name Code Class Level Instan
104. l RFID command macro programs C Macro Builder C Macro Builder File View Display Options About Denis Available Commands Macro Untitled Length 35 220 Left H Start 22 Macro Response Options Arr In this macro all responses are enabled 22 Error Behavior Options Co Set Macro Response Options ACES Tes DATA res ERAS Ter NTAGS Yes STRINGS Yes 480 Tag Search Tag Search Timeout 2000me e Tag Read ID Tag Read ID Timeout 2000ms de Tag Read Data Tag Read Length 10 4ddrez 0 Timeout 2000ms de Start Continuous Read Data Tag Write Timestamp Format 0 ddrezs 11 Timeout 2000me a Stop Continuous Read Data END T ag write Data T ag Fill Data Ca Tag write Timestamp Tag Increment Decrement Memory sch SLI Tag Write AFI amp SLI Tag Lock AFI AR SLI Tag EAS Operation e SLI Tag Lock Memory Blocks ch SLI Multi T ag Inventory 639 SLI Multi Tag Search E SLI Multi Tag Read Data All SLI Multi T ag Write Data All SLI Multi Tag Fill Data All SLI Multi T ag Write AF All amp SLI Multi Tag Lock AFI All AB SLI Multi T ag EAS Operation i Branch gt Conditional Branch y Transmit Last Response 125 Transmit Custom String A Set Outputs A Clear Outputs A Execute Macro wait El Note 22 Custom Header T erminator Compiled Macro Raw Hex 00 04 F1 00 1F 00 00 03 08 07 DO 00 03 07 07 DO 00 07 05 00 00 00 04 07 DO 00 06 92 00 00 2 Macro Response Options Legacy DE 07 000000 Figure 46 C M
105. l mechanism from master to slave First bit shown in transition gt OUT 0 1 RX BUFFER FULL data written by master Second bit shown in transition IN 0 1 EX BUFFER EMPTY data read by slave vi 0 0 A slave read tx buff master write tx butt d 1 0 D master wnte tx buff 1 1 slave read tx buff Figure 71 Master to Slave Reception State Machine 124 PROFIBUS INTERFACE Resynchronization Protocol Resynchronization may be used at the master startup both to detect if a slave is on line or not or to restart the messaging protocol from a predefined state lt is also used during normal operations in case of errors requiring a protocol reset procedure to be started Bits order OUT 0 bit Sync request IN 0 bit2 Sync acknowledge Sync request UNSYNCRONIZED Sync acknowledge 1 1 IN 0 IN 1 OUT 0 OUT 1 reset EEN Sync request finish 0 1 Sync finish ack 0 0 D C Figure 72 Resynchronization State Machine 9 4 3 SAP Field SAP Service Access Point is an identifier that is used to share the same communication channel between processes of two remote stations This allows splitting the single service into different services SAP 0 is actually used by the slave to transfer acquisition information it should also be used to transfer application data from Master to Slave SAP 2 is currently reserved SAP 255 is currently reserved Only SAP 255 and 2 are reserved All other S
106. leared d The clearing of bit 01 in the Output Data Ready Mask indicates to the BIS M 626 that the host has received the response and that it is now OK to write NOTE another response to Node Output Page 33 This completes the Modbus TCP handshaking cycle 102 STANDARD TCP IP INTERFACE E 7 STANDARD TCP IP INTERFACE d 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 In this environment the BIS M 626 acts as the server and the host or PLC acts as client Standard TCP IP sessions are established between the host computer and the BIS M 626 via TCP IP client software A TCP IP session generally consists of three stages connection setup data transactions and connection termination All connections to the BIS M 626 are initiated by client side software only If for example an existing connection terminates unexpectedly the BIS M 626 will not attempt to contact the client software or re establish a connection The client is responsible for opening maintaining and closing all TCP IP sessions After establishing a successful connection communications between the host and the BIS M 626 can proceed When communication is no longer necessary it is the responsibility of the client side application
107. lists the IP address and network settings currently stored on the BIS M 626 74 ETHERNET IP INTERFACE O 4 Click the button labeled EDIT located below Network Settings A web ed A ab E A A A et A A RR AE sed D fwa nun Network Settings IP Address 192 168 253 110 Subnet Mask 255 255 255 0 Gateway IP Address 0 0 0 0 PPP A AAA RE AAA AA IL RA A AA AO ee TIRAR APA MAA AL AAA A E H The IP Configuration Page will be displayed IP Configuration Page The P Configuration Page is used to modify and save changes to the IP Address Subnet Mask and Network Gateway IP Address IP Configuration IF Address 92 168 253 110 Subnet Mask 955 255 9555 Gateway IP Address 0 0 0 0 save Settings Cancel Changes The unit resefs aufomancally when seffings are modified Man Page Figure 48 The IP Configuration Page 5 Inthe fields provided enter your new IP configuration values for the BIS M 626 6 Click the Save Settings button to store your new IP configuration then cycle power to the controller to store the changes in the main memory The Ethernet module will reset and your IP changes will be implemented 7 After the BIS M 626 has restarted verify the new IP configuration by opening a Web browser and manually entering the BIS M 626 s new IP address in the URL field If successful you should arrive back at the HTTP Server Main Page 75 gt BIS M 62 MANUAL 5 5 ONDEMAN
108. lor LED Description READY READY LED is ON after the power E sequence has completed AMBER The RF LED illuminates when RF power is being transmitted by the antenna The COM communications LED flashes ON and OFF when data is being transmitted between the AMBER antenna and a tag When in Continuous Read mode the COM LED will remain ON and will turn OFF briefly only while data is being read from or written to a tag GE AMBER Default IP Address enabled 192 168 253 110 CUSTOM meer User User assigned IP Address enabled User assigned IP Address enabled Address enabled 3 1 4 BIS M 623 071 A01 03 ST30 DEVICENET Models LED Name LED Color LED Description READY a READY LED is ON after the power e sequence has completed AMBER The RF LED illuminates when RF power is being transmitted by the antenna The COM communications LED flashes ON and OFF pe data is being transmitted between the antenna and a tag AMBER When in Continuous Read mode the COM LED will remain ON and will turn OFF briefly only while data is being read from or written to a tag SOLID GREEN on line and connection established FLASHING GREEN on line but no connections established or needs commissioning DEVICENET GREEN RED FLASHING RED connection timed out or recoverable fault detected SOLID RED unrecoverable fault detected i e duplicate node address 58 LED INDICATORS 3 1 5 BIS M 622 070 A01 03 ST33 PROFIBUS Mo
109. mand Data Byte Command Data Byte Command Data Byte Command Data Byte Command Data Byte Command Data Byte Command Data Byte CBx Command Data Byte i ex 4 Data Consistency Byte OBDCB 31 180 Data Consistency Byte IBDCB HH k vO OANA OBS GO bit 152 PROFIBUS INTERFACE When the Slave sees Bit 1 of the OBCB amp 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 amp IBDCB See the Green changes below Output Buffer Input Buffer EIERE Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 8A 7 6 5 4 3 2 4 3 2 il 0 ESOS TOI ey TII TOI LO OOS Ea o o a A AA o2 ic tracker length in bytes fo fo CBx Command word Sen MSB CBx Command word length LSB CBx Command Type Always AA CBx Command Opcode 0x06 Write Tag Data CBx Command byte not used CBx Command CBx Command CBx Command OxE8 1000 CBx Command CBx Command address 0 CBx Command CBx Command Node 1D Timeout MSB Timeout LSB ms timeout Start Address MSB Start Address LSB Length MSB Length LSB 50 bytes CBx Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Data Byte Command Data Byte Data Consistency Byte OBDCB 31 182 Data Consistency Byte IBDCB Data Data Data Data Data Da
110. n the Slave sees Bit 1 of the OBCB amp 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 amp IBDCB See the Green changes below Output Input Buffer EIERE Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 5 4 3 Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Data Consistency Byte OBDCB 31 180 Data Consistency Byte IBDCB 156 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 Input Buffer a 2 Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 7 6 5 4 AE IO Ca ed CITO aa VA EEE 02 oe racket length in bytes ua fo Command Command Command Command Command Command Data Consistency Byte OBDCB 31 180 Data Consistency Byte IBDCB 157 BIS M 62 MANUAL Next the Master signals that this fragment is ready by toggling Bit 1 of the OBCB A OBDCB Since this is the final fragment the Master clears Bit 3 to 0 See the Green changes below Output Buffer Input Buffer moren Output Bu
111. ng to ControlLogix and legacy support for RA PLC5E and RA SCL5 05 programmable logic controllers 73 gt 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 Among its features is the ability to modify and save changes to the controller s IP address which Is stored internally on the BIS M 626 BIS M 626 Industrial Ethernet RFID Controller Default IP Address 192 168 253 110 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 3 Press ENTER The HTTP Server Main Page will be displayed HTTP Server Main Page Description Station 1 Network Settings IP Address 192 168 253 110 Subnet Mask 255 255 255 0 Gateway IP Address 0 0 0 0 HF CNTL IND v1 0 A Industrial Ethernet RFID Control Network Status MAC Address 00 40 9D 26 D9 70 OnDemand Status Revision 1 27 Link Duplex FULL Serial Config Link Speed 100 MBPS EMS Web Page OnDemand Config Figure 47 The HTTP Server Main Page The HTTP Server Main Page
112. nit Mount the Antenna Adapter to the bottom of the antenna as follows 3 for Antenna models 371 372 and 373 use the two 25 mm M5 screws washers and nuts provided with the BIS M 500 PVC 07 A01 02 Extension Cable kit for Antenna models 370 use the two 35mm M5 screws provided with the BIS M 370 000 A02 antenna The M5 washers and nuts are in the Extension Cable kit Connect one end of the antenna extension cable to the RF port on the top of the Processor unit Side Adapter attach the other end to the RF port on the bottom of the Antenna Side Adapter Tighten both ends of the extension cable firmly by hand Fasten the processor unit and the antenna to your mounting fixtures using M5 or 410 diameter screws not included and secure them with appropriate washers and nuts To complete the installation refer to the specific procedure for your Processor unit under par 2 6 2 23 Minimum Mounting Distance Between Adjacent Antennas 27 oO BIS M 62_ MANUAL 2 2 4 Antenna to Tag Range RF read write range can be adversely affected by many environmental factors including electrical noise metallic objects and liquids 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 Balluff Tag BIS M 62 Series RFID Antenna HF ANT Testing
113. nnector 5 Mounting Bracket 2 Ready LED 6 RS232 Configuration Connector 3 RF LED 7 Host DeviceNet and Power Connector 4 COM LED DeviceNet Status LED PBS Models Figure E G HF Antenna Connector 6 RS232 Configuration Connector 2 Ready LED 7 Power Connector 3 RF LED Host Profibus Out Connector 4 COM LED 9 Host Profibus In Connector 5 Mounting Bracket Profibus Status LEDs PNT Models 4 Figure F a HF Antenna Connector 6 RS232 Configuration Connector 2 Ready LED 7 Power Connector 3 RF LED Profinet 2 Connector 4 COM LED 9 Profinet 1 Connector 5 Mounting Bracket Profinet Status LEDs BIS M 371 000 A01 4 BIS M 372 000 A01 BIS M 373 000 A01 BIS M 370 000 A02 Figure G 10 OVERVIEW nu 1 OVERVIEW 1 1 INTRODUCTION Welcome to the BIS M 62 Processor Manual This manual will assist you in the installation configuration and operation of the BIS M 62 family of processor units The BIS M 62 is a complete line of feature rich passive high frequency read write Radio Frequency Identification devices that provide RFID data collection and control solutions to shop floor item level tracking and material handling applications BIS M 62 processor units are designed to be compact rugged and reliable in order to meet and exceed the requirements of the industrial industry For an overview of RFID operating principles and tags see Appendix Fehler Ver
114. ntation sequence IN 0 bit4 5 7 set to 0 0 0 when this messaging protocol is used IN 0 bit6 set to 1 when this messaging protocol is used 170 PROFINET INTERFACE lt gt function of the OUT O 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 O and next toggle brings them to 1 OUT 0 bit3 More Bit it must be set to 1 when this is not the last piece of a fragmentation sequence It must be set to 0 when this is the last piece of a fragmentation sequence OUT 0 bit4 5 7 set to 0 0 0 when this messaging protocol is used OUT 0 bit6 set to 1 when this messaging protocol is used The following figure shows how it is possible to exchange messages with flow control using bit 0 and bit 1 in the IN OUT buffers FIELDBUS MASTER SLAVE tx buffer full bit 0 rx buffer empty bit 1 lt tx buffer empty bit 0 rx buffer full bit 1 j Figure 76 Message Exchange with Flow Control Handshake byte 0 rx buffer byte 1 Nout 171 BIS M 62 MANUAL 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 mec
115. o after an RFID tag is read the worst delivery time from the Profinet Controller to the Master station is about 30 ms plus the intrinsic PROFINET 10 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 In order to implement the flow controlled version of the driver I O Exchange Areas must be congruently compiled in both directions INPUT Area is the Exchange buffer from Profinet Controller to the Master while OUTPUT Area is the exchange buffer from the Master to the Profinet Controller Only the first three bytes are used by the Balluff AnyBus Protocol layer in both buffers for the extended protocol These are byte 0 Control Field used to issue and control the Balluff AnyBus Protocol primitives such as flowcontrol fragmentation and resynchronization byte 1 Service Access Point Field used to distinguish among different services but also to provide future expandability Since this SAP definition is introduced by the Balluff AnyBus Protocol it must not be confused with the AnyBus SAP that is defined by the international standard byte 2 Length Field that contains the number of bytes used by the application layer This number must always be less than or equal to MaxInBytes 3 for the IN buffer and less than or equal to MaxOutBytes 3 for the OUT bu
116. onse Node ID Command Timeout LSB CBx Response Timestamp Month Command Not Used CBx Response Timestamp Day Command Not Used CBx Response Timestamp Hour Command Not Used CBx Response Timestamp Minute Command Not Used CBx Response Timestamp Second CBx Response Data length 1 byte the Error Code CBx Response Data Byte 1 Error Code 7 Tag Not Found CBx Response byte not used 31 182 Data Consistency Byte OBDCB Data Consistency Byte IBDCB In this case the response is a Tag Not Found error The Master can see that Bit 0 of the IBCB amp IBDCB has been toggled so it knows that the response in the Input Buffer is ready Since Bit 2 of the IBCB amp IBDCB is not set to 1 it knows that the response is complete not a fragment 132 PROFIBUS INTERFACE The Master now toggles Bit 0 of the OBCB amp OBDCB to acknowledge that it has received the response See the Green changes below Output Buffer Input Buffer Bee 2 Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 6 5 4 7 6 5 4 OTA JG eee KK O fo o femo oo Command word SE MSB a Response word an MSB Command word length LSB CBx Response word length LSB Command Type Minimum of 6 words Command Opcode Response Type FF Error Command byte not used Response Opcode FF Error Command Node ID Response Instance Counter Command Timeout MSB Response Node ID Command Timeout LSB Respons
117. ontroller Tags a Write Tag and a Read Tag Controller Tag Naming Controller Tags need to be assigned a name and size Be sure to use the same Write Tag Name and Read Tag Name that you specified in the OnDemand Node Configuration i e EMS WRITE1 and EMS READ1 Controller Tag Size Due to handshaking overhead Controller Tags must have the size capacity to store an integer array equal to your previously specified Write Read Size three words So for example if the Read Size you specified earlier was 100 words the corresponding Read Tag in the PLC must be able to store an array of 103 integers Controller Tags SAMPLE 435NBA controller Scope SAMPLE 435NBA c Show Show All sl Sort Tag Name Edu ag Name s Value es Mask Style gt ESKE Hex e The Write Tag holds messages and response data generated by the BIS M 626 that is bound for the host or PLC e The Read Tag holds RFID commands and instructions intended for the BIS M 626 79 O BIS M 62 MANUAL d 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 Main Page to continue 80 ETHERNET IP INTERFACE O 5 7 CHECKING ONDEMAND STATUS Now that you have configured the BIS M 626 s Node and defined corresponding Write and Read Tags in t
118. or the final fragment of a fragmented response and so the Master can know when all the fragments of a response have been returned from the 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 Byte 3 through Byte N 2 are used for the actual CBx response or response fragment to be sent Byte N 1 The final byte of the Input Buffer is the Data Consistency Byte for the Input Buffer It is a copy of the Input Buffer Control Byte The Master should check that these two bytes are the same before considering the Input Buffer s data to be valid d The input and output buffers can exceed 64 bytes The combined total of the input and output buffers cannot exceed 152 bytes NOTE 9 5 1 Example 1 Normal Command Response Sequence For this example the Master will send a CBx Read Tag ID command to the Slave the Processor unit to read an 8 byte tag ID from an RFID Tag First we will see a Tag Not Found error assuming that the tag is not read and then we will see a successful read of the Tag ID We will assume for this example that both the Input and Output Buffers have been configured to 32 bytes each This means that the processor unit response for this command can fit entirely in the
119. ound data immediately after it is generated If you configured a low Read Delay value the Read Counts on the OnDemand Status Page will accumulate rapidly This occurs because a low Read Delay value instructs the BIS M 626 to poll the PLC for new data more frequently power to the BIS M 626 and verify that Ethernet IP services are running If the BIS M 626 and PLC do not successfully establish a connection cycle LN properly on the PLC If that does not resolve the issue restart Ethernet IP CAUTION Services on the PLC and the 1756 ENBT module 81 gt 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 o RSLogix 5000 SAMPLE_435NBA in SAMPLE_GTW_TEST ACD 1756 L1 File Edit View Search Logic Communications Tools Window Help Bla S ae 2 s l v aja No Forces b No Edits ie al gt D A s Abt A vo Controller Tags SAMPLE 435NBA controller EX Controller Tags SAMPLE 435NBA controller Scope SAMPLE_435NBA c D Show Show All v Sort amp Value Forc Style Type Leo Hex y JINT 203 16 0000 Hex 16 0000 Hex 16 0000 Hex 16 0000 Hex 3 Controller SAMPLE 435NBA Controller Tags Controller Fault Handler ma Power Up Handler Sco
120. owledges 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 See the Green changes below Output Buffer Input Buffer Be AE Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 7 6 5 4 3 2 1 0 EO ONO 1 0 a CI 02 foc Packet length in bytes 100 190 a Command word an MSB CBx Command word length LSB Minimum of 6 words CBx Command Type Always AA CBx Command Opcode 0x05 Read Tag Data CBx Command byte not used CBx Command Node ID CBx Command Timeout MSB CBx Command Timeout LSB OxE8 1000 ms timeout CBx Command Start Address MSB CBx Command Start Address LSB address 0 CBx Command Length MSB CBx Command Length LSB 50 bytes Data Consistency Byte OBDCB Ste 82 Data Consistency Byte IBDCB 144 PROFIBUS INTERFACE O 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 Bit 3 is not a toggle If it is 1 then there are more fragments to follow If it is 0 it is either a complete response or the final fragment of a response NOTE See the Green changes
121. pe SAMPLE_435NBA c Show Show All sl Sot TagName Tag Name amp Value Force Ma Style De EMS READ1 ee Hex Tag Name gt EMS WRITE1 EMS READ1 0 16 0000 Hex EMS READ1 1 EMS READ1 2 EMS READ1 3 16 0000 Hex 16 0000 Hex 16 0000 Hex EMS WRITE1 1 EMS WRITE1 2 EMS WRITE1 3 3 Motion Groups Ungrouped Axes Trends Data Types Ep User Defined og Strings Og Predefined Og Module Defined 3 1 0 Configuration f 3 1756 ENBT A ENBT EMS READ1 4 EMS READ 5 EMS READ 6 EMS READ1 7 EMS READ1 8 EMS READ1 9 EMS READ1 10 EMS READ1 11 EMS READ1 12 EMS READ1 13 EMS READ1 14 16 0000 16 0000 16 0000 16 0000 16 0000 16 0000 16 0000 16 0000 16 0000 16 0000 Hex Hex Hex Hex Hex Hex Hex Hex Hex Hex Hex EMS_WRITE1 4 EMS_WRITE1 5 EMS_WRITE1 6 EMS_WRITE1 EMS_WRITE1 8 EMS_WRITE1 9 EMS_WRITE1 10 EMS_WRITE1 11 EMS_WRITE1 12 EMS_WRITE1 13 EMS_WRITE1 14 16 0000 16 0000 16 0000 16 0000 16 0000 16 0000 16 0000 16 0000 16 0000 16 0000 16 0000 Hex Hex Hex Hex Hex Hex Hex Hex Hex Hex Hex Figure 52 RSLogix 5000 5 8 1 Ethernet IP Handshaking To ensure that messages to and from the BIS M 626 are properly delivered and received a handshaking mechanism has been implemented that uses a pair of dedicated words in the exchange The first two words in
122. ppropriate documentation from your host PLC program provider 71 E BIS M 62 MANUAL 5 1 ETHERNET IP CONFIGURATION OVERVIEW Based upon on the standard TCP IP protocol suite EtherNet IP is a high level application layer protocol for industrial automation applications that uses traditional Ethernet hardware and software to define an application layer protocol that structures the task of configuring accessing and controlling industrial automation devices Ethernet IP classifies Ethernet nodes as predefined device types with specific behaviors The set of device types and the EIP application layer protocol is based on the Common Industrial Protocol CIP layer used in ControlNet Building on these two widely used protocol suites Ethernet IP provides a seamlessly integrated system from the RFID Subnet network to the Host and enterprise networks The BIS M 626 is designed to communicate as an EtherNet IP client device which will receive and execute RFID commands issued by the host PLC acting as EtherNet IP Server Paragraphs 1 3 through 1 7 contain instructions that will help you accomplish the following e Assign the BIS M 626_ an IP address via HTTP Server e Configure the BIS M 626 s Subnet Node via OnDemand Utilities e Create Controller Tags in the PLC e Verify PLC and BIS M 626 Subnet Node connectivity 5 2 HTTP SERVER 8 ONDEMAND PLC SUPPORT Below is a partial list of the programmable logic controllers that are supporte
123. r Bit 1 is toggled by the Slave to acknowledge a packet command or command fragment from the Master 175 gt BIS M 62_ MANUAL Bit 2 is set by the Slave after it completes resynchronization and then cleared once the Master has acknowledged that resynchronization is complete Bit 3 is set by the Slave when the total CBx response being returned to the Master is larger than the space available in the Input Buffer or that the packet being returned is a fragment and that there are more fragments to follow This bit is cleared for the final fragment of a fragmented response and so the Master can know when all the fragments of a response have been returned from the 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 Byte 3 through Byte N 2 are used for the actual CBx response or response fragment to be sent Byte N 1 The final byte of the Input Buffer is the Data Consistency Byte for the Input Buffer It is a copy of the Input Buffer Control Byte The Master should check that these two bytes are the same before considering the Input Buffer s data to be valid d The combined total of the input and output buffers cannot exceed 248 bytes For specific exchange data examples refer
124. r and PLC DeviceNet Communtcatons smmmmssressrresrrrenrrrenrr nan 109 Configuring Data Rate and Node Address ssmnssrssressresrrrsorrrorrrrrrrrrrerrrrnr rss rr rr norr norra 114 DeviceNet Exchanging Data and Handehakimg rann 115 DeviceNet Handshaking Exvample smsssssessessressaessrerrrsrrnrrrrrarrrnr rss rank rr rna rr r rr rr rn nanna 116 PROFIBUS INTERFACE siie 119 Profibus OVA 119 FO PS 119 Dal PTE pe 120 PrOIOCOLIMpIEMENIAllON ae nun 121 DEMON sa 121 Go 110 HI o E 122 SAP elisa id RE 125 E A AO 125 Application Dala BUM een 126 Examples of Profibus Command Response Mechanism sssssessersresresrrrrrrnrrrrrnr nanna 126 Example 1 Normal Command Response Sequence arrnnnrnnnnrnnnnnnnnnnnnnrnnennnnnennnen 128 Example 2 Unsolicited Responses Continuous Read Mode 138 Example 3 Fragmentation of Hesponses ennen ren ren reor ennen 142 Example 4 Fragmentation of Commande siosrnsrrssrrsresrarrresrenrrnrrrr ran rerna rer r ran ren r nr anna 151 Example 5 Resynehr nlZe OD sia 162 PROFINET INTERFACE cai a 167 A e SVIS EE 167 POMMERN 167 Datt EE 168 Protocol IMplementalON siii 169 PENIONS ER 169 STL EN 170 PP 173 PENN FE ua 173 Application Dala BUTE seen 174 Examples of Profnet Command Response Mechamtem rna 174 TEGHNIGAL FEATURES caida dde 178 BIS VI 62 RrOCOSSON UNIS renren 178 BIS TEST AENEAS assessor 179 REFERENCES CONVENTIONS This manual uses the following conventions User or Operator re
125. r pinout Connect the BCCO6ZF M12 5 pin female connector to the M12 5 pin male connector on the processor unit Connect the other end of the cable wires or user supplied connectors to the power supply Apply power to the processor unit after all cable connections have been made The LEDs on the unit will flash The READY LED is ON after the power up sequence has completed INSTALLATION gt 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 M Configuration Tool uses the PC RS232 serial port to communicate to the processor unit s RS232 serial port To enable communication 1 To connect the processor unit s RS232 serial port to the PC you have two choices the first one is the quickest a Connect the BCCOETJ M12 8 pin female connector to the M12 8 pin male interface connector on the BIS M 62_ Connect the BCCOETJ 9 pin female D sub connector to an RS232 COM port on the host computer or b Build your own communication cable using the BCCOAO3 connector M12 8 pin female connector and follow the schematic shown in par 2 3 5 2 On the host computer set COM port parameters to 9600 baud 8 data bits 1 stop bit no parity and no handshaking Run the Dashboard M Configuration Tool 47 BIS M 62 MANUAL 2 6 6 Installing the BIS M 628 075 A01 03 ST34 PROFINET PNT to Power Supply
126. r to the Master this means that the Controller writes to the Input buffer and the PLC writes to the Output buffer The dimension of the exchange areas can be set to different values by the PLC through the GSD file the Profinet Controller allows up to 248 bytes as a combined total of the Input and Output Areas For further information regarding Fieldbus interfacing including downloadable support files go to the HMS website at http www anybus com choose the link to the support page select the Anybus CompactCom product type and then your network type 168 PROFINET INTERFACE lt gt 10 4 PROTOCOL IMPLEMENTATION 10 4 1 Definitions In the protocol description we ll use the following definitions e Input field is the set of master inputs that can be modified by the specific slave e Output field is the set of master outputs that can be read by the specific slave e MaxinBytes is the number of input bytes shared by the master and the specific slave e MaxOutBytes is the number of output bytes shared by the master and the specific slave e IN Nin represent the input byte number Nin where numbering starts from 0 to MaxInBytes 1 e OUT Nout represent the output byte number Nout where numbering starts from 0 to MaxOutBytes 1 Obviously MaxInBytes and MaxOutBytes are respectively the configured INPUT and OUTPUT AREA sizes The I O Exchange Areas are actually updated and read every 30 ms at the Profinet Controller side S
127. r unit response to the tag read command cannot completely fit in the input buffer and the response will be fragmented or sent in multiple fragments 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 In this case the CBx command we are sending is 12 bytes This length is the length of the command bytes we are interested in sending not the full size of the buffer The length also does not include the Data Consistency Byte at the end of the buffer That is just a mirror of the Control Byte In Byte 3 through Byte 14 the Master places the 12 bytes of this particular CBx command Some CBx commands are larger but all will be at least 12 bytes even if some of those 12 bytes are not actually used See the Green changes below Output Buffer Input Buffer CIC CCT Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 7 6 5 EIE EEN 02 oe Packet length in bytes oz fo lt lt CBx Command word length MSB CBx Command word length LSB Minimum of 6 words CBx Command Type Always AA CBx Command Opcode 0x05 Read Tag Data CBx Command byte not used CBx Command Node ID CBx Command Timeout MSB CBx Command Timeout LSB OxE8 1000 ms timeout CBx Command Start Address MSB CBx Command Start Address LSB address 0 CBx Command Length MSB CBx Command Length LSB 50 bytes EE Data Consistenc
128. rades can only be made within the same major release family i e 2 xx lt gt 2 xy Do not attempt software upgrades downgrades between major releases i e 2 xx lt gt 3 XX See the Balluff Dashboard M User s Manual for more details on software upgrades 4 2 3 Creating and Using RFID Macros with C Macro Builder 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 Because macros reside within the processor unit s internal memory they can be programmed to instruct the processor unit to automatically read and or write a specified set of data to an RFID tag without the processor unit ever having to receive a command from the host In fact the processor units do not even require a connection to a host in order to execute macros Each macro can contain up to 255 bytes of data and each supported processor unit can store up to eight macros at a time Though they are stored locally on the processor unit macros are also backed up in the Gateway s flash memory as well Why use macros The power of macros is in distributed intelligence the reduction in network bus traffic and the ability to accelerate routine decision making at the point of data collection What can macros do In addition to the automated reading and writing of data macro capabilities include e The
129. rcing Output Using Processor unit Power Controller Figure 38 Open Collector Sinking Output Using Processor unit Power 54 INSTALLATION gt Output Connections Using External Power Vuser Controller 6 30 Vde VGND GNDuser Figure 39 Open Emitter Sourcing Output Using External Power Vuser 6 30 Vde Controller GNDuser Figure 40 Open Collector Sinking Output Using External Power 55 lt gt BIS M 62 MANUAL Vuser 6 30 Vdc Controller GNDuser Figure 41 Open Collector Sinking Output for a LED Using External Power Note The resistor R1 in series with the LED LD1 sets the forward current a value of 1 2 KQ will provide about 20 mA LED current when run from 24 Vdc 2 3 Digital l 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 To determine which command protocol to utilize please refer to the list below for the different Balluff RFID devices CBx Protocol e BIS M 62_ Series Fieldbus and Non Fieldbus models Industrial Ethernet IND ABx Protocol Fast and Standard e BIS M 620 068 Series Serial mod
130. rerrrren rr rn rrrnrr rn nr rr nn 58 BIS M 623 071 A01 03 ST30 DEVICENET Models ooccccoccccccoccnccccccncconcncnoncncnnos 58 BIS M 622 070 A01 03 ST33 PROFIBUS Model 59 BIS M 628 075 A01 03 ST34 PROFINET Model 60 CONFIGURATION METHODS nn a ae 61 CONO Tag aS 61 Node ID Configuration Using Configuration Tags 61 EON NO UA OR TOO anne ee 62 Configuration Using Balluff Dasbboad N 63 Software Upgrades Using Balluff Dashboarg y nennen 65 Creating and Using RFID Macros with C Macro Builder rararrarernrrorarernarennnennnnnn 65 Command Protocol ee 69 ETHERNET IP INTERFACE u ee 71 Ethernet IP Configuration Overview s ssssssrrssrrssrrssrrssrrerrrrrrarrrrrr rss rr rr rr rr nns nenne nenne nennen 72 HTTP Server amp OnDemand PLC Support roria a aR E E EEEE 72 HTTP Server and OnDemand Utultes rr r rr rr nr norra 73 IP Configuration via HTTP Genver nennen 74 OnDemand Configuration for Ethernet IP Renee nenne nenne nnennenenn 76 Contiquring PES GontrollerTadS aa ee 79 Checking OnDemand Status ee 81 Verifying Data Exchange with RSLogix 5000 nenn nennn nenne nennen 82 Eihernetlp Hanashakindg an Keen 82 Ethernet IP Handshaking Exvample anne nenne nenn nenne nennen 83 Emnene P Obec NON SS 84 Ethernet IP Required ONES e 85 EtherNet IP Vendor Specific Obiechts Uassssiimtussdsnsisisdis ssprdsnnskondss daki n tess H se dar en dn 89 BIS M 626 Consume Data Object 0x64 32 lnstoancesl nr nana 89 Application Object 0x67 _ 10 lnstan
131. rolLogix Only STRING 92 ETHERNET IP INTERFACE Name Description Data Type deis Value Rule Default Data Access Read File Number SLC PLC Only NX 0 Where X is the UNT y File Number Read File Offset SLC PLC Only N7 Y Where Y is the UINT File Offset Read Poll Rate Measured in 10ms ticks 0 disabled UINT 100 6000 ticks max Common Services Service Implementation H Service Name Code Class Level Instance Level 0x0E Yes Yes Get Attribute Single 93 gt BIS M 62 MANUAL 94 MODBUS TCP INTERFACE gt 6 MODBUS TCP INTERFACE d 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 6 1 MODBUS TCP OVERVIEW Under the Modbus TCP protocol the BIS M 626 acts as a Modbus Server and the PLC acts as a Modbus Client By utilizing Produce and Consume registers for mapping commands and responses data produced by the BIS M 626 is consumed by the Modbus Client and data produced by the Modbus Client is consumed by the BIS M 626 e Modbus Client Host or PLC must connect to the Modbus Server BIS M 626_ on port 502 e Maximum number of words transferred to from an RFID tag per read wri
132. s Macros are supported on the following BIS M 62 Processor units Ethernet Profibus Profinet DeviceNet RS232 and USB interfaces What happens to existing Macros if a processor unit must be replaced When using a Subneti6 Gateway users do not need to worry Macros and triggers normally residing in an RFID processor unit s flash memory are always backed up in the Gateway s flash memory as well Therefore if a processor unit should ever require replacement all existing macro and trigger settings are automatically exported from the Gateway to the new RFID processor unit In short when an RFID processor unit is initially connected to the Gateway macro and trigger data from the processor unit s flash memory is compared to the macro and trigger data backed up in the Gateway from the previous RFID processor unit lf the data does not match that which is stored on the Gateway the processor unit s flash memory will be overwritten with the backed up data stored in the Gateway s flash memory 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 www balluff com 67 gt BIS M 62 MANUAL C Macro Builder is an easy to use GUl driven Configuration Tool for Windows that allows users to create powerfu
133. supply Apply power to the processor unit after all cable connections have been made The LEDs on the unit will flash The READY LED is ON after the power up sequence has completed INSTALLATION gt 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 M 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 To connect the processor units RS232 serial port to the PC you have two choices the first one is the quickest a Connect the BCCOETJ M12 8 pin female connector to the M12 8 pin male interface connector on the BIS M 628 Connect the BCCOETJ 9 pin female D sub connector to an RS232 COM port on the host computer or b Build your own communication cable using the BCCOAO3 connector M12 8 pin female connector and follow the schematic shown in par 2 3 6 2 On the host computer set COM port parameters to 9600 baud 8 data bits 1 stop bit no parity and no handshaking Run the Dashboard Configuration Tool 49 O 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
134. t 126 Produce Data 31 000 31 249 UINT 0 Get A PE PP PA ES Produce Data 32 000 32 249 UINT fo Get 131 Produce Data 32 250 32 249 JUINT 10 Get KZ Produce Data 32 500 32 249 UINT fo Get IKK Produce Data 32 750 32 767 JUINT np Get 91 O BIS M 62_ MANUAL Common Services Service Implementation Code Class Level Instance Level Service Name 0x05 No Yes Reset gt 0x0E ve Yes Let Attribute Single 0x10 No ie Set Attribute Single This Service Code is used to flush all attributes to zero 5 9 3 Application Object 0x67 _ 10 Instances Class Attributes Instance 0 Attribute Se Default Data Access ID Name Description Data Type Value Rule A Revisin__________ UINT Instance Attributes Instances 1 32 Attribute T Default Data Access ID Name Description Data Type Value Rule Instance Type 0 3 0 Disable 1 ControlLogix USINT Get 2 SLC 5 05 3 PLC5E 2 PLCIP Address UDINT Aa gt PLC Slot Location 0 Max Write Size in Words 0 Disabled UINT Get 1 100 Words Write Tag Name SHORT ControlLogix Onl STRING Write File Number SLC PLC Only NX 0 where X is the File Number E DE Write File Offset SLC PLC Only Get N7 Y where Y is the File Offset Write Heartbeat Timeout Measured in 10ms ticks 100 Get 0 disabled Max value 6000 ticks Max Read Size in Words 0 Disable UINT Get Max Value 100 Cont
135. t Buffer Input Buffer en m Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 5 7 6 5 4 eee 01 00 Always 0 Im fame foo foo tracker Length In bytes 02 42 Packet tengan In Bytes SS Response word an MSB CBx Response word length LSB Minimum of 6 words CBx Response Type AA Normal Response CBx Response Opcode 0D Continuous Read Response Response Instance Counter Response Node ID Response Timestamp Month Response Timestamp Day Response Timestamp Hour Response Timestamp Minute Response Timestamp Second Response Data length 6 bytes the Tag ID CBx Response Data Byte 1 Tag ID Byte 1 CBx Response Data Byte Tag ID Byte 2 CBx Response Data Byte Tag ID Byte 3 CBx Response Data Byte Tag ID Byte 4 CBx Response Data Byte Tag ID Byte 5 CBx Response Data Byte Tag ID Byte 6 31 180 Data Consistency Byte OBDCB EARLIER Data Consistency Byte IBDCB No new responses will come from the reader until the Master has acknowledged the previous response by toggling Bit 0 of the OBCB amp OBDCB 141 O BIS M 62_ MANUAL 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 This means that the processo
136. t the command is in the Output Buffer The Master alerts the Slave that the command is ready lt 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 So if it is O it is toggled to 1 to indicate a new command If it is 1 it is toggled to 0 to indicate a new command If the bit is 1 setting it NOTE to 0 and then back to 1 will cause the command to be issued twice 129 BIS M 62 MANUAL See the Green changes below Output Input Buffer mere er ae Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 6 5 4 5 2 1 0 parara A EMNENE Le rn CC o2 foc trasket length in bytes oz fo o Command word a MSB Command word length LSB Command Type Command Opcode Command byte not used Command Node ID Command Timeout MSB Command Timeout LSB Command Not Used Command Not Used Command Not Used Command Not Used ie ja Data Consistency Byte OBDCB Se GRE Data Consistency Byte IBDCB When the Slave sees Bit 1 of the OBCB amp 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 130 PROFIBUS INTERFACE See the Green changes below Output Input B
137. t to 1 in order to specify the messaging protocol number 1 is in use Bit 2 of the Output buffer is used to request a clear of the synchronization numbers bit O and bit 1 of both Input and Output buffers This is called a resynchronization request and it is always initiated by the Master Station The Slave must acknowledge the request using bit 2 of the Input buffer Bit 3 is used to control a fragmentation sequence in both directions More precisely function of the IN O byte IN 0 bit0 TxBufferFull toggles when new data is available on IN 1 IN Nin input area IN O bit1 RxBufferEmpty toggles when rx block has been read on OUT 1 OUT Nout IN 0 bit2 Resync Acknowledge set to 1 as an acknowledge to a resync request IN 0 bit3 More Bit it must be set to 1 when this is not the last piece of a fragmentation sequence lt must be set to O when this is the last piece of a fragmentation sequence IN 0 bit4 5 7 set to 0 0 0 when this messaging protocol is used IN 0 bit6 set to 1 when this messaging protocol is used 122 PROFIBUS INTERFACE O function of the OUT O byte OUT O 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
138. t16 Network trunk and distributed 2 4 2 Total System Current Consumption The current consumption values of each product are given in the Technical Features paragraph of the relative Installation manual and refer to the min and max input voltage range These values already include an adequate safety margin The consumption values given in the following examples have been interpolated for an input voltage of 24 Vac Max Gateway Current 200 mA 12 Vdc 133 mA 24 Vdc Max Processor unit Current 366 mA 24 Vdc for BIS M 62 series Calculating Total System Current Consumption Total System Current Consumption Max Gateway Current Max Processor unit Current x Number of Processor units Example A Subnet16 network powered at 24 Vdc is composed of a BIS Z GW 001 connecting eight BIS M 620 067 A01 04 Processor units Total System Current Consumption 0 133 A 0 366 A X 8 3 061 A 39 gt BIS M 62 MANUAL 2 4 3 Cable Voltage Drop In addition each RFID Processor unit on the Subnet will experience a certain amount of voltage drop depending on the length of the cable Cable Resistance per Meter e ThinNet 0 058 ohms per meter per wire e ThickNet 0 0105 ohms per meter per wire Calculating Voltage Drop Voltage Drop Max Processor unit Current x Number of Processor units x Cable Resistance per Meter per Wire x Cable length in Meters Example A Subneti6 network is composed of a BIS Z GW
139. ta Data Data Data Data Data Data Data Data Byte Byte Byte Byte Byte Byte Byte Byte Byte Byte Byte Byte Byte Byte 153 BIS M 62 MANUAL 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 Input Buffer ae 2 Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 7 6 5 4 ERARIO EEN EE Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Data Consistency Byte OBDCB Data Consistency Byte IBDCB 154 PROFIBUS INTERFACE Next the Master signals that this fragment is ready by toggling Bit 1 of the OBCB A 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 EIERE Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Command Data Consistency Byte OBDCB Data Consistency Byte IBDCB 155 BIS M 62_ MANUAL Whe
140. te OBCB IBCB 81 7 6 5 4 3 7 6 5 4 ARCA IR ON DE EI ERIK FR ER 0 a 180 Always UO O Always KA 02 oo Packet length in bytes foz 32 packet length in bytes CBx Response word length MSB CBx Response word length LSB Minimum of 6 words CBx Response Type AA Normal Response CBx Response Opcode OD Continuous Read Response CBx Response Instance Counter CBx Response Node ID CBx Response Timestamp Month CBx Response Timestamp Day CBx Response Timestamp Hour CBx Response Timestamp Minute CBx Response Timestamp Second CBx Response Data length 6 bytes the Tag ID CBx Response Data Byte 1 Tag ID Byte 1 CBx Response Data Byte 2 Tag ID Byte 2 CBx Response Data Byte 3 Tag ID Byte 3 CBx Response Data Byte 4 Tag ID Byte 4 CBx Response Data Byte 5 Tag 1D Byte 5 CBx Response Data Byte 6 Tag ID Byte 6 30 00 Data Consistency Byte OBDCB 31 180 Data Consistency Byte IBDCB This response contains a timestamp that is 60 seconds after the previous response and tag has different data Note that the Instance Counter in the CBx response increments for each response The Master can see that Bit 0 of the IBCB amp IBDCB has been toggled so it knows that a new response in the Input Buffer is ready 140 PROFIBUS INTERFACE The Master now toggles Bit 0 of the OBCB amp OBDCB to acknowledge that it has received the response See the Green changes below Outpu
141. te cycle 100 Words 200 Bytes e Disable any firewall services running on the PC Firewalls can potentially block communications between the BIS M 626 and the host and or PLC 6 2 MODBUS TCP CONFIGURATION VIA HTTP SERVER To configure the BIS M 626 for Modbus TCP 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 Among its features is the ability to modify and save changes to the controller s IP address which is stored internally on the BIS M 626 BIS M 626 Industrial Ethernet RFID Controller Default IP Address 192 168 253 110 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 host 2 In the URL address field enter the BIS M 626 s IP address 192 168 253 110 factory default 3 Press ENTER The HTTP Server Main Page will be displayed 95 O BIS M 62 MANUAL HTTP Server Main Page Description Station 1 Network Settings IP Address 192 168 253 110 Subnet Mask 255 255 255 0 Gateway IP Address 0 0 0 0 DATALOGIC HF CNTL IND v1 0 A En Industrial Ethernet RFID Control Network Status samen MAC Address 00 40 9D 26 D9 70 Revision 1 27 Link Duplex FULL Serial Config Link Speed 100 MBPS EMS Web Pag
142. the last five words of the command to Node Input Page 01 beginning at register 40002 After which the host will fill in the first word at holding register 40001 with the Overall Length of the command packet Last Five Words of a Read Data Command Word MSB LSB Description 02 TOxAA 1005 Command ID Read Data 03 0x00 0x01 Node ID 0x01 04 L oxEg_______ Timeout Value 1 second 05 poxoo JOx20 Read Start Address 0x0020 06 Log Tom Block Size 4 Bytes After writing the last five words of the command the host will write the Overall Length value to holding register 40001 of Node Input Page 01 First Word of a Read Data Command Word MSB LSB Description 01 0x00 0x06 Overall Length in words The moment the Overall Length value at holding register 40001 of Node Input Page 01 changes from 0x0000 to a non zero value the BIS M 626 will recognize the waiting data and will execute the command 6 3 2 Modbus TCP Handshaking Example 1 The host or PLC issues an RFID command to the BIS M 626_ writing the command string to the holding registers for Device ID 01 Node Input Page 01 An Overall Length value of 0x0006 is written last to holding register 40001 2 The BIS M 626 recognizes that the Overall Length value at holding register 40001 has changed for Device ID 01 Node Input Page 01 indicating that a command is waiting to be executed 3 The BIS M 626_ executes the command and then clears the
143. this version has been specifically designed for factory automation MAIN FEATURES Maximum Number of Nodes 126 Distance 100 m to 24 Km with repeaters and fibre optic transmission Baud rate 9600 to 12M bps 119 gt BIS M 62 MANUAL 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 PLC Profibus Network Profibus Slaves Profibus Slaves RFID RFID RFID RFID RFID Controller Controller Controller Controller Controller Figure 66 Profibus DP Network Diagram Basically two shared memory areas Exchange Areas are used to exchange information between the SLAVE and the MASTER both devices provide information to each other Figure 67 Profibus Communication Data Exchange Areas Diagram Input and Output areas always refer to the Master this means that the Processor unit writes to the Input buffer and the PLC writes to the Output buffer The dimension of the exchange areas can be set to different values by the PLC through the GSD file the Profibus Processor unit allows up to 152 bytes as a combined total of the Input and Output Areas For further information regarding Fieldbus interfacing including downloadable support files go to the HMS website at http www anybus com choose the link to the support page select the Anybus CompactCom product type and then your n
144. to 1 OUT 0 bit3 More Bit it must be set to 1 when this is not the last piece of a fragmentation sequence lt must be set to O when this is the last piece of a fragmentation sequence OUT 0 bit4 5 7 set to 0 0 0 when this messaging protocol is used OUT 0 bit6 set to 1 when this messaging protocol is used The following figure shows how it is possible to exchange messages with flow control using bit O and bit 1 in the IN OUT buffers FIELDBUS MASTER SLAVE tx buffer full bit 0 rx buffer empty bit 1 lt tx buffer empty bit 0 rx buffer full bit 1 j Figure 69 Message Exchange with Flow Control Handshake byte 0 rx buffer byte 1 Nout 123 BIS M 62_ MANUAL 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 First bit shown in transition IN 0 0 TX BUFFER FULL data written by slave Second bit shown in transition gt OUT 0 1 0 TX BUFFER EMPTY data read by master 0 0 master read tx buff slave write tx buff NZ 0 1 1 0 B slave write tx N 1 1 Se Figure 70 Slave to Master Transmission State Machine Data Transmission Master Slave The receive state machine is shown to understand how a single block is transmitted by the master and received by a slave This protocol guarantees a basic flow contro
145. to Profinet Master ba FEE H be BEN BCCO6ZF BCCO6ZF BIS M 628 075 w antenna PNT 1 SE to Configuration PC to Configuration PC to Configuration PC PNT 2 PNT 2 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 lO network via compatible cables directly to a PROFINET Master host The default IP Address is 192 168 253 110 1 2 48 Select a suitable location for the BIS M 628 Processor unit Antenna Mount the BIS M 37 antenna to the BIS M 628 Processor unit either directly or remotely as described in par 2 2 Mount the processor unit and antenna to your mounting fixture using M5 or 10 diameter screws not included and secure them with appropriate washers and nuts Tighten screws to 1 7 Nm or 15 Ibs per inch 10 Attach PROFINET compatible data cables to the 4 pin D Coded female M12 interface connectors on the processor unit Connect the other end of the cables to your PROFINET network Build a power supply cable using the BCC06ZF M12 5 pin female connector Use 18 AWG max to 24 AWG min wires for connection to the power supply lines according to the Vdc connector pinout Connect the BCC06ZF M12 5 pin female connector to the M12 5 pin male connector on the processor unit Connect the other end of the cable wires or user supplied connectors to the power
146. to a different location of the tag but if it is desirable to send one long CBx command it can be accomplished using this method of fragmentation Sending the command In Byte 2 of the output buffer the Master places the length in bytes of the data packet first Fragment of the CBx Command we are sending in this case the first fragment will be 28 bytes the maximum size of a packet when the output buffer is 32 bytes The entire CBx command we are planning to send over 3 fragments is 62 bytes In Byte 3 through Byte 30 the Master places the first 28 bytes of this CBx command See the Green changes below Output Buffer Input Buffer moser Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 7 6 5 4 He ER e a OE EEE 02 16 Packet Langen in bytes Poa Jon CBx Command word length MSB CBx Command word length LSB CBx Command Type Always AA CBx Command Opcode 0x06 Write Tag Data CBx Command byte not used CBx Command Node ID CBx Command Timeout MSB CBx Command Timeout LSB OxE8 1000 ms timeout CBx Command Start Address MSB CBx Command Start Address LSB address 0 CBx Command Length MSB CBx Command Length LSB 50 bytes CBx Command Data Byte CBx Command Data Byte CBx Command Data Byte CBx Command Data Byte CBx Command Data Byte CBx Command Data Byte CBx Command Data Byte CBx Command Data Byte CBx Command Data Byte CBx Comm
147. to terminate the connection e The TCP IP client software running on the host or PLC must connect to the TCP IP server BIS M 626 on port 2101 e Maximum number of words transferred to from an RFID tag per read write cycle 100 Words 200 Bytes e Disable any firewall services running on the PC Firewalls can potentially block communications between the BIS M 626 and the host and or PLC 7 2 STANDARD TCP IP IP CONFIGURATION VIA HTTP SERVER To configure the BIS M 626 for standard TCP IP 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 Among its features is the ability to modify and save changes to the controller s IP address which is stored internally on the BIS M 626 BIS M 626 Industrial Ethernet RFID Controller Default IP Address 192 168 253 110 103 gt BIS M 62 MANUAL 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 3 Press ENTER The HTTP Server Main Page will be displayed Description Station 1 Network Settings IP Address 192 168 253 110 Subnet Mask 255 255 255 0 Gateway IP Address 0 0 0 0 HF CN
148. to the Input Buffer and toggles Bit 0 of the IBCB amp IBDCB to indicate that the response is ready If the master has not acknowledged receiving the previous response the processor unit will not be able to place the response in the Input Buffer NOTE 135 BIS M 62 MANUAL See the Green changes below Output Input Buffer u eee Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 6 5 4 5 7 6 5 4 CS Cee EN ep 0 0 a pe E r Too eeso Command word Zen MSB CBx Response word length MSB Command word length LSB CBx Response word length LSB Command Type Minimum of 6 words Command Opcode E CBx Response Type Command byte not used AA Normal Response Command Node 1D CBx Response Opcode Command Timeout MSB 07 Command Echo of Tag Read ID Command Timeout LSB CBx Response Instance Counter Command Not Used CBx Response Node ID Command Not Used CBx Response Timestamp Month Command Not Used CBx Response Timestamp Day Command Not Used CBx Response Timestamp Hour CBx Response Timestamp Minute CBx Response Timestamp Second CBx Response Data length 8 bytes the Tag ID CBx Response Data Byte 1 Tag ID Byte 1 CBx Response Data Byte 2 Tag ID Byte 2 CBx Response Data Byte 3 Tag ID Byte 3 CBx Response Data Byte 4 Tag ID Byte 4 CBx Response Data Byte 5 Tag ID Byte 5 CBx Response Data Byte 6 Tag ID Byte 6 CBx Response Data B
149. uffer eet Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 6 5 4 5 1 0 PARIO PARO a po faeson I o o2 foc trasket lenge in bytes oz fo Command word a MSB Command word length LSB Command Type Command Opcode Command byte not used Command Node ID Command Timeout MSB Command Timeout LSB Command Not Used Command Not Used Command Not Used Command Not Used Data Consistency Byte OBDCB ee EN Data Consistency Byte IBDCB The Slave writes 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 Since the entire response fits in the buffer it does not need to use fragmentation The Slave also simultaneously makes the same changes to the IBDCB 131 BIS M 62 MANUAL See the Green changes below Output Input Buffer mere ere Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 82 6 5 4 5 83 7 6 5 4 3 2 ill 0 LOO LOTO CAPO REE Oti p00 Always 000 Always KA ozs foc racket length in bytes 02 Om packet length in bytes ____ Command word on MSB CBx Response word length MSB Command word length LSB CBx Response word length LSB Command Type Minimum of 6 words Command Opcode CBx Response Type FF Error Command byte not used CBx Response Opcode FF Error Command Node ID CBx Response Instance Counter Command Timeout MSB CBx Resp
150. unction Receive Data Transmit Data Signal Ground 33 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 5 SHIELD Figure 19 M12 5 pin B Coded Male Connector Profibus IN Function 5 Vdc Bus Power for termination A Line Data negative GND Bus Ground for termination B Line Data positive Shield Profibus Shield The Profibus OUT Connector M12 5 pin B coded Female is used for connecting the Processor unit to a Profibus network PIN 4 B Line PIN 5 SHIELD PIN 1 5 Vdc PIN 3 GND PIN 2 A Line Figure 20 M12 5 pin B Coded Female Connector Profibus OUT Function 5 Vdc Bus Power for termination A Line Data negative GND Bus Ground for termination B Line Data positive Shield Profibus Shield 34 INSTALLATION The Profibus models are ONLY powered through their VDC power connector M12 5 pin Male PIN 4 PIN 5 N C N C Not Connected Figure 21 M12 5 pin Male Connector Power Supply 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 PIN 5 N C PIN 4 N C PIN 3 N C N C N C Not Connected Figure 22 M12 8 pin Male Connector RS232 Function 3 Receive Data Transmit D
151. vailable on the Balluff Web site www balluff com When using node commissioning in RSNetWorx for DeviceNet modify only one parameter at a time either data rate or node address After changing the data rate you must manually cycle power to your DeviceNet network for the change to take effect Factory Default Configuration Data Rate 125Kb Node Address 63 114 DEVICENET INTERFACE O 8 2 4 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 However to ensure that messages to and from the Controller are properly delivered and received a handshaking mechanism has been implemented that uses a pair of dedicated words in the exchange The first two words in the Input Controller Tag and Output Controller Tag are dedicated to handshaking When new information is generated the data producing device increments the counter value stored in the second word of a controller tag either Input or Output depending on the device The data consuming device copies that same value to the counter in the first word of the reciprocal or opposite controller tag This handshaking scheme signals to the data producer that the information has been received The image below
152. weisquelle konnte nicht gefunden werden 1 2 HF SERIES FEATURES e High performance industrial multi protocol RFID processor units e Available support for multiple communication protocols Subnet16 M standard TCP IP Ethernet IP MODBUS TCP Profibus DP V1 and Profinet IO e Supports multiple interface connections RS232 RS485 Ethernet DeviceNet Profibus Profinet e Reads Writes ISO 14443A and ISO 15693 compliant RFID tags e Compatible with BIS m 1xx Series RFID tags from Balluff e Supports Balluff s ABx Fast amp CBx RFID command protocols e Operates at the internationally recognized ISM frequency of 13 56 MHz e Housed in rugged IP65 rated enclosure e LED status indicators display READY status COM activity RF activity and depending on the model Subnet16 Node ID DeviceNet Profibus or Profinet network status e Auto configurable and software programmable contains flash memory for firmware upgrades and internal configuration storage 1 3 ABOUT THIS MANUAL This manual provides guidelines and instructions for installing configuring and operating HF Series Processor units This document does NOT include explicit details regarding the HF Series Processor units commands Specific RFID command related information such as the process of issuing commands from a host PC or Programmable Logic Processor units PLC to the HF Series Processor units is available in the CBx Command Protocol Processor manual which is availabl
153. wing 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 The tabs are used to identify where input and output data is mapped for each identified node In the image below input data is mapped to start at 1 1 Data 0 0 on the PLC 6 Run the Scanner Configuration Applet and verify the mapping of the address where the PLC will write input data for the Controller 27 1756 DNB A 2 JEG General Module Scanlist Input Output ADR Summary Taas 963 Cob Poled 30 1 1 Data O 0 Unmap Advanced r gt Options Memory Assembly Data v Start Diwtord o E Bis 31 0 OTTO a 63 Cobalt DN Gatewa Data 3 Oo 63 Cobalt DM Gateway 1 1 Datal8 OK Cancel Apply Help Figure 62 1756 DNB A Input Properties Tab 112 DEVICENET INTERFACE O 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 0 Data 0 0 on the PLC 2 1756 DNB A len Co Polled 30 1 0 Data 0 0 Advanced gt Options Memory Assembly Data v Start Dyford 0 _ Bits 31 0 ES 1 0 Datall 10Datal 1 63 Cobalt DN Gateway 1 0 Dataldl Cancel Apply Help F
154. wnload the EDS file to the computer running your network s Rockwell Automation software i e the host computer 2 Using the EDS Hardware Installation Tool located in the RSLinx Tools program group import the EDS file into your RSNetWorx DeviceNet system Refer to Rockwell Automation s documentation for specific instructions 3 After you have imported the EDS file close and restart all Rockwell Automation programs If you are uncertain which programs to close cycle power to the host computer after importing the EDS file 108 DEVICENET INTERFACE gt 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 On the host computer start RSNetWorx for DeviceNet 2 Go online click NETWORK and select ONLINE a DeviceNet RSNetWorx for DeviceNet File Edit View Network Device Diagnostics Tools Help als ale 3 3 gt Online DeviceNet VT Categ KI a Cp n le U Dire KE Det to DeviceNet 7 DeviceNet Safety Scanner KE DeviceNet to SCANport KI Dodge EZLINK KI General Purpose Discrete UO IC Generic Device KT Human Machine Interface KT Inductive Proximity Switch I Limit Switch KT Motor Overload LA Properties ae Er DLC Figure 58
155. x Response Data Byte CBx Response Data Byte CBx Response Data Byte CBx Response Data Byte CBx Response Data Byte 31 182 Data Consistency Byte OBDCB Data Consistency Byte IBDCB The Master can see that Bit 3 of the IBCB amp IBDCB has been set to 1 so it knows that the response in the Input Buffer is just a fragment of a longer response and not a complete response and that there are more fragments to follow 145 BIS M 62 MANUAL The Master now toggles Bit 0 of the OBCB amp OBDCB to acknowledge that it has received the response fragment See the Green changes below Output Buffer Input Buffer EIERE Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 5 4 3 Er Command word Br MSB or Response word Er MSB CBx Command word length LSB CBx Response word length LSB Minimum of 6 words Minimum of 6 words CBx Command Type Always AA f CBx Response Type CBx Command Opcode AA Normal Response 0x05 Read Tag Data CBx Response Opcode CBx Command byte not used 05 Continuous Read Response CBx Command Node ID Response Instance Counter CBx Command Timeout MSB Response Node 1D CBx Command Timeout LSB Response Timestamp Month OxE8 1000 ms timeout Response Timestamp Day CBx Command Start Address MSB Response Timestamp Hour CBx Command Start Address LSB gt Response Timestamp Minute address 0 Response Timestamp Second CBx Command Length MSB
156. y Byte OBDCB 31 180 Data Consistency Byte IBDCB 142 PROFIBUS INTERFACE O Now that the command is in the Output Buffer The Master alerts the Slave that the command is ready lt 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 So if it is O it is toggled to 1 to indicate a new command If it is 1 it is toggled to 0 to indicate a new command If the bit is 1 setting it NOTE to 0 and then back to 1 will cause the command to be issued twice See the Green changes below Output Buffer Input Buffer Output Buffer Control Byte OBCB 6 5 4 3 2 1 GOE CN CN ON Oa a 00 gt OG gt OC Packet length in bytes CBx Command word length MSB CBx Command word length LSB Minimum of 6 words CBx Command Type Always AA CBx Command Opcode 0x05 Read Tag Data CBx Command byte not used CBx Command Node 1D CBx Command Timeout MSB CBx Command Timeout LSB OxE8 1000 ms timeout CBx Command Start Address MSB CBx Command Start Address LSB address 0 CBx Command Length MSB CBx Command Length LSB 50 bytes 30 31 82 Data Consistency Byte OBDCB Ets Jee Data Consistency Byte IBDCB 143 BIS M 62_ MANUAL When the Slave sees Bit 1 of the OBCB 8 OBDBC toggle it grabs the command from the Output Buffer The Slave then ackn
157. yte 7 Tag ID Byte 7 CBx Response Data Byte 8 Tag ID Byte 8 31 181 Data Consistency Byte OBDCB ER DR Data Consistency Byte IBDCB You can see the Tag ID in the data portion of the CBx response Tag ID E00401000E20DDAF The Master can see that Bit 0 of the IBCB amp IBDCB has been toggled so it knows that the response in the Input Buffer is ready Since Bit 2 is not set to 1 it knows that the response is complete not a fragment 136 PROFIBUS INTERFACE The Master now toggles Bit 0 of the OBCB amp OBDCB to acknowledge that it has received the response See the Green changes below Output Buffer Input Buffer moser Output Buffer Control Byte Input Buffer Control Byte OBCB IBCB 6 5 7 6 5 4 ORA eee Always 0 E K e Command word SE MSB or Response word Er MSB Command word length LSB CBx Response word length LSB Command Type Minimum of 6 words Command Opcode gt CBx Response Type Command byte not used AA Normal Response Command Node ID CBx Response Opcode Command Timeout MSB 07 Command Echo of Tag Read ID Command Timeout LSB Response Instance Counter Command Not Used Response Node 1D Command Not Used Response Timestamp Month Command Not Used Command Not Used Response Timestamp Day Response Timestamp Hour Response Timestamp Minute Response Timestamp Second Response Data length 8 bytes the Tag ID CBx Response Data Byte 1

BIS M-62_ Processor Unit

Contents

Download Pdf Manuals

Related Search

Related Contents