P3964R error codes

No	Error constant	Description
4	P3964ERR_ZVZ	The character delay time was exceeded. CDT = 220 ms. The character delay time is the maximum time interval between the transmission of two succeeding characters.
5	P3964ERR_QVZ	The acknowledgement delay time was exceeded. The other end sent an acknowledgement character (DLE = 10H) twice as the telegram was being handled. ADT = 2 s.The first acknowledgement was expected at the start of the transmission. The output ErrorState when an error initially occurs is "Wait_DLE_TXstart". The cause might lie with a faulty physical connection or an incorrect interface parameter.The second acknowledgement is expected after the user data has been transmitted. If an error occurs, the ErrorState is "Wait_DLE_TXend". In this case the cause might, for instance, be data loss, data corruption or data bytes of a data word that have become swapped (see the SwapWords input).
6	P3964ERR_WVZ	The repeat delay time was exceeded. RDT = 4 s. A telegram is repeated if an error occurs. If the telegram is not repeated by the other device, the 3964R function block reports this error.
7	P3964ERR_WRONGBCC	Checksum error during data reception. Each telegram is provided with a checksum. When the data is received, the calculated checksum is compared with the checksum that has been received.
9	P3964ERR_COMERRTX	Interface error when transmitting
10	P3964ERR_COMERRRX	Interface error when receiving
11	P3964ERR_NOTXDATA	Parameterisation error. The number of bytes that are to be sent, TxCount, is zero.
20	P3964ERR_NAK	A telegram was refused by the other device with a negative acknowledgement (NAK). This error can occur in the following transmission states (ErrorState), amongst others:Wait_DLE_TXstart: The local PLC begins a telegram with a start character. The other device refuses the telegram with NAK.Wait_DLE_TXend: The other device refuses the telegram with NAK after the user data has been transmitted. In this case the cause can, for example, be a checksum error at the other device.