Unable to Detect Configuration

This error usually occurs because the communications link is simplex or the device is not connected. In order for a successful configuration detection to occur, the computer needs to have a reliable bi-directional communications path to the device.

If the device and firmware are correct, and detection still fails, or is erratic, then the communication link may be bad, or the device is heavily loaded. In order to determine whether a suitable device is connected, the detection software uses timeouts for responses. If a DM is heavily loaded, then the response delay may exceed this timeout limit, and detection fails.

If the device is connected to a network computer, then the remote machine may be unreachable, or the network link may be very slow. These conditions can be checked by pinging the remote computer. Note that when the local and remote computer are on the same network, the IP numbers must match in accordance with the subnet masks in order to establish a connection. E.g. two computers with IP addresses 192.168.10.1 and 192.168.10.2 can connect, but 192.168.10.1 will not connect to 192.169.10.2, with the subnet mask 255.255.0.0.

Before repeating an attempt to detect or download a configuration, it is recommended to ensure that data is flowing through the system – wait until blocks are seen to be received.