Profinet module: Difference between revisions

no edit summary
No edit summary
No edit summary
 
Line 81: Line 81:
The communications relations tab is the second tab on the "Statistics for PROFINET device" page. This tab shows all communication relations for a specific device. All communication relations, where the device took part either as a sender or receiver, are listed here. This page consists of five (5) sub-pages or tabs, which we will go over in detail below.
The communications relations tab is the second tab on the "Statistics for PROFINET device" page. This tab shows all communication relations for a specific device. All communication relations, where the device took part either as a sender or receiver, are listed here. This page consists of five (5) sub-pages or tabs, which we will go over in detail below.


==== Profinet Real-Time (PN-RT) ====
==== PROFINET Real-Time (PN-RT) ====
This tab (1<sup>st</sup> tab) lists all cyclic RT frames and groups them by frame ID. Also, both a column and graph depict all errors extracted from the data and transfer status of each frame. Based on the cycle counter, frame loss, repeated frames and wrong frame sequence are indicated. You can sort all data and statistics displayed in the columns, for instance to quickly find the communication relation generating the most errors or most traffic.
This tab (1<sup>st</sup> tab) lists all PROFINET Cyclic RT frames and groups them by frame ID. Also, both a column and graph depict all errors extracted from the data and transfer status of each frame. Based on the cycle counter, frame loss, repeated frames and wrong frame sequence are indicated. You can sort all data and statistics displayed in the columns, for instance to quickly find the communication relation generating the highest jitter, most errors or most traffic.
 
For PROFINET Cyclic frames, a jitter calculation is performed. The calculation is based on the increment of the cycle counter of two subsequent frames and the timestamps of these two frames as seen by the Allegro Network Multimeter. An error field shows the number of all responses with an error status, the number of not answered requests and the number of responses without a request.
 




Line 125: Line 128:
==== Profinet over UDP ====
==== Profinet over UDP ====
This tab (5<sup>th</sup> tab) lists all PROFINET Acyclic CM (Context Manager) frames that where sent over UDP from or to this device. The protocol is used during startup for the creation of application and communication relations, and allows for acyclic write and read requests between two PROFINET devices.
This tab (5<sup>th</sup> tab) lists all PROFINET Acyclic CM (Context Manager) frames that where sent over UDP from or to this device. The protocol is used during startup for the creation of application and communication relations, and allows for acyclic write and read requests between two PROFINET devices.
For PROFINET Acyclic requests in the scope of CM (Context Manager), Response Time Analysis between a request and a response is depicted as seen by the Allegro Network Multimeter.
You can sort all data and statistics displayed in the columns, for instance to quickly find the communication relation generating the highest response times, most errors or most traffic.




Line 130: Line 138:




'''Jitter'''


For cyclic frames a jitter calculation is performed. The calculation is based on the increment of the cycle counter of two subsequent frames and the timestamps of both two frames as seen by the Multimeter.  
The search bar allows to enter MAC, IP or vendor name to easily filter and depict only the elements matching your search criteria. Also complex filter expressions may be used in the search bar. Such complex filter is initiated by starting a search string with an open parenthesis '''('''. See [[Live filtering of tables]] for a detailed description about how to use this feature.
An error field shows the number of all responses with an error status, the number of not answered requests and the number of responses without a request.


Whenever graphs depict spikes in frame count that you want to investigate further...simply selecting a spike in the graph with the mouse (click 'n drag) makes the Allegro UI zoom into that specific time frame. This not only helps narrow down the timeframe to troubleshoot, it also results in the most optimized pre-filtered pcap files with PROFINET for the conversation, if those are needed. 


'''Response times'''
The download buttons on the far right, provides you with such a pre-filtered pcap. It will only contain the conversation from that specific IP/MAC during the selected time interval. Both forward capturing in real-time as well as retroactive packet extraction from an active ring buffer are possible.
 
For acyclic requests in the scope of CM (Context Manager) times are measured between a request and a response (as seen by the Multimeter).
325

edits