Transcript PROFIBUS Bus Monitor

PROFIBUS Bus
Monitor
 Monitor Features
 Enables to record and to analyze the data communication
on the bus
 Supports transmission rates up to 12 Mbps
 Monitor doesn’t need an own PROFIBUS station address,
because it just listens to the communication
 Provides a wide range of trigger and filter functions
 Data are written to a rolling buffer
 Available as free download from the PIC web page
 Runs on hardware CP 5511 (PCMCIA) and CP 5611 (PCI)
-
“Amprolizer”
Page 1
PROFIBUS Bus
Monitor
 Start monitor
Double click on monitor icon
-
“Amprolizer”
Page 2
PROFIBUS Bus
Monitor
 Select hardware
Select board used to run the monitor (5411
(ISA), 5511 (PCMCIA) or 5611 (PCI))
-
“Amprolizer”
Page 3
PROFIBUS Bus
Monitor
 Overview of PROFIBUS Monitor Features
Selects HEX/DEC Display
Opens Filter Window
Creates Live List
Starts Bus Trace
Deletes All Messages
Closes Data Window
Opens Data Window
Saves File in ASCII (Save As...
Saves to a File (Save As…)
Opens an Existing File
-
“Amprolizer”
Page 4
PROFIBUS Bus
Monitor
 How to create a”Live List”
1
(1)
2
3
1) Click on heart to create “Live List”, (“Online”->”Station
List”as an alternative)
2) Choose transmission rate
3) Click “OK”
-
“Amprolizer”
Page 5
PROFIBUS Bus
Monitor
 Result “Live List”
Active stations (master)are
shown in red, passive stations
(slave) in blue
-
“Amprolizer”
Page 6
PROFIBUS Bus
Monitor
 Start monitoring function - Part I
(1)
1
2
3 (if used)
Click on blue arrow to start monitoring, (“Online”->”Start”as an alternative) and choose stop
condition; if you use a trigger condition to stop monitoring, click on “Trigger” for specification
-
“Amprolizer”
Page 7
PROFIBUS Bus
Monitor
 Define trigger (if used) - Part I
3B) Define address or
data you want to trigger
on:
DA (station address of
receiver)
SA (station address of
sender)
FC (function code, e.g.
high prior response to
data exchange request)
DSAP (service access
point of receiver)
SSAP (service access
point of sender)
DataLen (number of
user data inside a
telegram [bytes])
Data[N] (position of the
byte inside the data
unit)
3B
3A
3A) Define position of the trigger (are you mainly interested in
what happens before, after or before AND after the trigger event
-
“Amprolizer”
Page 8
PROFIBUS Bus
Monitor
 Define trigger (if used) - Part II
3C) Define value to trigger on
3D) Define position inside data unit (only if “Message Frame” = “Data[N]”)
3C
3D
Monitoring stops when
ONE of the defined
trigger conditions is
fulfilled
3E) Perform steps 1-4
again for “Trigger 2” (if
needed)
!!! Values !!!
2 digits mean “HEX”
3 digits mean “DEC”
3E
3F
3F) Click “OK” to confirm your
selection
-
“Amprolizer”
Page 9
PROFIBUS Bus
Monitor
 Start monitoring function - Part II
Select used transmission rate
4
5) Select station filter (if
needed)
6) Decide whether you
want to see just DP
related telegrams
5
6
7
7) Click “OK” to confirm your selection and start monitoring
-
“Amprolizer”
Page 10
PROFIBUS Bus
Monitor
 Result of monitoring function - Part I
Time stamp
for begin of
telegram
Time between last message and this one
Length of user data [byte]
User data
Function
code
Error
messages
Used
Service
Access
Points
Used
PROFIBUS
service (see
next page)
Start
Delimiter of
telegram (see
next page)
Station
address of
sender and
receiver
-
“Amprolizer”
Page 11
PROFIBUS Bus
Monitor
 Services (all services can be performed with low or high priority)
 SDA request (“Send Data w/ Acknowledge”; function is acknowledged by “Short
Acknowledgement” frame)
 SDN request (“Send Data w/ No Acknowledge”; function without remote confirmation)
 SRD request (“Send & Receive Data”)
 OK (“Short Acknowledgement” frame (E5h))
 DL (response to SRD request with low prior data)
 DH (response to SRD request with high prior data; used by DP slaves to indicate
diagnostic information to the master)
 Token (special telegram to pass the bus control between masters)
 FDL_Status (request to check whether new master stations are connected to the bus)
 SD - Start Delimiter





SD1 (=10h) - Telegrams of fixed length without data field
SD2 (=68h) - Telegrams with variable length of data field
SD3 (=A2h) - Telegrams of fixed length with data field (constant length)
SD4 (=DCh) - Token passing
SC (=E5h) - Short Acknowledgement telegram
-
“Amprolizer”
Page 12
PROFIBUS Bus
Monitor
 Result of monitoring function - Part II
Telegram, which
fulfills trigger
condition is colored
-
“Amprolizer”
Page 13