PCS 91.BOS english Reg 10258/0100 One does not refer in the manual explicitly to the devices of the PCS plus/win series, the description applies to all devices. With differentiations between the equipment series the following allocations apply: PCS topline = micro/mini: PCS 009, PCS 090, PCS 095, PCS 095.1, PCS 095.
Systeme Lauer GmbH & CoKG Postfach 1465 D-72604 Nürtingen Operator reference manual: PCS 91.BOS Version: 04. Februar 2003 Person responsible: Zoch Operating manuals, reference manuals, and software are protected by copyright. All rights remain reserved. The copying, duplication, translation, conversion in the whole or into parts are not permitted. An exception applies to making a copy of the own use. • We reserve the right make changes to the reference manual without prior notice.
Notes for the user Please read the manual before beginning and keep the manual for later use. Target group The manual has been conceived and written for users who are experienced in the use of PCs and automation technology. Typographical conventions [KEY] Keys that are to be pressed by the user are given in square brackets, e.g [CTRL] or [DEL] Courier On-screen messages are given in the Courier font, e.g. C:\> Courier bold Keyboard input to be made by the user are given in Courier bold, e.g.
Inhaltsverzeichnis Notes for the user 0-3 Quality and support 0-5 Safety regulations 0-6 Norms 0-7 Information for driverselection 0-8 A LAUER driver A-1 First commisioning ......................................................... A-1 A1.1 Description of the handling software ........................ A-3 A1.2 Scan time extension ............................................... A-3 A1.3 Parameterization of the PCSKOMM PB .................. A-4 A1.4 Set-up of the cross-reference DB .................
Quality and support In our company, quality comes first. From the electronics component up to the finished device, the quality assurance test competently and comprehensively. National an internation test standards (ISO, TÜV, Germanischer Lloyd) are the basis. Within 48 hours, every device passes a 100% check and continuous test under worst case conditions at changing temperatures (0...50°C) and test voltages. A guarantee for maximum quality.
Safety regulations This reference manual contains the most important remarks in order to safely operate the device. 0-6 • This operator‚s guide, particulary the safety remarks are to be noted byall persons working with the device. • Furtherrmore, the rules and regulations for the accident prevention applying to the application location are to be observed. • Use as directed. The device is deigned for the application in the industrial area.
Norms The device is constructed using up-to-date technologies and fulfils the requirements of the following guidelines and norms: • Compliant with the EMC Directive 89/336/EEC and the German law on electro-magnetic compatibility • Interference compliant with the generic requirements norm EN 500812 and product norm EN 55022: • Measurement of the conducted interference voltage as per EN 55022 • Measurement of the radiated radio interference field power as per EN 55022 class A • Interference immunity
Information for driverselection A Lauer driver Communication with PCS micro/mini, plus/midi und maxi. Requires PLCProgramme. Operating panel: PCS 009/090/095/900/920/950 and 9000 PLC-system: CL300/CL400/CL500 Interface: PCS 830.1/830.3 Protocol: Lauer Protocol Adaptercable: PCS 736 Kind of driver: Expander driver B Buep 19-Expander driver Communication with PCS micro/mini, plus. Requires PLC-Programme.
A LAUER driver A1 First commisioning Adressing of the board The PCS 830 board is slot-independent. It uses 4EZ/AZ addresses (4 additional input bytes and 4 additional output bytes) and can be freely addressed in steps of 4 via the DIL-switch which is located on the board. Please take care that the set address does not intersect with already used addresses. Selection of the address Among others, the areas EZ0 to EZ63 and AZ0 to AZ63 are reserved for analog I/O boards.
A LAUER driver Example: Baud rate setting for 19200 baud. 8-segment DIL-switch (upper board edge): OFF log 0 ON log 1 DIL Nr.
A LAUER driver A1.1 Description of the handling software The enclosed -PCSKOMM PB manages the data transfer between the transfer area (a data block by default) and a PCS 830. The README.DOC file contains current notes concerning the use of the various projects. 1. The PB uses the MBs 246 to 255 as temporary flags. Writing to these MWs does not influence the PB as long as they are not simultaneously used by interrupt programs.
A LAUER driver Customer-specific presettings are to be inserted at 2 positions: PB INIT customer specific presetting for restart PB COFF customer specific assignment for an error case Attention! In all projects on the floppy disk, the INIT and COFF PBs are to be adjusted specifically for the connected operating console. The contained HLT commands are to be deleted. A1.
A LAUER driver A1.4 Set-up of the cross-reference DB The cross-reference data block contains 256 decimal word addresses. During a restart, these addresses are stored by the download procedure on the PCS 830 board. Values for these addresses must be taken from the CL300 software manual (operation list). The address pointers are required for indirect addressing. The PCS 830 board addresses must be specified in the first 3 words (0-2).
A LAUER driver Word no.: D0 D2 D4 Meaning: RDADR: Boards - base address +2 reading (EZ) WRADR: Boards - base address +2 writing (AZ) STAADR: Boards - base address +1 reading (EZ) A1.5 Operation the PLC with EPROM/EEPROM Please note the following. When using EPROM and EEPROM memory modules in the programmable controller, the communication area cannot be located within one data block since these data words are fixed in EPROM/EEPROM and thus cannot be manipulated anymore (write operations are not possible).
A LAUER driver The following transfer operations must be performed for the integration into your program (not required functions can be left out): • Before calling -PCSKOMM PB: all values read by the PCS must be copied into the corresponding DWs. This affects DW12 to DW22 and all variables but only if you do not directly access the corresponding words by altering the cross-reference data block (example: flag words, data buffers, input words etc.).
A LAUER driver A2 Communication Adaptercable PCS 736 The connection is made via 2 TTY channels. The PCS supplies the line current for both channels. Thus, a strict potential separation exists with regard to the programmable controller. When using shielded standard cable (4 * 0.
A LAUER driver Programming cable PCS 733 Connection PC to PCS Use this cable for programming (loading of the driver and user program) the PCS. Data transmission PCS-PCS 830 Data traffic between the PCS and the programmable controller is effected in data packets. Each data packet is assigned a checksum. The package content is checked for possible errors by the PCS 830. Each packet consists of a minimum of one sub-packet which performs a clearly defined task.
A LAUER driver The tasks are listed below in detail: TASK PRIOR. LENGTH START CRITERION 1. Write keyboard status 2. Reset message bit 3. Write PLC setpoint 8 7 6 3 2 2..3 4. Read actual values 5 2..24 *) 5. Read message bits 6. Send PCS status 7. Read LEDs, flashing LEDs, memory and display behavior 8. Read command word 4 4 9 3 3 3 3 4**) 9. Send time and date 2 3..
A LAUER driver • 55555 The handling PB performs the data interchange in both directions. The required times are to be taken from the description of the handling PB. • 6666666666666666666 The answer package is transferred. Also the length of this package is variable. As soon as the package is completely received by the PCS, a new package is assembled, as described under 1.
A LAUER driver A2.1 Description PCS 830.3/.1 handling Settings of the board adressing (6-segment DIL switch) The PCS board 830.3 is an interface module with three built-in TTY (20 mA) interfaces (active or passive). The PCS 830.1 is identical but it is only equipped with 1 TTY interface (2 current sources). It is used for the communication between a BOSCH programmable controllers CL300, CL400, CL500 or PC600 and one (PCS 830.1) or three (PCS 830.3) operating consoles. The PCS 830.3 and PCS 830.
A LAUER driver Address assignment table EZ/AZ 0-3 4-7 8-11 12-15 16-19 20-23 24-27 28-31 32-35 36-39 40-43 44-47 48-51 52-55 56-59 60-63 0-60 0-60 0-60 D0W 0E02 0E06 0E0A 0E0E 0E12 0E16 0E1A 0E1E 0E22 0E26 0E2A 0E2E 0E32 0E36 0E3A 0E3E 0EXX 0EXX 0EXX D1W 1002 1006 100A 100E 1012 1016 101A 101E 1022 1026 102A 102E 1032 1036 103A 103E 10XX 10XX 10XX The following table contains the possible address settings for the 3 channels of the PCS 830.3 (or 1 channel for the PCS 830.1).
A LAUER driver Channel parameters (8-segment DIL-switch) Using one 8-segment DIL-switch, parameter settings for the communication between the PCS-operating console and the PCS 830.3 can be separately made for each channel (at the PCS 830.1 likewise only one channel). The position of the DIL-switch segments for the corresponding channel can be take from section 1.16 and 1.17 (Specifications).
A LAUER driver Status indicators The PCS 830.3/31 features a 7-segment „ST.x“ display which informs about the state of the channel. The following display states are currently possible: „0“ programmable controller is set to „STOP“, i.e. the PCS 830.3/31 waits for the „RUN“ signal and/or for the outputs to be enabled. This display is simultaneously shown for all three channels. „1“ The corresponding channel waits for the complete reception of the cross-reference list.
A LAUER driver „.“ This point lights as so soon as the corresponding channel has received a tested package and is thus ready for the data interchange between the PCS 830.3/31 and the programmable controller. With an increasing data throughput this point will be dimmed (scan time depended). This can be influenced by specifying the ZV, S,... timeout parameter and the „AA“ driver parameter.
A LAUER driver The implementation is limited (besides the cyclical call of the PCSKOMM PB) to reading of and writing to the DWs in the transfer data block (only with default assignment!). The presence of the (selectable) transfer data block is not examined. It must be present in the programmable controller with the required net length (dynamic). Otherwise the programmable controller shows a fault (possibly only at the first call of a present value).
A LAUER driver The test and the repetition of the packages is organized in the PCS 830.3/ 1. The design of the PCSKOMM handling block contains provisions for aborting the communication on every coccuring fault and signalling it to the outside. After this, communication must be explecitely restarted using the RSETx input (P2 parameter). Of course, this does not affect repetitions caused by reparable faults as these are treated in the PCS 830.3/1 internally. A2.
A LAUER driver P3: Genral error message (here: -EROR1..EROR3) The P3 general fault bit is set for any error in the connection between the programmable controller and the PCS operating console. DW3 (default assignment) can be evaluated for the exact cause of error. This bit is reset as soon as the first packet has been correctly received. CL300, CL500, PC600: bit parameters (example - EROR1, A0.0) P4: Flag for the first processing of the handling block (here: FIRSTRU1..
A LAUER driver P7: Presetting PB (here: -COFF) Here, the PB must be specified which should be called at the communication start of the corresponding channel. This block must be generated for customer-specific presettings. This block is of course available on the floppy disk (once for all three channels) but it contains only one „HLT“ instruction which will switch the CPU to STOP (status „1“) with the remark to program the block.
A LAUER driver Example (CL300): D 44 W22 D 46 W23 word 0) D D 48 W24 (output word 1) D 50 W25 D 52 W26 Word Word N N 2092 0256 ;corresponds to D22W D ;corresponds to M0W (flag Word D Word Word N 0194 ;corresponds to A1W N N 2098 2100 ;corresponds to D27W ;corresponds to D26W D D Attention! Take note, that after re-adressing of the board (6-seg. DIL-switch) you must adjust the first three words of the cross-reference data. Word no.
A LAUER driver • CL500 Attention! The entire system (all processors) must be stopped and restarted after changing the cross-reference list. Otherwise the cross-reference list will not be newly transferred. No outputs (independantly of the processor) may be disabled when starting the entire system. This would result in a faulty reception of the cross-reference list. A2.
A LAUER driver The implementation has been successfully completed if the K8000H fault (time-out - no PCS connected) appears in DW3 (default assignment) and the flags P4 (restart) and P3 (general error message) are both set to logical 1. In addition, the PCS 830.3/1 must indicate the „STATUS“ value „7“ for all accessed channels. An example (OB1) is contained on the floppy disk which indicates a fault on output A0.0..0.2, expects a reset pushbutton on E0.0..E0.2, uses the flag M20.0..M20.
A LAUER driver A3 Program listing Tip! Inspect the function of the handling software to avoid failures of the PCS or PLC. Statement listing CL300 Prg. contr. documentation Projekt: 3P83110/ZS0 1 2 3 4 5 6 7 8 PZ: UN U = 1 B B B 4 A-24 Date: Apr.
A LAUER driver 5 6 UN = PZ: U UN = BE 7 8 9 10 B B 3 B B B -FIRSTRU2 -FIRSTRU2 ;FLAG FOR FIRST SCAN PCS2 SET TO ZERO -FIRSTRU3 -FIRSTRU3 -FIRSTRU3 ;FLAG FOR FIRST SCAN PCS3 SET TO ZERO Prg. contr. documentation Projekt: 3P83110/ZS0 1 2 3 4 5 6 7 8 9 10 PZ: U UN = PZ: U UN = PZ: U UN = BE 1 B B B 2 B B B 3 B B B Bosch CL300 Version 3.30z File: OB8.P3O (OB8) Date: Apr.
A LAUER driver Statement listing CL400/CL500 Since the listing of the CL400 is absolutely identical to the CL500 it is not printed here. Prg. contr. documentation Projekt: 5P83110/ZS0 1 2 3 4 5 6 7 8 DEF PZ: U = Bosch CL500 Version 3.30z Date: Apr. 4, 1995 File: OB1.P5O (OB1) Page: 2 SM30.3.
A LAUER driver Prg. contr. documentation Projekt: 5P83110/ZS0 1 2 3 4 5 DEF PZ: U = = = BE Bosch CL500 Version 3.30z File: OB6.P5O (OB6) SM30.3.-LOGO 1 B B B B -LOGO -FIRSTRU1 -FIRSTRU2 -FIRSTRU3 ;FLAG FOR FIRST SCAN PCS1 SET TO ZERO ;FLAG FOR FIRST SCAN PCS2 SET TO ZERO ;FLAG FOR FIRST SCAN PCS3 SET TO ZERO Prg. contr. documentation Projekt: 5P83110/ZS0 1 2 3 4 5 DEF PZ: U = = = BE Bosch CL500 Version 3.30z File: OB7.P5O (OB7) 1 2 3 4 5 Date: Apr. 4, 1995 Page: 6 SM30.3.
A LAUER driver Prg. contr. documentation Projekt: 5P83110/ZS0 Bosch CL500 Version 3.30z File: COFF.P5O (PB2) Date: Apr.
A 5 6 7 8 9 LAUER driver ;*****HANDLING BLOCK PCS2***** PZ: 2 UN B -QVL_OUT ;ONE XREF DATA BLOCK PER SCAN CYCLE ->PCS830.
A LAUER driver Prg. contr. documentation Projekt: 6P83110/ZS0 4 5 6 PZ: U UN = PZ: U UN = 1 B B B 2 B B B 7 8 9 U UN = B B B 10 BE 1 2 3 -FIRSTRU1 -FIRSTRU1 -FIRSTRU1 -FIRSTRU2 -FIRSTRU2 -FIRSTRU2 -FIRSTRU3 -FIRSTRU3 -FIRSTRU3 Prg. contr. documentation Projekt: 6P83110/ZS0 Bosch PC600 Version 3.30z File: OB29.P60 (OB29) Date: Apr. 4, 1995 Page: 6 ;FLAG FOR FIRST SCAN PCS3 SET TO ZERO ;FLAG FOR FIRST SCAN PCS3 SET TO ZERO PZ: 3 ;FLAG FOR FIRST SCAN PCS3 SET TO ZERO Bosch PC600 Version 3.
A LAUER driver Prg. contr. documentation Projekt: 6P83110/ZS0 Bosch PC600 Version 3.30z File: COFF.P60 (PB1) Date: Apr.
A LAUER driver A4 Technical apendix A4.1 PCS 830.3 This part of the manual contains special informations which are reqiered for the setup: cable assignment, transfer addresses and a short explanation of the data transfer using the communication port and the I/O bus. Mechanical design Board with 64-pole DIN 41612 „C“ connector Power supply Via motherboard: 12 V Current requirement 300 mA max.
A LAUER driver Circuit board diagram X1 (DIN 41612 „C“ connector) D1-3: 8-segment DILs, channel parameters (1 per cannel) D4-6: 6-segment DILs, addressing in the EZ/AZ-field (1 per cannel) A4.2 PCS 830.1 Mechanical design Board with 64-pole DIN 41612 „C“ connector Power supply Via motherboard: 12 V Current requirement 250 mA max.
A LAUER driver Circuit board diagram X1 (DIN 41612 „C“ connector) D1: 8-segment DIL, channel parameters D2: 6-segment DIL, addressing RIA (24V, earth, 0V): 3-pole inline connector for the active operation of the current sources A4.3 Interfaces TTY1..3 Pin assignment of the TTY interfaces: Pin no. Case 1 10 12 13 14 16 19 21,24 Meaning screen (connec. with frontplate and RIA shield. termin.) „ „ „ „ „ „ „ TX+ current source 1 (20mA) active with stab.
A LAUER driver Communications cable PCS 736 For each interface, the connection is made via 2 TTY channels. The line currents for both channels are supplied by the PCS operating console. Thus, the programmable controller is galvanically isolated. When using shielded standard cable (2 * 2 * 0.
A LAUER driver A4.4 Data transfer PCS 830.x I/O BUS The PCS 830.3/31 uses for each channel (separately settable) 4 addresses respectively in the EZ/AZ area on the I/O bus.
B Buep 19-Expander driver B1 First commissioning Preface The successful parameterization of the PCS 009/090/095/PCS plus as described in the PCS manual is presupposed. This appendix relates exclusively to the use of the PCS together with the BOSCH CL300 programmable controller via the programming interface by means of the BUEP19 protocol. In the following, this controller is referred to as programmable controller and the driver to be loaded into the PCS as 3P90BUEP.
B Buep 19-Expander driver Interfaces Interface and baud rate can be selected from combinations set with the DIL switches 5 and 6 on the rearside of the PCS 090. The choice consists of: RS-232C or TTY, 19200, 9600, 4800, or 1200 baud. The speed of the communication depends decisively on the baud rate (e.g. a changed variable must be read 2 times!). Select only on a slower baud rate if you have longer distances between the participants. We recommend to communicate with 19200 baud via TTY.
B Buep 19-Expander driver Connection to the PLC Trouble-shooting 1. Set DIL switches 8 and 9 on the rear side of the PCS to OFF. The DIL switches 5 and 6 are set according to the selected baud rate and interface. Initiate a PCS reset. 2. Supply operating voltage (19..33V) to the PCS. At least the ERR LED must light now. 3. Connect the programming interface of the programmable controller to the PCS using a suited cable. 4. Now, the ERR LED at the PCS must be activated.
B Buep 19-Expander driver • TIMEOUT Time monitoring for the serial data interchange is active in the PCS as well as in the programmable controller. In case of an error, an error message is displayed on the PCS and the ERROR LED flashes. The PCS tries to set up communication again in the background. The error message is erased if this has been successful. In the PCSPRO, the timeout time for order processing is adjustable in the range of 500ms to 2.55 s.
B Buep 19-Expander driver Notes concerning the connection of the PCS to a PLC: • Connect the cable screening to the central common of the control cabinet. • Ensure appropriate chassis groundings with regard to the PCS housing on the one hand and the PLC bus board on the other. Remember that a copper grounding strip, due to its large surface, ensures a considerably higher RF conductivity than normal stranded interconnecting wire.
B Buep 19-Expander driver B1.2 Description of the handling software The 3P90BUEP communication block is located on the PCS 91.BOS floppy disk. The scan time without user program (only PCSKOMM and the I/O cycle) totals about 40 ms. A maximum of 80 ms are possible. Since the maximum scan time of the ZE300 totals 1600ms the user program should not require more than approx. 1500 ms.
B Buep 19-Expander driver P3: General error message (bit, here A0.0) The P3 general fault bit is set for any error in the connection between the programmable controller and the PCS. This bit is automatically reset as soon as the communication is running without a fault. P4: Flag for the first processing of the handling block (bit, here M20.0) This flag should be reset before the first call of the handling block. At the first execution, it is automatically set to 1.
B Buep 19-Expander driver Now, the ERR LED (PCS) and the A0.0 output LED (programmable controller) must have been deactivated. Also the 7-segment display at the CPU must remain dark. Thus, the communication is active. Attention! In all projects on the floppy disk, the INIT and COFF PBs are to be adjusted specifically for the connected operating console. The contained HLT commands are to be deleted. B1.
B Buep 19-Expander driver B2 Communication Adapter cable PCS 706 Connection of the PCS - PLC via TTY interface LCA 035/235 PCS to PLC via RS-232 interface Use a zero-modem cable for the connection of the PLC to PCS via RS-232C. Systeme Lauer offers the LCA 035/235 cable for this purpose. The necessary connections are as follows: © Systeme Lauer GmbH & Co KG • Kelterstr.59 • 72669 Unterensingen • Tel.
B Buep 19-Expander driver Screening The shield should be connected on both sides to a metallized connector hood. If non-metallized connector hoods are used, the shield may also be connected to pin 1, but this is not recommended due to interferences, because the data lines should be completely covered by the shield (if possible).
B Buep 19-Expander driver The tasks are listed below in detail: TASK PRIOR. LENGTH 1. Write keyboard status 2. Reset message bit 3. Write PLC setpiont 8 7 6 3 2 2..3 4. Read actual values 5 2..24*) 5. Read message bits 6. Send PCS status 7. Read LEDs, flashing LEDs, memory and display behavior 8. Read command word 4 4 3 9 max.
B Buep 19-Expander driver Structure of the reading cycle: PCS ENQ READ DATA DB AREA —— → ← → PLC ACK ← → ← ACK → ← ACK → ← Structure of the writing cycle: ACK PCS ENQ —— → ← → SPS ← → ← → ← ACK EOT WRITE DATA DB AREA EOT ACK PERFORMED ACK → ← ENQ DATA THE DB AREA EOT ACK ENQ ORDER SUCCESSFULLY EOT The packets designated above as „data“ specify the real content of the communication.
C Buep 19e-Expander driver C1 First commissioning Preface The successful parameterization of the PCS as described in the PCS 091/991/925/995 manual is presupposed. This appendix relates exclusively to the use of the PCS micro/mini/midi and plus together with the BOSCH CL200/CL400/CL500 PLC via the programming interface by means of the BUEP19E protocol. In the following, this controller is referred to as programmable controller and the driver to be loaded into the PCS as 5P90BUEP.
C Buep 19e-Expander driver Loading of the 5P90BUEP Driver After selecting the 5P90BUEP driver in PCSPRO you have to set various variables which are used by the drivers for the correct addressing of the programmable controller. These are: baud rate, interface, data block number, board address, number of sub-packets and timeout time. Interfaces Interface and baud rate can be selected from combinations set with the DIL switches 5 and 6 on the rearside of the PCS 090.
C Buep 19e-Expander driver Connection of the PCS to the PLC 1. Set DIL-switch 8 to „OFF“ and DIL 9 to „ON“ (on the rearside the PCS). Set the DIL-switches 5 and 6 according to the selected baud rate and interface. Initiate a reset of the PCS. 2. Apply operating voltage (19..33V) to the PCS. At least the ERR LED must light now. 3. Connect the programming interface of the programmable controller to the PCS using a suited cable. 4. Set the P2 restart input to „1“. 5.
C Buep 19e-Expander driver Communication ERROR When communicating with each other the PCS operates as master (AST) and the PLC as slave (PST). Thus, it is the PCS´s task to set up the communication and to perform monitoring. Thereby, 3 criteria must be monitored: is communication active, is communication processing in the PLC active, and does the PLC indicate faults. Data are transferred to/ read from the PLC via the BUEP19E protocol. The timeout times for the protocol are fixed (2.4s max.
C Buep 19e-Expander driver Notes concerning the connection of the PCS to a PLC: • Connect the cable screening to the central common of the control cabinet. • Ensure appropriate chassis groundings with regard to the PCS housing on the one hand and the PLC bus board on the other. Remember that a copper grounding strip, due to its large surface, ensures a considerably higher RF conductivity than normal stranded interconnecting wire.
C Buep 19e-Expander driver C1.2 Description of the handling software The 3P90BUEP communication block is located on the BOSCH floppy disk. The scan time load is less than 1 ms. The effective response time speed between PLC and PCS depends on the baud rate and the cyclical call time of PCS_KOMM. The response time is approx. 0.2 seconds without user program and 19200 baud communication rate. Description of the programs • OB1 Call of the programs using parameters.
C Buep 19e-Expander driver P3: Name of the used timer for timeout (here: T0) P4: Time value for timeout monitoring. Structure: e.g. K4.2 = 4 seconds timeout multiplication element 1 = 100 ms, 2 = 1 s value P5: General error message (bit, here M100.0) The P5 general fault bit is set for any error in the connection between the programmable controller and the PCS. This bit is automatically reset as soon as the communication is running without a fault. C1.3 Implementation of the software The README.
C Buep 19e-Expander driver C1.
C Buep 19e-Expander driver C2 Communication Adapter cable PCS 706 Connection PCS to PLC via TTY interface Screening The shield should be connected on both sides to a metallized connector hood. If non-metallized connector hoods are used, the shield may also be connected to pin 1, but this is not recommended due to interferences, because the data lines should be completely covered by the shield (if possible).
C C-10 Buep 19e-Expander driver LCA 035/235 PCS to PLC via RS-232 interface Use a zero-modem cable for the connection of the PLC to PCS via RS-232C. Systeme Lauer offers the LCA 035/235 cable for this purpose. The necessary connections are as follows: Programming cable PCS 733 Connection PLC to PCS Use this cable for the programming (loading of the driver and user program) of the PCS. © Systeme Lauer GmbH & Co KG • Kelterstr.59 • 72669 Unterensingen • Tel.
C Buep 19e-Expander driver Data transmission PCS-PLC Data transfer between the PCS and the PLC is effected in data packets. Each data packet is assigned a checksum (CRC). The package content is checked for possible errors by the PLC operating system and the PCS. Each packet consists of a minimum of one sub-packet which performs a clearly defined task. The tasks to be integrated in a packet are determined by the PCS based on numerous single criteria. A criterion represents the importance of a task.
C Buep 19e-Expander driver It is the master´s task to set up the communication and to send orders to the PLC. PCS and PLC communicate with the following settings: TTY or RS-232C, 19200/9600/4800/1200 baud, 8 bit, EVEN parity, 1 stop bit. Only the interchange of the packets is described in this manual. Refer to the BOSCH „BUEP 19 transfer protocol“ manual for the structuring of the packets.
D Buep 19e-Direct driver D1 First commissioning Preface The successful parameterization of the PCS as described in the PCSPRO manual is presupposed. This appendix relates exclusively to the use of the PCS 900/950 together with the BOSCH PLC by means of the BUEP19E protocol. In the following, this controller is referred to as PLC and the driver to be loaded into the PCS as B19EDIR. The BOSCH specific terminology and the programming of the PLC with the BOSCH software are presupposed as known.
D Buep 19e-Direct driver Loading of the 5P90BUEP driver After selecting the 5P90BUEP driver in PCSPRO you have to set various variables which are used by the drivers for the correct addressing of the PLC. These are: baud rate, interface, cross-reference list, board address, and timeout time. Interfaces Interface and baud rate can be selected from combinations set with the DIL switches 5 and 6 on the rearside of the PCS. The choice consists of: RS-232C or TTY, 19200, 9600, or 4800 baud.
D Buep 19e-Direct driver Connection to the PLC After setting and loading the programmable controller corresponding to section 4.5 and 4.6, you can connect the PCS to the PLC corresponding to the following instructions. Attention! Check the function of the PCS after parameterization and/or driver installation. All parameterized functions must be examined. Otherwise, malfunctions of the PCS and/or the programmable controller are possible. Trouble-shooting 1.
D Buep 19e-Direct driver Communication ERROR When communicating with each other the PCS operates as master (AST) and the PLC as slave (PST). Thus, it is the PCS´s task to set up the communication and to perform monitoring. Thereby, 3 criteria must be monitored: is communication active, is communication processing in the PLC active, and does the PLC in dicate faults. Data are transferred to/ read from the PLC via the BUEP19E protocol. The timeout times for the protocol are fixed (2.4s max.
D Buep 19e-Direct driver Notes concerning the connection of the PCS to a PLC: • Connect the cable screening to the central common of the control cabinet. • Ensure appropriate chassis groundings with regard to the PCS housing on the one hand and the PLC bus board on the other. Remember that a copper grounding strip, due to its large surface, ensures a considerably higher RF conductivity than normal stranded interconnecting wire.
D Buep 19e-Direct driver The BOSMULPS communication block is located on the BOSCH floppy disk. The effective response time speed between PLC and PCS depends on the baud rate, the used interface, and the data volume. E.g. the SK interface is therefore approx. 50% slower than the direct CPU interface. • Access types The used B19EDIR driver is a direct driver i.e. it exchanges data words between the PLC and the PCS directly. No or just a small PLC program is required.
D Buep 19e-Direct driver D1.2 Synchronous communication The access to the data in the PLC must be synchronized if you want to make use of the entire functional extent of the PCS. I.e. the PLC and the PCS access data alternately. Therefore, a synchronization word is transmitted to the PLC. OB1 examines this word and releases the access of the PLC application program in the „test“ program.
D Buep 19e-Direct driver D1.3 Description of the handling software • OB1 Call of the programs using parameters. Change the settings for the PCS_KOMM program here.Thus, no changes are required in PCS_KOMM. The „TEST“ data access program is selected in PCS_KOMM. • Test Example for a data access: F1 activates the menu 1, F2 disabled all menus, F3 sets the message bits M0..15, F4 disables these message bits again. The keys are copied to the LEDS.
D Buep 19e-Direct driver Other: Timer T1 „TIMER“ is used for timeout monitoring in the PCS_KOMM program. INIT Determines the initialization values of the PCS data area. Here, you can pre-assign the interlocks for the data transfer. Allow only so much data exchange as needed. With the exchange of fewer data, the communica-tion speed is increased. COFF Determines the measures at a communication loss. The block is executed once after a communication loss.
D Buep 19e-Direct driver • Set the E0.0 input to „1“ Now, the ERR LED (PCS) and the A0.0 output LED (PLC) must have been deactivated. Also the 7-segment display at the SK must remain dark. Thus, the communication is active. Using this protocol, the addressed CPU can be accessed from an arbitrary programming unit connector. This way, it is possible to manage several PCSs by one CPU if each PCS is assigned it´s own communication block and data block.
D Buep 19e-Direct driver R200 coupling card settings Pay attention that in the CPU of the CL200 is loadrd at least the Firmware version 1.5 of 06.03.1996 eingespielt ist. On the settings of the card pay attention to the DIP-switches S1 and S2.
D Buep 19e-Direct driver D2 Communication Adapter cable PCS 706 Connection PCS-PLC via TTY interface Screening The shield should be connected on both sides to a metallized connector hood. If non-metallized connector hoods are used, the shield may also be connected to pin 1, but this is not recommended due to interferences, because the data lines should be completely covered by the shield (if possible).
D Buep 19e-Direct driver LCA 035/235 PCS to PLC via RS-232 interface Use a zero-modem cable for the connection of the PLC to PCS via RS-232C. The necessary connections are as follows: Programming cable PCS 733 Connection PLC to PCS Use this cable for the programming (loading of the driver and user program) of the PCS. © Systeme Lauer GmbH & Co KG • Kelterstr.59 • 72669 Unterensingen • Tel.
D Buep 19e-Direct driver D3 Program listing ;************************************************************************** ; OB1 ;************************************************************************** ; File name: OB1 ; Function: Organizational block 1 2 3 4 ;************************************************************************** ; P r o g r a m ;************************************************************************** BA -PCS_KOMM,6 P0 W -DB1 P1 B -RESTART P2 W K4.2 P3 B M100.
D Buep 19e-Direct driver ;************************************************************************** ; P r o g r a m ;************************************************************************** 1 BX -P0 ; open PCS DB ;************************************************************************** ; Processor reset => INIT ;———————————————————PZ: 1 2 U B -P_RI ; start after Halt 3 O B -NEU_RI ; restart 4 SPB -START_KO ; ------> ; no processing in case of timeout and restart input = 0 ;———————————————————————————
D Buep 19e-Direct driver -TEST PB1 -TIMER 28 29 30 31 32 PCS data access example T0 PCS communication watch dog timer ; set fault watch dog has triggered ;————————————————————————————— -KOM_FEL S B -P3 ; watch dog is active X0 W D,D ; initialize application data block ;————————————————————————————BA -P0 ; open user data block BA -P5 ; COFF BE ; ————————————————————> ; End watch dog ; ******************************************************************* ; ************************************************
D 1 Buep 19e-Direct driver ;************************************************************************** ; TEST: Example program for PCS 090/095 data access ;************************************************************************** BA -DB1 ; open data block 2 3 4 L VGL SPN W W D8,A K8000H,A -TEST1 5 6 L T W W K0081H,A A,D28 ; F1 -> preset value menu 1 -TEST1 7 8 9 L VGL SPN W W D8,A K4000H,A -TEST2 10 11 L T W W K0000H,A A,D28 ; F2 -> preset value menu 1 off -TEST2 12 13 14 L VGL SPN W
D Buep 19e-Direct driver ;*********************************************************************************************** ;** COFF (APPLICATION-SPECIFIC ERROR PRESETTING; PCS COMMUNICATIONS LOSS) ;*********************************************************************************************** ;!!!!! ADD ;********************************** ;********************************** ;********************************** ;********************************** ;********************************** 1 2 3 4 PCS AND EQUIPMEN
Index A L Adapter cable ........................ A-8, B-9, C-9, D-12 Address assignment table ............................... A-13 Adressing of the board ...................................... A-1 Asynchronous communication .......................... D-6 LCA 035/235 ................................ B-9, C-10, D-13 Loading of the 3P90BUEP driver ....................... B-1 Loading of the 5P90BUEP Driver ..................... C-2 Loading of the 5P90BUEP driver ......................
Index V Variable settings ................................................ B-1 Z ZV,S parameters .............................................. A-10 i-2 © Systeme Lauer GmbH & Co KG • Kelterstr.59 • 72669 Unterensingen • Tel.
