Delta DeviceNet Builder

Delta DeviceNet Builder: network setup, EDS and PDF manuals

Delta DeviceNet Builder is a Windows engineering utility for supported Delta DeviceNet master/scanner and slave/adapter devices. Model-specific tasks include discovery, EDS registration, scan lists, I/O mapping, parameters and diagnostics. It is not a PLC ladder editor. CPU logic is prepared separately in ISPSoft or WPLSoft for supported legacy DVP CPUs.

V2.04 is the latest version name in the official download-centre records checked on 14 November 2026. Its listed issue date is 29 December 2017. The official DeviceNet Builder V2.04 download follows Delta’s terms/verification flow. Obtain the installer from the manufacturer; the PDF links below are prepared for the AVM document archive.

Hardware and roles · Network setup sequence · Versions and Windows · PDF manuals

Supported hardware and distinct roles

DVP scanner: DVPDNET-SL provides DeviceNet access and scan-list management with a compatible DVP PLC. Select its master/slave role according to its manual. DVPCOPM-SL uses CANopen; a similar name or connector does not establish interchangeability.

DVP remote I/O: RTU-DNET is a DeviceNet remote I/O/adapter module supporting the documented DVP Slim I/O and RS-485/Modbus functions. It is not treated as a standalone scanner equivalent to DVPDNET-SL. Delta’s product page identifies RTU-DNET as discontinued in June 2024; this status does not apply automatically to all DeviceNet hardware or the software.

AS series: the AS01DNET-A switch separates Master/Slave and RTU roles. In master/slave mode it works with a compatible AS PLC. RTU mode uses external 24 VDC power and compatible AS I/O modules on its right. The AS manual, PDF 491 requires DeviceNet Builder V2.04 or later for master/slave setup.

AH series: AH10DNET-5A operates as master or slave with a compatible AH500 CPU. AHRTU-DNET-5A is an AH remote I/O module. DVP RTU-DNET, AS01DNET-A and AHRTU-DNET-5A have different expansion, power and mapping arrangements.

Drive cards: CMC-DN01 and CMM-DN01/CMM-DN02 are DeviceNet slave cards. The CMC manual shows installation on VFD-C2000; the CMM manual covers MS300/MH300 and states minimum firmware requirements. Confirm card slot, drive model, firmware, EDS and data lengths before treating any card as suitable for another Delta drive.

DeviceNet, CANopen and EtherNet/IP

DeviceNet and CANopen can share a CAN physical basis but use different communication and device-description systems. CANopen Builder and DVPCOPM-SL form a separate tool/hardware pairing. EtherNet/IP requires its own Ethernet configuration. A shared EDS filename extension does not make descriptions interchangeable between protocols.

An EDS device-description file identifies vendor, product type/code, revision and connection/parameter information. Select the correct DeviceNet model and revision from the device-description files. A utility such as EDS Builder is not another DeviceNet Builder version. Installing an EDS does not automatically complete the PLC logic or actual scan list.

PC engineering connection and fieldbus are separate

Connecting the PC to a PLC over USB, serial or Ethernet does not mean that the DeviceNet bus connects directly to the PC. AH/AS examples establish the engineering channel in COMMGR and open the module tool through ISPSoft/HWCONFIG. COM settings in a legacy DVP example are not universal settings for newer CPUs.

Check MAC ID/node addresses 00–63 and standard DeviceNet rates of 125, 250 and 500 kbit/s. Nodes must share the correct rate and have unique addresses. Extended 10/20/50/800 kbit/s or 1 Mbit/s settings on certain Delta modules are not universal DeviceNet-device capabilities. The PC serial baud rate is separate from the bus rate.

Wire V+, V−, CAN_H, CAN_L and shield according to the exact model diagram. Check bus power separately from PLC/module power. The DVPDNET-SL manual specifies 121 Ω termination between CAN_H and CAN_L at both physical ends of the network; do not add a resistor to every node. Also check pinout, cable type and model suitability for connection parts such as UC-DN01Z-01A and UC-DN01Z-02A.

DeviceNet network setup sequence

