Technical FAQs

Ask a Question

How do I troubleshoot an Altivar Process Drive that would not connect when trying to communicate with a Modbus over Ethernet (Modbus TCP) network?

Issue:
How do I troubleshoot an Altivar Process Drive that would not connect when trying to communicate with a Embedded Modbus Ethernet network?

Product Line:
Altivar Process Drives (ATV630, ATV930, ATV650, ATV950, ATV660, ATV960, ATV680, ATV980)

Environment:
All serial numbers for Altivar Process Drives

Cause:
N/A

Resolution:
Note: This FAQ goes over some basic checks and troubleshooting tips. For extended troubleshooting please refer to your drives Embedded Modbus Ethernet manual that is attached at this FAQ. 

Drive Will Not Connect
  • Installation
  • Network
    • No Duplicate IP addresses
    • Make sure Modbus Address is correctly set
  • Programming
    • Make sure all Basics Settings are configured correctly in the drive and that the drive is properly Powercycled after all settings are made
      • Configure Modbus Settings
        • [Communication] [Comm parameters] [Modbus SL] [Modbus Fieldbus]
      • Configure Ethernet Settings
        • [Communication] [Comm parameters] [Embd Eth Config]
Drive Connects but Will Not Run on a Command
  • Checking the Network
    • If you cannot write to the drive, first verify you can read from the drive. If unable to read from the drive then re-verify the drive is connect properly to the Modbus Ethernet network
    • Verify that you are reading the proper input and output addresses
    • Check for possible register offsets
  • Checking the Drive
    • Confirm that the drive is properly to receive commands from the Network
    • Check Command and Reference Menu
      • [Complete settings] [Command and Reference]
    • ​Check Control Mode
      • Are we using IO Profile or DriveCom (Separate or Not Separate)
    • Check drive for any faults
      • Check top left corner of the keypad.
  • ​Addtional Troubleshooting Tips:
Was this helpful?
What can we do to improve the information ?