Handbuch Identifikations-Systeme BIS Kompaktauswerteeinheit BIS M S115 M S115_841305_0611_en.p65

Transcription

1 1 Handbuch Identifikations-Systeme BIS Kompaktauswerteeinheit BIS M S115 English please turn over! 2 No D/E Edition 0611 Subject modification. Replaces edition Balluff GmbH Schurwaldstrasse Neuhausen a.d.f. Germany Phone Fax balluff@balluff.de

2 3 Contents Safety Notes... 4 Introduction BIS M-4 Identification System... 5/6 Basic knowledge f using the BIS M-4 Process... 7 Configuration Err Numbers... 29/30 Read/Write Times Installation Interface Infmation Connection Diagrams Technical Data Ordering Infmation Accessies Appendix, ASCII Table Safety Notes Proper use and operation Installation and operation Deployment and inspection Malfunction Scope BIS M-4 process gether with the other BIS M system components comprise the Identification System and may only be used f this purpose in industrial applications cresponding Class A of the EMC Directive. Installation and operation are permitted by trained specialists only. Unauthized modifications and improper use will result in loss of the right make warranty and liability claims. When installing the process, follow exactly the connection diagrams provided later in this document. Take special care when connecting the process external controllers, especially with respect the selection and polarity of the connections including the power supply. Only approved power supplies may be used. F specific infmation, the Technical Data section. When deploying the identification system, all relevant safety regulations must be followed. In particular, measures must be taken ensure that any defect in the identification system does not result in a hazard persons equipment. This includes maintaining the permissible ambient conditions and regular inspection f proper function of the identification system and all the associated components. At the first sign that the identification system is not wking properly, it should be taken out of service and guarded against unauthized use. This document applies the process BIS M-40_ _-00-S115. 4

3 5 Introduction BIS M-4 Identification System This manual is intended guide the user in installing and commissioning the components in the BIS M-4 identification system, so that start-up time is reduced an absolute minimum. Principle Applications System component function The BIS M-4 identification system belongs the categy of non-contacting systems, which can both read and write. This dual function permits uses where not only infmation permanently sred in the data carrier can be transpted, but also current infmation can be collected and transpted. The main areas of application include in production f controlling material flow (e.g., f part-specific processes), in wkpiece transpt using conveying systems, f obtaining safety-relevant data, in process materials ganization. The process and the read head fm a compact unit which is contained in a housing. The data carrier represents an independent unit. It does not require line-fed power and receives its energy from the integrated read head in the BIS M-4 identification system. The read head continuously sends a carrier signal which supplies the data carrier as soon as the latter has reached the required distance from the read head. The read/write process takes place during this phase. This may be static dynamic. The data are output serially and made available the host system. These host systems may be: a control computer (e.g., industrial PC) having a serial pt, a programmable logic controller (PLC). 5 6 Introduction BIS M-4 Identification System System components The main components of the BIS M-4 identification system are the process with integrated read head, and the data carrier(s). Connections host system Connections host system BIS M BIS M Schematic representation of an identification system (example) Data carriers BIS M-1.. 6

4 7 BIS M-4 Process Basic knowledge f application Data integrity with CRC_16 When sending data between the read/write head and the data carrier a procedure is required f recognizing whether the data were crectly read written. The process is supplied with standard Balluff procedure of double reading and comparing. In addition this procedure a second alternative is available: CRC_16 data checking. Here a test code is written the data carrier, allowing data be checked f validity at any time location. Advantages of CRC_16 Data checking even during the non-active phase (CT outside read/write head zone). Shter read times since each page is read only once. Advantages of double reading No bytes on the data carrier need be reserved f sring a check code. Shter write times since no CRC needs be written. Since both variations have their advantages depending on the application, the user is free select which method of data checking he wishes use ( Configuration 8-15). To use the CRC check method, the data carriers must be initialized. You use either data carriers with the data map facry configured (all data are 0), you must use the process write the special initialization command 'Z' the data carriers. It is not permitted operate the system using both check procedures! 7 8 Configuration Befe programming, the process configuration must be carried out, in case the facry settings will not be used. Configuration is done using a computer and the Balluff software Configuration software BIS, and it is sred in the process. It may be overwritten at any time. The configuration can be sred in a file, making it accessible when required. No data carrier is allowed in front of the read head while configuring the process. 8

