Ken Roach
Lifetime Supporting Member + Moderator
Okay, so you are probably back to the original problem that caused you to replace the drive and three comm modules.
The 20-COMM-D really sits between two networks: it talks to the DeviceNet scanner via DeviceNet, and talks to the drive via DPI.
If the drive can't talk to the 20-Comm-D over DPI, it gives a DPI comms fault and an "8x" error code.
If the drive can talk to the 20-COMM-D but the 20-COMM-D can't talk over DeviceNet to the scanner, the drive faults on a Network communication fault and gives an "7x" error code.
So it's very important to tell the difference. Read the code off the HIM module.
What you're at it, go to the 1788-CN2DN's node table and figure out what the error code is from the 1788-CN2DN's perspective.
The 20-COMM-D really sits between two networks: it talks to the DeviceNet scanner via DeviceNet, and talks to the drive via DPI.
If the drive can't talk to the 20-Comm-D over DPI, it gives a DPI comms fault and an "8x" error code.
If the drive can talk to the 20-COMM-D but the 20-COMM-D can't talk over DeviceNet to the scanner, the drive faults on a Network communication fault and gives an "7x" error code.
So it's very important to tell the difference. Read the code off the HIM module.
What you're at it, go to the 1788-CN2DN's node table and figure out what the error code is from the 1788-CN2DN's perspective.