22.07.2013 Views

II - DCE FEL ČVUT v Praze

II - DCE FEL ČVUT v Praze

II - DCE FEL ČVUT v Praze

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Table 4-13 HART group error displays<br />

Bit No. Group error display in Byte 1 Meaning<br />

0 Always 0 Not used<br />

1 Command rejected Used in the following cases:<br />

For a module command which does not exist.<br />

If you try to activate the burst mode when it is already activated.<br />

If you try to deactivate the burst mode when it was activated by<br />

another client.<br />

If you try to change the polling address of the HART field<br />

device.<br />

2 Further status information available. Corresponds to bit 4 in the 2nd HART status byte. You can<br />

obtain further status information with HART command 48.<br />

3 HART device status<br />

––> “Modification of parameters”<br />

entry in diagnostic data, data record 1<br />

I/O Modules with Intrinsically-Safe Signals<br />

C79000-G7076-C152-04<br />

The field device transmits its device state. This information is<br />

found in the 2nd HART status byte which is accepted<br />

unchanged.<br />

4 HART command status The field device transmits displays on the receipt of the<br />

command. Information on this can be found in the 1st HART<br />

status byte.<br />

5 Error during HART communication<br />

––> “HART group error” entry in<br />

diagnostic data, data record 1<br />

6 HART protocol error during<br />

response<br />

––> “HART group error” entry in<br />

diagnostic data, data record 1<br />

7 Wire break<br />

––> Parallel entry “Wire break” in<br />

diagnostic data, data record 1<br />

Table 4-14 HART protocol error during response from field device to module<br />

The field device has detected a communication error while<br />

receiving the command. Information on the error can be found in<br />

the 1st HART status byte which is accepted unchanged.<br />

Error during HART communication between field device and<br />

module, i.e. the response was incorrectly received. Information<br />

on the cause of the error can be found in the next byte.<br />

See Table 4-14.<br />

The connection to the measuring transducer or the signal control<br />

element has been broken.<br />

Bit No. HART protocol error in byte 2 Meaning<br />

0 Bad frame timing Waiting time elapsed without response being received from<br />

field device.<br />

1 Always 0 Not used<br />

SIMATIC S7 HART Analog Modules<br />

2 Bad character transmission timing The pause between two bytes was not observed.<br />

3 Checksum error in response The checksum calculated does not match the checksum<br />

transmitted.<br />

4 Response frame error Error receiving HART signal (in UART)<br />

5 Response overrun error Error receiving HART signal (in UART)<br />

6 Response parity error Error receiving HART signal (in UART)<br />

7 HART access not possible The connection to the field device is constantly busy. This<br />

error is registered if the transmission time exceeds 10<br />

seconds.<br />

4-33

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!