5 9 Configuration Interface BIS M-4 The first screen shows the parameters baud rate, number of data and sp bits, and parity type f the serial interface selected. The graphic shows the facry settings. The other settings are carried out in the cresponding masks which are illustrated in the following Configuration Parameters BIS M-60_0 10

6 11 Configuration Procol Type Examples f terminating telegrams: Operation with blockcheck BCC is facry set. F host devices which require a terminar, the additional use of Carriage Return 'CR' Line Feed with Carriage Return 'LF CR' is made available. The following page contains examples of the various possibilities. Procol Variants Telegram with command, Address and no. of bytes End Acknowledge with blockcheck BCC 'R ' BCC <ACK> '0' with Carriage Return 'R ' 'CR' <ACK> '0' with Carriage Return 'R ' 'CR' <ACK> '0' 'CR' with Carriage return and Line feed 'R ' 'LF CR' <ACK> '0' 'LF CR' Configuration Parameters Immediately send CT data Each time another data carrier is detected, it is read accding the configuration and the data are output. This setting eliminates the read command in dialog mode. Dynamic Mode This function switches off the err-message "No data carrier present", i.e.: -> In dynamic mode, a read write telegram is sred until a data carrier enters the wking range of the cresponding read/write head. -> Without dynamic mode, a read write telegram is acknowledged with an err message (<NAK> '1') if there is no data carrier present in front of a read/write head; the process goes in the ground state. Send power-on message If this function is activated, the process sends the device name and software version as soon as power is turned on. Serial number when CT Pres. If the function f "Serial number when CT Present" is parameterized, 01Hex followed by the 4-byte unique serial number + 4 Byte '0Hex' is sent. 12

7 13 Configuration Parameters (continued) Read and send data carrier data without direct command: The specified data amount (number of bytes beginning at start address) is read from the newly detected data carrier. After reading, the data are aumatically output. If desired, a BCC and/ 1 2 freely definable terminars may be sent also Configuration Parameters (continued) CRC_16 initialization To be able use the CRC_16 check, the data carrier must first be initialized with the command identifier Z ( 27). The CRC_16 initialization is used like a nmal write job. The latter is rejected (with an err message) if the process recognizes that the data carrier does not contain the crect CRC_16 checksum. Data carriers as shipped from the facry (all data are 0) can immediately be written with CRC-checked data. If CRC_16 data checking is activated, a special err message is output the interface whenever a CRC_16 err is detected. If the err message is not caused by a failed write request, it may be assumed that one me memy cells on the data carrier is defective. That data carrier must then be replaced. If the CRC err is however due a failed write request, you must reinitialize the data carrier in der continue using it. 14

8 15 Configuration CRC_16 and Codetag Present CRC_16 and memy capacity If CRC_16 was parameterized and a data carrier is recognized whose CRC_16 checksum is increct, the read data are not output. The CT present LED comes on and the digital output is set - the data carrier can be processed using the initialization command (Z). The checksum is written the data carrier as a 2-byte datum f each CRC block (cresponds 16 bytes). 2 bytes are used (lost) f each CRC block, i.e., the CRC block contains only 14 bytes of user data. This means that the actual usable number of bytes is reduced: Data carrier model Memy capacity Usable bytes with CRC_16 BIS M-1-01/_ = 752 bytes 658 bytes The preceding sections describe basic telegram sequence, and configuration and wiring of the interfaces. What now follows is infmation about the proper construction of the telegrams themselves. Specific telegrams exist in the BIS M Identification System f particular tasks. They always begin with the command which is associated with the telegram type. Telegram types with their associated commands (ASCII characters) 'L' 'P' 'C' 'R' 'W' 'Q' 'Z' 'U' Read the data carrier with 2-byte reservation Write the data carrier with 2-byte reservation Write a constant value the data carrier with read/write select with 2-byte reservation Read the data carrier Write the data carrier Restart the process (acknowledge) Initialize CRC_16 data check Read data carrier ID and output with status byte. Please note: Continuous querying on the interface is not permitted! The minimum wait time between two commands is 300 ms! 16

