User Manual UM EN IL PB BK DI8 DO4/EF-PAC - RealPars
AUTOMATIONUser manualUM ENIL PB BK DI8 DO4/EF-PACOrder No. –Diagnostic and firmware functionsof the IL PB BK DI8 DO4/EF-PAC bus coupler
AUTOMATIONUser manualDiagnostic and firmware functions of the IL PB BK DI8 DO4/EF-PAC buscoupler12/2009Designation:UM EN IL PB BK DI8 DO4/EF-PACRevision:01Order No.:–This user manual is valid for:DesignationOrder No.IL PB BK DI8 DO4/EF-PAC26923227725 en 01PHOENIX CONTACT
IL PB BK DI8 DO4/EF-PACPlease observe the following notesIn order to ensure the safe use of the product described, you have to read and understandthis manual. The following notes provide information on how to use this manual.User group of this manualThe use of products described in this manual is oriented exclusively toPhoenix Contact accepts no liability for erroneous handling or damage to products fromPhoenix Contact or third-party products resulting from disregard of information contained inthis manual.Explanation of symbols used and signal wordsThis is the safety alert symbol. It is used to alert you to potential personal injuryhazards. Obey all safety messages that follow this symbol to avoid possibleinjury or death.DANGERThis indicates a hazardous situation which, if not avoided, will result in death or seriousinjury.WARNINGThis indicates a hazardous situation which, if not avoided, could result in death or seriousinjury.CAUTIONThis indicates a hazardous situation which, if not avoided, could result in minor ormoderate injury.The following types of messages provide information about possible property damage andgeneral information concerning proper operation and ease-of-use.NOTEThis symbol and the accompanying text alerts the reader to a situation which may causedamage or malfunction to the device, either hardware or software, or surroundingproperty.This symbol and the accompanying text provides additional information to the reader. It isalso used as a reference to other sources of information (manuals, data sheets, literature)on the subject matter, product, etc.PHOENIX CONTACT7725 en 01
IL PB BK DI8 DO4/EF-PACGeneral terms and conditions of use for technical documentationPhoenix Contact reserves the right to alter, correct, and/or improve the technicaldocumentation and the products described in the technical documentation at its owndiscretion and without giving prior notice, insofar as this is reasonable for the user. Thesame applies to any technical changes that serve the purpose of technical progress.The receipt of technical documentation (in particular data sheets, installation instructions,manuals, etc.) does not constitute any further duty on the part of Phoenix Contact to furnishinformation on alterations to products and/or technical documentation. Any otheragreement shall only apply if expressly confirmed in writing by Phoenix Contact. Pleasenote that the supplied documentation is product-specific documentation only and that youare responsible for checking the suitability and intended use of the products in your specificapplication, in particular with regard to observing the applicable standards and regulations.Although Phoenix Contact makes every effort to ensure that the information content isaccurate, up-to-date, and state-of-the-art, technical inaccuracies and/or printing errors inthe information cannot be ruled out. Phoenix Contact does not offer any guarantees as tothe reliability, accuracy or completeness of the information. All information made availablein the technical data is supplied without any accompanying guarantee, whether expresslymentioned, implied or tacitly assumed. This information does not include any guaranteesregarding quality, does not describe any fair marketable quality, and does not make anyclaims as to quality guarantees or guarantees regarding the suitability for a special purpose.Phoenix Contact accepts no liability or responsibility for errors or omissions in the contentof the technical documentation (in particular data sheets, installation instructions, manuals,etc.).The aforementioned limitations of liability and exemptions from liability do not apply, in sofar as liability must be assumed, e.g., according to product liability law, in cases ofpremeditation, gross negligence, on account of loss of life, physical injury or damage tohealth or on account of the violation of important contractual obligations. Claims fordamages for the violation of important contractual obligations are, however, limited tocontract-typical, predictable damages, provided there is no premeditation or grossnegligence, or that liability is assumed on account of loss of life, physical injury or damageto health. This ruling does not imply a change in the burden of proof to the detriment of theuser.7725 en 01PHOENIX CONTACT
IL PB BK DI8 DO4/EF-PACStatement of legal authorityThis manual, including all illustrations contained herein, is copyright protected. Use of thismanual by any third party is forbidden. Reproduction, translation, and public disclosure, aswell as electronic and photographic archiving or alteration requires the express writtenconsent of Phoenix Contact. Violators are liable for damages.Phoenix Contact reserves all rights in the case of patent award or listing of a registereddesign. Third-party products are always named without reference to patent rights. Theexistence of such rights shall not be excluded.How to contact usInternetUp-to-date information on Phoenix Contact products and our Terms and Conditions can befound on the Internet at:www.phoenixcontact.com.Make sure you always use the latest documentation.It can be downloaded lished byIf there are any problems that cannot be solved using the documentation, please contactyour Phoenix Contact subsidiary.Subsidiary contact information is available at www.phoenixcontact.com.PHOENIX CONTACT GmbH & Co. KGFlachsmarktstraße 832825 BlombergGermanyPhone 49 - (0) 52 35 - 3-00Fax 49 - (0) 52 35 - 3-4 12 00Should you have any suggestions or recommendations for improvement of the contents andlayout of our manuals, please send your comments totecdoc@phoenixcontact.com.PHOENIX CONTACT7725 en 01
Table of contents1The PROFIBUS bus coupler .1-12Diagnostics .2-1342.1Activating/deactivating the diagnostic formats.2-12.1.1Diagnostics in the IL PB BK DI8 DO4 format . 2-22.1.2Status PDU diagnostic format . 2-82.1.3ID-specific diagnostic format .2-92.2Representing the error codes .2-102.2.1Local diagnostic indicators .2-102.2.2Error type and error no. .2-11Acyclic communication (DP/V1 and PCP) .3-13.1Acyclic communication via the Class 1 master (C1 master) . 3-13.2Acyclic communication via the Class 2 master (C2 master) . 3-13.3PCP communication basics.3-23.4Acyclic communication in DP/V1 mode . 3-43.4.1The communication mechanism .3-43.4.2Examples . 3-73.5Acyclic communication in DP/V0 mode via process data .3-133.5.1Mechanism for transmission in the process data .3-133.5.2Examples for VC1 services . 3-18Dynamic configuration .4-14.1Empty spaces. 4-14.2Principle of dynamic configuration . 4-44.3Startup. 4-64.3.1Planning configuration . 4-64.3.2Options for specifying the active configuration . 4-74.3.3Specifying the active configuration via DP/V0 . 4-84.3.4Specifying the active configuration via DP/V1 . 4-114.3.5Summary . 4-125PROFIsafe application notes .5-16IO-Link .6-16.1AIO-Link call .6-1Appendix . A-17725 en 01A1Error codes for PCP communication. A-1A2Error codes for DP/V1 and VC1 communication. A-3A3Error codes for F-Parameters . A-4A4Format of the parameter telegram . A-5PHOENIX CONTACTi
IL PB BK DI8 DO4/EF-PACBiiObject dictionaries . B-1PHOENIX CONTACTB1Slot 0 . B-1B2Slot 1 . B-8B3Slots 2 to 63. B-87725 en 01
The PROFIBUS bus coupler1The PROFIBUS bus couplerPROFIBUS bus couplerThe PROFIBUS bus coupler configures the station and manages data exchange with aPROFIBUS master. It also provides the power supply for the connected Inline terminals.PROFIsafe I/O modules can also be used.The PROFIBUS bus coupler can be ordered using Order No. 2692322. Connectors,labeling fields, and an end plate are supplied as standard.41I2ACF-PO4/EI8 DK D 322B B 692IL P r-No.: 2eOrdSIBUOFPR0 24O1PWR0 241210 3X127725A001Figure 1-1Scope of supply7725 en 01––––The IL PB BK DI8 DO4/EF-PAC PROFIBUS bus couplerPROFIBUS bus coupler (1)Connectors (2)Labeling field (3)End plate (4)PHOENIX CONTACT1-1
IL PB BK DI8 �–––PROFIBUS connection via 9-pos. D-SUB female connectorInterface physics RS-485 for PROFIBUSElectrical isolation of PROFIBUS interface and logicDP/V1 for Class 1 and Class 2 mastersData transmission speed of 9.6 kbps up to 12 Mbps(automatic detection)Rotary encoding switches for setting the PROFIBUS addressSupported PROFIBUS addresses 1 to 126Up to 16 PCP devices can be connectedDevice description using GSD fileI & M functionsEight digital inputsFour digital outputsDiagnostic and status LEDsAutomatic baud rate detection on the local bus (500 kbps or 20 Mbps)Additional features of EF version:– Approved for PROFIsafe– IO-Link call (firmware 2.0 or later)When using the bus coupler in a PROFIsafe system, please refer to the documentation forthe safety terminals used (see "PROFIsafe application notes" on page 5-1).For additional information about the bus coupler, please refer to the following documents:Data sheet: DB EN IL PB BK DI8 DO4/EF-PACUser manual: IL SYS INST UM E, Order No. 2698737They can be downloaded at:www.phoenixcontact.net/catalogConfiguration and start-up with the Step7 SIMATIC Manager are described in detail in theUM EN IL PB BK DP/V1 user manual.1-2PHOENIX CONTACT7725 en 01
Diagnostics2DiagnosticsThe diagnostic concept for the bus coupler consists of two components. Firstly, diagnosticdata is supplied to the control system via PROFIBUS in the form of diagnostic bytes.Secondly, local diagnostics are available, whereby the error type is indicated by the specificflashing codes of the LEDs on the bus coupler.2.1Activating/deactivating the diagnostic formatsThe diagnostic format can be set as a parameter on the terminal. You can select either"IL PB BK DI8 DO4 Format", "Status-PDU Diagnostics" or "ID-Specific Diagnostics". Bydefault, "IL PB BK DI8 DO4 Format" is activated. The"Status-PDU Diagnostics" format mustbe set for diagnostics of PROFIsafe I/O modules.Figure 2-17725 en 01Diagnostic formats dialog boxPHOENIX CONTACT2-1
IL PB BK DI8 DO4/EF-PAC2.1.1Diagnostics in the IL PB BK DI8 DO4 formatThis diagnostic format consists of the following blocks:1 PROFIBUS standard diagnostics2 ID-specific diagnostics3 Status diagnostics (terminal status)4 Channel-specific diagnostics5 Revision diagnostics (manufacturer-specific)6 Status-PDU (manufacturer-specific)From block 2 onwards the diagnostic telegram is dynamic. The individual number of bytesin a block depends on the station structure.The header bytes are used to distinguish between all blocks.Table 2-1ByteIL PB BK DI8 DO4-PAC format diagnosticsBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0Meaning1XXXXXXXXStation status 12XXXXXXXXStation status 23XXXXXXXXStation status 34XXXXXXXXPROFIBUS master address500001011Manufacturer ID high byte (0Bhex)601010000Manufacturer ID low byte (50hex)Block 1Block 27018LD 8LD 7LD 6LD 5LD 4LD 3LD 2LD 1Local bus devices 1 to 89LD 16LD 15LD 14LD 13LD 12LD 11LD 10LD 9Local bus devices 9 to 16.150LD 63LD 62LD 61LD 60LD 59LD 58LD 572-2PHOENIX CONTACTNumber of local bus devicesID-specific diagnostics (header).Local bus devices 57 to 637725 en 01
DiagnosticsTable 2-1ByteIL PB BK DI8 DO4-PAC format diagnosticsBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0Meaning16001710000010Status type terminal status1800000000Slot ( 0 general status of the buscoupler)19000000SPSPBlock 3Number of local bus devicesStatus (header)Specifier20ST LD 4ST LD 3ST LD 2ST LD 1Status, local bus devices 1 to 421ST LD 8ST LD 7ST LD 6ST LD 5Status, local bus devices 5 to 8. 35 0 ST LD 63 ST LD 62 ST LD 61 Status, local bus devices 61 to 63Block 4361370IO38.ChannelCT1.CT.107725 en 01Channel-specific diagnostics (header)slot 2Channel.65Channel and error type slot 1Slot numberIO.IN/OUT and channel number slot 1ET0.Channel-specific diagnostics (header)slot 1SlotIOET.Slot numberChannelCTIN/OUT and channel number slot 2ETChannel and error type slot 1.Channel-specific diagnostics (header)slot 10IN/OUT and channel number slot 10Channel and error type slot 10PHOENIX CONTACT2-3
IL PB BK DI8 DO4/EF-PACTable 2-1ByteIL PB BK DI8 DO4-PAC format diagnosticsBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0Meaning11XXXXXXVersion (start with C1)6700001100Status (header)6810100000Reserved (header)6900000000Reserved (header)7000000000Reserved (header)71000000BBLocal bus baud rate1 500 kbaud2 2 Mbaud72XXXXXXXXDiagnostic location (FF OK)73XXXXXXXXUser ID code,1st local bus device with error74XXXXXXXXUser length code,1st local bus device with error75XXXXXXXXLB state (high byte)76XXXXXXXXLB state (low byte)770000000XSystem limit violated?78XXXXXXXXNumber of accessible local bus devicesBlock 566Block 62-4PHOENIX CONTACT7725 en 01
DiagnosticsBlock 1: PROFIBUS standard diagnosticsX:Value 1 is activated. Value 0 is deactivated.M: Slave transmits 0, master adds if necessary.Table 2-27Byte 1: Status 16543210MXSlave is not ready for data exchangeXError in configuration telegramXExtended diagnostics follows in the telegramXThe requested function is not supported by the slaveMInvalid response from slaveXError in parameter telegramMSlave assigned to another masterTable 2-37Byte 2: Status 26543210XXFixed to 1 for DP operationXWatchdog activatedXFreeze command receivedXSync command received0ReservedMSlave is deactivatedTable 2-4Byte 3: Status 365432100000000XByte: Master address65432100-125 (00hex-7Ehex)Table 2-67ReservedSlave has more diagnostic information than displayed in the telegramTable 2-57Slave must be reparameterizedStatic diagnostics17Station does not existMaster address following parameterization, default address is 255 (FFhex)Byte 5 and 6: ID number65432100-225 (00hex-FFhex)ID number high byte0-225 (00hex-FFhex)ID number low byte7725 en 01PHOENIX CONTACT2-5
IL PB BK DI8 DO4/EF-PACBlock 2: ID-specific diagnosticsThe table shows the faulty local bus devices. For every faulty terminal, a "1" is entered.In the first byte of the block, bits 0 to 5 specify the number of local bus devices and thereforethe length L of the block (8 devices for each byte, maximum). The minimum length of thisblock is 2 bytes (1-byte header 1 byte (8 devices, maximum)), the maximum length is9 bytes (1-byte header 8 bytes (63 devices, maximum)). The size of the ID-specificdiagnostic block depends on the number of configured terminals.Block 3: Status PDU (terminal status)For every local bus device there are 2 bits for status encoding:ST LD x: 00 Terminal data validST LD x: 01 Terminal data invalid due to an errorST LD x: 10 Terminal data invalid due to incorrect terminal being connectedST LD x: 11 Terminal data invalid or no terminal connected(despite configuration)The specifier (SP) equals 1 in the event of a faulty state. The specifier equals 2 if the terminalchanges from a faulty state to an error-free state. If the specifier equals 0, the state has notchanged.SP: 0 No evaluationSP: 1 Error occurs (number 0)SP: 2 Error disappears (number 0)SP: 3 ReservedIn the first byte of the block, bits 0 to 5 specify the number of local bus devices and thereforethe length of the Status-PDU block. The minimum length of this block is 5(4-byte header 1 byte (4 devices, maximum)), the maximum length is 20 (4-byte header 16 bytes (63 devices, maximum)). The size of the status PDU block therefore depends onthe number of configured terminals.2-6PHOENIX CONTACT7725 en 01
DiagnosticsBlock 4: Channel-specific diagnosticsUp to 10 channel errors are indicated here. There are 3 bytes per channel error, this blockcan be a maximum of 30 bytes in size. Each channel error is an individual and independenterror. In order to display the channel errors, the I/O terminal must support PCP (PeripheralsCommunication Protocol) and channel-specific diagnostics must be activated on the buscoupler.IO: 00bin ReservedIO: 01bin InputIO: 10bin OutputIO: 11bin Input and outputChannel: Channel number of the relevant channel (0 to 63)CT: 000bin ReservedCT: 001bin 1 bitsCT: 010bin 2 bitsCT: 011bin 4 bitsCT: 100bin 1 byteCT: 101bin 1 wordCT: 110bin 2 wordsCT: 111bin ReservedET: 0 ReservedET: 1 Short circuitET: 2 UndervoltageET: 3 Surge voltageET: 4 OverloadET: 5 OvertemperatureET: 6 Cable breakET: 7 Upper limit value exceededET: 8 Lower limit value exceededET: 9 General errorBlock 5: Revision diagnosticsIndicates the firmware version, e.g., C3hex Version 37725 en 01PHOENIX CONTACT2-7
IL PB BK DI8 DO4/EF-PACBlock 6: Status PDUThe sixth block is also encoded as a status PDU block, but in manufacturer-specific format.The information stored here does not usually need to be evaluated.Byte 5 indicates the baud rate at which the local bus is operated.Byte 7 and byte 8 indicate the ID and length code of the first faulty terminal. This can be usedas additional information for blocks 2 and 3, if required.The value of byte 11 is 1 if a system limit was violated.Byte 12 indicates the number of available terminals.The bus coupler is always counted as a local bus device (LD). In the event of an error onthe bus coupler, the corresponding bits for local bus device 1 are set in the diagnostics.2.1.2Status PDU diagnostic formatThis diagnostic format consists of the following blocks:1 PROFIBUS standard diagnostics (see also 2.1.1 on page 2-2)2 Status-PDU (manufacturer-specific)Table 2-7Byte XStatus PDU diagnostics incl. error codesBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0Meaning1XXXXXXXXStation status 12XXXXXXXXStation status 23XXXXXXXXStation status 34XXXXXXXXPROFIBUS master address500001011Manufacturer ID high byte (0Bhex)601010000Manufacturer ID low byte (50hex)700001001Status (header) length810100001Status type e.g., A1hex (header)9XXXXXXXXSlot number (header)Block 1Block 22-810000000XXStatus specifier (header)11XXXXXXXXError code, high byte12XXXXXXXXError code, low byte13XXXXXXXXUser ID code,local bus device with error14XXXXXXXXUser length code,local bus device with error15XXXXXXXXFW version (e.g., 33hex)PHOENIX CONTACT7725 en 01
DiagnosticsBlock 2: Status PDUA distinction is made between the following status types (byte 8):A1hexPROFIsafe F-Parameter error (see also Appendix A3)A2hexPROFIsafe iParameter errorA3hexPROFIsafe device error81hexStandard status messageByte 11 and byte 12 provide more detailed information on the standard status message:High byteError typeLow byteError numberFor error descriptions, please refer to Section 2.2, "Representing the error codes",Section A 3, "Error codes for F-Parameters" or the documentation of the individualmodule.2.1.3ID-specific diagnostic formatThis diagnostic format consists of the following blocks:1 PROFIBUS standard diagnostics (see also 2.1.1 on page 2-2)2 ID-specific diagnostics (see also 2.1.1 on page 2-6)Table 2-8Byte XID-specific (terminal) diagnosticsBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0Meaning1XXXXXXXXStation status 12XXXXXXXXStation status 23XXXXXXXXStation status 34XXXXXXXXPROFIBUS master address500001011Manufacturer ID high byte (0Bhex)601010000Manufacturer ID low byte (50hex)701XXXXXXNumber of devices (values 0 to 63)8XXXXXXXXTerminals 1 to 8 (values 0 to 255)Block 1Block 29XXXXXXXXTerminals 9 to 16 (values 0 to 255)10XXXXXXXXTerminals 17 to 24 (values 0 to 255)11XXXXXXXXTerminals 25 to 32 (values 0 to 255)12XXXXXXXXTerminals 33 to 40 (values 0 to 255)13XXXXXXXXTerminals 41 to 48 (values 0 to 255)14XXXXXXXXTerminals 49 to 56 (values 0 to 255)15XXXXXXXXTerminals 57 to 63 (values 0 to 127)7725 en 01PHOENIX CONTACT2-9
IL PB BK DI8 DO4/EF-PAC2.2Representing the error codes2.2.1Local diagnostic indicatorsError type and error no. are indicated by flashing codes of the local diagnostic LEDs (LEDFS and LED FN).PWRBFDIAUL BFUS FSUM FNI2-PAC4/EFDODI8 2BK 9232IL PB-No.: 26erOrdSIBUOFPRPWR0 240 241210 X17725A002Figure 2-22-10PHOENIX CONTACTLocal diagnostic indicators on the bus coupler7725 en 01
Diagnostics2.2.2Error type and error no.In the controller, error type and error no. are available via status-PDU diagnostics.Table 2-9Error type(FS ON,FN flashing)Error type and error no. (also FS/FN flashing codes)Error no.Error cause(FS OFF,FN flashing)17725 en 01Error remedyParameter errors on PROFIBUS1A parameter block is faulty.The number of terminals does not correspond to thenumber of parameter blocks or the header byte of themodule parameter is incorrect or the parameter blockis incomplete.2Too many data blocks for thestation.The number of terminals does not correspond to thenumber of parameter blocks.3The data length of the parameterblock is too short.Check the number of parameters.4The PD PCP module appearsseveral times in the configuration.Check the configuration with regard to the number ofPD PCP modules. There must only be one PD PCPmodule. (Except for PROFIsafe terminals - these havetwo PD PCP modules).5The data block length wasexceeded.Check the number of terminals.6A parameter block is notcomplete.Check the structure of the parameters for theterminals.7The number of parameter blocks Check the configuration.is larger than the maximumnumber of terminals in the station.8F-Parameter error,PROFIsafe-parameter errorActivate Status-PDU diagnostics whenparameterizing the bus coupler in your controller anddetermine the exact error location and error cause.9iParameter error, PROFIsafeparameter errorActivate Status-PDU diagnostics whenparameterizing the bus coupler in your controller anddetermine the exact error location and error cause.PHOENIX CONTACT2-11
IL PB BK DI8 DO4/EF-PACTable 2-9Error type(FS ON,FN flashing)Error type and error no. (also FS/FN flashing codes) (continued)Error no.Error cause(FS OFF,FN flashing)22-12Error remedyConfiguration error on PROFIBUS1Fewer terminals have beenconfigured than are available inthe station.Add these terminals to the configuration.2More terminals have beenconfigured than are available inthe station.Delete the extra terminals from your configuration.3Configuration block is faulty.Determine the exact error location using the terminalspecific diagnostics in your control system.4The ID code in the configurationdoes not correspond to theterminal.Determine the exact error location using the terminalspecific diagnostics in your control system. Check theconfiguration in the hardware configurator.5The length code of the configuredterminal does not correspond tothe length code of the terminal.Determine the exact error location using the terminalspecific diagnostics in your control system. Check theconfiguration in the hardware configurator.6The data length of the parameterblock is faulty.Check the number of parameters. The parameterlength must not be longer than the output data lengthof the relevant terminal.7PROFIBUS address of theIL PB BK DI8 DO4/EF-PAC islarger than 126.Check the PROFIBUS address of theIL PB BK DI8 DO4/EF-PAC. After the address is set,the IL PB BK DI8 DO4/EF-PAC must be restarted.8More than 244 bytes are requiredfor the configuration.Reduce the number of terminals in the station or groupseveral Inline terminals in the configuration, so that theconfiguration data is compressed.PHOENIX CONTACT7725 en 01
DiagnosticsTable 2-9Error type and error no. (also FS/FN flashing codes) (continued)Error type(FS ON,FN flashing)Error no.Error cause(FS OFF,FN flashing)3Configuration and parameter errors on the local bus41General PCP parameterizationfailed.2PCP communication was aborted. Check the PCP PDU size of the PCP devices.3Module error occurred duringinitialization.Try to restart the station.4An error occurred in the I/O circuit(e.g., short circuit or overload atthe actuator).Remove the error from your I/O devices.5Terminal errorActivate channel-specific diagnostics whenparameterizing the bus coupler in your controller anddetermine the exact error location and error cause.6Safety terminal errorActivate Status-PDU diagnostics whenparameterizing the bus coupler in your controller anddetermine the exact error location and error cause.7More than 62 Inline devices areconnected.Re-configure the station structure with regard to themaximum permissible number of Inline devices.8More than 16 PCP devices areconnected.Reduce the number of PCP devices in the station.9The sum of the process data in thelocal bus is greater than 244bytes.Check the amount of process data and reduce thenumber of devices in the station.Check the station configuration and the PCP devices.Local bus error within the station17725 en 01Error remedyLocal bus was stopped.Check the configuration of the station.PHOENIX CONTACT2-13
IL PB BK DI8 DO4/EF-PAC2-14PHOENIX CONTACT7725 en 01
Acyclic communication (DP/V1 and PCP)3Acyclic communication (DP/V1 and PCP)DP/V1DP/V1 extends the cyclic data exchange function according to IEC 61158 to include acyclicservices. This makes it easy to operate even complex terminals.PCPPCP is used in the local bus to exchange data acyclically. This is usually theparameterization data of complex terminals (e.g., IB IL RS 232) or variable length data.DP/V1 is a mechanism which corresponds to PCP at PROFIBUS level. TheIL PB BK DI8 DO4/EF-PAC coupler prepares the data records, which are sent via DP/V1from the Class 1 or Class 2 master, for the PCP mechanism in the local bus. PCP data fromthe local bus is in turn converted into DP/V1 telegrams by the bus coupler.Before programming the application, check whether your control system or configurationtool supports DP/V1. If not, the functions can be used via the cyclic process data channel(DP/V0), see Section 3.5 on page 3-13 and onwards.The different communication types will be described in the following.3.1C1 masterAcyclic communication via the Class 1 master(C1 master)The C1 master carries out parameterization during slave startup and is also the master forcyclic data traffic. It may also be necessary to read a parameter acyclically from the terminalas an option using this C1 master.Corresponding read and write access rights are therefore defined for the C1 master. As italready has a connection to the slave during cyclic data traffic, the C1 master does not haveto establish an explicit connection (using "Initiate"), but can communicate with the slavedirectly via "Read" and "Write".3.2C2 masterAcyclic communication via the Class 2 master(C2 master)For communication in the C2 master, the data fields are identical to those for C1communication, and it is only the SAPs (Service Access Points) which differ. Additionalfields are "Initiate" and "Abort" to establish and release the connection via SAP49 an
IL PB BK DI8 DO4/EF-PAC 2-2 PHOENIX CONTACT 7725_en_01 2.1.1 Diagnostics in the IL PB BK DI8 DO4 format This diagnostic format consists of the following blocks: 1 PROFIBUS standard diagnostics 2 ID-specific diagnostics 3 Status diagnostics (terminal status) 4 Channel-specific diagnostics 5 Revision diagnostics (manufacturer-specific)
Morphy Richards Fastbake Breadmaker 48280 User Manual Honda GCV160 User Manual Canon Powershot A95 User Manual HP Pocket PC IPAQ 3650 User Manual Navman FISH 4200 User Manual - Instruction Guide Jensen VM9021TS Multimedia Receiver User Manual Sanyo SCP-3100 User Manual Honda GC160 User Manual Canon AE-1 Camera User Manual Spektrum DX7 User Manual
Ademco Passpoint Plus User Manual Morphy Richards Fastbake Breadmaker 48280 User Manual Honda GCV160 User Manual Canon Powershot A95 User Manual HP Pocket PC IPAQ 3650 User Manual Navman FISH 4200 User Manual - Instruction Guide Jensen VM9021TS Multimedia Receiver User Manual Sanyo SCP-3100 User Manual Honda GC160 User Manual Canon AE-1 Camera .
E-816 DLL Manual, PZ120E E-621.CR User Manual, PZ160E E-816 LabVIEW Software Manual, PZ121E E-621.SR, .LR User Manual, PZ115E Analog GCS LabVIEW Software Manual, PZ181E E-625.CR User Manual, PZ166E PIMikromove User Manual, SM148E E-625.SR, .LR User Manual, PZ167E E-665 User Manual, PZ127E E-801 User Manual
Nov 11, 2010 · User Story 1 User Story 2 User Story 4 User Story 5 User Story 5 (Cont.) User Story 3 User Story 6 User Story 7 rint 1 User Story 8 2 User Story 1 User Story 2 User Story 4 . Process Template Light on security artifacts/documentati on. OWASP Making SDL-Agile Manageable Toolin
manual, icom 718 user manual, icom 7000 user manual, icom 705 user manual, icom bc-160 user manual, icom ic-41pro user manual Your Icom radio generates RF electromagnetic energy . manual contains important operating instructions for the IC-F14/ . FA-SC56VS: 150–162 MHz. EvaluationIcom IC-R30 Handheld Broadband Receiver, Easy to.
user manual. The user manual will give you the information you need to operate the ap-pliance properly and safely. Carefully read this user manual prior to using the appliance. Keep the user manual AND the installation manual in a safe place. As a user you are only entitled to perform the work described in the user ma-nual.
User property /PROP/USER n User sensor /SENSOR/USER m USER'S SUBROUTINES Read and initialise user data: Define and execute user programs: User window USERWIS.f USERWI.f User material laws 29, 30, 31 shell LECM nn .f SIGEPS nn C.f solid LECM nn .f SIGEPS nn .f User property spring LECG nn .f and RINI nn .f RUSER nn .f
VOS 4.2.1 IP camera integration user manual CCS 4.2.1 user manual or GE-NAV 3.0 user manual . Safety guidelines 4 TruVision NVR 40 User Manual Safety guidelines . If you are using the VisioWave/UltraView CCS or VSC software solution, refer to the appropriate CCS or VSC user manuals. TruVision NVR 40 unit overview TruVision NVR 40 User .
