NET_VAR_CONTROL: Configuring the x Data Structure Guide

What the x Connection Does

The x connection carries the data structure that links NET_VAR_CONTROL with the downstream function blocks. Treat it as a shared structured value: connect the same structure through every participating block rather than entering an IP address or scalar value directly at x. The evidence does not provide the structure's declared type, member names, or exact editor syntax, so obtain those details from the library declaration or demo project instead of guessing them.

Build from the Library Demonstrations

Open the network library as a project and locate its demo folder. The available evidence identifies both master and slave demonstrations and states that the relevant blocks must exist on both controllers and must not be excluded from compilation.

1. Load net_var_master_demo on one controller and net_var_slave_demo on the other.
2. Enter each controller's counterpart address: the master-side configuration points to the slave, and the slave-side configuration points to the master.
3. Leave the remaining demo logic unchanged during the first test so configuration faults remain distinguishable from application changes.
4. Compile both sides and confirm that every required block is included.

The discussion references both Chapter 12 and Chapter 13 of an unspecified manual. Because the evidence conflicts on the chapter number, locate the section covering NET_VAR_CONTROL or network variables by subject rather than relying on either number alone.

Resolve the “Too Large” Compilation Failure

An imported master block appeared to fit only after blocks were excluded from compilation; the imported block then remained untranslated and did not operate. Re-enabling it reproduced the “too large” message. This establishes a resource or compiled-size constraint, not a valid workaround: a required block that is hidden or excluded cannot provide the intended function.

Restore every required network-variable block to the compilation set, compile the complete application, and assess the resulting size against the target controller's available capacity. Removing the library's demo section does not prove that the operational blocks fit. The evidence supplies no controller model, memory totals, compiler report, or exact limit, so the required remedy cannot be narrowed to code reduction, library reduction, or a different controller without those measurements.

Verify the Two-Controller Configuration

Verification requires a clean build on both controllers with the master and slave blocks included. Confirm that each side contains the correct demo role, references the opposite controller's address, and passes one compatible x structure through its participating blocks. Do not treat a download as successful if the compiler silently skipped the imported block.

If the system still fails, preserve the unmodified demo except for the two counterpart addresses and record which side fails compilation or operation. This isolates address configuration, block inclusion, and controller-capacity problems before application logic is added.

FAQ