9 17 Telegram Contents Start address and The start address (A3, A2, A1, A0) and the number of bytes send no. of bytes (L3, L2, L1, L0) are sent in decimal as ASCII characters. F the start address, the range can be used, and f the number of bytes A3... L0 represent one ASCII character each. Please note: Start address + number of bytes may not exceed the data carrier capacity. Reserved Acknowledge Start Transmitted Bytes The commands 'L' (read data carrier with L-command), 'P' (write data carrier with P-command), 'C' (write the data carrier with C-command) and 'Z' (initialize CRC_16 data check) cause the 2 bytes given after the address and the number of 8 bytes be read/written be reserved with '1'. The acknowledgement <ACK> '0' is sent by the Identification System if the serially transmitted characters were recognized as crect and there is a data carrier in the active zone of a read/write head. In the 'R' command, the <ACK> '0' is only sent if the data is ready f transmission. <NAK> + Err No.' is sent if an err was recognized if there is no data carrier in the active zone of a read/write head. <STX> starts the data transmission. The data are transmitted code transparent (no data conversion) BCC Block Check The BCC block check is fmed as an EXOR of the serially transmitted binary characters of the telegram block. Example: Read 128 bytes starting at address 13. The command line without BCC is: 'L '. The BCC is fmed: 'L = EXOR 0 = EXOR 0 = EXOR 1 = EXOR 3 = EXOR 0 = EXOR 1 = EXOR 2 = EXOR 8 = EXOR 1 = EXOR 1' = EXOR Block check result: BCC = = 'E' Variants f finish with BCC, If necessary the finish using block check BCC can be replaced with a special ASCII character. This is: Carriage Return 'CR' F hosts which always require a terminar character, this must always be included in the telegrams. Available are: Carriage Return 'CR' Line Feed with Carriage Return 'LF CR'. The various procol variants are represented on the following. See also: Configuration starting on 8. 18

10 19 Description of Various Procol Variants Reference is now made the command string 'L E' with 'E' as BCC ( preceding ). This command string is here shown in its possible variants; also shown are the various fms of acknowledgement with and without terminar: Command line from Acknowledge from BIS Acknowledge from BIS host system BIS f crect reception f increct reception with BCC but no terminar No terminar No terminar 'L E' <ACK> '0' <NAK> '1' with 'CR' instead of BCC, no terminar No terminar No terminar 'L CR' <ACK> '0' <NAK> '1' no BCC, with terminar 'CR' with terminar 'CR' with terminar 'CR' 'L CR' <ACK> '0 CR' <NAK> '1 CR' no BCC, with terminar 'LF CR' with terminar 'LF CR' with terminar 'LF CR' 'L LF CR' <ACK> '0 LF CR' <NAK> '1 LF CR' F <NAK> with err number a '1' was used here (no data carrier present) as an err example. The respective positions f the additional terminar are shown in the tables in italics Read from data carrier with command L Write data carrier with command P Task Data Flow Command Start address of first byte be sent Number of bytes be sent End reserved Acknowledge 3) Start transmission Data (from start address start address + no. of bytes) End Acknowledge 3) Read Write from host 'L' system BIS from BIS host system from host 'P' system BIS from BIS host system A3 A2 A1 A0 ' ' ' ' A3 A2 A1 A0 ' ' ' ' L3 L2 L1 L0 ' ' ' ' L3 L3 L1 L0 ' ' ' ' '1' '1' BCC <STX> 'CR' 'LF CR' <ACK>'0' 'CR' <NAK> 'LF CR' + Err- No. 1) 1) '1' '1' BCC <STX> D1 D2 D3... Dn D1 D2 D3... Dn <ACK>'0' 'CR' <NAK> 'LF CR' + Err- No. 1) 1) BCC BCC <ACK>'0' 'CR' <NAK> 'LF CR' + Err- No. 1) The command 'Quit' is not permitted at this point. Instead of block check BCC, depending on procol variant either Carriage Return 'CR' LIne Feed with Carriage Return may be used. 3) <ACK> '0' is returned as acknowledgement if there is no err, <NAK> + Err No. if an err occurs. F procol variants which always require a terminar, either 'CR' 'LF CR' must be inserted here. Values inside apostrophes represent the respective character(s) in ASCII code. 20

