Table of Contents
Advertisement
•
Err SDO Input Fail: occurs when SDO dialog between
Master node and Slave fails in Read.
The list of exchanged CANopen objects is defined on
the "SDO Input" table built in GF_Net. The following
will be specified:
SDO Read phase,
- the CANopen object in which the error occurred,
showing Index and SubIndex,
- as appropriate, a possible problem due to failed
reception of the SDO or possible reception of an ABORT
message.
•
Err SDO Output Fail: occurs when SDO dialog between
Master node and Slave fails in Write.
The list of exchanged CANopen objects is defined on
the "SDO Output" table built in GF_Net. The following
will be specified:
- if the error occurred during the SDO Write phase,
-the CANopen object in which the error occurred,
showing Index and SubIndex,
- as appropriate, a possible problem due to failed
reception of the SDO or possible reception of an ABORT
message
•
Err PDO Tx (S => M) control: control: occurs when
control by the Master of PDOs in reception fails. In this
case, the first PDO NOT received will be highlighted.
Search for the indicated COBID in GF_Net to find the
PDO causing the problems
•
Err Network Fail: occurs when the Master detects a HW
error in the network. In this case, a series of possible
causes is shown for troubleshooting.
•
Err Node not Exist: occurs when the Master does not
detect the presence of the Device in the network.
Emergency information
To see information on the Emergency message sent by the
Slave device, select the device from the list on the left and
the EMGY tab at the bottom right.
Available information:
•
Network Number: number of the CAN network to which
the device is connected.
•
Node Number: node number assigned to the device.
•
Dev Name: device name as defined in GF_Net
•
Emgy ErrCode: contents of Emergency message Error
Code field according to CANopen standard
•
Emgy ErrReg: contents of Emergency message Error
Register field according to CANopen standard
•
Aux Code (byte 1): shows first data byte of Emergency
message.
•
Aux Code (byte 2): shows second data byte of
Emergency message
•
Aux Code (byte 3): shows third data byte of Emergency
message
•
Aux Code (byte 4): shows fourth data byte of Emergency
message.
•
Click the Hex box to display the error codes and byte contents
in hexadecimal format instead of decimal format.
If there is no error, the value of the error codes and byte
contents is zero.
80949_MAN_eView BOX_05-2019_ENG
- if the error occurred during the
Attention: Although coded according to a general
standard, the indication of local errors by the device
is often specific to the device in use.
Therefore, it is advisable to refer to the Slave device
manual.
EtherCAT
Click the EtherCAT button on the lower navigation bar to
access diagnostics of the network and of EtherCAT devices.
The component is divided into 3 Zones:
•
a line describing network status.
•
a list of EtherCAT devices described in the system.
•
a button that lets you access advanced information on
the network.
The description line is divided into 2 sections:
The first part (on the left) has the following structure:
EtherCAT (ETH# 2): 8
The number in parentheses indicates the physical card (as
seen by the 'ipconfig' shell command or by gsetup) on which
the EtherCAT network was configured.
The number after the word cfg, indicates the EtherCAT
network activation status:
•
1
INIT.
•
2
PREOPERATIONAL.
•
3
SAFE OPERATIONAL
•
8
OPERATIONAL.
+16
Error Flag in OR in above cases
The message (and its color) on the right specify the EtherCAT
master diagnostics:
•
"OK" Green - Good operating condition;
•
"Cable disconnected" Red – Communication bus
probably disconnected; no slave in communication;
•
"Slave(s) not connected" Red - One or more slaves not
connected;
•
"Not OK" Orange - Master in generic error condition;
•
"Slave(s) status not expected" Red - One or more slaves
in unexpected status.
The main window lists the configured devices. Several
columns are shown, with the following content:
•
Status: operating status:
•
"----"
Slave not previously communicated with;
•
"INIT"
Slave in init condition;
•
"PREO" Slave in Pre Operational condition;
•
"BOOT" Slave in bootstrap condition;
•
"SAFE" Slave in Safe Operational condition;
31
Advertisement
Table of Contents
