See Device not Shown in the Workbench Help for a detailed discussion of this problem.

If you are communicating through the Ethernet port at connector X11, you might not see your drive in the connect window for any of the following reasons:

• Poor cable connection. Make certain you have a good connection between your computer and the drive by checking to see if you see a blinking light next to the connector (at each end).
• Improper rotary switch setting. Make certain that the S1 and S2 rotary switches on the front of the drive are set to 0 (bottom position), unless you are attempting a point to point connection and your computer is set up to connect in this manner.
• Conflict with another device that is networked to your computer (including your wireless connection). In some cases, turning off your wireless card will fix this. You can turn your wireless card back on after you establish communication with the AKD).
• Improper TCP/IP settings. Make certain that the TCP/IP settings in the network port that you are communicating through are working properly.

In most cases, firmware is downloaded using WorkBench without setting the hardware into a specific “download” state. If you need to download firmware, but are unable to connect to WorkBench, use the procedure described in Forcing the drive into firmware download mode in the Workbench help.

Autotuning of your application delivered unexpected results while tuning the current feed forward value. Please deactivate "Tune Acceleration FF" in the Workbench Performance Servo Tuner screen and restart the tuning.

Up to 500 s depending on the active current. See page Foldback Times.

5 seconds with Ipeak. Smaller currents can be sustained for longer periods. See Foldback Times.

There are two ways to find out about what parameter is behind a text box in Workbench.

1. Right click on the text box and select Parameter Info from the menu. A popup appears next to the window selected. Note if you clicked the Help, you get taken to the page in the help system. Pressing F1 also does the same.
2. Click the “Tell me more about this topic” link at the top of each page.

First, check the LED on the RJ45 connector. If the LED is not illuminated, then no communication with the drive is possible. Possible causes for loss of communication with the drive include:

• The network cable is disconnected.
• A wiring problem exists between the drive and the network switch/hub.
• The switch/hub is not powered.

If the LED is lit and the IP address on the drive is 0.0.0.0, then the most likely problem is that the drive hardware has not detected a valid link.

This problem is related to the MSI installer. You can resolve it as follows:

1. Cancel the installation.
2. Make sure that you have enough disk space on your hard disk (~500MB) to allow Windows .NET update if necessary. If you do not have enough disk space, then make additional space for the installation.
3. Relaunch the installer (you may need to try this several times, the problem is random).

The AKD2G provides up to 28 I/0.

• 16 I/O is standard for the single axis
• 28 I/O is standard for the dual axis
• An I/O expansion is available for the single axis model, which adds an additional 12 I/O on X22 for a total of 28 I/O.

Yes, Workbench works both for the AKD and AKD2G, but parameters/programs are not transferrable from the AKD to the AKD2G at this point.

Yes, there is a dual channel STO for each axis in the drive.

No. The AKD2G is optimized for single cable motors but separate power and feedback two cable motors do work with the AKD2G. You need to order the SFA cable adapter or use X23.

The current rating of AKD2G is per axis, so a 3A continuous AKD2G dual axis has 3A continuous available for each axis.

No. Resolver is not offered as a “safe encoder” by Kollmorgen. You will need a digital safe encoder. The AKD2G offers H-DSL and EnDat 2.2 as safe solutions.

There are three possible solutions to this.

• Hardwiring I/O to X23
• Using EtherCAT
• Designing a dedicated control mechanism with MechaWare