Error Codes RK512

4

16#04

RK512ERR_P3964ERR_ZVZ

The character delay time was exceeded. ZVZ = 220 ms. The character delay time is the maximum time interval between the transmission of two succeeding characters.

5

16#05

RK512ERR_P3964ERR_QVZ

The acknowledgement delay time was exceeded. The other device sent an acknowledgement character (DLE = 10H) twice as the telegram was being handled. QVZ = 2 sec. The first acknowledgement is expected at the start of the transfer. The output ErrorState is "Wait_DLE_TXstart" in case of an error. 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

16#06

RK512ERR_P3964ERR_WVZ

The repeat delay time was exceeded. WVZ = 4 sec. In the event of an error a telegram is repeated. If the telegram is not repeated by the other device, the 3964R function block reports this error.

7

16#07

RK512ERR_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

16#09

RK512ERR_P3964ERR_COMERRTX

Interface error when transmitting

10

16#0A

RK512ERR_P3964ERR_COMERRRX

Interface error when receiving

11

16#0B

RK512ERR_P3964ERR_NOTXDATA

Parameterization error. The number of bytes that are to be sent, TxCount, is zero.

120

16#78

RK512ERR_P3964ERR_NAK

A telegram was refused by the other device with a negative acknowledgement (NAK). The error may occur in the following transmission states (ErrorState):Wait_DLE_TXstart: The local PLC initiates 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.

12

16#0C

RK512ERR_INVALIDDATATYPE

Invalid data type A telegram with unsupported data type ID was received. Only data blocks with the identifier 'D' can be handled.

16

16#10

RK512ERR_ERRORPROTOCOLHEADER

Wrong protocol header The header of a data telegram does not match the RK512 specification

20

16#14

RK512ERR_DBNOTAVAILIBLE

Data block not available. A data block that is not available has been transmitted or requested. Data blocks that are accessed by the partner device must first be registered for this purpose with the DBconfig method.

22

16#16

RK512ERR_INVALIDCOMMAND

Invalid command A telegram with invalid command ID (SEND / FETCH) was received.

52

16#34

RK512ERR_INVALIDSIZE

Either the DbSize or the NrOfBytes parameter is invalid, or a data telegram that is too long has been received.

53

16#35

RK512ERR_INVALIDDBADR

Invalid data block address The data block address DbAdr is invalid.

54

16#36

RK512ERR_SYNCERROR

Synchronization error A can occur if both communication partners start to transmit at the same time.

257

16#101

RK512ERR_TIMEOUT

Timeout at RK512 telegram level An expected response telegram was not received within the waiting time TREA.

258

16#102

RK512ERR_ERRORREMOTEREATEL

Error in the response telegram The response telegram from the communication partner contains an error message. The error number can be read from the additional error information in AUX.

259

16#103

RK512ERR_INVALIDSIZEREMOTEREATEL

The communication partner's reaction telegram has an incorrect length

260

16#104

RK512ERR_TIMEOUTREAPEATSENDFETCH

Timeout during sending A Send or Fetch telegram could not be sent, despite several attempts

261

16#105

RK512ERR_3964ERROR

Error on the 3964R protocol level. Predictable errors on this level are not reported as a general RK512ERR_3964ERROR error, but with a detailed error number.

262

16#106

RK512ERR_3964NOTBUSYNOTREADY

The transmission of a telegram has been halted without having been successfully completed.