11 21 Telegram example f 20: Read from data carrier with command L with block check (BCC) -> Read 10 bytes starting at address 50 of the data carrier. The host sends 'L H' BCC (48Hex) Address of first byte read Number of bytes read reserved The BIS process acknowledges with The host system gives the start command The BIS process provides the data from the data carrier After the telegram sequence, head 2 remains selected. <ACK> '0' <STX> '1' BCC (31Hex) Telegram example f 20: Write data carrier with command P with block check (BCC) -> Write 5 bytes starting at address 100 of the data carrier. The host sends 'P L' BCC (54Hex) Address of first byte write Number of bytes write reserved The BIS process acknowledges with The host system gives the start command and data The process acknowledges with <ACK> '0' <STX> '3' BCC (33Hex) <ACK> '0' Values inside apostrophes represent the respective character(s) in ASCII code Writing a constant value in the data carrier with command C This command can be used erase a data carrier data. One saves the time f the transmission of the write byte. Task Data Flow Command Start address of first byte be sent Write from host 'C' system BIS from BIS host system A3 A2 A1 A0 ' ' ' ' Number of bytes be sent L3 L3 L1 L0 ' ' '1' ' ' '1' End BCC reserved Acknowledge 3) 1) The command 'Quit' is not permitted at this point. Instead of block check BCC, depending on procol variant either Carriage Return 'CR' LIne Feed with Carriage Return may be used. 3) <ACK> '0' is returned as acknowledgement if there is no err, <NAK> + 'Err No.' if an err occurs. F procol variants which always require a terminar, either 'CR' 'LF CR' must be inserted here. Start transmission Data (from start address start address + no. of bytes) End <STX> D BCC <ACK>'0' 'CR' <NAK> 'LF CR' + Err- No. 1) 1) Acknowledge 3) <ACK>'0' 'CR' <NAK> 'LF CR' + Err- No. Data within angle brackets are control characters. Values inside apostrophes represent the respective character(s) in ASCII code. 22

12 23 Telegram example f 22: Write data carrier with command C with block check (BCC) -> Write 101 bytes of ASCII data value 0 (30Hex) starting at address 20 of the data carrier. The host sends 'C A' BCC (41Hex) Address of first byte write Number of bytes write reserved The BIS process acknowledges with The host system gives the start command and data The process acknowledges with <ACK> '0' <STX> '0 2' BCC (32Hex) <ACK> '0' Data within angle brackets are control characters. Values inside apostrophes represent the respective character(s) in ASCII code Read from Data carrier, Write Data carrier Read Write from host system BIS from BIS host system from host system BIS from BIS host system 'R' 'W' Start address of first byte send A3 A2 A1 A0 ' ' ' ' A3 A2 A1 A0 ' ' ' ' Number of bytes send L3 L3 L1 L0 ' ' ' ' 1) L3 L3 L1 L0 ' ' ' ' End BCC BCC Task Data Flow Command Acknowledge 3) 1) The command 'Quit' is not permitted at this point. Instead of block check BCC, depending on procol variant either Carriage Return 'CR' LIne Feed with Carriage Return may be used. 3) <ACK> '0' is returned as acknowledgement if there is no err, <NAK> + Err No. if an err occurs. F procol variants which always require a terminar, either 'CR' 'LF CR' must be inserted here. <ACK>'0' 'CR' <NAK> 'LF CR' + Err-No. <STX> Start transmission 'CR' 'LF CR' Data (from start address start address + no. of bytes) D1 D2 D3... Dn End BCC <STX> D1 D2 D3... Dn BCC <ACK>'0' 'CR' <NAK> 'LF CR' + Err-No. 1) 1) Acknowledge 3) <ACK>'0' 'CR' <NAK> 'LF CR' + Err-No. Values inside apostrophes represent the respective character(s) in ASCII code. 24

