GdNet Diagnostics interface
The main interface of Gefran’s tool for GdNet Diagnostics is:
The component is divided into 3 Zones:a line describing network statusa list of GdNet devices described in the systema button that lets you access advanced information on the networkThe description line is divided into 2 sections:The first part (on the left) has the following structure:GdNet (ETH# 2) cfg: 9The number in parenthesis describes on which physical board (as seen by the ipconfig shell command) you are configuring the GdNet network.The number (linked to a color) that appears after the word cfg indicates GdNet activation status:-1 (dark gray) GDNet activation not yet launched2 (cyan) GDNet assigned to more than one network3 (magenta) GDNet assigned to unsupported hw4 (yellow) GDNet I/O cfg file not found5 (red) Elaboration of I/O cfg file ended with err6 (blue) GDNet not configured7 (light gray) No device found in GDNet I/O cfg file8 (dark green) GDNet being activated9 (bright green) GDNet activation ended correctlyother (black ) Not provided for (unexpected error)The second part is an index of network operation (First level).It shows the status of 3 variables. In order, from left to right:Status AEquals 1 (green) if all configured devices are correctly connected and have all boards configured. Operating conditions are perfectly in line with the configuration.Otherwise, equals 0 (yellow): at least one device missing, or a single board of a device is missing (in any case, a correct and admissible operating condition).Status BEquals 1 (green) if all devices detected so far are currently connected, even if fewer than that of configuration, and if there is no mismatch condition in the boards found (see GetCards). In addition, all of the valid boards found when the device was first connected must currently be present.Otherwise, equals 0 (red): at least one device not connected (previously, it was), or mismatch for a board of a single device (condition detected at first connection), or a single board found at first connection is no longer present.FailEquals 0 (green) if no board of no device has fault A or P active.Equals 1 (red) if at least one board has fault A or P active.The center window lists the configured devices. It has 3 columns with the following content:- rotary number (node number) and device name (as entered in the hardware configurator)- operating status“ ” Slave not configured“Cfg” Configured Slave never found“Sw0” Slave about to go operational“Mis” Slave lost“Prg” Slave in program“Ope” Slave operative- Device type“MC” Motion control (drive)“GL2” GiLogikUsing the cursor keys, go to the list and press Enter. You can scroll the list with the Up and Down keys. Press Enter again to select an item on the list; press Esc to resume navigating on the page. You can also scroll the list by using the touch screen and select an item by double-clicking.Selecting an item on the list lets you go to deeper diagnostics (Second and third level or device and board level) by displaying a panel dedicated to the device in question.
The interface displayed keeps the initial description line and the Advanced button at the bottom of the window.The list of devices is replaced by a description line, a values grid, and the Return to List button.Of course, the button let you return to the initial display with the list of devices.The description line provides second level (device) diagnostics.The grid provides third level (board) diagnostics.Second level diagnostics: device.The first part (on the left) is a copy of the information on the deleted device provided by the list: type, name, and node.The second part follows the information on the first line, but dedicated to the selected device. It shows the status of 3 variables. In order, from left to right:Status AEquals 1 (green) if the device is in operate status and all configured boards are present.Equals 0 (yellow): if the device is not in operate, or at least one of the configured boards is missing.Status BEquals 1 (green) if the device is in operate and all boards detected at first connection are present. In addition, no board mismatch was detected at first connection.Equals 0 (red) ) if the device is not in operate, or at least one of the boards detected at first connection is missing, or at least one mismatch was detected at first connection.FailEquals 0 (green) if no board has fault A or P active.Equals 1 (red) if at least one board has fault A or P active.Third level diagnostics: board.There are 3 groups of faults (A, P, H).For GiLogik modules, the meanings are as follows:fault A: board with operating problems (for example, outputs in short circuit on digital output boards)fault P : intelligent board equipped with a microcontroller that dialogs incorrectly with the ETH100 controller, local bus masterfault H : board on which a code change has been detectedFor drives, the meanings are as follows:fault A: SDO control errors (currently cannot be activated in Project)fault P:index 0: Local errors signaled by application sw of motion control devicefault H:index 0: No dialog between GDNet node and application sw of motion control deviceMismatch identifying code of application sw of motion control deviceMismatch Ipa IDB configurationMismatch IPA ODB configurationThe number has the following meaning:0 Fault not present1 Fault present2 Fault present recognized3 Fault not present not recognizedIf a fault is present, set the “Card no.” field to the number required; the field in question will be highlighted in yellow to acknowledge the fault present.Advanced sectionWith the Advanced button, you can access a 2-page section for advanced diagnostics. There is a series of specific counters that are useful if service is requested.
The component is divided into 3 Zones:a line describing network statusa list of GdNet devices described in the systema button that lets you access advanced information on the networkThe description line is divided into 2 sections:The first part (on the left) has the following structure:GdNet (ETH# 2) cfg: 9The number in parenthesis describes on which physical board (as seen by the ipconfig shell command) you are configuring the GdNet network.The number (linked to a color) that appears after the word cfg indicates GdNet activation status:-1 (dark gray) GDNet activation not yet launched2 (cyan) GDNet assigned to more than one network3 (magenta) GDNet assigned to unsupported hw4 (yellow) GDNet I/O cfg file not found5 (red) Elaboration of I/O cfg file ended with err6 (blue) GDNet not configured7 (light gray) No device found in GDNet I/O cfg file8 (dark green) GDNet being activated9 (bright green) GDNet activation ended correctlyother (black ) Not provided for (unexpected error)The second part is an index of network operation (First level).It shows the status of 3 variables. In order, from left to right:Status AEquals 1 (green) if all configured devices are correctly connected and have all boards configured. Operating conditions are perfectly in line with the configuration.Otherwise, equals 0 (yellow): at least one device missing, or a single board of a device is missing (in any case, a correct and admissible operating condition).Status BEquals 1 (green) if all devices detected so far are currently connected, even if fewer than that of configuration, and if there is no mismatch condition in the boards found (see GetCards). In addition, all of the valid boards found when the device was first connected must currently be present.Otherwise, equals 0 (red): at least one device not connected (previously, it was), or mismatch for a board of a single device (condition detected at first connection), or a single board found at first connection is no longer present.FailEquals 0 (green) if no board of no device has fault A or P active.Equals 1 (red) if at least one board has fault A or P active.The center window lists the configured devices. It has 3 columns with the following content:- rotary number (node number) and device name (as entered in the hardware configurator)- operating status“ ” Slave not configured“Cfg” Configured Slave never found“Sw0” Slave about to go operational“Mis” Slave lost“Prg” Slave in program“Ope” Slave operative- Device type“MC” Motion control (drive)“GL2” GiLogikUsing the cursor keys, go to the list and press Enter. You can scroll the list with the Up and Down keys. Press Enter again to select an item on the list; press Esc to resume navigating on the page. You can also scroll the list by using the touch screen and select an item by double-clicking.Selecting an item on the list lets you go to deeper diagnostics (Second and third level or device and board level) by displaying a panel dedicated to the device in question.
The interface displayed keeps the initial description line and the Advanced button at the bottom of the window.The list of devices is replaced by a description line, a values grid, and the Return to List button.Of course, the button let you return to the initial display with the list of devices.The description line provides second level (device) diagnostics.The grid provides third level (board) diagnostics.Second level diagnostics: device.The first part (on the left) is a copy of the information on the deleted device provided by the list: type, name, and node.The second part follows the information on the first line, but dedicated to the selected device. It shows the status of 3 variables. In order, from left to right:Status AEquals 1 (green) if the device is in operate status and all configured boards are present.Equals 0 (yellow): if the device is not in operate, or at least one of the configured boards is missing.Status BEquals 1 (green) if the device is in operate and all boards detected at first connection are present. In addition, no board mismatch was detected at first connection.Equals 0 (red) ) if the device is not in operate, or at least one of the boards detected at first connection is missing, or at least one mismatch was detected at first connection.FailEquals 0 (green) if no board has fault A or P active.Equals 1 (red) if at least one board has fault A or P active.Third level diagnostics: board.There are 3 groups of faults (A, P, H).For GiLogik modules, the meanings are as follows:fault A: board with operating problems (for example, outputs in short circuit on digital output boards)fault P : intelligent board equipped with a microcontroller that dialogs incorrectly with the ETH100 controller, local bus masterfault H : board on which a code change has been detectedFor drives, the meanings are as follows:fault A: SDO control errors (currently cannot be activated in Project)fault P:index 0: Local errors signaled by application sw of motion control devicefault H:index 0: No dialog between GDNet node and application sw of motion control deviceMismatch identifying code of application sw of motion control deviceMismatch Ipa IDB configurationMismatch IPA ODB configurationThe number has the following meaning:0 Fault not present1 Fault present2 Fault present recognized3 Fault not present not recognizedIf a fault is present, set the “Card no.” field to the number required; the field in question will be highlighted in yellow to acknowledge the fault present.Advanced sectionWith the Advanced button, you can access a 2-page section for advanced diagnostics. There is a series of specific counters that are useful if service is requested.