The internal timeout is used in two ways: first as the wait for the drive's ASCII channel to become available (a previous command, possibly from another process, may still be in progress), then as the wait for the command's response. Each wait generates a timeout error if exceeded, so a call can block for up to twice the internal timeout before erroring. Axis: Homing
/* This sample application demonstrates drive-based homing with a Kollmorgen AKD drive using the RapidCode .NET API.
AKD Drive-based ASCII homing uses preloaded methods available on the drive.
This allows for homing to be performed entirely in the drive without network latencies producing more accurate results.
Drive homing is the recommended homing strategy since it avoids network latencies by having the drive execute the homing routine.