13 25 Telegram example f 24: Read from Data carrier with block check (BCC) Read from Data carrier: -> Read 10 bytes starting at address 50. The host sends 'R V' BCC (56Hex) Address of first byte read Number of bytes read The BIS process acknowledges with The host gives the start command The BIS process provides the data from the data carrier <ACK> '0' <STX> 'SOH' BCC (01Hex) Telegram example f 24: Write Data carrier with block check (BCC) Write Data carrier: -> Write 5 bytes starting at address 100. The host system sends 'W S' BCC (53Hex) The BIS process acknowledges with <ACK> '0' The host sends the data <STX> '3' BCC (33Hex) The BIS process acknowledges with <ACK> '0' The 'R' and 'W' commands represent a subtype of the 'L' and 'P' commands. Values inside apostrophes represent the respective character(s) in ASCII code Restart the Process (Quit) Sending the Restart command causes a telegram in process be abted and puts the process in the ground state. After this telegram is acknowledged, an approx. 500 ms pause should be allowed befe starting a new telegram. Imptant! The Quit command is not permitted while the process is waiting f a terminar (BCC, 'CR' 'LF CR'). In this situation, the Quit would be increctly interpreted as a terminar datum. Task Data Flow Command End Acknowledge End Restart from host system BIS 'Q' BCC (Quit) from BIS host system 'Q' BCC 1) 1) The command 'Quit' is not permitted at this point. Instead of block check BCC, depending on procol variant either Carriage Return 'CR' LIne Feed with Carriage Return may be used. Telegram example: Restart the Process (Quit) with block check (BCC) Put the BIS system in the ground state. The host sends 'Q Q' BCC (51Hex) The BIS process acknowledges with 'Q Q' BCC (51Hex) Values inside apostrophes represent the respective character(s) in ASCII code. 26

14 27 Initialize CRC_16 data check This telegram initializes a data carrier located at the read/write head f use of CRC_16 data checking. This telegram must also be send again if a CRC err results from a failed write operation, i.e., the data carrier must be reinitialized in der use it again. Please note the table on 15! The indicated number of usable bytes may not be exceeded, i.e., the sum of start address plus number of bytes must not exceed the data carrier memy capacity! Task Data Flow Command Start address of first byte be sent Initialize CRC_16 range from host system BIS from BIS host system 'Z' A3 A2 A1 A0 ' ' ' ' Number of bytes be sent L3 L3 L1 L0 ' ' '1' ' ' '1' End BCC reserved Acknowledge 3) 1) The command 'Quit' is not permitted at this point. Instead of BCC block check, depending on the procol variant either Carriage Return 'CR' Line Feed with Carriage Return 'LF CR' may be used. 3) <ACK> '0" is sent as an acknowledgement if there was no err, <NAK> + 'Err-No.' if there was an err. F procol variants which always need a terminar, either 'CR' 'LF CR' must be inserted here. Data (from start address start address + no. of bytes) End <STX> D1 D2 D3... Dn BCC <ACK>'0' 'CR' <NAK> 'LF CR' + Err- No. 1) 1) Start transmission Acknowledge 3) <ACK>'0' 'CR' <NAK> 'LF CR' + Err- No. The characters between the apostrophes represent the respective ASCII character(s). '_' = Space = ASCII 20Hex Query status byte, data carrier type, data carrier ID With the telegram the status byte (Tag Present), data carrier type and data carrier ID of data carriers are read and sent. In contrast the standard command, here the reply is not an <ACK> <NAK>, but rather a fixed data telegram. Task Data Flow Command End Status message End Check Status Message From host system BIS 'U' BCC From BIS host system S1 Type1 ID1 BCC 1) 1) The Command 'Quit' is not permitted at this point. Instead of BCC block check, depending on the procol variant either Carriage Return 'CR' Line Feed with Carriage Return 'LF CR' may be used. S1 = Status byte ('1' no data carrier; '0' data carrier) Typ1 = Data carrier type (01Hex = BIS M-1-01/_ of the data carrier ID1 = Data carrier ID of the data carrier Telegram example: Query status byte, data carrier type and data carrier ID The host sends 'U U' BCC (55Hex) The BIS process acknowledges with '0J ' BCC (35Hex) if a data carrier was recognized The BIS process acknowledges with '1xxxxxxxxx1' BCC (31Hex) if no data carrier was recognized (x = 'NUL') Values inside apostrophes represent the respective character(s) in ASCII code. 28