1. Record the full CPU, scanner, adapter/slave, drive-card and I/O module codes. Back up PLC logic, DeviceNet configuration, EDS files, firmware details and drive parameters. Match master/slave/RTU switch positions and physical module order to the project.

2. Confirm the supported programming/configuration cable and PC–PLC channel using the manufacturer diagram. Then check DeviceNet bus power, node addresses, rate, shielding and termination. A connector fitting physically does not establish electrical compatibility.

3. Register the correct EDS and discover devices over the supported connection. Compare model, node and revision with the physical label. Discovery does not mean that a device has entered the master scan list or that cyclic I/O is active.

4. Add the required slaves to the master scan list; verify connection type, input/output sizes and mapping. Determine whether each field requires bytes, words or a parameter count. The AS01DNET-A manual explains that a slave absent from the scan list does not receive an automatic I/O connection.

5. Download the required configuration to the intended master/slave. Check project saving separately from writing settings to a module. Once its operating/RUN conditions are satisfied, monitor communication state, errors and actual I/O values. Begin with a few known values while the machine is in a permitted safe operating state.

I/O mapping, drive parameters and explicit messages

Whose perspective defines Input and Output? A master input may be data sent by a slave; a master output carries commands to the slave. Match the PLC register area, slave connection lengths and drive parameter map. Do not copy D-register addresses from an old example into another CPU/module arrangement without checking.

CMM-DN01/DN02 example: PDF 21 explains that the Parameter Editor fields accept decimal values, including H2000 → 8192. This is a specific drive parameter map, not a universal PLC register address for DeviceNet objects. Set input/output counts together with the selected Data_in/Data_out parameters.

For explicit messages, obtain class, instance, attribute and service from the device’s DeviceNet object model. Do not interpret them directly as Modbus 4xxxx addresses or CANopen PDO/SDO entries. Check supported services, data types, access rights and firmware requirements in the card’s object tables.

Discovery works but I/O does not

Read the model-specific MS/NS state and fault code. Compare configured and physical node addresses, slave types and data sizes. In this DVPDNET-SL edition, E2 relates to a missing/offline scan-list slave and E6 to data larger than expected. Other models may use different fault-code tables.

PC access to the PLC, DeviceNet bus connectivity and cyclic mapping are separate stages. If a device is visible but PLC values do not change, check scanner operating state, input/output areas, slave parameter mapping and the registers used by the PLC program. A drive accepting network control also needs command/frequency-source settings matching its own manual.

Versions, package records and Windows

Delta’s 2011 bulletin documents V1.03 → V1.05. Current central records list V2.02 dated 25 August 2014 and V2.04 dated 29 December 2017. These provide four manufacturer-documented version names. A third-party V2.0 reference is retained separately as a research candidate, not as a verified official installer release.

Two official V2.04 records differ: the PLC record lists 150 MB and Windows XP / 7 (32/64-bit) / 8 (32/64-bit) / 10 (64-bit). The Fieldbus record lists 110 MB and Windows 2000 / XP / Vista / 7 (32/64-bit). Their title and date match, but the metadata difference is preserved; installer byte equality was not checked.

Windows 11 support is not explicitly confirmed by these records. A multilingual label does not independently establish a Turkish interface. The previous official V2.02 record supports legacy-installation research; V2.02 does not satisfy the AS01DNET-A requirement for V2.04 or later. This is not claimed to be an exhaustive archive of every intermediate build. Record module firmware, EDS revision and software version separately.

PDF manuals and archive scope

The following six English manufacturer documents are model/application references, not a standalone DeviceNet Builder V2.04 interface manual. Historical DVPDNET-SL and CMC editions help document existing installations; confirm current hardware/firmware scope against the applicable model documents.

DVPDNET-SL DeviceNet scanner operation manual — Historical edition: network setup, scan list, PLC mapping, explicit messages and fault codes. The printed date is preserved; this is not presented as the 2023 edition. PDF 6: pinout and 121 Ω termination; PDF 44: E2–E7 diagnostics. Language: EN; 2012-03-27; Rev.03; 44 pages; 1.30 MB.

