Balluff BISM4XX00 BIS M-400-007-001-00-S115 User Manual M 4 007 S115 854304 0910 en p65
Balluff Inc BIS M-400-007-001-00-S115 M 4 007 S115 854304 0910 en p65
Balluff >
Contents
- 1. User Manual 1 of 2.pdf
- 2. User Manual 2 of 2.pdf
User Manual 1 of 2.pdf
| Download: |  |
| Mirror Download [FCC.gov] | |
| Document ID | 2707949 |
| Application ID | GEVuNt7HWq7urpgBY9E0kQ== |
| Document Description | User Manual 1 of 2.pdf |
| Short Term Confidential | No |
| Permanent Confidential | No |
| Supercede | No |
| Document Type | User Manual |
| Display Format | Adobe Acrobat PDF - pdf |
| Filesize | 230.42kB (2880213 bits) |
| Date Submitted | 2015-08-07 00:00:00 |
| Date Available | 2015-08-10 00:00:00 |
| Creation Date | 2009-10-29 17:26:41 |
| Producing Software | Acrobat Distiller 6.0.1 (Windows) |
| Document Lastmod | 2009-11-04 16:31:21 |
| Document Title | M-4_ _-007-S115_854304_0910_en.p65 |
| Document Creator | PageMaker 6.5 |
| Document Author: | heinz |
M-4_ _-007-S115_854304_0910_en.p65 Manual Identification Systems BIS Compact Processor BIS M-4_ _-007-...-S115 Deutsch – bitte wenden! No. 854 304 D/E • Edition 0910 Subject to modification. Replaces edition 0706. Balluff GmbH Schurwaldstrasse 9 73765 Neuhausen a.d.F. Germany Phone +49 7158 173-0 Fax +49 7158 5010 balluff@balluff.de www.balluff.com M-4_ _-007-S115_854304_0910_en.p65 Contents Safety Notes ............................................................................................................................... 4 Introduction BIS M-4_ _ Identification System ...................................................................... 5/6 Basic knowledge for using the BIS M-4_ _ Processor ............................................................ 7 Configuration ......................................................................................................................... 8-16 Programming Information .................................................................................................... 17-29 Error Numbers ..................................................................................................................... 30/31 Read/Write Times .................................................................................................................... 32 Installation RS232 ............................................................................................................... 33-42 Interface Information RS232 .................................................................................................... 43 Connection Diagrams RS232 ................................................................................................... 44 Installation RS422 .................................................................................................................... 45 Interface Information RS422 .................................................................................................... 46 Technical Data .......................................................................................................................... 47 Ordering Information ................................................................................................................ 48 Accessories .............................................................................................................................. 49 Symbols / Abbreviations ......................................................................................................... 50 Appendix, ASCII Table ............................................................................................................. 51 english Safety Notes Proper use and operation BIS M-4_ _ processor together with the other BIS M system components comprise the Identification System and may only be used for this purpose in industrial applications corresponding to Class A of the EMC Directive. Installation and operation Installation and operation are permitted by trained specialists only. Unauthorized modifications and improper use will result in loss of the right to make warranty and liability claims. When installing the processor, follow exactly the connection diagrams provided later in this document. Take special care when connecting the processor to external controllers, especially with respect to the selection and polarity of the connections including the power supply. Only approved power supplies may be used. For specific information, see the Technical Data section. Deployment and inspection When deploying the identification system, all relevant safety regulations must be followed. In particular, measures must be taken to ensure that any defect in the identification system does not result in a hazard to persons or equipment. This includes maintaining the permissible ambient conditions and regular inspection for proper function of the identification system and all the associated components. Malfunction At the first sign that the identification system is not working properly, it should be taken out of service and guarded against unauthorized use. Scope This document applies to the processor BIS M-40_-007-00_-0_-S115 (Software version V1.4, Hardware version V2.0 and higher). english M-4_ _-007-S115_854304_0910_en.p65 Introduction BIS M-4_ _ Identification System This manual is intended to guide the user in installing and commissioning the components in the BIS M-4_ _ identification system, so that start-up time is reduced to an absolute minimum. Principle The BIS M-4_ _ identification system belongs to the category of non-contacting systems, which can both read and write. This dual function permits uses where not only information permanently stored in the data carrier can be transported, but also current information can be collected and transported. Applications The main areas of application include – in production for controlling material flow (e.g., for part-specific processes), in workpiece transport using conveying systems, for obtaining safety-relevant data, – in process materials organization. System component function The processor and the read head form 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 or dynamic. The data are output serially and made available to the host system. These host systems may be: – a control computer (e.g., industrial PC) having a serial port, or – a programmable logic controller (PLC). english Introduction BIS M-4_ _ Identification System System components The main components of the BIS M-4_ _ identification system are – the processor with integrated read head, and – the data carrier(s). Connections to host system Schematic representation of an identification system (example) english Data carriers BIS M-1.. BIS M-401... BIS M-400... Connections to host system M-4_ _-007-S115_854304_0910_en.p65 BIS M-4_ _ Processor Basic knowledge for application Data integrity with CRC_16 When sending data between the read/write head and the data carrier a procedure is required for recognizing whether the data were correctly read or written. The processor is supplied with standard Balluff procedure of double reading and comparing. In addition to this procedure a second alternative is available: CRC_16 data checking. Here a test code is written to the data carrier, allowing data to be checked for validity at any time or location. Advantages of CRC_16 Advantages of double reading Data checking even during the non-active phase (CT outside read/write head zone). No bytes on the data carrier need to be reserved for storing a check code. Shorter read times since each page is read only once. Shorter write times since no CRC needs to be written. Since both variations have their advantages depending on the application, the user is free to select which method of data checking he wishes to use (see Configuration 8-16). To use the CRC check method, the data carriers must be initialized. You use either data carriers with the data map factory configured (all data are 0), or you must use the processor to write the special initialization command 'Z' to the data carriers. It is not permitted to operate the system using both check procedures! english Configuration Before programming, the processor configuration must be carried out, in case the factory settings will not be used. Configuration is done using a computer and the Balluff software Configuration software BIS, and it is stored in the processor. It may be overwritten at any time. The configuration can be stored in a file, making it accessible when required. ☞ english No data carrier is allowed in front of the read head while configuring the processor. M-4_ _-007-S115_854304_0910_en.p65 Configuration Interface BIS M-40.-007-... The first screen shows the parameters baud rate, number of data and stop bits, and parity type for the serial interface selected. The graphic shows the factory settings. The other settings are carried out in the corresponding masks which are illustrated in the following . english 10 Configuration Parameters BIS M-40.-007-... 10 english M-4_ _-007-S115_854304_0910_en.p65 11 Configuration Protocol Type Examples for terminating telegrams: Operation with blockcheck BCC is factory set. For host devices which require a terminator, the additional use of Carriage Return 'CR' or Line Feed with Carriage Return 'LF CR' is made available. The following page contains examples of the various possibilities. Protocol Variants Telegram with command, Address and no. of bytes End Acknowledge with blockcheck BCC with Carriage Return Terminator 'R 0000 0001' BCC'0' 'R 0000 0001' 'CR' '0' with Terminator Carriage Return 'R 0000 0001' 'CR' '0' 'CR' with Terminator Carriage return and Line feed 'R 0000 0001' 'LF CR' '0' 'LF CR' english 12 Configuration – Immediately send CT data Each time another data carrier is detected, it is read according to the configuration and the data are output. This setting eliminates the read command in dialog mode. – Dynamic Mode This function switches off the error-message "No data carrier present", i.e.: -> In dynamic mode, a read or write telegram is stored until a data carrier enters the working range of the corresponding read/write head. -> Without dynamic mode, a read or write telegram is acknowledged with an error message ( '1') if there is no data carrier present in front of a read/write head; the processor goes into the ground state. – Send power-on message If this function is activated, the processor sends the device name and software version as soon as power is turned on. – Serial number when CT Pres. If the function "Type and serial number when CT pres." is parameterized, the number of the data carrier type followed by the 8-byte unique serial number (at Mifare 4 bytes + 4 bytes '0Hex ') is sent. Parameters 12 english 11 M-4_ _-007-S115_854304_0910_en.p65 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 automatically output. If desired, a BCC and/or 1 or 2 freely definable terminators may be sent also. english 14 Configuration Parameters (continued) – CRC_16 initialization To be able to use the CRC_16 check, the data carrier must first be initialized with the command identifier Z (see 28). The CRC_16 initialization is used like a normal write job. The latter is rejected (with an error message) if the processor recognizes that the data carrier does not contain the correct CRC_16 checksum. Data carriers as shipped from the factory (all data are 0) can immediately be written with CRC-checked data. If CRC_16 data checking is activated, a special error message is output to the interface whenever a CRC_16 error is detected. If the error message is not caused by a failed write request, it may be assumed that one or more memory cells on the data carrier is defective. That data carrier must then be replaced. If the CRC error is however due to a failed write request, you must reinitialize the data carrier in order to continue using it. 14 english 13 M-4_ _-007-S115_854304_0910_en.p65 15 Configuration CRC_16 and Codetag Present If CRC_16 was parameterized and a data carrier is recognized whose CRC_16 checksum is incorrect, 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). CRC_16 The checksum is written to the data carrier as a 2-byte datum for each CRC block (corresponds to 16 bytes). 2 bytes are used (lost) for 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: Supported data carriers and memory capacity Mifare Balluff data carrier type Manufacture Name Memory capacity Usable bytes using CRC Memory type BIS M-1_ _-01 Philips Mifare Classic 752 Byte 658 Byte EEPROM Manufacture Name Usable bytes using CRC Memory type ISO15693 Balluff data carrier type Memory capacity BIS M-1_ _-02 Fujitsu MB89R118 2000 Byte 1750 Byte FRAM BIS M-1_ _-031 BIS M-1_ _-041 Philips Texas Inst. SL2ICS20 TAG-IT Plus 112 Byte 256 Byte 98 Byte 224 Byte EEPROM EEPROM BIS M-1_ _-051 Infineon SRF55V02P 224 Byte 196 Byte EEPROM BIS M-1_ _-061 EM EM4135 288 Byte 252 Byte EEPROM BIS M-1_ _-071 Infineon SRF55V10P 992 Byte 868 Byte EEPROM on request english 16 Configuration Data carrier type Select the data carrier type, you want to process: - ALL TYPES - MIFARE - ISO 15693 ALL TYPES: All Mifare data carriers supported by Balluff can be processed. ISO 15693: All ISO15693 data carriers supported by Balluff can be processed. (See 16 english All data carriers supported by Balluff can be processed. MIFARE: 15 "Supported data carriers and memory capacity".) 15 M-4_ _-007-S115_854304_0910_en.p65 17 Programming Information The preceding sections describe basic telegram sequence, and configuration and wiring of the interfaces. What now follows is information about the proper construction of the telegrams themselves. Specific telegrams exist in the BIS M Identification System for 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' Read the data carrier with 2-byte reservation Write to the data carrier with 2-byte reservation 'C' Write a constant value to the data carrier with read/write select with 2-byte reservation 'R' Read the data carrier 'W' 'Q' Write to the data carrier Restart the processor (acknowledge) 'Z' 'U' Initialize CRC_16 data check Read data carrier ID and output with status byte. Please note: – Continuous querying on the interface is not permitted! english 18 Programming Information Telegram Contents 18 english Start address and The start address (A3, A2, A1, A0) and the number of bytes to send no. of bytes (L3, L2, L1, L0) are sent in decimal as ASCII characters. For the start address, the range 0000 to "memory capacity -1" can be used, and for the number of bytes 0001 to "memory capacity". A3 ... L0 represent one ASCII character each. Please note: Start address + number of bytes may not exceed 1024 bytes. Reserved The commands 'L' (read data carrier with L-command), 'P' (write to data carrier with P-command), 'C' (write to 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 to be read/written to be reserved with '1'. Acknowledge The acknowledgement '0' is sent by the Identification System if the serially transmitted characters were recognized as correct and there is a data carrier in the active zone of a read/write head. In the 'R' command, the '0' is only sent if the data is ready for transmission. + Error No.' is sent if an error was recognized or if there is no data carrier in the active zone of a read/write head. Start starts the data transmission. Transmitted Bytes The data are transmitted code transparent (no data conversion). 17 M-4_ _-007-S115_854304_0910_en.p65 19 Programming Information BCC Block Check The BCC block check is formed 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 0013 0128 11'. The BCC is formed: 'L = 0100 1100 EXOR 0 = 0011 0000 EXOR 0 = 0011 0000 EXOR 1 = 0011 0001 EXOR 3 = 0011 0011 EXOR 0 = 0011 0000 EXOR 1 = 0011 0001 EXOR 2 = 0011 0010 EXOR 8 = 0011 1000 EXOR 1 = 0011 0010 EXOR 1' = 0011 0000 EXOR Block check result: BCC = 0100 0101 = 'E' Variants for finish with BCC, Terminator If necessary the finish using block check BCC can be replaced with a special ASCII character. This is: – Carriage Return 'CR' For hosts which always require a terminator character, this must always be included in the telegrams. Available are: – Carriage Return 'CR' or – Line Feed with Carriage Return 'LF CR'. The various protocol variants are represented on the following . See also: Configuration starting on 8. english 20 Programming Information Description of Various Protocol Variants Reference is now made to the command string 'L 0013 0128 11 E' with 'E' as BCC (see preceding ). This command string is here shown in its possible variants; also shown are the various forms of acknowledgement with and without terminator: Command line from host system to BIS Acknowledge from BIS for correct reception Acknowledge from BIS for incorrect reception with BCC but no terminator 'L 0013 0128 11 E' No terminator '0' No terminator '1' with 'CR' instead of BCC, no terminator 'L 0013 0128 11 CR' No terminator '0' No terminator '1' no BCC, with terminator 'CR' 'L 0013 0128 11 CR' with terminator 'CR' '0 CR' with terminator 'CR' '1 CR' no BCC, with terminator 'LF CR' 'L 0013 0128 11 LF CR' with terminator 'LF CR' '0 LF CR' with terminator 'LF CR' '1 LF CR' For with error number a '1' was used here (no data carrier present) as an error example. The respective positions for the additional terminator are shown in the tables in italics. 20 english 19 M-4_ _-007-S115_854304_0910_en.p65 21 Programming Information Read from data carrier with command L Write to data carrier with command P Task Read Data Flow Com- Start address Number of mand of first byte to bytes to be be sent sent from host system to BIS 'L' A3 A2 A1 A0 '0 0 0 0' to memory capacity -1 L3 L2 L1 L0 '0 0 0 1' to memory capacity 5) reserved '1' End 2) '1' from host system to BIS Terminator 4) BCC or see 2) Start transmission Terminator 4) 'CR' or 'LF CR' '0' 'CR' or or 'LF CR' + ErrorNo. from BIS to host system Write Acknowledge 3) 'P' A3 A2 A1 A0 '0 0 0 0' to memory capacity -1 1) L3 L3 L1 L0 '0 0 0 1' to 'memory capacity 5) Data (from start address to start address + no. of bytes) D1 D2 D3 ... Dn End 2) Terminator 4) BCC or see 2) 1) '1' '1' BCC or see 2) D1 D2 D3 ... Dn BCC or see 2) '0' 'CR' or or 'LF CR' + ErrorNo. from BIS to host system Acknowledge 3) '0' or + ErrorNo. 1) 'CR' or 'LF CR' 1) 1) The command 'Quit' is not permitted at this point. 2) Instead of block check BCC, depending on protocol variant either Carriage Return 'CR' or LIne Feed with Carriage Return may be used. 3) '0' is returned as acknowledgement if there is no error, or + Error No. if an error occurs. 4) For protocol variants which always require a terminator, either 'CR' or 'LF CR' must be inserted here. 5) The number of bytes to send may not exceed 1024 bytes. Values inside apostrophes represent the respective character(s) in ASCII code. english 22 Programming Information Telegram example for 21: Read from data carrier with command L with block check (BCC) -> Read 10 bytes starting at address 50 of the data carrier. 'L 0 0 5 0 0 0 1 0 1 1 H' BCC (48Hex) The host sends Address of first byte to read Number of bytes to read reserved The BIS processor acknowledges with '0' The host system gives the start command The BIS processor provides the data from the data carrier 1 2 3 4 5 6 7 8 9 0 '1' BCC (31Hex ) Telegram example for 21: Write to data carrier with command P with block check (BCC) -> Write 5 bytes starting at address 100 of the data carrier. 'P 0 1 0 0 0 0 0 5 1 1 L' BCC (54Hex) The host sends Address of first byte to write Number of bytes to write reserved The BIS processor acknowledges with The host system gives the start command and data The processor acknowledges with '0' 1 2 3 4 5 '3' BCC (33Hex) '0' Values inside apostrophes represent the respective character(s) in ASCII code. 22 english 21 M-4_ _-007-S115_854304_0910_en.p65 23 Programming Information Writing a constant value in the data carrier with command C This command can be used to erase a data carrier data. One saves the time for the transmission of the write byte. Task Data Flow Com- Start address Number of mand of first byte to bytes to be be sent sent Write from host system to BIS 'C' A3 A2 A1 A0 '0 0 0 0' to memory capacity -1 reserved L3 L3 L1 L0 '0 0 0 1' '1' to memory capacitity 5) End 2) '1' Acknowledge 3) Terminator 4) Start transmission BCC or see 2) Terminator 4) Data (from start address to start address + no. of bytes) End 2) BCC or see 2) '0' 'CR' or or 'LF CR' + ErrorNo. from BIS to host system Acknowledge 3) Terminator 4) '0' 'CR' or or 'LF CR' + ErrorNo. 1) 1) 1) The command 'Quit' is not permitted at this point. 2) Instead of block check BCC, depending on protocol variant either Carriage Return 'CR' or LIne Feed with Carriage Return may be used. 3) '0' is returned as acknowledgement if there is no error, or + 'Error No.' if an error occurs. 4) For protocol variants which always require a terminator, either 'CR' or 'LF CR' must be inserted here. 5) The number of bytes to send may not exceed 1024 bytes. Data within angle brackets are control characters. Values inside apostrophes represent the respective character(s) in ASCII code. english 24 Programming Information Telegram example for 23: Write to 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 0 0 2 0 0 1 0 1 1 1 A' BCC (41Hex ) Address of first byte to write Number of bytes to write reserved The BIS processor acknowledges with The host system gives the start command and data The processor acknowledges with '0' '0 2' BCC (32Hex) '0' Data within angle brackets are control characters. Values inside apostrophes represent the respective character(s) in ASCII code. 24 english 23 M-4_ _-007-S115_854304_0910_en.p65 25 Programming Information Read from Data carrier, Write to Data carrier Task Read Data Flow Command from host system to BIS 'R' Start address of first byte to send Number of bytes to send A3 A2 A1 A0 '0 0 0 0' to memory capacity -1 L3 L3 L1 L0 '0 0 0 1' to memory capacity 5) End 2) from host system to BIS Terminator 4) BCC or see 2) Start transmission Terminator 4) 'CR' or 'LF CR' '0' 'CR' or or 'LF CR' + Error-No. from BIS to host system Write Acknowledge 3) 'W' A3 A2 A1 A0 '0 0 0 0' to memory capacity -1 1) L3 L3 L1 L0 '0 0 0 1' to memory capacity 5) D1 D2 D3 ... Dn BCC or see 2) Data (from start address to start address + no. of bytes) D1 D2 D3 ... Dn End 2) Terminator 4) BCC or see 2) BCC or see 2) '0' 'CR' or or 'LF CR' + Error-No. from BIS to host system Acknowledge 3) '0' 'CR' or or 'LF CR' + Error-No. 1) 1) 1) The command 'Quit' is not permitted at this point. 2) Instead of block check BCC, depending on protocol variant either Carriage Return 'CR' or LIne Feed with Carriage Return may be used. 3) '0' is returned as acknowledgement if there is no error, or + Error No. if an error occurs. 4) For protocol variants which always require a terminator, either 'CR' or 'LF CR' must be inserted here. 5) The number of bytes to send may not exceed 1024 bytes. Values inside apostrophes represent the respective character(s) in ASCII code. english 26 Programming Information Telegram example for 25: Read from Data carrier with block check (BCC) Read from Data carrier: The host sends -> Read 10 bytes starting at address 50. 'R 0 0 5 0 0 0 1 0 V' BCC (56Hex ) Address of first byte to read Number of bytes to read The BIS processor acknowledges with The host gives the start command The BIS processor provides the data from the data carrier Telegram example for 25: Write to Data carrier with block check (BCC) '0' 1 2 3 4 5 6 7 8 9 0 'SOH' BCC (01Hex) Write to Data carrier: -> Write 5 bytes starting at address 100. The host system sends 'W 0 1 0 0 0 0 0 5 S' BCC (53Hex) The BIS processor acknowledges with '0' The host sends the data 1 2 3 4 5 '3' BCC (33Hex) The BIS processor acknowledges with '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. 26 english 25 M-4_ _-007-S115_854304_0910_en.p65 27 Programming Information Restart the Processor (Quit) Sending the Restart command causes a telegram in process to be aborted and puts the processor in the ground state. After this telegram is acknowledged, an approx. 500 ms pause should be allowed before starting a new telegram. Important! The Quit command is not permitted while the processor is waiting for a terminator (BCC, 'CR' or 'LF CR'). In this situation, the Quit would be incorrectly interpreted as a terminator or datum. Task Data Flow Command End 2) Restart (Quit) from host system to BIS 'Q' Acknowledge End 2) BCC or see 2) from BIS to host system 'Q' BCC or see 2) 1) 1) The command 'Quit' is not permitted at this point. 2) Instead of block check BCC, depending on protocol variant either Carriage Return 'CR' or LIne Feed with Carriage Return may be used. Telegram example: Restart the Processor (Quit) with block check (BCC) Put the BIS system into the ground state. The host sends 'Q Q' BCC (51 Hex) The BIS processor acknowledges with 'Q Q' BCC (51 Hex) Values inside apostrophes represent the respective character(s) in ASCII code. 27 english 28 Programming Information Initialize CRC_16 data check This telegram initializes a data carrier located at the read/write head for use of CRC_16 data checking. This telegram must also be send again if a CRC error results from a failed write operation, i.e., the data carrier must be reinitialized in order to 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 memory capacity! Task Initialize CRC_16 range Data Flow Com- Start address Number of mand of first byte to bytes to be sent be sent from host system to BIS 'Z' A3 A2 A1 A0 '0 0 0 0' to usable bytes at CRC -1 reserved L3 L3 L1 L0 '0 0 0 1' '1' to usable bytes at CRC -1 End 2) '1' Acknowledge 3) Terminator 4) BCC or see 2) Start transmission Data (from start address to start address + no. of bytes) End 2) D1 D2 D3 .... Dn BCC or see 2) '0' 'CR' or or 'LF CR' + ErrorNo. from BIS to host system 1) Acknowledge 3) Terminator 4) '0' 'CR' or or 'LF CR' + ErrorNo. 1) 1) The command 'Quit' is not permitted at this point. 2) Instead of BCC block check, depending on the protocol variant either Carriage Return 'CR' or Line Feed with Carriage Return 'LF CR' may be used. 3) '0" is sent as an acknowledgement if there was no error, or + 'Error-No.' if there was an error. 4) For protocol variants which always need a terminator, either 'CR' or 'LF CR' must be inserted here. The characters between the apostrophes represent the respective ASCII character(s). '_' = Space = ASCII 20 Hex. 28 english M-4_ _-007-S115_854304_0910_en.p65 29 Programming Information 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 to the standard command, here the reply is not an or , but rather a fixed data telegram. Task Data Flow Check Status Message From host system to BIS 'U' Command End 2) Status message End 2) S1 Type1 ID1 BCC or see 2) BCC or see 2) From BIS to host system 1) 1) The Command 'Quit' is not permitted at this point. 2) Instead of BCC block check, depending on the protocol variant either Carriage Return 'CR' or Line Feed with Carriage Return 'LF CR' may be used. S1 = Status byte ('1' no data carrier; '0' data carrier) Typ1 = Number of the data carrier type (see 15 "Supported data carriers and memory capacity") ID1 = ID of the data carrier type is 8 bytes long (at Mifare 4 Byte + 4 Byte '0 Hex') Telegram example: Query status byte, data carrier type and data carrier ID The host sends 'U The BIS processor acknowledges with '0J123400005' BCC (35Hex ) if a data carrier was recognized U' BCC (55Hex ) The BIS processor acknowledges with '1xxxxxxxxx1' BCC (31 Hex) if no data carrier was recognized (x = 'NUL') Values inside apostrophes represent the respective character(s) in ASCII code. english 30 Error Numbers Error Numbers The BIS M-4_ _ always outputs an error number. The meaning of these error numbers is indicated in the following table. No. Error Description Effect No data carrier present Telegram aborted, processor goes into ground state. Read error Read telegram aborted, processor goes into ground state. Possible read error: - data carrier removed - Key false Write error Write telegram aborted, processor goes into ground state. Possible write error: - data carrier removed - Key false Interface error Processor goes into ground state. (parity or stop bit error) Telegram format error Processor goes into ground state. Possible format errors: - Command is not 'L', 'P', 'C', 'R', 'W', 'Z' or 'U'. - Start address or number of bytes exceed permissible range CAUTION: An aborted write could cause new data to be written to the data carrier which may be incomplete! *) *) Note: If a CRC data check is used, error message “E” could result if error 4 was not cleared. 30 english 29 M-4_ _-007-S115_854304_0910_en.p65 31 Error Numbers Error Numbers (continued) No. Error Description Effect BCC error, the transmitted BCC is wrong Telegram is aborted, processor goes into ground state. CT error Bad CT signal, processor goes into ground state. CRC error: the CRC on the data carrier is wrong. *) Telegram aborted, processor goes into ground state. *) Note: If a CRC data check is used, error message “E” could result if in the preceding command error 4 was reported. english 32 Read/Write Times 32 Read times Data carrier with each 16 bytes/block Time for data carrier recognition/serial ID Read bytes 0 to 15 For each additional 16 bytes add another BIS M-1_ _-01 BIS M-1_ _-02 < 30 ms < 20 ms < 30 ms < 20 ms < 15 ms < 10 ms Write times Data carrier with each 16 bytes/block Time for data carrier recognition/serial ID Write bytes 0 to 15 For each additional 16 bytes add another BIS M-1_ _-01 BIS M-1_ _-02 < 30 ms < 20 ms < 65 ms < 40 ms < 45 ms < 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 to static operation, no CRC_16 data checking. english 31 M-4_ _-007-S115_854304_0910_en.p65 33 BIS M-4_ _ Installation Installing the BIS M-4_ _, permissible distances When installing two BIS M-400 on a metal base, there is normally no mutual interference. If a metal frame is located in an unfavorable location, problems may result when reading out the data carriers. In this case the read distance will be reduced to 80 % of the maximum value. Testing is recommended in critical applications ! Metal frame Distance from data carrier to data carrier BIS BIS BIS BIS M-101-01/L M-108-02/L M-110-02/L M-111-02/L BIS M-102-01/L BIS M-112-02/L BIS M-105-01/A BIS M-122-02/A BIS M-120-01/L BIS M-150-02/A BIS M-151-02/A BIS M-400-007-00_-.. > 10 cm > 15 cm > 10 cm BIS M-401-007-001-.. > 20 cm > 20 cm > 25 cm BIS M-451-007-001-.. > 25 cm Minimum distance from read head to read head: BIS M-400-007-00_-... => min. 20 cm BIS M-401-007-001-... => min. 60 cm BIS M-451-007-001-... => min. 60 cm english 34 BIS M-400-007-001-_ _-S115 Installation Installation and permissible distances Clear zone c Clear zone b 83 10 50 M12x1 M30x1.5 Clear zone a 13 36 Data carrier 34 english Active surface Tightening torque max. 40 Nm 33 M-4_ _-007-S115_854304_0910_en.p65 35 BIS M-400-007-001-_ _-S115 Installation Characteristic data by data carrier Characteristic data by data carrier (installed in clear zone) at v = 0 (static condition) Clear zone Center axis offset at a distance of: (mm) Distance (mm) 15 20 30 35 BIS M-101-01/L 0-20 ±14 ±10 ±5 100 30 50 BIS M-102-01/L 0-28 ±20 ±20 ±15 150 30 50 100 BIS M-105-01/A 20 20 BIS M-105-02/A 0-11 ±8 100 20 20 BIS M-108-02/L 0-28 0-7 ±16 ±7 ±14 ±14 100 30 25 BIS M-110-02/L 0-20 ±12 ±8 ±5 100 30 25 BIS M-111-02/L 0-28 ±16 ±14 ±14 100 30 25 BIS M-112-02/L 0-38 ±22 ±20 ±20 ±16 ±10 150 30 50 ±10 ±6 100 30 (Data carrier is flush installed) BIS M-108-02/L 0-16 Speed in m/s read min. distance 10 3,5 3,5 14 DT BIS M-... 101-01/L 102-01/L 105-01/A 105-02/A 108-02/L 110-02/L 111-02/L 112-02/L ID No. 2.4 3.3 1.25 0.93 1.6 1.33 1.6 2.4 1.3 No. of bytes 16 1.65 2.2 0.8 0.55 0.76 32 1.5 1.8 0.7 0.42 0.8 0.65 0.8 48 1.28 1.58 0.5 0.38 0.6 0.5 0.6 0.86 64 1.1 1.4 0.4 0.3 0.5 0.43 0.5 0.7 write min. distance 10 3.5 3.5 14 No. of bytes 16 1.05 1.45 0.52 0.27 0.7 0.5 0.7 0.9 1.1 0.38 0.19 0.45 0.33 0.45 32 0.73 48 0.58 0.8 0.2 0.15 0.36 0.23 0.36 0.48 64 0.48 0.65 0.15 0.12 0.28 0.17 0.28 0.38 0.6 english 36 BIS M-401-007-001-_ _-S115 Installation Installation and permissible distances 36 english 35 M-4_ _-007-S115_854304_0910_en.p65 37 BIS M-401-007-001-_ _-S115 Installation Characteristic data by data carrier Characteristic data by data carrier (installed in clear zone) at v = 0 (static condition) Distance (mm) BIS M-101-01/L Clear zone Center axis offset at a distance of: (mm) 0-28 20 30 40 50 60 ±15 200 70 50 ±30 ±24 ±15 200 70 50 ±40 ±28 ±4 250 70 80 200 50 70 BIS M-102-01/L 0-45 BIS M-120-01/L 0 - 50 ±28 ±18 ±4 BIS M-108-02/L 0-40 ±25 ±20 ±15 BIS M-110-02/L 0-30 ±20 ±10 200 50 70 BIS M-111-02/L 0-40 ±25 ±20 ±15 200 50 70 BIS M-112-02/L 20-60 ±35 ±35 ±25 ±25 200 50 70 ±40 ±30 Speed in m/s read min. distance 14 15 10 12 20 DT BIS M-... 101-01/L 102-01/L 120-01/L 108-02/L 110-02/L 111-02/L 112-02/L ID No. 4.1 4.5 4.8 3.2 2.6 3.2 4.3 2.7 3.8 4.2 1.88 1.4 1.88 2.6 32 2.28 3.9 1.56 1.13 1.56 2.3 48 1.76 2.25 3.25 1.25 0.85 1.25 1.8 64 1.5 1.9 0.98 0.65 0.98 1.5 No. of bytes 16 write min. distance 10 12 20 No. of bytes 16 1.55 2.2 3.1 1.25 0.85 1.25 1.65 32 1.34 1.78 14 2.25 15 0.84 0.55 0.84 1.08 48 1.3 1.75 0.7 0.38 0.7 0.88 64 0.93 1.53 0.5 0.25 0.5 0.78 english 38 BIS M-400-007-002-_ _-S115 Installation Clear zone c Clear zone b Clear zone a Installation and permissible distances Tightening torque max. 40 Nm Data carrier 38 english Active surface 37 M-4_ _-007-S115_854304_0910_en.p65 39 BIS M-400-007-002-_ _-S115 Installation Characteristic data by data carrier Characteristic data by data carrier (installed in clear zone) at v = 0 (static condition) Distance (mm) read/ write Clear zone Center axis offset at a distance of: (mm) 10 15 20 25 BIS M-101-01/L 0-15 ±9 ±6 ±4 100 30 25 BIS M-102-01/L 0-18 ±16 ±12 ±8 150 30 50 BIS M-105-01/A 0-6 ±4 100 20 10 BIS M-105-02/A 0-9 ±6 100 20 10 BIS M-108-02/L 0-20 ±14 ±12 ±10 ±7 100 30 25 BIS M-110-02/L 0-15 ±8 ±6 ±4 100 30 25 BIS M-111-02/L 0-20 ±12 ±10 ±10 100 30 25 BIS M-112-02/L 0-28 ±20 ±18 ±18 ±16 ±12 150 30 50 (Data carrier is flush installed) BIS M-105-01/A 0-5 ±2 100 20 BIS M-105-02/A 0-5 ±2 100 20 BIS M-108-02/L 0-12 ±8 ±6 100 30 Speed in m/s read min. distance 3,5 3,5 DT BIS M-... 101-01/L 102-01/L 105-01/A 105-02/A 108-02/L 110-02/L 111-02/L 112-02/L ID No. 2.6 0.85 0.6 1.3 1.3 1.8 No. of bytes 16 1.3 0.54 0.38 32 1.75 0.48 0.28 0.66 0.5 0.66 48 0.88 1.4 0.38 0.21 0.52 0.87 0.4 0.7 0.52 0.87 0.88 1.15 64 0.78 1.3 0.33 0.17 0.48 0.3 0.48 0.73 3.5 3.5 write min. distance No. of bytes 16 0.9 1.38 0.38 0.25 0.51 0.38 0.51 0.82 32 0.62 1.05 0.24 0.11 0.33 0.25 0.33 0.58 48 0.44 0.78 0.19 0.08 0.27 0.18 0.27 0.4 64 0.38 0.62 0.11 0.2 0.15 0.2 0.32 english 40 BIS M-451-007-001-_ _-S115 Installation Clear zone c Clear zone b Clear zone a Installation and permissible distances Data carrier Active surface 40 english 39 M-4_ _-007-S115_854304_0910_en.p65 41 BIS M-451-007-001-_ _-S115 Installation Characteristic data by data carrier Characteristic data by data carrier (installed in clear zone) at v = 0 (static condition) Distance (mm) read/ write X-axis offset at a distance of: (mm) Clear zone Y-axis offset at a distance of: (mm) 0...10 25 40 50 0...10 25 40 50 BIS M-150-02/A 0-60 ±50 ±40 ±30 ±10 ±10 ±10 ±8 ±5 200 70 BIS M-151-02/A 0-60 ±50 ±40 ±30 ±10 ±10 ±10 ±8 ±5 200 70 (in air) BIS M-150-02/A 0-40 ±40 ±30 ±10 ±10 ±8 ±5 200 70 BIS M-151-02/A 0-5 ±40 ±30 ±10 ±10 ±8 ±5 100 20 english 42 BIS M-4_ _-007-_ _ _-00-S115 Installation Pin assignments BIS M-4_ _-007-... -00-S115 OUT TP Color code using cables BKS-S116-PU / -S115-PU yellow TxD gray RxD NC pink red RTS (TP) green -VS blue +VS brown COM white RS232 = 00 42 english 41 M-4_ _-007-S115_854304_0910_en.p65 43 BIS M-4_ _-007-_ _ _-00-S115 Interface Information Interface V.24 / RS232 M-4_ _-007-...-00-S115 9 pin connector ➀ RTS connection (TP) allows TP display in the BISCOMRW.EXE program. ➁ OUT TP switches to +24V when there is a data carrier in the capture zone. english 44 BIS M-4_ _-007-_ _ _-00-S115 Connection Diagrams Wiring the outputs OUT TP (only for RS232) Supply voltage: Output current: Voltage drop at 50 mA: 44 english DC 24 V +10% / –20% (incl. ripple) max. 200 mA < 1.5 V 43 M-4_ _-007-S115_854304_0910_en.p65 45 BIS M-4_ _-007-_ _ _-02-S115 Installation Pin assignments BIS M-4_ _-007-... -02-S115 RS422 = 00 Color code using cables BKS-S116-PU / -S115-PU OUT TP yellow TxD gray RxD pink NC red RTS (TP) green -VS blue +VS brown COM white 45 english 46 BIS M-4_ _-007-_ _ _-02-S115 Interface Information Interface RS422 4-wires point-to-point M-4_ _-007-...-02-S115 1) 1) Termination * For the power supply and the RS422 interface a galvanic isolation is recommended! Twisted pair cable data links. 46 english M-4_ _-007-S115_854304_0910_en.p65 47 BIS M-4_ _ Technical Data General data Housing M-400-... CuZn nickel-plated Temperature range Ambient temperature 0 °C to +70 °C Enclosure rating Enclosure rating IP 67 Supply voltage VS Current consumption DC 24 V +10 % / –20 % (incl. ripple) LPS Class 2 ≤ 50 mA with no load Power Tag Present (TP) LED green LED yellow Supply voltage LED function indicator M-401-... plastic (PBT) Process Control Equipment Control No 3TLJ File No E227256 CE Declaration of Conformity and user safety ☞ This product was developed and produced considering the claimed European standards and guidelines. You can separately request a Declaration of Conformity. Further safety measures you can find in chapter Safety (see 4). english 48 BIS M-4_ _ Ordering Information Part Numbers BIS M-4_ _-007-00_-0_-S115 Balluff Identification System Series M Hardware type 4_ _ = Processor 400 = M30 housing 401 = Maxisensor 451 = Maxisensor for data carrier on metal Software type 007 = Balluff-Protocol Hardware version 001 = Coil 002 = M18 read/write head Interface 00 = RS232 02 = RS422 (4-wires, point-to-point) Module S115 = M12 8-pole female 48 english 47 M-4_ _-007-S115_854304_0910_en.p65 49 BIS M-4_ _ Ordering Information Accessories (optional, not included in scope of delivery) Type Part No. Mating connector without cable Cable Cable (Pin assignments see (Pin assignments see BKS-S115-00 40) 40) BKS-S116-PU-.. 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 for 2 m cable BKS-S116-PU-15 Part number for 15 m cable For BIS M-4_ _-007-00_-0_-S115 and a baud rate of 19.200 cable length max. 15 m 9.600 cable length max. 20 m english 50 Symbols / Abbreviations DC Current LPS Limited Power Source Class 2 Function ground ESD Symbol 50 english 49 M-4_ _-007-S115_854304_0910_en.p65 51 Appendix, ASCII Table DeciControl Hex ASCII mal Code 00 Ctrl @ NUL DeciControl Hex ASCII mal Code 22 16 Ctrl V SYN DeciHex ASCII mal 44 2C DeciHex ASCII mal 65 41 DeciHex ASCII mal 86 56 DeciHex ASCII mal 107 6B 01 Ctrl A SOH 23 17 Ctrl W ETB 45 2D 66 42 87 57 108 6C 02 Ctrl B STX 24 18 Ctrl X CAN 46 2E 67 43 88 58 109 6D 03 Ctrl C ETX 25 19 Ctrl Y EM 47 2F 68 44 89 59 110 6E 04 Ctrl D EOT 26 1A Ctrl Z SUB 48 30 69 45 90 5A 111 6F 05 Ctrl E ENQ 27 1B Ctrl [ ESC 49 31 70 46 91 5B 112 70 06 Ctrl F ACK 28 1C Ctrl \ FS 50 32 71 47 92 5C 113 71 07 Ctrl G BEL 29 1D Ctrl ] GS 51 33 72 48 93 5D 114 72 08 Ctrl H BS 30 1E Ctrl ^ RS 52 34 73 49 94 5E 115 73 Ctrl _ US 53 35 74 4A 95 5F 116 74 SP 54 36 75 4B 96 60 117 75 09 Ctrl I HT 31 1F 10 0A Ctrl J LF 32 20 11 0B Ctrl K VT 33 21 55 37 76 4C 97 61 118 76 12 0C Ctrl L FF 34 22 56 38 77 4D 98 62 119 77 13 0D Ctrl M CR 35 23 57 39 78 4E 99 63 120 78 14 0E Ctrl N SO 36 24 58 3A 79 4F 100 64 121 79 15 0F Ctrl O SI 37 25 59 3B 80 50 101 65 122 7A 16 10 Ctrl P DLE 38 26 60 3C 81 51 102 66 123 7B 17 11 Ctrl Q DC1 39 27 61 3D 82 52 103 67 124 7C 18 12 Ctrl R DC2 40 28 62 3E 83 53 104 68 125 7D 19 13 Ctrl S DC3 41 29 63 3F 84 54 105 69 126 7E 20 14 Ctrl T DC4 42 2A 64 40 85 55 106 6A 127 7F DEL 21 15 Ctrl U NAK 43 2B english 51
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.6 Linearized : Yes XMP Toolkit : Adobe XMP Core 4.0-c316 44.253921, Sun Oct 01 2006 17:14:39 Producer : Acrobat Distiller 6.0.1 (Windows) Creator Tool : PageMaker 6.5 Modify Date : 2009:11:04 16:31:21+01:00 Create Date : 2009:10:29 17:26:41+01:00 Metadata Date : 2009:11:04 16:31:21+01:00 Document ID : uuid:67a8bef4-b73b-453c-a95f-6aa83754f23a Instance ID : uuid:4459e22c-f70c-44b4-a78e-4a27dffb8f80 Format : application/pdf Title : M-4_ _-007-S115_854304_0910_en.p65 Creator : heinz Page Count : 26 Author : heinzEXIF Metadata provided by EXIF.tools