10 TROUBLESHOOTING
Although by no means exhaustive, Table 42 provides possible c auses behind some of the most common
errors experienced when using the interface card.
Table 42: Troubleshooting
No communications
between the
interface card and
the inverter
Inverter displays
“Er4” code
• Confirm that the interface card connector is
properly seated.
• Rebooting the interface card via the Fuji
Configuration Studio disrupts the communication
with the inverter. Reset the fault.
• If the card is connected in a ring topology, all
devices in the ring must be configured with the
same ring redundancy protocol (i.e. MRP). The
appropriate ring redundancy protocol must also be
enabled on the interface card. Otherwise a ring
topology will create an Ethernet loop and result in
undefined/erratic behavior.
No communications
between the
network and the
interface card
Communications
cannot be
established, the
Ethernet “link” LED
is off, or the Ethernet
“activity” LED
flashes only
infrequently or not at
all
• Confirm that the card is running normally (Module
Status LED is not blinking red) and connected to
the local Ethernet network.
• Ensure that the card is programmed with
compatible network settings. Consult with your
network administrator to determine the compatible
settings.
• Confirm that the destination IP address
programmed into the controller equipment or
computer matches that of the interface card, as
displayed by the studio.
• Confirm that intermediate firewalls or routers have
been configured to allow access to the interface via
the applicable TCP/UDP ports.
• Try a known working Ethernet cable and switch.
• If attempting to access the web server on a
computer whose web browser is configured to use
a proxy server, ensure that the proxy server is
accessible to the computer, and that the interface
card is accessible to the proxy server.
No PROFINET
communication
PROFINET I/O
communication
cannot be
established. The
“Network Status”
LED is not solid
green.
• Confirm that the card’s PROFINET device name
matches the name assigned in the controller’s
configuration.
• Confirm that the card’s network settings match the
settings assigned in the controller’s configuration.
• Confirm that the I/O cycle update time is set to 1ms
or larger.
• Ensure that the card is connected to a 100Mbps full
duplex capable switch.
• Ensure that the card can be discovered using the
controller’s discovery tool.
To Next Page
Loading...