Anybus Communicator Configuration
Contents
1. Figure 34 Show Sub network 08 06 2012 KQ GNI EX Page 32 47 COGNEX 60 Suo network Monitor me File Colum ns Select All Deselect All i TRIGGER Produce L eremm F TRAIN FOCUS Froduce GET MATCH STRING Produce A SET MACH STRING Produce GET FOCUS VALUE Produce SET FOCUS VALUE Produce F CONFIG SAVE Produce n n Area 15 bytes 51 2 I n Sapa SSpSSS0S0500000000000 p zi E Trigger or or Ste tusbites Reserved Figure 35 Sub network monitor You can see the trigger bytes addresses green variable data blue for each transaction and if there is any address used by two different data it will appear in red see figure 35 Setting the Profibus Master There are two ways to add a Profibus slave to the Profibus DP Master simulator Manually by using the GSD file of the device in our case the Communicator Automatically by scanning the Profibus network e Manual configuration 1 Run the Profibus DP Master simulator 2 Click on the Open GSD bution and select the GSD file included in the CD of the Anybus Communicator see figure 36 08 06 2012 KQ GNI EX Page 33 47 COGNEX Open G50 Leok in z ESD Files Communication2. 2 Interface ysical Interface Serial El Module Control Status word Disabled Module Disabled El Protocol Protocol Mode Genenc Data Mode El Statistics Riecerve Counter Location 040015 Statistics Enable Transmi Aeceme Coumte Ttarizmil Counter Location 00016 Figure 10 Communicator part configuration The Transmit and Receive Counters indicate how many transactions have successfully been exchanged on the sub network They are used to help tracing errors during data exchange 08 06 2012 KQ GNI EX Page 12 47 COGNEX 6 Select the Sub Network part set the different parameters as the figure 11 Configuration Alphabetic Categorized El Communication Bitrate bits s 57600 Data bits 8 Parity None Physical standard 9232 Stop bits EndCharacter End character value 0x00 Use End character Disabled El StartCharacter Stat character value DxO Use Start character Disabled El Timing Message delimiter 10u 100 Figure 11 Sub Network configuration Setting up the Communicator communication part is done Next step is adding the DMCCs to the gateway Please refer to the command reference help file supplied with the DataMan SetupTool for more information Programming the DataMan Control Commands The following DMCCs will be configured on the gateway Trigger Train Focus Get Match String set Match String Get Focus Value Set Focus Value Config Save We will also see how to configure
3. Master Simulator PROFIBUS UART HMS Industrial ABC POP ID 1803 Figure 41 ProfiBus scanning The software scans all the slave addresses When a Profibus slave is found its corresponding icon is displayed Double click on the gateway Icon 4 When the slave Profibus is found click on the abort button then double click on the address of the slave found and click on the Ok button of warning popup message When the communication is established you can see the values of the Input Output data and the communication status displayed is connected 08 06 2012 KQ GNI EX Page 38 47 COGNEX Testing the DMCCs We will now test all the DMCC configured on the Communicator We will proceed for each DMCC as followed 1 Set the parameter value if any parameter is needed As an example the Trigger dmcc parameter is either ON or OFF 2 Change the trigger byte of the corresponding dmcc 3 The Communicator will then send the DMCC and display the DataMan reader response if any is expected TRIGGER command The parameter s address is on byte 2 3 and 4 We will first set this parameter to ON Set the bytes as shown in the tab below on the Output Data part Byte index Output Data Hexadecimal value ASCII character 3 ee n Edit 218 AF a ail of C Freeze Outputs mif lm Communication Active C Single Bit Mode Status Connected Parameter C
4. 79 4E 01001110 N 18 00 00000000 00 00000000 00000000 00 00000000 00 00000000 00 00000000 Oo DJ il 41 01000001 44 01000100 45 01000101 00000000 19 53 01010011 5 83 00 00000000 10 00 00000000 o 7 Figure 44 Decoded string display Mor Demy Oo mum Train Focus command This command is very similar to the first one The parameter is the same ON or OFF The only differences are the trigger and parameter addresses We will only see the ON parameter Set the bytes as shown in the tab below Byte index Output Data Hexadecimal value ASCII character 6 sdBd1B3 40185 6 8XC Change the value of byte 5 the reader should novv start the auto focus process Get Match Siring command This command doesn t need any parameter We only have to change the trigger byte value which is the 9 byte Then we can see in the Input Data part the current match string recorded on the reader 08 06 2012 KQ GNI EX Page 41 47 COGNEX Edit m TE B Bl 4131 l 11 ih L Freeze Outputs ei gt Communication Active C Single Bit Mode Status Connected Parameter Contig Output Data Input Data 76543210 AF momi O 78 01001110 N ooon 76543210 TA Y 01100001 2 01100010 63 01100011 54 01100100 01100101 66 01
5. COGNEX Edit T F F H H mi mimi vi L Freeze Qutputs ei gt Communication Active C Single Bit Mode Status Connected Parameter Config Output Data Input Data 15643210 25643210 00110100 4 ne 32 00110111 OO 00000000 00100010 22 L U n 11 1 15 23 0A 00001010 10 00000000 00 00000000 00000000 00 00000000 00 00000000 00 00000000 00000000 eo 32 00110111 7 5 7 1 110 00 00000000 Figure 48 new focus value 00000001 20 34 00110100 4 OO mal m On Re Go m 5 mu Config Save command We only need to change the trigger byte value for this command It is the last on byte number 30 There is only one way to verify that the configuration has been saved reboot your reader 08 06 2012 KQ GNI EX Page 45 47 COGNEX Notes and Limitations e One Anybus Communicator module has to be used for each DataMan reader of the Profibus network This restriction comes from the RS232 Serial communication RS232 Serial communication has no addressing functionality It doesnt allow sending commands to a specific device with Multi Port connection e The number of bytes available to program transactions is 244 bytes for each type of transaction even though the internal memory for the Input and Output data parts is bigger than 244 bytes this restriction comes from the Profibus slave specifications e T
6. we added the end characters CR LF We need to configure those end characters on the gateway Add a Word constant name it CRLF and set its value to OXODOA Train Focus DMCC This command is composed of Header gt e Command TRAIN FOCUS please note the space character between the command and the parameter e Parameter ON or OFF End characters CR LF II gt TRAIN FOCUS represents 15 bytes so we will need three DWords one Word and one byte as constants 08 06 2012 COGN Page 18 47 COGNEX Right click on the node and add a transaction Produce Name it TRAIN FOCUS Set its update mode to Change of state on trigger and its trigger byte address to 0x0204 see figure 18 Devices Configuration ey Fieldbus Alphabetic Categorized in Communicator AS 232 422 405 Ele subnetwork El General By 09200 Offline options for fieldbus Clear 81 22 TRIGGER Producel Update mode Change of state on trigger H E Reader Response Consume Timing a TRAIN FOCUS Produce Update time 10m 100 El Trigger Trigger byte address 020204 Figure 18 Train Focus transaction produce Add three DWords one Word and one byte as constant Configure them as shown in the tab below ASCII character Hexadecimal value Ox7C7C3E54 RAIN RAIN 0x5241494E Ox2E464F43 0x5553 SP space Right click on the transaction TRAIN FOCUS and add a Variable Data Name
7. Figure 32 connecting the Profibus cable Turn off the module power supply and configure the Profibus slave address of the Anybus Communicator Take off the plastic hatch located in front of the gateway and set the rotary switch with the desired address in this document the address used is 02 see figure 33 Then turn on the module power supply 08 06 2012 KQ GNI EX Page 30 47 COGNEX Figure 33 setting the communicator slave address Profibus Address Switch B x 10 Switch A x 1 Data description According to the configuration made in this document the data in the Input Data and Output Data part of the Anybus Communicator memory are organized as follow Input Data part 1 to 15 0 0000 to 000 Memory address Output Data part part 1 Memory 0 0201 to 0x0200 0x0203 0x0204 0x0205 to 0x0207 0x0209 Trigger Train Focus Set Match String command trigger Trigger status trigger Train Focus status trigger 08 06 2012 KQ GNI EX Page 31 47 COGNEX Output Data part part 2 Memory 0 020 to 0x0218 0x0219 021 0x02B to 0 021 0x021D Those tabs will help us to remember each bytes correspondence when using the ProfiBus master simulator Remember that the Anybus Configuration Manager Tool allows having an overview of the used input and output memory File Subnetwork Tools View Help 5 bed Sy
8. Produce Maximum Data length OxO00F H E Reader Response Consume El Operations FES TRAIN FOCUS Produce Byte swap No swapping E GET MATCH STRING Produce End Character Value z 2452 SET MACH STRING Produce Fill ur used Bytes Disabled Filler Value 000 Object Delimiter No Character Figure 23 New match string settings 08 06 2012 COGN Page 23 47 COGNEX e Get Focus value DMCC Requirements Reader must have a liquid lens for this command to be processed This DMCC looks like gt GET FOCUS VALUECRLF IleGET FOCUS VALUECRLF represents 20 bytes five DWords will be needed as constant data Right click on the node and add a transaction Produce Name it GET FOCUS VALUE Set its update mode to Change of state on trigger and its trigger byte address to 0x0219 see figure 24 Devices m Configuration oo ey Fieldbus Alphabetic Categonzed pone Communicator 52327422 455 E K Subretwork El General co DM200 Offline options for fieldbus Clear H E TRIGGER Produce Update mode Change of state on trigger H E Reader Response Consume El Timing ES TRAIN FOCUS Produce Update time 1 Orns 100 H E GET MATCH STRING Produce El Trigger FE SET MACH STRING Produce Trigger byte address 0 0219 H E GET FOCUS VALUE Froduce Figure 24 Get focus value transaction produce Add five DWord Constant and configure them as shown in the tab below ASCII chara
9. TRIGGER please note the space character between the command and the parameter The parameter ON or OFF End characters CR LF 1 Right click on the Node select Add Transaction Produce and name the transaction TRIGGER Set the update mode to change state on 08 06 2012 COGN EX Page 15 47 COGNEX trigger and set the trigger address to 0x0200 which is the first byte of the output memory see figure 13 Devices Configuration m ua Alphabetic Categorized oe Communicator 523224227 485 El Subnetwork General i A E 094200 Offline options for fieldbus Clear FE as Produce Update mode Change of state on trigger El Timing Update time 10m 100 El Trigger Trigger byte address 020200 Figure 13 Trigger transaction produce II gt TRIGGER represents 11 bytes so we will need two DWords one Word and one byte as constant data 2 Right click on the transaction TRIGGER add a DWord Constant and name it gt T Set its Value property to Ox7C7C3E54 It correspond to the hexadecimal value of the ASCII characters gt T see figure 14 Devices Configuration Alphabetic Categorized lag Fieldbus Communicator 52327422 455 Sat Subnetwork Kl duzu A IT DM200 Vale 0 7 2 3 4 F E TRIGGER Produce ie ay Te Figure 14 DWord Il 3 Add another DWord constant and name it RIGG Set its value to 0x52494747 hexadecimal
10. add a transaction Produce Name it GET MATCH STRING Set its update mode to Change of state on trigger and its trigger byte address to 0x0208 see figure 20 08 06 2012 COGN Page 20 47 COGNEX Devices Configuration ey Fieldbus Alphabetic Categorized Communicator RS 232r 422r AAN ay at Subnetwork 2 General 2 7 DM200 Offline options for fieldbus Clear H E TRIGGER Produce Update mode Change of state on trigger Ea Reader Response Consume El Timing AES TRAIN FOCUS Produce Update time 1 Orns 100 AE GET MATCH STRING Produce El Trigger Trigger byte address 020200 Figure 20 Get Match String transaction produce Add seven DWord Constant and configure them as shown in the tab below Devices Configuration ey Fieldbus Alphabetic Categorized Communicator Rs 23224227495 2 4 m subnetwork El General H E TRIGGER Produce 21 2 1 Reader Response Consume H E TRAIN FOCUS Produce A GET MATCH STRING Produce Br b z ETD a ir VALI if DMA if TCH if STAI r MR Figure 21 Get match string produce The response of the reader to this command is the trained match string t vvill be followed by the characters CR LF so the response will be stored in the previously configured Reader Response transaction consume 08 06 2012 COGN Page 21 47 COGNEX Set Match String DMCC Requirements The match string val
11. it r En ml H z 1805 i eeen Documents My Network Fie nama HMSE 1883 ged Ss Fie ol oe m mi Cancel Figure 36 loading the GSD file Two GSD files are provided the HMSB1803 gsd file has to be used with the C versions of AB7000 model and the HMS_1803 gsd file has to be used vvith the B versions of AB7000 model Please note that the GSD files are also available on HMS vvebsite 3 Add the necessary number of input and output bytes According to the configuration made 15 bytes are necessary for input data and 30 bytes are necessary for output data see figure 37 Then click on the Ok button 08 06 2012 CoO GNEX lt Page 34 47 Module List INPUT 8 Bute 4 word INPUT 16 Byte 8 word INPUT 52 Byte 16 word INPUT 64 Bute 32 word INPUT 126 Byte word OUTPUT 1 Byte OUTPUT 2 Bute 1 word OUTPUT 4 Bute 2 word OUTPUT 8 Bute 4 word OUTPUT 16 Byte 8 word NITRPUIT 42 Bake 116 mardi 4 ill Default Parameter Figure 37 Configuration Editor Current Configuration o Byte 4 word 4 Byte 2 word 2 Byte 1 word 1 Byte 16 Byte 8 word Byte 4 word 4 Byte 2 word 2 Byte 1 word Curent Parameter Cancel 4 Click on the Communication Settings button set the Current Master Address to 1 and the COM port with the serial port number corresponding to the Anyous Communicator module see figure 38 Figure 38 ProfiBus ma
12. on No Read Step Size Update on Validation Failure Figure 6 Match string validation 08 06 2012 CoO GNEX lt Page 9 47 COGNEX Anybus Communicator Configuration Setting up the Anybus Communicator 1 Install the Anybus Communicator Configuration software on your PC to configure the Communicator You will find the installation files of the software on the CD delivered with the Anybus Communicator 2 Connect the Configuration Cable to the Anybus Communicator then connect the Configuration Cable to the serial port of your PC see figure 7 Figure 7 Configuration cable 08 06 2012 Page 10 47 COGNEX 2 Supply the Anyous Communicator with an external 24 Volts 280 mA power supply For more information about the electrical specifications of the Anybus Communicator please refer to the HMS documentation 3 Launch the Anybus Configuration Manager Tool software When you use this software for the first time a wizard window appears and permits to be assisted to create the configuration In this document this wizard is not used select Blank Configuration and click on the Ok button see figure 8 Ge Anybus Configuration Manager Communicator RS232 422 485 Untitled 14 46 File Fieldbus Tools View Help Dekndsailiuiikmxrmsms 90ence buanu Ge Select Configuration Devices E Fieldbus J Communicator AS232
13. the gateway to receive data decoded by the reader Please note that any DMCC can be configured and used as long as it Is supported by the DataMan reader 08 06 2012 KQ GNI EX Page 13 47 COGNEX Creation of the node on the Sub Network 1 Right click on the Sub Network select Add node name the node with the Hostname of the reader We will name it DM200 Set the slave address to 1 see figure 12 Devices Configuration F Fieldbus TEE EEN Communicator Roederer ed Eid Subnetwork General C M200 slave address Figure 12 add node The packets exchanged on the Sub Network are represented by transactions Two types of transaction are used e The transaction Produce to send the DMCC from the Gateway to the DataMan e The transaction Consume for responses sent by the reader Transactions can contain Constant Variable Data Checksum etc The data exchanged on the sub network and the data exchanged on the higher level network reside in the same internal memory This memory is divided in three parts here we will use e The Input Data from address 0x0000 to Ox01F3 Used by the transactions Consume Output Data from address 0x0200 to Ox02F3 Used by the transactions Produce Configuring transactions General configuration e Several constant data can be added to a transaction These are used to configure the static part of the command Once added to the transaction these data
14. value of ASCII characters RIGG 4 Add a Word constant name it ER and set its value to 0x4552 Hexadecimal value of ASCII characters ER 5 Add a byte constant name it space and set its value to 0x20 6 Right click on the transaction TRIGGER and add a Variable Data Name it trigger status It will be the parameter of the trigger command 08 06 2012 COGN Page 16 47 COGNEX a Set its address to the next available byte of the output memory 0x201 b The parameter of the TRIGGER command can be either ON or OFF so we will need at most three bytes Set its maximum length to 3 c No modification is needed for the other parameters see figure 15 Devices Configuration Hgt Fieldbus Alphabetic Categorized Communicator 5232 422 4595 Bee Subnetwork El General 2 ok 200 Data location 00201 E TRIGGER Produce Maximum Data length 0 000 5 7 Operations Eyle swap No swapping End Character Value Fill un uzed Bytes Disabled Filler Value 0200 Object Delimiter Character Figure 15 Trigger status settings 7 Add a last Word constant for the end characters CRLF Name it CRLF and set its value to OxODOA e Receiving data from the DataMan reader A transaction consume is needed to get data decoded by the reader Right click on the Node and select Add Transaction Consume Name the transaction Reader Response You shouldn t have to mod
15. 100110 57 01100111 01101000 00000000 11 OO 00000000 12 OO 00000000 13 OO 00000000 x Fe Go nl mm m 5 n 14 00 00000001 Pff 15 00 00000000 19 00 00000000 16 OO 00000000 10 00 00000000 Figure 45 Current match string display set Match String command For this command we have to enter the new match string the double quote CR and LF end characters We will set the new match string to new string set the following value Hexadecimal value es 7 6E 65 5 s 77 00 20 7 58 73 1h 1V 74 5 7 88 o 20 72 r 1 1 1 1 1 S 1 1 1 1 6E n 2 67 22 2 3 4 5 6 7 8 9 0 1 2 3 08 06 2012 KQ GNI EX Page 42 47 COGNEX Now change the value of byte 10 to trigger the DMCC You can verify the new match string value with the SetupTool software or using the previous DMCC Get Match String Change the value of byte 9 to see the new match string Edit foo zl EL sf 41 31 l if at L Freeze Outputs ei gt Communication Active C Single Bit Mode Status Connected Parameter Contig Output Data Input Data FER43210 16543210 01101110 01100101 01110111 00100000 01110011 01110100 01110010 01101001 00000001 01101110 01100101 01110111 00100000 01
16. 110011 01110100 01101110 01100111 Oo OOO Fe Oo Figure 46 new match string display Get Focus Value command This command doesn t need any parameter so we only have to change the trigger byte to send the DMCC Change the value of byte 26 You should then receive the current value in the Input Data 08 06 2012 KQ GNI EX Page 43 47 COGNEX Edit EH 7V BB 4131311 th L Freeze Outputs Communication Active 1 Single Bit Mode Status Connected Parameter Contig Output Data Input Data FER43210 FER43210 1 00110011 3 2 36 00110101 5 53 3 00 00000000 4 00 00000000 D 5 00 00000000 16 oo 00000000 7 D 8 D OOOUTTOT 23 00001010 10 00000000 00 00000000 00 00000000 118 00 00000000 23 OO 00000000 1110 00 00000000 Figure 47 Get Focus Value results 00000000 29 00 00000000 With my current settings the focus is set to value 35 Set Focus Value command This command has only one parameter the new focus value which is coded on two bytes We will set the new value to 47 Byte index Output Data Hexadecimal value ASCII character 2 75 2 28 4 Now change byte 27 value to trigger the DMCC As shown previously you can verify the new value using the SetupTool or by sending the Get Focus Value command To do so change the value of byte 26 08 06 2012 KQ GNI EX Page 44 47
17. 74 cae Subnetwork Cancel Blank Configuration ATU Master A Wizard option will guide you through and explain all steps of a configuration The output froma wizard will result working configuration ready to download lt iz also possible to edit the configuration in the standard configuration tool after Wizard completion The Elank Configuration option will open the standard configuration tool and a configuration can be created from scratch Here itis also possible to open an existing configuration from file or via upload from a Communicator module Don t show this Window again Fields E 8 17 2012 9 54 AM Contig Line Figure 8 Anybus Configuration Manager Tool startup The Anybus Communicator is divided in three parts e The Fieldbus that corresponds to the Profibus network The Communicator which contains the settings of the gateway e The Sub Network which corresponds to the serial communication with the DataMan reader 08 06 2012 KQ GNI EX Page 11 47 COGNEX 4 Select the Fieldbus part and check that the Fieldbus type is set to Profibus DP see figure 9 Configuration Alphabetic Categorized ET Fieldbus Fieldbus Type Protibus DP Fl Fieldbus Communicator 2527422 465 El p Subnetwork 4 Figure 9 FieldBus configuration o Select the Communicator part set the different parameters as shown in figure 10
18. COGNEX The information contained in this document has been developed solely for the purpose of providing general guidance to Cognex customers who need to configure communications between an DataMan reader and a Profibus Master using an Anybus Communicator module and data contained in this document serves informational purposes only The information in this document is proprietary to Cognex No part of this document may be reproduced or transmitted in any form or by any means electronic or mechanical including photocopying without the written permission of Cognex Information in this document does not represent a commitment on the part of Cognex and in especially is not intending to be binding upon Cognex to any particular course of business Cognex assumes no responsibility for errors or omissions in this document Cognex does not make any express or implied representation or warranty as to the accuracy or completeness of the information for a particular purpose Cognex shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of this document 08 06 2012 COGN Page 1 47 COGNEX Overview This document describes how to configure the communication between a DataMan reader and a Profibus Master using an Anybus Communicator module This document includes the following topics UVEVEe 60 eteene cee se ene pee cee ea ee ences be
19. Output Data Input Data 75543210 7155453210 1 00000000 12 4 01001111 r9 amp 4 01001110 WN hiz 00 00000000 4 00000000 4 00 00000000 Figure 42 Trigger status to 1 OO 0 0000000 R 00000000 2 II 08 06 2012 KQ GNI EX Page 39 47 COGNEX Now change the first byte value to 1 or anything but 0 As we set the trigger mode to continuous in the beginning it is triggering continuously Depending of the trigger mode the trigger should have triggered once or several times In Continuous trigger mode the reader acquires images until he decodes a code or until we send him the Trigger command with the parameter OFF Thats what we will do first Set the bytes as shown in the tab below Change byte 1 value The reader should have stopped triggering We will ask the reader to trigger once again and this time we will put a code inside its field of view Once decoded the output string should be displayed in the Input Data part of the Master simulator Figure 43 Sample 1D code 08 06 2012 KQ GNI EX Page 40 47 COGNEX Edit m ZF sl sf 3 20 if iv L Freeze Outputs Communication Active LI Single Bit Mode Status Connected Parameter Contig Output Data Input Data 76543210 76543210 1 01000001 2 43 01000011 4 45 01000101 4 53 01010011 50 01010000 E 8 AF 01001111
20. can t be changed e The bigger constant data is the DWord 4 bytes You might have to parse your static data into several DWords Words or bytes to fit the whole static part 08 06 2012 COGN EX Page 14 47 COGNEX e Only one variable data can be added Its size is configurable This variable data can be modified by the Profibus master and will be used for the parameter of the command Transaction Produce parameters e Offline options for fieldbus set to Clear will clear the data when the fieldbus goes offline e There are several Update modes o Cyclically the command is sent repeatedly o On data change command sent once the variable data value changes o Single shot command sent only once when the gateway starts o Change of state on trigger command sent when the trigger byte value is changed on the Profibus side This is the mode we will use in that documentation e The Update Time is the interval between two commands when using the cyclically update mode e The Trigger byte address allows us to set the address of the trigger byte Address starting from 0x0200 can be used e Transaction Consume parameters e Only the Offline timeout time needs to be configured It defines after how long the data received from the DataMan reader will be cleared e The Trigger part is no used for this kind of transaction with our products e Trigger DMCC This command is composed of Header gt e Command
21. cter Hexadecimal value 0x7C7C3E47 0x45542046 OCUS OCUS 0x4F435553 0x2E56414C UE CRLF UE CRLF 0x55450D0A e Set Focus value DMCC Requirements Reader must have a liquid lens for this command to be processed This DMCC looks like gt SET FOCUS VALUE value CRLF 08 06 2012 COGN Page 24 47 COGNEX IleGET FOCUS VALUE represents 19 bytes four DVVords one Word and one byte will be needed as constant data Right click on the node and add a transaction Produce Name it SET FOCUS VALUE Set its update mode to Change of state on trigger and its trigger byte address to 0x021A see figure 25 Devices Configuration Er Fieldbus Alphabetic Categorized Communicator AS 2327 4227485 Ely Subnetaork El General a 1200 Offline options for fieldbus Clear H E TRIGGER Produce Update mode Change of state on trigger EJ Reader Response Consume El Timing EZ TRAIN FOCUS Produce Update time 1 Ons 100 2 GET MATCH STRING Produce El Trigger 1 1 SET MACH STRING Produce Trigger byte address 00214 EJ GET FOCUS VALUE emj GET FOCUS VALUE Produce Figure 25 Set focus value transaction produce 08 06 2012 KQ GNI EX Page 25 47 COGNEX Add four DWord Constant one Word Constant and one byte Constant Configure them as shown in the tab below ETF Add a variable data name it focus value and set its address to 0x021B The focu
22. d Imager Settings Operation Settings Image Display Interval 200 ime Live Display Trigger delay ms 0 Light Settings Trigger Type Continuous extemal Figure 3 DataMan trigger mode 08 06 2012 COGN EX Page 6 47 COGNEX 3 Go to the communication settings and set the settings as shown in figure Communication Settings Data Bits Stop Bits L Enable Multi Port RS 232 Sharing Figure 4 Communication settings 08 06 2012 CoO GNEX lt Page 7 47 COGNEX 4 Go to the data formatting options and enable the standard formatting Add the full string to the output data and cross the CR LF checkbox The CR LF characters will be used as terminating characters you can set whatever you want as long as you configure the gateway accordingly See figure 5 Data Formatting 1D Stacked Postal Leading Text Remove Figure 5 Data formatting 08 06 2012 CoO GNEX lt Page 8 47 COGNEX 5 Last setting is to enable the validation match string for the Data Matrix symbology Set the match string value to abcdefgh see figure 6 Data Validation D Stacked Postal 7 None DoD UID Validation 7 150 Validation 7 651 Match String Validation 7 Pattem Matching Validation Match String sbedefgh F Increment Decrement Numerical Component Start Position Length Auto Update
23. d0ctineni5 47 08 06 2012 COGN EX Page 2 47 COGNEX The Anybus Communicator module acts as a gateway between serial application protocol and PROFIBUS DP based network The standard RS232 is used on the sub network between the DataMan reader and the Anybus Communicator The Profibus communication is used between the Anybus Communicator and the Profibus Master the gateway acts as a PROFIBUS DP slave m Profibus Network computer Configuration via o rr x ee PLC ProfiBus Master Anybus Communicator ProfiBus Slave serial Communication DataMan Reader serial communication Figure 1 Anybus connection overvievv 08 06 2012 KQ GNI EX Page 3 47 COGNEX The Anybus Communicator can be used to set up specific DataMan Control Commands to be sent to the sub network to the DataMan The sending of DMCCs is triggered by the Profibus master It also allows modifying the parameters of the DMCCs and getting the DataMan response Three steps are needed to configure the Communicator 1 First one is the communication between the DataMan reader and the Anybus Communicator 2 Next one is the communication between the Anybus Communicator and the Profibus Master 3 Last one is to configure the DMCCs needed on the Anybus Communicator Needed hardware The Profibus Communicator AB7000 model includes the following components
24. e The Anybus Communicator module e The configuration cable to connect the gateway to the PC e The CD with documentation the GSD file and the Anybus Configuration Manager software needed for the Anybus Communicator configuration The following items will be needed to use a DataMan reader with the Communicator e Profibus master in this document the Profibus DP Master simulator software will be used Cable to connect the Anybus communicator to the Profibus Master e DataMan reader In this document a DataMan 200 will be used but any reader is supported as long as it uses serial communication e DataMan 200 RS232 cable RS232 female to male adapter to connector the DataMan serial cable to the Anybus communicator 08 06 2012 COGN EX Page 4 47 Connecting the DataMan reader to the AnyBus Communicator Connect the Dataman Rs232 cable to the DB9 female connector of the Anybus communicator see figure 2 Figure 2 Connection between the DataMan and the Communicator 08 06 2012 KQ GNI EX Page 5 47 COGNEX Configuring the DataMan reader some settings need to be modified on the DataMan to communicate with the Communicator 1 Connect the reader using the SetupTool Version 4 4 1 will be used in this documentation 2 Set the trigger mode to continuous This step is not a requirement but the testing of the DMCCs in the last part of this documentation are made according to the Continuous trigger mode Light an
25. e nes EA bocce ones tense eee 2 177600 0101006607 4 Connecting the DataMan reader to the AnyBus Commuhnicator 5 Configuring the DataMan reader 6 Anybus Communicator Configuration 10 Setting up the Anybus Communicator 10 Programming the DataMan Control Commands 13 Creation of the node on the Sub Netvvorlk s 14 COMMUTING 14 Loading the configuration to the Commuhnicator 29 Connecting the Anybus Communicator to the Profibus Master 30 1400000000 aa ssda 31 Seting 06001 Master ayan 33 OSU TNC ii 39 TRIGGER COMMANA rr as 39 1717006000 41 Get Match String commandq 41 Set Match String 42 Get Focus Value commandq 43 Set FOCUS Value Pa 44 CONTIGO Ve command sb 45 Notes and Limilat015 Damas b 46 Related
26. he maximum Baud rate for serial communication supported by the Anybus Communicator is 57600 bps compared to DataMan readers which support up to 115200 bps e The signals necessary for the serial communication with the Anybus Communicator are the signals RS232 Rx RS232 Tx and the Ground The maximum Baud rate supported by the Anybus Communicator for Profibus communication is 12 Mbit s The communication speed will depend of the baud rate of the Profibus Master the Anybus Communicator will automatically detect the baud rate used by the Profibus Master e The time before the data are valid and available for the Profibus network or for the subnetwork is at maximum 15 ms The latency of the Anybus Communicator can vary from 10 to 15 ms according to the number of bytes mapped e A Consume transaction cannot be associated to a specific Produce transaction When packets arrive on the subnetwork of the Anybus Communicator all the Consume transactions that match the packet format will be updated To be compatible a Consume transaction should have a specified memory range that can contain all the data received and a structure adapted to the data For example if you create a Consume transaction with at the beginning a Constant equal to the ASCII character S if the packet received does not contain a S character at the beginning the Consume transaction will be not updated e Only one Variable data can be present in a transaction It
27. idation has to be enabled in the DataMan reader configuiration for the commands to be correctly executed You might have to change the data validation programming target using the DMCC DVALID PROG TARG By default once the data validation is enabled it is set to datamatrix This DMCC looks like SSET DVALID MATCH STRING my string CRLF This command will allow us to set the match string from the Profibus master It is a little bit tricky to use because of the string parameter which has to be encapsulated by double quotes According to how we configured the previous commands we would expect to use a variable data for the string only but we will have to add the last double quote CR and LF end characters Please see a detailed explanation below lf using a variable data of 15 bytes for the string parameter only the command sent by the gateway would look like 5SET DVALID MATCH STRING xxxxxxxxxxxxxxx CRLF Where xxxxx is the string parameter When sending 15 bytes from the Profibus master the command will work but if less than 15 bytes are sent then null characters will be received by the reader Those characters can t be added to a string so the reader won t process the command For that reason the variable data will have to contain the match string and the end characters of the command which are double quotes CR and LF IESET DVALID MATCH STRING represents 28 bytes seven DWords will be
28. ify any settings see figure 16 Devices mn E l Configuration ey 77 Alphabetic Categorized lt Communicator AS 232 422 455 El Subnetwork El General T 09200 Uttline options for sub network Clear H E TRIGGER Produce El Timing ees Reader Response Consume filine timeout time 1 100 O Trigger Trigger byte Disabled Trigger byte address Figure 16 Reader response transaction consume 08 06 2012 COGN Page 17 47 COGNEX Add a variable data by right clicking on the transaction consume previously created Name it output string As for the variable data of a transaction produce we need to set its address This data will be stored in the input memory We will set its address to the first byte available 0x0000 Depending on the code or codes you are expecting to decode the maximum data length might have to be modified We will set it to 15 bytes X000F see figure 17 Devices Configuration m Fieldbus Alphabetic Categorized Communicator Ra 232 422 48 i lye Subrnetwork El General l E m 0200 Data location 020000 H E TRIGGER Produce Maximum BE en ee 0000 2 2 2 Reader Response Consume El Operations ar output string Bute swap No swapping End Character Value Fill un used Bytes Disabled Filler Value U Object Delimiter Character Figure 17 Output string settings When setting up the DataMan reader
29. is a restriction of the Anybus communicator 08 06 2012 COGN EX Page 46 47 COGNEX Related documents The latest user manual the GSD file and the Anybus Configuration Manager software for the Anybus Communicator can be found on the HMS website http VvvVVV anybus com support support asp P1D 1048 ProductType Anybus 08 06 2012 KQ GNEX lt Page 47 47
30. it focus status Set its address to 0x0205 As for the TRIGGER command the parameter is either ON or OFF so the maximum length of this data is three bytes see figure 19 08 06 2012 COGN Page 19 47 COGNEX Devices Configuration o Fieldbus Alphabetic Categorized Communicator 52322422 455 El Subnetwork E General H E 1200 Data location 00205 AES TRIGGER Produce Maximum Data length 0 40005 AES Reader Response Consume 2 Operations l A E TRAIN FOCUS Producel 5 7 1 7 End Character Yale 0400 Fill un used Bytes Disabled Filler Value 0200 Object Delimiter Character Figure 19 Focus status settings Add a last Word constant for the end characters CR LF Name it CRLF and set its value to OxODOA We are done programming the train focus command Get Match String DMCC We will now add a command to get the currently trained match string Requirements The match string validation has to be enabled in the DataMan reader configuration for the commands to be correctly executed You might have to change the data validation programming target using the DMCC DVALID PROG TARG By default once the data validation is enabled it is set to datamatrix This DMCC looks like gt GET DVALID MATCH STRING CRLF l5 GET DVALID MATCH STRING CR LF represents 28 bytes so we will need seven DWords as constant Right click on the node and
31. needed as constant data As explained above a variable data is needed for the new match string the double quotes and the CR and LF end characters We will set its maximum length to 15 bytes Right click on the node and add a transaction Produce Name it SET MATCH STRING Set its update mode to Change of state on trigger and its trigger byte address to 0x0209 see figure 22 08 06 2012 COGN EX Page 22 47 COGNEX Devices z Configuration ey Fieldbus Alphabetic Categorized Communicator AS 232 422 485 Ee subnetwork E General Ey 09200 Offline options for fieldbus Clear H E TRIGGER Produce Update mode Change of state on trigger H E Reader Response Consume El Timing l H E TRAIN FOCUS Produce Update time 1 100 E GET MATCH STRING Produce E Trigger SET MACH STRING Produce Trigger byte address 00209 Figure 22 Set match string transaction produce Add seven DWord Constant and configure them as shown in the tab below ASCII character G ETD VALI D MA TCH STRI NG SP space Add variable data name it new match string CRLF set its address to 0x020A and length to OxOOOF see figure 23 Devices Configuration m m Fieldbus Alphabetic Categorized Communicator AS 232 422 455 El Subnetwork El General By 09200 Data location 0 0 04 E TRIGGER
32. ommunication with the Anybus Communicator module see figure 29 File ECRLF Tools View Help Cah 5 5 amp x Fe TEFIE Figure 29 Connecting to the Communicator Then transfer it to the Anybus Communicator by clicking on the Download to Communicator button see figure 30 File Subnetwork_ Tools View Help Oe a af ms Xi Eu Download to Communicator 5232 422 485 efi skiers Cr Figure 30 Downloading the configuration to the Communicator At the end of the configuration transfer the Led 6 presents on the module should be green and flashing see the figure 31 Figure 31 Communicator led status You can then save the configuration to your computer and close the Anybus Configuration Tool software 08 06 2012 KQ GNI EX Page 29 47 COGNEX Connecting the Anybus Communicator to the Profibus Master In this document the Profibus master used is a Profibus DP Master simulator software from HMS Install the Profibus DP Master simulator software on your computer by following the HMS software instructions Disconnect the configuration cable from the serial port of your computer and connect the Anybus communicator to the Profibus DP Master In this document connect the Anybus communicator to the serial port of my computer using a Profibus RS232 converter and the cable delivered vvith the Profibus DP Master simulator see figure 32
33. s value can vary between 25 and 56 We will need two characters so set its length to 0x0002 see figure 26 Devices Configuration m Fieldbus Alphabetic Categorized Communicator AS 23224222455 Saat Subnetwork El General T 09200 Data location 020218 H E TRIGGER Produce Maximum Data length Ox0002 H E Reader Response Consume El Operations GES TRAIN FOCUS Produce Byte swap No swapping H E GET MATCH STRING Produce End Character Value 00 H E SET MACH STRING Produce Fil un used Bytes Disabled H E GET FOCUS VALUE Produce Filler Value 00 FE SET FOCUS VALUE Produce Object Delimiter No Character Figure 26 focus value settings Now we only need to add the end characters CR and LF Add a Word Constant and set its value to OxODOA Contig Save DMCC This command is not difficult to configure as there is no parameter but it is definitely useful When all the needed modifications are applied to the DataMan 08 06 2012 COGN Page 26 47 COGNEX settings it is a must to save the current configuration so that the reader will run it next time it boots This DMCC looks like gt CONFIG SAVE CRLF We only need constant data here a total of 16 bytes four DWords will be used as constant Right click on the node and add a transaction Produce Name it CONFIG SAVE Set its update mode to Change of state on trigger and its trigger byte address to 0x021D see figure 27 De
34. ster settings 08 06 2012 COGNEX Page 35 47 COGNEX 5 Click on the Communicator Windows button set the Current Slave Address to 2 see figure 39 O Ex Diag l Stat Diag 3 C Pim Fault m sara aa T ar Faut Diag Ovestlow L Freeze Outputs Communication Active Idera Number 7 Single Bat Mode Paamte 17 Output in Input User Diagnose 76543210 LL Figure 39 ProfiBus slave settings 08 06 2012 CoO GNEX lt Page 36 47 COGNEX 6 Click on the Start with GSD button click on the Ok button of the warning popup message see figure 40 S Fle Address Communication Window Extra NOS O Ext Diag Curera Slave Address 7 Stat Diag El Pim Faut Eda M T ar zr arar T of Clg Fault O Disg L Freeze Output Eommunucaban Acts ident Humber S L Single pi Mode ie aa Pawsa Dupa Dala Figure 40 Start ProfiBus Master with GSD 08 06 2012 CoO GNEX Page 37 47 COGNEX e Automatic configuration 1 Run the Profibus DP Master simulator 2 Click on the Communication Settings button set the Current Master Address to 1 and the COM port with the serial port number corresponding to the Anybus Communicator module 3 Click on the Start Search PROFIBUS slave address button see figure 41 amp PROFIBUS DP Master Simulator Searching 30 File Address Communication Window Extra 63 Search Slaves a
35. vices Configuration Glee Fieldbus Alphabetic Categorized Communicator 5 23274227485 El Subnetwark El BEDEN oer 64200 Offline options fieldbus Clear H E TRIGGER Produce Update mode Change of state on trigger H E Reader Response Consume El Timing A E TRAIN FOCUS Produce Update time 1 Orne 100 H E GET MATCH STRING Produce El Trigger H E SET MACH STRING Produce Trigger byte address 020210 H E GET FOCUS VALUE Produce HES SET FOCUS VALUE Produce z CONFIG SAVE Produce Figure 27 Config Save transaction produce Add four DWord Constant and name them as shown in the tab below ASCII character Hexadecimal value 0x7C7C3E43 ONFI ONFI Ox4F4E4649 G SAV G SAV x472E5341 E CRLF E CRLF 0x56450D0A 08 06 2012 COGN Page 27 47 COGNEX Devices H Fieldbus z Communicator 5 25274222465 Ely Subretwork EL T 0200 H E TRIGGER Produce H E Reader Response Consume E4 TRAIN FOCUS Produce Eq GET MATCH STRING Produce SET MACH STRING Produce GET FOCUS VALUE Produce SET FOCUS VALUE Produce CONFIG SAVE Produce Figure 28 Config Save settings The configuration of the gateway is now done 08 06 2012 Configuration Alphabetic Categorized 2 General Value Oe 564500 04 COGNEX Page 28 47 COGNEX Loading the configuration to the AnyBus Communicator Click on the Connect button to establish the c
Download Pdf Manuals
Related Search