Weidmüller Device Editor
The Device Editor configures the IO station of a Weidmüller device. You build the module layout in the editor, send it to a selected device, and read back what the device actually reports.
Open it from the Weidmüller connection in the connections tree: select the connection and click Device Editor. It opens in a floating window over the IDE.
Select a Device
Section titled “Select a Device”The editor opens with Select a device to configure. Until you pick one, the editor works locally: you can build a configuration and download it, but Push to device and Get from device stay disabled.
Selecting a device reads its current state once, so the editor starts from what the device holds rather than from an empty station.
Push to Device
Section titled “Push to Device”Push to device sends the configuration currently open in the editor.
What happens next depends on the device:
- Devices that deploy automatically apply the stored configuration to the physical IO station themselves. You get a second confirmation naming the version that was applied — for example, Applied to the physical IO station as version 12. Only this message means the hardware was reconfigured.
- Devices that do not keep the configuration stored until you apply it with the Weidmüller device tooling.
Messages you may see
Section titled “Messages you may see”| Message | What it means |
|---|---|
| Stored on the device as version N | The device accepted and stored the configuration. If the device deploys automatically, a separate confirmation follows. |
| Applied to the physical IO station as version N | The configuration reached the hardware. This is the confirmation that matters. |
| Pushed to the device, but the device rejected it | The device stored nothing. The device’s own error message is included. |
| Stored as version N, which differs from the version you sent | The device stored a different version from the one sent. Read back from the device before trusting the editor’s view. |
Get from Device
Section titled “Get from Device”Get from device asks the device what it currently holds and loads the answer into the open editor. The editor is updated in place — it is not reset, and anything you have not pushed is replaced by what the device reports.
| Message | What it means |
|---|---|
| Loaded the version stored on the device (N) | The editor now shows the device’s stored configuration. |
| Loaded the IO station the device reports | The device reported its physical modules. The stored configuration version is named when the device holds one. |
| The device holds no stored configuration, so there was nothing to load | The device has never been configured. The editor is unchanged. |
| Device runs N; cloud stored M | The version the device runs differs from the one stored in the cloud. The device is the authority on what is running. |
The IO Station Panel
Section titled “The IO Station Panel”Below the editor, the IO station panel shows what the device reported, next to the configuration you have open. The editor itself shows one layout at a time, so this panel is where the two are compared.
It reports:
| Station state | The state the device reports for its station |
| Read at | When the device last reported it |
| Service | The version of the device service, when reported |
| Comparison | Matches the configuration shown, or the number of differences |
Two cases are called out explicitly rather than shown as an empty table:
- The device has not reported its IO station yet — nothing has been read back.
- The device reports no modules in its IO station — the device answered, and its station is genuinely empty.
Download Configuration
Section titled “Download Configuration”Download configuration saves the configuration open in the editor as a file. It works without a device selected and sends nothing to the device.
Troubleshooting
Section titled “Troubleshooting”Push and Get never answer
Section titled “Push and Get never answer”Cause: The Weidmüller device management service is not enabled on the device. It is the service that reads and writes the IO station, and it is optional — a device can run the logiccloud runtime perfectly well without it, and then there is nothing to answer the Device Editor.
Solution: Open the device, choose Edit device processes, enable Weidmüller device management service, and try again. See Weidmüller u-control 2000.
Reading from the device times out
Section titled “Reading from the device times out”Cause: The device did not answer in time. It may be offline, or busy reading its station.
Solution: Use Retry reading from the device, which appears next to the other actions after a timeout.
”the editor is not loaded, so it could not be shown”
Section titled “”the editor is not loaded, so it could not be shown””Cause: The device answered, but the editor window was no longer in a state that could display the result.
Solution: Close and reopen the Device Editor, then read from the device again. The device’s configuration is unaffected.
The device reports modules the configurator did not take
Section titled “The device reports modules the configurator did not take”Cause: The device reported an IO station the editor could not load — usually a module the configurator does not recognise. The message names how many modules the device reported and why they were not taken.
Solution: Use the IO station panel to see what the device actually reports. It stays accurate even when the editor cannot show the layout.
Push and Get are disabled
Section titled “Push and Get are disabled”Cause: No device is selected. Both actions need a target device.
Solution: Select a device under Select a device to configure.