15 29 Err Numbers Err Numbers The BIS M-4 always outputs an err number. The meaning of these err numbers is indicated in the following table. No. Err Description Effect 1 No data carrier present Telegram abted, process goes in ground state. 2 Read err Read telegram abted, process goes in ground state. Possible read err: - data carrier removed - Key false 4 Write err Write telegram abted, process goes in ground state. Possible write err: - data carrier removed - Key false CAUTION: An abted write could cause new data be written the data carrier which may be incomplete! *) 6 Interface err Process goes in ground state. (parity sp bit err) 7 Telegram fmat err Process goes in ground state. Possible fmat errs: - Command is not 'L'/'P'/'C'/'R'/'W'/'Q'/'Z' 'U'. - Start address number of bytes exceed permissible range *) Note: If a CRC data check is used, err message E could result if err 4 was not cleared Err Numbers Err Numbers (continued) No. Err Description 8 BCC err, the transmitted BCC is wrong Effect Telegram is abted, process goes in ground state. D CT err Bad CT signal, process goes in ground state. E CRC err: the CRC on the data carrier is wrong. *) Telegram abted, process goes in ground state. *) Note: If a CRC data check is used, err message E could result if in the preceding command err 4 was repted. 30

16 31 Read/Write Times Read times Data carrier BIS M-1 with each 16 bytes/block Time f data carrier recognition/serial ID < 20 ms Read bytes 0 15 < 20 ms F each additional 16 bytes add another < 10 ms Write times Data carrier BIS M-1 with each 16 bytes/block Time f data carrier recognition/serial ID < 20 ms Write bytes 0 15 < 40 ms F each additional 16 bytes add another < 30 ms Variations in the ms range are possible. Electrical interference may increase the read/write times. All data are typical values. Deviations are possible depending on the application and combination of read/write head and data carrier! The data apply static operation, no CRC_16 data checking BIS M-4 Installation Installing the BIS M-4, permissible distances When installing two BIS M-400 on a metal base, there is nmally no mutual interference. If a metal frame is located in an unfavable location, problems may result when reading out the data carriers. In this case the read distance will be reduced 80 % of the maximum value. Testing is recommended in critical applications! Metal frame Distance from data carrier data carrier BIS M /L BIS M /L BIS M /A BIS M /L BIS M S115 > 10 cm > 15 cm > 10 cm - BIS M S115 > 20 cm > 20 cm - > 25 cm Minimum distance from read head read head: BIS M S115 => min. 20 cm BIS M S115 => min. 60 cm 32

17 33 BIS M S115 Installation Installation and permissible distances Clear zone c Clear zone b Clear zone a M30x1.5 M12x1 Data carrier Active surface 36 Tightening rque max. 40 Nm Characteristic data by data carrier read Speed in m/s write Characteristic data by data carrier (installed in clear zone) Distance (mm) at v = 0 (static condition) Center axis offset at a distance of: (mm) Clear zone a b c min. distance DT BIS M /L /L /A /L /L /A ID No No. of bytes BIS M /L 0-20 ± 14 ± 14 ± 10 ± BIS M /L 0-28 ± 20 ± 20 ± 20 ± BIS M /A 0-7 ± No. of bytes No. of bytes No. of bytes BIS M S115 Installation Installation and permissible distances Clear zone c Clear zone b Clear zone a Ø 5.3 Data carrier Characteristic data by data carrier Active surface Characteristic at v = 0 (static condition) Clear zone data by data carrier (installed Distance Center axis offset at a in clear zone) distance of: (mm) (mm) a b c BIS M /L 0-28 ± 20 ± BIS M /L 0-45 ± 30 ± 24 ± 24 ± 20 ± ± 40 ± 40 ± 40 ± 34 ± ± 4 x ± BIS M /L y ± 30 ± 30 ± 28 ± 22 ± 18 ± 12 ± 4 Speed in m/s read write min. distance DT BIS M /L /L /L /L /L /L ID No No. of bytes No. of bytes No. of bytes No. of bytes

18 35 BIS M S115 Installation Installation and permissible distances Clear zone c Clear zone b Clear zone a Data carrier Active surface Tightening rque max. 40 Nm Characteristic data by data carrier Characteristic data by data carrier (installed in clear zone) at v = 0 (static condition) Distance Center axis offset at a distance of: (mm) read/ (mm) write Clear zone a b c Speed in m/s read write min. distance DT BIS M /L /L /A /L /L /A BIS M /L 0-15 / 0-15 ± 9 ± 9 ± 6 ± BIS M /L 0-18 / 0-18 ± 16 ± 16 ± 12 ± 8 ± BIS M /A 0-6 / 0-6 ± 5 ± (Data carrier is flush installed) BIS M /A 0-5 / 0-5 ± 4 ± ID-Nr No. of bytes No. of bytes No. of bytes No. of bytes BIS M _-00-S115 Installation Pin assignments BIS M S115 RS232 = 00 Col code using cables BKS-S116-PU / -S115-PU 1 OUT TP yellow 2 TxD grey 3 RxD pink 4 NC red 5 RTS (TP) green 6 -VS blue 7 +VS brown 8 COM white 36