RTU-DNET remote I/O application manual, Rev.04 — DVP Slim I/O expansion, DeviceNet and RS-485/Modbus functions, mapping and an application example. Not the manual for AS01DNET-A or AHRTU-DNET-5A. The revision code comes from the document; 20160704 in the official filename is not treated as a printed publication date. Language: EN; Rev.04; no printed date; PDF created 2016-06-22; 50 pages; 1.37 MB.

AS module manual: AS01DNET-A master/slave and RTU — Chapter 11 starts at PDF 479. PDF 481: master/slave and RTU roles; PDF 491: DeviceNet Builder V2.04 or later for master/slave setup; PDF 560 onward: COMMGR, network and remote I/O example. Preserves the shared PDF name and bytes from the DCISoft package. Language: EN; 2022-05-16; 11th revision; 724 pages; 25.62 MB.

AH500 module manual: AH10DNET and AHRTU-DNET — Chapter 10: AH10DNET-5A master/slave, PDF 390 onward. Chapter 11: AHRTU-DNET-5A remote I/O; PDF 470 onward: COMMGR connection, DeviceNet Builder, parameters and monitoring. Same shared document as the previous CANopen Builder/DCISoft archives. Language: EN; 2020-12-25; Rev.07; 810 pages; 28.25 MB.

CMC-DN01 DeviceNet slave card operation manual — Card installation on VFD-C2000, DeviceNet wiring, EDS, network setup, drive mapping and objects. Historical model/edition reference; not interchangeable with CMM-DN01/DN02. Language: EN; 2011-12-26-A; 27 pages; 2.37 MB.

CMM-DN01/DN02, MS300/MH300 DeviceNet manual — Chapters 4–5: DeviceNet Builder, parameter mapping, scan list and a DVP28SV/DVPDNET-SL example. PDF 21 explains hex/decimal conversion such as H2000 → 8192. Cover requirements: MS300 V1.07 / MH300 V1.02 or later; CMM-DN02 card V1.01 or later. Language: EN; June 2023; Edition 00; 47 pages; 3.08 MB.

Editor’s note

Identify whether the hardware is a scanner, remote I/O adapter or drive slave card. A DeviceNet label does not make their roles equivalent. Record the AS01DNET-A RTU/Master-Slave switch position before starting.

Back up PLC logic, scan list, EDS files and drive parameters before modifying a working network. Photograph node switches and module order. Saving a PC file is separate from reading/writing module settings; check the result afterward.

Do not proceed directly from discovery to output tests. Verify the actual node and I/O lengths, then monitor a known input or status word. Prepare for mechanical movement before testing a drive run command; communication indicators alone are insufficient.

For intermittent faults, check bus power, terminals, CAN_H/CAN_L, shielding and 121 Ω termination at the two physical ends. Do not load the bus with a resistor at every device. Verify wiring with the relevant power removed instead of moving live conductors.

If data arrives with incorrect values, check byte/word counts, input/output perspective and hexadecimal/decimal notation. In the CMM example, H2000 and 8192 represent the same number. Verify one or two parameters before expanding the map.

When maintaining an older machine, preserve the working software version together with card firmware and EDS revision. Remember the V2.04-or-later requirement for AS01DNET-A and check Windows compatibility separately. Reset and firmware changes should not be the first diagnostic step.

Related topics

Delta PLC software · Delta ISPSoft · Delta WPLSoft · Delta COMMGR

Delta CANopen Builder · Delta DCISoft · Delta device description files · Delta EDS device description files

Delta DVP PLC series · Delta AS PLC series · Delta AH PLC series · Delta DVPDNET-SL

Delta RTU-DNET · Delta AS01DNET-A · Delta AH10DNET-5A · Delta AHRTU-DNET-5A

Delta DVPCOPM-SL · Delta UC-DN01Z-01A · Delta UC-DN01Z-02A · Delta Plc Cables

Delta PMSoft · Delta TPEditor · Delta LCSoft

External references

Official Delta DeviceNet Builder download centre · Manufacturer 2011 software-update bulletin · Official RTU-DNET product/discontinuation entry