Table of Contents
Advertisement
•
Describes type of protocol:
•
"M-TCP" Modbus in TCP;
•
"M-RTU" Modbus in RTU;
and additional information:
•
For TCP IP address;
•
For RTU type of serial, COM used, baudrate, parity;
•
node/line: identifies line and node.
•
device name: device name (as inserted in HW
configurator). Information is shown in tabular form. Click
the ICT button to access ICT diagnostics
Note on ID and node/line
Each device is inserted on a communication line and each
line has an identification number within such line. Obviously,
devices positioned on different lines can have the same node
numbers. To positively identify each device (including by
PLC), the ID lets you point uniquely at each slave as it was
configured by GF_Net (manually or automatically).
A line is defined as a communication channel shared by
multiple devices. For Modbus RTU, each port (COM) is a
line. For Modbus TCP, each IP address is a line.
If there are errors on multiple devices and these are
positioned on the same line, the errors may be caused by the
line status (for example, detached cable).
Move to the list with the cursor keys and press "enter" to
scroll the list with the "up" and "down" keys.
Press "enter" again to select an item on the list, or press
"esc" to return to navigation on the page.
You can scroll the list by using the touch screen and then
select an item on the list with a double click.
Selecting an item on the list lets you go to diagnostics for the
requested device.
The panel's top section shows the same information as on
the list:
•
Type
Type of communication.
•
Descr
Description.
•
Node
Modbus node.
•
Id
Unique identifier.
•
Device name.
•
Two status LEDs:
•
Act
status of last communication made
•
Sts
presence of at least one communication
error
•
The center zone is divided into two parts.
The top section is for the device being analyzed,
while the bottom zone is for the line on which the
device is positioned.
80949_MAN_eView BOX_05-2019_ENG
Device section
The section is divided into two lines:
•
successful communications (OK).
•
failed communications (Fail)
Each line shows 3 values
•
cnt
Counter showing number of
communications made.
•
time
tenths of a second since last
communication.
•
buff
number of buffer of last communication.
In case of unbroken communications, the count increases
and the time stays low. In case of stopped communication,
the counter stops and the time increases.
In case of communication error, the sts LED goes from green
to yellow and stays yellow until the user resets the error with
the Reset button. The act LED shows the status of the last
communication made.
The number under the reset button shows the error code of
the last failed communication..
Sezione linea
The line section is divided the same way as the device line,
but its counters count all of the communications of all the
devices on the same line (shown next to the word Line).
There is also an additional field:
dev
Unique identifier of the device (on the line) to which
the count refers (OK and/or Fail).
Here too there is a Reset button to reset the error latch on
the line.
Buffer section
The bottom zone has a line for the device buffers. The buffers
group the variables to be exchanged with the device.
The left zone shows the buffers for the device and a field for
setting the number of the buffer to be analyzed. Setting a
valid value lets you display the buffer's composition.
On the other hand, if you press the "Go to Last Error Buffer"
button, you go directly to the last buffer that had an error (if
and only if there is an error present). In this case, the buffer
also shows which variable caused the error and its possible
causes.
The top zone of the buffer shows:
•
Device name – Number of Buffer (number of line).
•
BufferType.
•
RemoteDataType.
•
Priority.
•
Enable.
35
Advertisement
Table of Contents