19 37 BIS M _-00-S115 Interface Infmation Interface V.24 / RS232 M S115 9 pin connecr ➀ RTS connection (TP) allows TP display in the BISCOMRW.EXE program. ➁ OUT TP switches +24V when there is a data carrier in the capture zone BIS M _-00-S115 Connection Diagrams Wiring the outputs OUT TP (only f RS23 Supply voltage: Output current: Voltage drop at 50 ma: DC 24 V +10% / 20% (incl. ripple) max. 200 ma < 1.5 V 38

20 39 BIS M-4 Technical Data General data Housing M M CuZn nickel-plated plastic (PBT) Temperature range Ambient temperature 0 C +70 C Enclosure rating Supply voltage LED function indicar Enclosure rating Supply voltage Current consumption Power Tag Present IP 67 (only when assembled) DC 24 V +10 % / 20 % (incl. ripple) 50 ma with no load LED green LED yellow The CE Marking verifies that our products confm the requirements of the EC Council Directive 89/336/EEC (EMC Directive) and the EMC Law. In our EMC Labary, which is accredited by the DATech f Testing Electromagnetic Compatibility, we have verified that Balluff products meet the EMC requirements of the following Generic Standards: EN (Emission), EN (Noise Immunity) BIS M-4 Ordering Infmation Part Numbers BIS M S115 Balluff Identification System Series M Hardware type 4 = Process 400 = M30 housing 401 = Maxisens Software type 007 = Balluff-Procol Hardware version 001 = Coil 002 = M18 read/write head Interface 00 = RS232 Module S115 = M12 8-pole female 40

21 41 BIS M-4 Ordering Infmation Accessies (optional, not included in scope of delivery) Type Part No. Mating connecr without cable BKS-S Cable (Pin assignments 35) BKS-S116-PU-.. Cable (Pin assignments 35) BKS-S115-PU-.. Cable is available in various standard lengths: 2 m, 5 m, 10 m, 15 m, 20 m, 25 m Example: BKS-S115-PU-02 Part number f 2 m cable BKS-S116-PU-15 Part number f 15 m cable F BIS M _-00-S115 and a baud rate of cable length max. 15 m cable length max. 20 m Appendix, ASCII Table Decimal Code ASCII Deci- Hex Control Hex Control mal Code ASCII Decimamamamal Deci- Deci- Deci- Hex ASCII Hex ASCII Hex ASCII Hex ASCII 0 00 NUL Ctrl V SYN 44 2C, A V 107 6B k 1 01 Ctrl A SOH Ctrl W ETB 45 2D B W 108 6C l 2 02 Ctrl B STX Ctrl X CAN 46 2E C X 109 6D m 3 03 Ctrl C ETX Ctrl Y EM 47 2F / D Y 110 6E n 4 04 Ctrl D EOT 26 1A Ctrl Z SUB E 90 5A Z 111 6F o 5 05 Ctrl E ENQ 27 1B Ctrl [ ESC F 91 5B [ p 6 06 Ctrl F ACK 28 1C Ctrl \ FS G 92 5C \ q 7 07 Ctrl G BEL 29 1D Ctrl ] GS H 93 5D ] r 8 08 Ctrl H BS 30 1E Ctrl ^ RS I 94 5E ^ s 9 09 Ctrl I HT 31 1F Ctrl _ US A J 95 5F _ t 10 0A Ctrl J LF SP B K ` u 11 0B Ctrl K VT 33 21! C L a v 12 0C Ctrl L FF " D M b w 13 0D Ctrl M CR # E N c x 14 0E Ctrl N SO $ 58 3A : 79 4F O d y 15 0F Ctrl O SI % 59 3B ; P e 122 7A z Ctrl P DLE & 60 3C < Q f 123 7B { Ctrl Q DC ' 61 3D = R g 124 7C Ctrl R DC ( 62 3E > S h 125 7D } Ctrl S DC ) 63 3F? T i 126 7E ~ Ctrl T DC4 42 2A * U 106 6A j 127 7F DEL Ctrl U NAK 43 2B + 42