Why Can’t DirectSOFT Connect to a DL05 over Ethernet?

The H0-ECOM appeared in network discovery, but DirectSOFT32 could not establish a programming link to the DL05. Check controller firmware compatibility before changing network settings: the reported compatibility threshold is DL05 firmware version 4.6; earlier versions do not support the ECOM.

Check the DL05 firmware before changing the network

A visible ECOM does not prove that the controller firmware supports communication through it. The installation initially described the DL05 firmware as current, but a later check found it was older than version 4.6. Updating the controller to firmware at or above that threshold was the next action. Treat this as the first decision gate, not as a reason to update every device immediately.

1. Read the DL05 firmware version using the available controller identification or programming diagnostics.
2. If it is earlier than 4.6, confirm the correct firmware and update procedure for the exact DL05 hardware revision before proceeding.
3. If the version is 4.6 or later, continue to transport and network checks rather than repeating firmware work.

Do not confuse the controller firmware with ECOM module firmware; they are separate devices with separate update risks. Check: record the DL05 firmware version and confirm whether it meets the 4.6 threshold before testing DirectSOFT32 again.

Separate ECOM discovery from the programming connection

NetEdit and the DSLaunch Link Setup module-setup function could see or configure the ECOM, and Query Network returned a device with MAC address 00 E0 62 20 23 A4. That proves the PC can discover the module on the local network, but it does not prove the DirectSOFT32 session is using the right transport, reaching the configured IP address, or communicating successfully through the controller.

Keep the observed identifiers together during troubleshooting so you do not configure a different module by mistake. In this installation, the ECOM was set to module ID 1, module name 005ECOM, and IP address 192.168.0.100. Verify that NetEdit is showing the expected MAC address before changing its settings. A discovery result is not a substitute for checking the PC’s IP configuration and the ECOM’s current address.

Check: match the MAC address, module ID, name, and IP address shown by the configuration utility to the intended ECOM, then confirm the PC can reach the same local network.

Set the DirectSOFT32 link to Winsock and UDP/IP

The DirectSOFT32 link required the Winsock transport and UDP/IP transport protocol in this case. Other transport selections produced “Error Opening Connection To Ethernet Device.” Select the matching transport explicitly in the link setup; seeing the ECOM in a module-setup dialog does not automatically prove the programming link uses those settings.

1. Open DSLaunch Link Setup and select the link intended for this DL05.
2. Choose Winsock Transport and UDP/IP Transport Protocol.
3. Enter or select the ECOM address that NetEdit currently reports, rather than relying on an old saved link definition.
4. Save the link and attempt the DirectSOFT32 connection once.

Record the exact message. The reported “Error Opening Connection To Ethernet Device” occurred with different transport choices; “Comm Error” and “Transport Protocol Error” occurred in different connection arrangements and should not be treated as interchangeable diagnoses.

Check: verify the saved link shows Winsock and UDP/IP, then note whether the resulting error changes or the programming session opens.

Compare the network and direct-cable symptoms

The two tests failed differently: the company-network test returned a blank Comm Error during auto-configuration, while the direct crossover-cable test returned a Transport Protocol Error. These messages identify where to continue testing; neither, by itself, proves that network speed, connection count, or cable type is the root cause.

Test arrangement	Observed result	Next check
Company network; ECOM at 192.168.0.100	Blank Comm Error during auto-configuration	Confirm the PC and ECOM are on compatible IP networks, verify the address is unique, then retry with Winsock and UDP/IP.
PC on a fixed IP; direct Ethernet crossover cable	Transport Protocol Error	Confirm both endpoint addresses and subnet settings, the selected DirectSOFT transport, and the current module configuration.
Other transport selection	“Error Opening Connection To Ethernet Device”	Return to Winsock and UDP/IP for this reported setup.

A fast server and a low number of active connections do not establish that the PC’s address, subnet, or link settings match the ECOM. Likewise, a direct cable isolates the company network but does not correct incompatible endpoint addressing or a mismatched protocol selection.

Check: for each arrangement, record the PC address, ECOM address, subnet configuration, selected transport, and exact error so the two paths can be compared consistently.

Validate addressing before repeating the direct-link test

For a direct connection, the PC and ECOM still need compatible IP settings. A fixed PC address alone is insufficient if it conflicts with the ECOM address or places the endpoints on different IP networks. The reported ECOM address was 192.168.0.100; the PC’s direct-test address and subnet were not recorded, so read them from the operating system rather than guessing them.

1. Read the ECOM’s current IP configuration in NetEdit.
2. Read the PC’s active Ethernet adapter address and subnet configuration.
3. Confirm the two endpoints are on the same local IP network and have distinct addresses.
4. Retry the direct connection using the crossover cable and the Winsock/UDP-IP link.
5. If the error persists, restore the company-network arrangement only after recording the direct-test result.

Do not assign a supposed “spare” address without checking the network’s address plan or confirming the address is unused. An address described as spare in the original setup does not guarantee it remains available at the time of commissioning.

Check: verify the PC and ECOM addresses are compatible and unique, then see whether the direct-link result changes.

Stop before repeating an ECOM firmware update

After the DL05 firmware issue was identified, an attempted ECOM firmware update left the module visible to NetEdit but unable to accept address or ID changes. The update errors were not explained by the supplied directions. Technical support then diagnosed a hardware problem after further troubleshooting, and a replacement module was planned. This is a warning that discovery alone does not mean a module remains writable or healthy.

If NetEdit still sees the ECOM but cannot change its address or ID after a failed update, stop repeating the update procedure. Preserve the current settings, record the update error messages and the state of the module, and use the official support channel for the ECOM manufacturer or supplier to identify the approved recovery path. Do not treat an unexplained update failure as proof that another firmware attempt will repair the module.

Check: confirm NetEdit can both read and write the module configuration before returning it to service; if writes fail, do not proceed to commissioning with that module.

Verify the complete DL05 programming path

Once the controller firmware passes the compatibility check and the ECOM accepts its configuration, verify the full path from DirectSOFT32 to the intended DL05. A successful network query is only a discovery check; a successful programming link is the commissioning result that matters.

1. Confirm DL05 firmware is version 4.6 or later.
2. Confirm the intended ECOM is identified by the expected MAC address and has the intended module ID, name, and current IP configuration.
3. Confirm the PC’s active Ethernet adapter and the ECOM have compatible, non-conflicting IP settings.
4. Confirm the saved DirectSOFT32 link uses Winsock transport and UDP/IP.
5. Open the programming connection and verify that DirectSOFT32 communicates with the intended DL05, not merely that discovery lists the ECOM.

If the network path still fails, compare the exact error under the company-network and direct-link arrangements against the recorded settings. Change one item at a time and retest, so a working transport or address correction remains identifiable.

Check: accept the repair only when DirectSOFT32 establishes communication with the intended DL05 and the ECOM remains configurable.

FAQ: Resolve DL05 Ethernet connection questions