On a Do-more PLC system with an ECOM100, emulate the DirectSOFT/DirectLOGIC ECSETUP IBox with staged logic to configure the module’s IP address, gateway address, and subnet mask. There is no native Do-more instruction for this task in the described setup, so the example sequences the required operations through an ECSetupIP code-block.
Check the ECOM100 and project before changing addresses
Confirm that the target is an ECOM100 installed in the Do-more system and identify the @ECOM_000 device name used by your project. The example uses that device name in its message-buffer configuration; change it to match the device name in your installation. Do not assume the example’s device reference matches your PLC configuration.
- Open the project in Do-more Designer and check that its version is 1.3 or later, the minimum version stated for the supplied example.
- Confirm that the project contains the ECSetupIP code-block and that its internal variables V100 through V143 are available for the message buffer.
- Locate the ECOM100 itself. The IBox-enable switch is on the module, not the CPU.
Check: Identify the ECOM100 device reference, available buffer variables, and the module’s DIP-switch bank before editing or running the logic.
Load the IP, gateway, and subnet values into the expected registers
ECSetupIP reads its input parameters from three data registers: D100 for the IP address, D101 for the gateway address, and D102 for the subnet mask. Populate these registers with the values intended for the ECOM100, using the address representation required by your DirectLOGIC ECSETUP IBox implementation and project. The example specifies the register assignments but does not define an encoding or validation range, so verify the value format in the applicable IBox documentation and your project before execution.
| Register or variable | Role in the example |
|---|---|
D100 |
IP address input |
D101 |
Gateway address input |
D102 |
Subnet mask input |
C100 |
Success output bit |
C101 |
Error output bit |
DLV42 |
Error-code output; zero indicates success |
V100–V143 |
Internal message buffer in the example |
Check: Confirm that each intended network value is in the assigned register and that the chosen representation matches the IBox implementation.
Enable IBox functionality on the ECOM100
A common wrong fix is to keep changing ladder logic when the module itself is not configured to enable IBox functionality. The example requires DIP switch 7 to be ON on the ECOM100. This switch is on the module, not the CPU. If it is off, the prerequisite for running the emulated IBox sequence is missing; editing the input registers does not substitute for enabling the module feature.
Set switch 7 according to the module’s installation procedure and confirm its position before running ECSetupIP. If switch access or the correct module identification is uncertain, stop rather than toggling CPU switches or guessing.
Check: Verify that DIP switch 7 is ON at the ECOM100 module itself.
Run ECSetupIP and monitor its result outputs
The example’s $Main logic uses an X0 contact to drive a RUN ECSetupIP box. Use the intended control condition in your application; do not treat the example input as a required field address for every installation. The code-block uses stages to sequence the steps needed for the IP configuration operation.
- Review the run condition and confirm it will invoke the code-block only when the three input registers contain the intended values.
- Run the ECSetupIP code-block using the project’s intended trigger.
- Monitor
C100,C101, andDLV42for the operation result.
Do not diagnose an unsuccessful operation from one output alone. Check the success and error bits together with the error-code register. The example defines DLV42 as zero on success; use the DirectLOGIC ECSETUP IBox documentation to interpret a nonzero code.
Check: Confirm that the operation completes with C100 indicating success, C101 indicating no error, and DLV42 equal to zero.
Correct the error-code destination before adapting the example
A subtle failure occurs when you move the error-code output to a different DLV address but leave the DLWX instruction’s destination unchanged. In the example, rung 4 contains a DLWX instruction whose “To DL V42” parameter must be updated to the corresponding destination. For example, if the error outputs are changed from DLV42 to DLV100, change the DLWX “To DL” parameter to V100 as well. Changing only the output references can leave the instruction writing to the old destination, so the monitored register will not report the expected result.
Keep the three input assignments, output assignments, message-buffer range, device reference, and DLWX destination aligned with the project. Make edits consistently, then inspect rung 4 and cross-check every output reference before retesting.
Check: If the error-code address changed, verify the rung 4 DLWX “To DL” destination matches it exactly.
FAQ: Diagnose ECOM100 IP setup behavior
Why does ECSetupIP not configure the ECOM100?
Check that DIP switch 7 is ON on the ECOM100 module, not the CPU. Then verify the device reference, input registers, and code-block run condition.
Why is DLV42 still zero when the setup fails?
Check whether the code-block ran and whether rung 4’s DLWX “To DL” destination still matches the configured error-code output address. Consult the ECSETUP IBox documentation for nonzero error-code meanings.
Why do I need to change the DLWX instruction when moving the error output?
The instruction has its own destination parameter. If you change the output from DLV42 to DLV100, update the rung 4 “To DL” parameter to V100 too.
Why does the example use V100 through V143?
Those variables form the example’s internal message buffer for the @ECOM_000 device. Adjust the buffer and device reference to fit the project’s actual installation.
Why should I not copy the example input values or addresses blindly?
The example assigns D100, D101, and D102 to the IP, gateway, and subnet values, but the value encoding and device name must match the project. Stop and contact official AutomationDirect support if the ECOM100, IBox documentation, or error-code destination cannot be identified confidently.