ProSoft Technology MVI56-PDPS User Manual
Page 50
MVI56-PDPS ♦ ControlLogix Platform
Diagnostics and Troubleshooting
Profibus DP Slave Communication Module
Page 50 of 88
ProSoft Technology, Inc.
April 22, 2008
Diag_Flag
Status diagnostics buffer
Bit 2
0 = The DP master fetches the diagnostics buffer.
1 = The DP master has not yet fetched the diagnostics buffer.
RAM Access Violation
Memory access > 1.5kByte
Bit 3
0 = No address violation
1 = For addresses > 1536 bytes, 1024 is subtracted from the current address, and
there is access to this new address.
DP-State
DP-State Machine state
Bits
4,5
00 = 'Wait_Prm' state
01 = 'Wait_Cfg' state
10 = 'DATA_EX' state
11 = Not possible
WD-State
Watchdog-State-Machine state
Bits
6,7
00 = 'Baud_Search' state
01 = 'Baud_Control' state
10 = 'DP_Control' state
11 = Not possible
Bit 0
Offline/Passive-idle
0 = SPC3 exits offline and goes to passive-idle. The idle timer and Wd timer
go offline.
1= SPC3 exits offline and goes to passive-idle. The idle timer and Wd timer
are started.
Bit 4, 5
10 = Data Exchange State is Normal. The SPC3 has a correct configuration.
Bits 6, 7
Watchdog
Timer
Automatic Baud Rate Identification
The SPC3 is able to identify the baud rate automatically. The "baud search" state
is located after each RESET and also after the watchdog (WD) timer has run out
in the "Baud_Control_state." As a rule, SPC3 begins the search for the set rate
with the highest baud rate. If no SD1 telegram, SD2 telegram, or SD3 telegram
was received completely and without errors during the monitoring time, the
search continues with the next lowest baud rate.