Ppi通讯协议

electrical & safety · industrial connectivty · software & electronics · advanced connectivityWoodheadPpi.DOC 06/05/2004Copyright © 2004 Woodhead Software & Electronics. All rights reserved.Protocol manualSiemens PPIapplicom ® 3.8a product of Woodhead Software & ElectronicsPpi.DOC 06/05/2004 Copyright © 2004 Woodhead Software & Electronics. All rights reserved. applicom®, Direct-Link TM, RJ-Lnxx TM, SST TM are registered trademarks of Woodhead Software & Electronics. Other product names are trademarks of their respective owners.Table of contents1.- Generalities (1)- Generalities (1)2.- SIEMENS PPI Protocol Functionalities for S7 200 Controllers2- Addressing Mode (2)- Addressing Words with an applicom® Interface (3)- Addressing Words with the SW1000SER Solution (4)- Addressing Double or Floating Words with the SW1000SER Solution (5)- Maximum number of variables per frames with the library (6)- Maximum number of variables per frames with PCDDE (6)- Maximum number of variables per frames with OPC server (6)3.- Configuration (7)Master Configuration (7)Device Configuration (9)4.- applicom® functions usable on the master channel (12)- Wait mode (12)- Deferred mode (12)- Cyclic mode (13)5.- Item of image variables (14)- Presentation (14)- Standard descriptor (15)- Siemens S7 PPI descriptor (18)6.- Appendices (24)- List of Additional Files for PPI (24)- Upgrades / Compatibility (24)7.- Return status of applicom® functions (25)- Introduction (25)- applicom® general statuses (26)- Statuses according to the protocol (27)8.- Glossary of terms (28)9.- Index (29)1. - Generalities - GeneralitiesThe PPI physical interface is identical to the PROFIBUS interface (RS485, pinout complies with standard EN 50170). The transmission speed can be set at 9 600 or 19 200 bauds. For exchanges, the applicom® product and the Siemens S7 PPI solution on SW1000SER are always masters, and the controllers are always slaves.The applicom® interface solution supports PPI+ (the applicom station is active, it manages thetoken and multi-master mode is possible); the device number used corresponds to the controller's network address.The SW1000SER solution supports PPI only (the station is passive, and only master/slave mode is possible), and it permits the device number to be dissociated from the controller's network address.The controller's network address is defined by means of SIEMENS STEP7-micro software.2. - SIEMENS PPI Protocol Functionalities for S7200 Controllers - Addressing ModeVariable S7 200 Addressingapplicom®(adr)Exchange Type(cyclic mode)Correspondingapplicom®Function(Library/DLL access) M v.wSM v.wVB v.wv*8+w10000+v*8+w524288+v*8+wRead bitsWrite bitsREADPACKBIT, READDIFBITWRITEPACKBIT,WRITEDIFPACKBITI v,w v*8+w Read input bits READPACKIBIT, READDIFIBITQ v.w v*8+w Read output bitsWrite output bitsREADPACKQBIT, READDIFQBITWRITEPACKQBIT,WRITEDIFPACKQBIT MV vSM vVB vv10000+v65536+vRead packed bytesWrite packed bytesREADPACKBYTE, READDIFBYTEWRITEPACKBYTE,WRITEDIFPACKBYTE IB v v Read packed inputbytesREADPACKIBYTE, READDIFIBYTEQB v v Read packed outputbytesWrite packed outputbytesREADPACKQBYTE,READDIFQBYTE ,WRITEPACKQBYTE,WRITEDIFPACKQBYTE MW vSMW vVW vv10000+v65536+vRead wordsWrite wordsREADWORD, READDIFWORDWRITEWORD, WRITEDIFWORDIW v v Read input words READIWORD, READDIFIWORDQW v v Read output wordsWrite output wordsREADQWORD, READDIFQWORDWRITEQWORD, WRITEDIFQWORD MD vVD vv65536+vRead double wordsWrite double wordsREADDWORD, READDIFDWORDWRITEDWORD, WRITEDIFDWORD v: Bytenumber.w: Bit number in the byte (0 to 7).Caution: The PPI protocol functions on the serial ports of all applicom® boards (PC1000, PC4000, etc.) that are equipped with a 5PFB485 or 6PFB485 module (module with galvanic isolation). However,only PC1500PFB and PC1500S7 boards have a SUB D9-pin female connector. For other boards, a male-female adapter is provided.Access to the applicom.dll library functions is not supported by the SW1000SER solution.- Addressing Words with an applicom® InterfaceVariables for SIEMENS S7 controllers are numbered by bytes and not by 16-bit words, as S5-range DB variables are. As a result, it may be necessary to access words or double words whose addresses are aligned with even or odd addresses. A read request for several words must enable the user to access a word table regardless of their physical addresses. To resolve this problem, the PPI protocol task returns as many variables as physical addresses.Example: An application wants to read word MW11 and word MW14 in one request. It therefore uses a 4-word read request beginning with address 11. The reply contents are in the following form: User Table Offset S7 Mnemonic Controller's Physical Address0 MW11 11 and 121 MW12 12 and 132 MW13 13 and 143 MW14 14 and 15Of course, this addressing principle does not apply to writing several variables in one request.Example: Writing two words beginning from address 11.User Table Offset S7 Mnemonic Controller's Physical Address0 MW11 11 and 121 MW13 13 and 14- Addressing Words with the SW1000SER SolutionThe input and output words are on byte addresses (see table below).The SW1000SER solution offers two alignment types for each configuration:• Word alignment:When reading several words, this mode returns words that are contiguous and with even orodd addresses.Example:A 3-word read beginning with address 0 will return words 0, 2 and 4.A 3-word read beginning with address 1 will return words 1, 3 and 5.During a write, the same addressing mode is applied.Example:A 3-word write beginning with address 0 will assign words 0, 2 and 4.A 3-word write beginning with address 1 will assign words 1, 3 and 5.• Byte alignment:When reading several words, this mode offers the advantage of returning words with evenand odd addresses.Example:A 4-word read beginning with address 1 will return words 1, 2, 3 and 4.When writing several words, the "word address alignment" is applied.- Addressing Double or Floating Words with the SW1000SER Solution The double or floating input and output words are on byte addresses (see table below).applicom® offers two alignment types for each configuration:• Double word alignment:When reading several double words, this mode returns double words that are contiguouswith a 4-step address.Example:A 3-word read beginning with address 0 will return words 0, 4 and 8.A 3-word read beginning with address 1 will return words 1, 5 and 9.A 3-word read beginning with address 2 will return words 2, 6 and 10.When writing several double words, the "double word address alignment" is applied.• Word alignment:When reading several double words, this mode returns double words that are contiguouswith the even or odd address.Example:A 3-double-word read beginning with address 0 will return words 0, 2 and 4.A 3-double-word read beginning with address 1 will return words 1, 3 and 5.When writing several double words, the "double word address alignment" is applied.• Byte alignment:When reading several double words, this mode offers the advantage of returning doublewords with an even and odd address.Example:A 4-word read beginning with address 1 will return double words 1, 2, 3 and 4.When writing several double words, the "double word address alignment" is applied.- Maximum number of variables per frames with the libraryObject Max. quantity in read Max. quantity in write1 Bit 1600200 Byte 200Word 128100 Double word 64 50- Maximum number of variables per frames with PCDDEObject Max. quantity in read Max. quantity in write1 Bit 16001 Byte 2001 Word 128Double word 64 1The number given for read frames corresponds to the maximum number of points (as imposed bythe server and/or the protocol) which can be grouped together during dynamic optimization of the framescarried out by the server. However, this number can be reduced to suit a specific item of equipment byconfiguring the length of frames in the topic(see chapter "Implementation/Topics configuration/Advancedoptions").Where write operations are concerned, a variable automatically entails the formation of a frame.- Maximum number of variables per frames with OPC serverObject Max. Quantity in read Max. Quantity in write1 Bit 1600200 Byte 200100 Word 128Double word 64 50The number given for read frames corresponds to the maximum number of points (as imposed bythe server and/or the protocol) which can be grouped together during dynamic optimization of the framescarried out by the server. However, this number can be reduced to suit a specific item of equipment byconfiguring the length of frames in the topic(see chapter "Implementation/Topics configuration/Advancedoptions").For the write frames, see chapter "OPC Server/Optimization of synchronous and asynchronousrequests".3. - Configuration Master ConfigurationSince the parameters associated with this protocol are pre-defined, only the speed needs to be selected.PPI Master Properties with the applicom® interface:PPI Master Properties with SW1000SER:Baud rate :You must select a transmission speed (9600 or 19200 bauds), independently on each channel. This speed must be consistent with that of the equipments connected on the channel.Serial port number:Only supported with the SW1000SER solution.The serial port number corresponds to the COM port that will be used on the machine by theSW1000SER interface for the selected protocol.The list includes the COM ports defined in the system.Flow control:Only supported with the SW1000SER solution.Flow control defines the communication signals used by the device or by a current loop converter (BC20mA), RS485, RS422.NoneNo flow control.DTR OnThe DTR signal is raised during serial port opening and remains constantly raised.RTSThe RTS signal is raised if there are bytes to transmit. It is dropped when all the emission buffer bytes have been emitted.RTS, DTR OnCombination of the DTR and RTS modes described above.RTS OnThe RTS signal is raised during serial port opening and remains constantly raised.For more details about using a converter, see chapter Use of RS232/RS485, RS422 and Current Loop Converters in the Software Solution Functions manual.Physical address of this station (0-126)The physical address of the PPI master is between 0 and 126.Device ConfigurationOnly supported with the SW1000SER solution.General PropertiesDevice numberapplicom® device number to be selected from the list of unconfigured devices.Value: from 000 to 127 for server equipment.LinkLinks the applicom® device number with the PPI physical address.Active configurationTick this box to activate the device configuration in the SW1000SER interface: deletes a device from the SW1000SER interface while retaining its configuration.NameTOPIC name for use in OPC and PCDDE (the TOPIC is used to link the device in the OPC and PCDDE servers).CommentsFree text associated with a device. The total number of characters must not exceed 80.Remote station physical address (0-126)The physical address of the remote station is a number from 0 to 126.Time-out (0-500 ms)Wait time between the question and the response: between 0 and 500.Protocol PropertiesThis page is accessible only in expert mode.ÖData alignment on reading 16-bit wordsThis parameter is used to align 16-bit data with byte addresses (value=1) or with word addresses (value=2) during word table reads. The default value for this parameter is 1.Ö Data alignment on reading 32-bit wordsThis parameter is used to align 32-bit data with byte addresses (value=1), word addresses (value=2) or double word addresses (value = 4) during double word table reads. The default value for this parameter is 1.4. - applicom® functions usable on the masterchannel -Wait modeOnly supported with an applicom® interface.readpackbit writepackbitreadpackibitreadpackqbit writepackqbitreadpackbyte writepackbytereadpackibytereadpackqbyte writepackqbytereadword writewordreadiwordreadqword writeqwordreaddword writedwordreadident-Deferred modeOnly supported with an applicom® interface.readdifbit writedifpackbitreaddifibitreaddifqbit writedifpackqbitreaddifbyte writedifpackbytereaddifibytereaddifqbyte writedifpackqbytereaddifword writedifwordreaddifiwordreaddifqword writedifqwordreaddifdword writedifdwordtesttransdif transdif transdifpack- Cyclic modeOnly supported with an applicom® interface.createcycstartcyc stopcyc actcyctranscyc transcycpackCyclic function Type:TYPE OF VARIABLE Function typeIN EQUIPMENT Reading Writing Packed bits X XInput packed bits XOutput packed bits X XPacked bytes X XBytesInput packed bytes XInput bytesOutput packed bytes X XOutput bytes X XWords X XInput words XOutput words X X32 bit double words X X5. - Item of image variables - PresentationImage variable items are the set of syntaxes that can be used to access variables through the "pcdde" DDE server or the OPC server.Report you to sections "DDE server/Principles regarding access to Data" or "OPC server/Data Access PrincipleDepending on the configuration of each device, the most suitable descriptor is by default automatically determined by the server. With the PPI protocol, the default descriptor is the SiemensSeries 7 descriptor (PPI, MPI).Caution: if you modify the default descriptor, some device access optimizations will be disabled,and performance may be negatively affected.However, you may be able to force the use of another descriptor (particularly the standard applicom® descriptor) by means of the advanced options.- Standard descriptorThe standard descriptor can be used for access to the equipments which have not specificdescriptors. The address field of the item name may be 10 digits long. It allows to compose a linearaddress from 0 to 4 giga.Single Mode Table Mode, Matrix Mode Internal bits Bx Bx_n, Bx_n_lInput bits BIx BIx_n, BIx_n_lBO_n_l Output bits BOx BOx_n,Internal bytes Ox Ox_n, Ox_n_lInput bytes OIx OIx_n, OIx_n_lOutput bytes OOx OOx_n, OOx_n_lASCII string in internal bytes M_Ox_nInternal words WxInput words WIxOutput words WOxInternal double words DxCaution: the addressing mode of the protocol task forbid to use the string and matrice modein the variables of word, double word and floating word type.Note : Limit values for n and l parameters are depending on the protocol. However, in case ofPCDDE, limits cannot never be superior than 128 for bits and bytes, 64 for words, 32 for double wordsand floating words.For more information on the limits in read and write, see :- Maximum number of variables per frames with PCDDE on page 6- Maximum number of variables per frames with OPC server on page 6For the variable addressing, refer to the chapter "- Addressing Mode" à la page 2.- Internal bits => Bx (BIT type)x : First bit number.Example : B4- Internal bits => Bx_n, Bx_n_ln : Number of bits.l : Number of bits per line (Matrix mode only).Examples : B4_10, B4_10_5- Input bits => BIx (BIT type)x : First bit number.Example : BI4- Input bits => BIx_n, BIx_n_ln : Number of bits.l : Number of bits per line (Matrix mode only). Examples : BI4_10, BI4_10_5- Output bits => BOx (BIT type)x : Number of bits.Example : BO4- Output bits => BOx_n, BOx_n_l n : Number of bits.l : Number of bits per line (Matrix mode only). Examples : BO4_10, BO4_10_5- Internal bytes => Ox (BYTE type) x : First byte number.Example : O4- Internal bytes => Ox_n, Ox_n_l n : Number of bytes.l : Number of bytes per line (Matrix mode only). Examples : O4_10, O4_10_5- Input bytes => OIx (BYTE type) x : First byte number.Example : OI4- Input bytes => OIx_n, OIx_n_ln : Number of bytes.l : Number of bytes per line (Matrix mode only). Examples : OI4_10, OI4_10_5- Output bytes => OOx (BYTE type)x : First byte number.Example : OO4- Output bytes => OOx_n, OOx_n_ln : Number of bytes.l : Number of bytes per line (Matrix mode only).Examples : OO4_10, OO4_10_5- ASCII string in internal bytes => M_Ox_n (BYTE type)For more information on the use of the ASCII string, you can consult the chapter "Use of message mode".x : Number of first byte which contains the string.n : Potential number of bytes which can contain the ASCII string (1 to 131).Example : M_O100_30In the example, the byte array from O100 to O129 can contain the string.- Internal words => Wx (16 bit WORD type)x : First word number.Example : W4- Input words => WIx (16 bit WORD type)x : First word number.Example : WI4- Output words => WOx (16 bit WORD type)x : First word number.Example : WO4- Internal double words => Dx (32 bit WORD type)x : First double word number.Example : D4- Siemens S7 PPI descriptorThis descriptor is usable for access to the Siemens S7 200 PLCs.This descriptor is the default descriptor determined by the OPC and DDE server.Single Mode Table Mode, Matrix Mode M bits Mx.y Mx.y_n, Mx.y_n_lSM bits SMx.y SMx.y_n, SMx.y_n_lVB bits VBx.y VBx.y_n, VBx.y_n_lInput bits Ix.y Ix.y_n, Ix.y_n_lOutput bits Qx.y Qx.y_n, Qx.y_n_lMV bytes MVx MVx_n, MVx_n_lSM bytes SMx SMx_n, SMx_n_lVB bytes VBx VBx_n, VBx_n_lInput bytes IBx IBx_n, IBx_n_lOutput bytes QBx QBx_n, QBx_n_lASCII string in MV bytes M_MVx_nASCII string in SM bytes M_SMx_nASCII string in VB bytes M_VBx_nMW words MWxSMW words SMWxVW words VWxInput words IWxOutput words QWxMD double words MDxDouble words VDxCaution: The protocol task addressing mode prohibits the use of array and string mode in word-, double word- and floating word-type variables with an applicom® interface.Note : Limit values for n and l parameters are depending on the protocol. However, in case of PCDDE, limits cannot never be superior than 128 for bits and bytes, 64 for words, 32 for double words and floating words.For more information on the limits in read and write, see :- Maximum number of variables per frames with PCDDE on page 6- Maximum number of variables per frames with OPC server on page 6For the variable addressing, refer to the chapter "- Addressing Mode" à la page 2.- M bits => Mx.y (BIT type)x : First byte number.y : Bit range in the byte (0 to 7).Example : M94.7- M bits => Mx.y_n, Mx.y_n_ln : Number of bits.l : Number of bits per line (Matrix mode only). Examples : M94.7_24, M94.7_24_8- SM bits => SMx.y (BIT type)x : First byte number.y : Bit range in the byte (0 to 7).Example : SM94.7- SM bits => SMx.y_n, SMx.y_n_l n : Number of bits.l : Number of bits per line (Matrix mode only). Examples : SM94.7_24, SM94.7_24_8- VB bits => VBx.y (BIT type)x : First byte number.y : Bit range in the byte (0 to 7).Example : VB94.7- VB bits => VBx.y_n, VBx.y_n_l n : Number of bits.l : Number of bits per line (Matrix mode only). Examples : VB94.7_24, VB94.7_24_8- Input bits => Ix.y (BIT type)x : First input byte number.y : Bit range in the input byte (0 to 7). Example : I94.7- Input bits => Ix.y_n, Ix.y_n_ln : Number of bits.l : Number of bits per line (Matrix mode only). Examples : I94.7_24, I94.7_24_8- Output bits => Qx.y (BIT type)x : First output byte number.y : Bit range in the output byte (0 to 7). Example : Q94.7- Output bits => Qx.y_n, Qx.y_n_l n : Number of bits.l : Number of bits per line (Matrix mode only). Examples : Q94.7_24, Q94.7_24_8- MV bytes => MVx (BYTE type)x : First byte number.Example : MV4- MV bytes => MVx_n, MVx_n_ln : Number of bytes.l : Number of bytes per line (Matrix mode only). Examples : MV4_10, MV4_10_5- SM bytes => SMx (BYTE type)x : First byte number.Example : SM4- Octets SM => SMx_n, SMx_n_l n : Number of bytes.l : Number of bytes per line (Matrix mode only). Examples : SM4_10, SM4_10_5- VB bytes => VBx (BYTE type)x : First VB number.Example : VB4- VB bytes => VBx_n, VBx_n_ln : Number of bytes.l : Number of bytes per line (Matrix mode only).Examples : VB4_10, VB4_10_5- Input bytes => IBx (BYTE type)x : First input byte number.Example : IB4- Input bytes => IBx_n, IBx_n_ln : Number of bytes.l : Number of bytes per line (Matrix mode only).Examples : IB4_10, IB4_10_5- Output bytes => QBx (BYTE type)x : First output byte number.Example : QB4- Output bytes => QBx_n, QBx_n_ln : Number of bytes.l : Number of bytes per line (Matrix mode only).Examples : QB4_10, QB4_10_5- ASCII string in MV bytes => M_MVx_n (BYTE type)x : Number of first byte which contains the string.n : Potential number of bytes which can contain the ASCII string (1 to 131).Example : M_MV100_10In the example, the byte array from MV100 to MV109 can contain the string.Note :For more information on the use of the ASCII string, you can consult the chapter "Use of message mode".- ASCII string in SM bytes => M_SMx_n (BYTE type)x : Number of first byte which contains the string.n : Potential number of bytes which can contain the ASCII string (1 to 131).Example : M_SM100_10In the example, the byte array from SM100 to SM109 can contain the string.Note :For more information on the use of the ASCII string, you can consult the chapter "Use of message mode".- ASCII string in VB bytes => M_VBx_n (BYTE type)x : Number of first byte which contains the string.n : Potential number of bytes which can contain the ASCII string (1 to 131).Example : M_VB100_10In the example, the byte array from VB100 to VB109 can contain the string.Note :For more information on the use of the ASCII string, you can consult the chapter "Use of message mode".- MW words => MWx (16 bit WORD type)x : First word number.Example : MW4- SMW words => SMWx (16 bit WORD type)x : First word number.Example : SMW4- VW words => VWx (16 bit WORD type)x : First word number.Example : VW4- Input words => IWx (16 bit WORD type)x : First word number.Example : IW4- Output words => QWx (16 bit WORD type)x : First word number.Example : QW4- MD double words => MDx (32 bit WORD type) x : First double word number.Example : MD4- Double words => VDx (32 bit WORD type)x : First double word number.Example : VD46. - Appendices - List of Additional Files for PPIWith an applicom® interface:taskMASTPPI. MasterNETPPI. PPI channel management taskWith the SW1000SER interface:taskCLIPFB.DLL MasterNETPFB.DLL. PPI channel management task- Upgrades / CompatibilityThe protocol requires EPROMs of version 3.2 or higher.7. - Return status of applicom® functions - IntroductionThe various applicom® functions return a status word that:- Guarantees the request quality.- Can be used to diagnose the cause of a failure.The meaning of the status word value is detailed in the following tables. In addition to the general meaning, "Further information" allows you to direct your diagnosis according to the protocol used.- applicom® general statuses-6 The TRANSCYC (or TRANSCYCPACK) function is used with a cyclic function number that is no longer activated.-5 The user program tries to perform a TRANSDIF (or TRANSDIFPACK) deferred transfer although the deferred request in progress is not completed.-1 TRANSDIF (or TRANSDIFPACK) deferred transfer request related to a write that took place correctly.0 No anomaly detected. The function took place correctly.function.1 UnknownThe requested function is not supported.address.2 IncorrectThe address of the variable you are soliciting is incorrect.data.3 IncorrectFurther details :Function: BINBCD, BCDBIN.- At least one of the accessed values is not in BCD format (0 ≤ value ≤ 9999).4 Irretrievable data.32 Bad parameter passed into the function.Incorrect number of variables.35 Data not available in cyclic read.Attempt to transfer data with TRANSCYC (or TRANSCYCPACK) before it has been read in the equipment. 40 Deferred read or write attempt when the deferred request register is full.Another task must free the resources by making an exitbus41 Deferred read or write attempt when the deferred request register is fullPerform deferred request transfers with TRANSDIF (or TRANSDIFPACK) in order to release the register (64positions).42 Deferred request transfer attempt with TRANSDIF (or TRANSDIFPACK) when the latter is empty (no deferredrequests in progress).45 Non-resident communication software.Initialize the applicom® interface before using it by typing command applicom (or PCINIT under Windows ).46 Board number not configured, or Master/client applicom® function aiming at a channel configured asslave/server, or vice versa.47 No applicom® interface.51 Driver system problem.59 Protection key missing on the applicom®interface..Using applicom® function without INITBUS function.66 Insufficient applicom® interface memory.97 Only supported with the SW1000SER solution.Access to the applicom.dll library denied.128 Only supported with the SW1000SER solution.Cannot open the serial port (port already opened by another application, etc.).255 Used by the « PCDDE » MS-Windows server. Initial value of « STATUS_READ » and « STATUS_WRITE ».This value indicates that no transaction has been made between « PCDDE » and applicom® interface.Comments :Negative status are information codes.- Statuses according to the protocol0 No anomaly detected. The function took place correctly.function.1 UnknownThe requested function is not supported.address.2 IncorrectThe address of the variable you are soliciting is incorrect.- Returned by the destination coupler equipment. Undeclared DB.data.3 IncorrectFurther details :- Inconsistent frame content.-data.4 IrretrievableFurther details :- Non-existent peripheral (for example: input or output card not present in the PLC).10 Layer 2 negative acknowledgment from the equipment (NACK).- UE (U ser E rror), Error in remote equipment.11 Layer 2 negative acknowledgment from the equipment (NACK).- RR (R emote R esource), Not enough resources in remote equipment.12 Layer 2 negative acknowledgment from the equipment (NACK).- RS (R emote S ervice), The layer 2 service used is not authorized on the SAP or the SAP is not activated.13 Layer 2 negative acknowledgment from the equipment (NACK).- RDL (R esponse FDL/FMA1/2 D ata L ow), Not enough resources in remote equipment to reply in low priority.14 Layer 2 negative acknowledgment from the equipment (NACK).- RDH (R esponse FDL/FMA1/2 D ata H igh), Not enough resources in remote equipment to reply inhigh priority.15 - LS (L ocal S ervice), local SAP not activated.16 - NO (N ot O K), Significance dependent on layer 2 service.32 Bad parameter passed into the function.Incorrect number of variables.33 Response time fault (Time-Out).- The remote equipment is not in the logic ring.34 Parity fault in reception or of control word (CRC16, BCC).configured.not36 EquipmentDefine the equipment configuration with the console and start again the applicom®product48 Only supported with an applicom® interface.The RS232 channel of the applicom® interface configured in "6 signals" cannot emit, since itwaited for the CTS signal from the modem for more than 3 seconds during an emission.。