Delta CANopen Builder

Delta CANopen Builder: network configuration and motion control

Delta CANopen Builder is Windows software for CANopen network configuration and motion programming on supported controllers. Configuring a DVPCOPM-SL or AH10COPM-5A network, creating a DVP10MC11T motion program and writing AS300 PLC logic are separate engineering tasks.

The latest Delta download record checked on 14 November 2026 is CANopen Builder V6.11. It is dated 31 August 2026, lists a 996 MB multilingual package and is available through the official CANopen Builder V6.11 download terms/verification page. The previous V6.10 record is dated 18 August 2025 and lists 928 MB.

Supported devices · EDS and PDO/SDO · Version selection · PDF references

Supported devices and distinct engineering tasks

DVP CANopen modules: DVPCOPM-SL uses network scanning, a slave list and data mapping. PLC ladder logic is prepared separately with WPLSoft or the appropriate ISPSoft environment. Adding a communication module does not turn a PLC into a multi-axis motion controller. The DVPCOPM-SL manual explains the combined workflow.

AH series: AH10COPM-5A forms a CANopen master or slave station with an AH500 CPU. CANopen Builder handles network settings; ISPSoft/HWCONFIG handles the associated PLC/module configuration. Check the physical node-address and speed switches as well. Chapter 15 of the AH500 module manual covers this module.

AS200 / AS300: the 2021 manufacturer manual describes an integrated CAN port on AS200 and the AS-FCOPM function card for AS300. CANopen Builder configures the network, while ISPSoft programs PLC logic. A slave/RTU arrangement using AS00SCM-A must also match the function card, operating mode and EDS. Do not extend the documented AS CANopen specifications to every later CPU without checking its own documentation.

DVP10MC11T: this controller has separate PLC and motion-control sections. Its manual specifies WPLSoft/ISPSoft for PLC logic and CANopen Builder for the MC motion program. Supported motion functions include axis commands, electronic cam and G-code. Preserve both the network/motion project and the separate PLC logic project.

DVP15MC11T / DVP50MC11T: the DVP15MC11T manual distinguishes the CANopen communication port from the CANmotion Motion port. The DVP50MC11T family uses EtherCAT motion networking on applicable models. The application name does not mean every controlled axis uses CANopen. Check the full model, suffix and firmware. EDS-based communication through a general CANopen port does not guarantee equivalent Motion-port axis functions.

AS500: AS524C-B uses CANopen motion, whereas AS516E-B uses EtherCAT motion. AS532EST-B/AS564EST-B have their own EtherCAT axis and operating limits. A general DS301 CANopen communication port is distinct from the synchronized motion network. See PDF pages 8 and 33 of the AS/AX-3 catalogue.

EDS, PDO, SDO and network parameters

An EDS file describes the CANopen object dictionary and communication capabilities to the engineering software. Match the exact device, firmware and EDS revision. The Delta EDS and device description file pages provide related guidance. An EtherNet/IP EDS must not be selected as a CANopen EDS.

Delta Turkey documents Tools → Device Library → Install for importing a CANopen EDS, followed by adding the device under the relevant CANopen network and configuring its PDOs. Menu names may vary by version. Importing a third-party device does not establish support for every motion profile or controller axis function.

PDOs exchange operating process data, while SDOs provide access to object-dictionary parameters. Check index/subindex, data length, signed/unsigned type, transmission direction and CPU mapping area together. A drive’s TxPDO is data received by the master; the direction must be interpreted from the device concerned.

Node ID, bit rate, master/slave role, NMT state and heartbeat must agree across the network. Detecting a device in a scan does not prove that PDO exchange or motion control is ready. Check the transition from pre-operational to operational, error indications and actual changing data. Node and PDO limits depend on the controller and firmware.

PC connection, cables and protocols

The PC-to-controller connection is separate from the controller-to-field network. The DVP10MC11T manual documents Ethernet transfer of network configuration, motion programs, cam curves and G-code from CANopen Builder. The DVPCOPM-SL example connects the PC through the PLC’s serial port. A single USB-to-CAN adapter or programming cable cannot be assumed suitable for every setup.

The CAN physical layer, CANopen, DeviceNet and EtherCAT are different layers or networks. DeviceNet Builder serves a different protocol. CANopen Builder is not a universal analyzer for all CAN devices. Requirements for COMMGR in an ISPSoft connection or DCISoft for Ethernet setup must be checked for the actual controller and connection route.

Wire CAN_H/CAN_L, shield and reference according to the device pinout. Check 120 Ω termination at the two physical ends, accounting for resistors already built into a device or adapter. For example, the archived DVP15MC manual states that termination is built into its Motion port. Do not add a separate terminating resistor at every node.

Legacy versions, Windows and project backups

Manufacturer records show V2.02, historical catalogues list V5, and later official support or announcements document V6.05, V6.06, V6.07, V6.08 and V6.09. The current download centre lists V6.10 and V6.11. These numbers identify software revisions or generations. Duplicate PLC and Industrial Fieldbus Solution listings do not establish separate editions. A complete official archive of every historical intermediate build was not found.

The V6.11 operating-system field lists Windows XP / 7 (32/64-bit) / 8 (32/64-bit) / 10 (64-bit). It does not explicitly confirm Windows 11 support. Windows 11 information for ISPSoft or WPLSoft must not be transferred to this product. A multilingual label also does not establish a Turkish user interface.

Before opening a project in a newer version, preserve the original project folder, EDS files, engineering-software version and device firmware details. Backward compatibility after saving is not assumed. Keep separate backups for PLC logic, network settings, motion programs and drive parameters.

Delta’s advisory dated 21 June 2024 recommends V6.09 or later for a specific project-file processing issue affecting V6.07 and earlier. Its main text is in Chinese and is labelled accordingly in this archive. Older versions are documented for historical reference and existing-machine maintenance.

PDF manuals and archive documents

The PDFs below are hardware, application and version references. An independently downloadable, verified general interface PDF for CANopen Builder V6.11 was not obtained during this research. Consult the help content supplied with the installed version for interface details. EN denotes English; ZH-CN denotes Simplified Chinese main text.

DVPCOPM-SL CANopen communication module operation manual — Network construction, CANopen Builder communication setup, EDS, PDO mapping, SDO/NMT and diagnostics. Historical edition: PDF created 2014-02-27; distributor listing dated 2017-11-28. Different from the 2022 Rev.03. Language: EN; Rev.02; publication date not printed; 49 pages; 0.99 MB.

DVP10MC11T multi-axis motion controller operating manual — Separate PLC and MC processors, CANopen Builder motion programming, Ethernet connection, G-code and electronic cam. This 2015 edition does not replace DVP15MC/DVP50MC documentation. Language: EN; 2015-09-01; 375 pages; 6.14 MB.

DVP15MC11T operation and motion control manual — CANopen communication versus CANmotion ports, axes/encoders, tasks, SYNC timing and motion commands. Date discrepancy: cover 2016-06-30; PDF 11 / printed 1-2 revision table 2018-05-30. Original file preserved; not assumed to cover every current suffix. Language: EN; 2018 revision body; cover dated 2016-06-30; 601 pages; 13.36 MB.

AH500 module manual: AH10COPM-5A — Chapter 15, starting at PDF 739: master/slave, hardware switches, CANopen Builder configuration and mapping. Large shared manual covering AH modules. Language: EN; 2020-12-25; 810 pages; 28.25 MB.

AS hardware and operation: CANopen functions — Chapter 10, starting at PDF 511: AS200 built-in CAN, AS-FCOPM for AS300, distinct CANopen Builder/ISPSoft roles and PDO/SDO examples. Preserves the filename and bytes from the ISPSoft archive. Language: EN; 2021-02-25; 654 pages; 30.13 MB.

AS / AX-3 catalogue: AS500 motion network distinctions — PDF 8 and 33: AS524C-B CANopen motion versus AS516E-B/AS532EST-B/AS564EST-B EtherCAT motion. General CANopen communication is distinct from the motion network. Preserves the previous filename. Language: EN; 2024-08-12 (file record); 64 pages; 11.06 MB.

Manufacturer advisory for CANopen Builder V6.07 and earlier — Main text in Simplified Chinese, with English headings. Delta recommends V6.09 or later for V6.07 and earlier. URL document number differs from the footer; the final revision table also states 2024-01-31. Original PDF unchanged. Language: ZH-CN; 2024-06-21 (main date); 2 pages; 0.60 MB.

AS 2023 archive catalogue: CANopen Builder V5 entry — Historical software table includes CANopen Builder [V5] marked Free. Catalogue date is not the software release date, and V5 is not the current release. Language: EN; 2023-01-16 (source filename); 64 pages; 11.08 MB.

Editor’s note

Start with a complete backup of the working machine. Reading PLC code alone may not preserve the network project, motion program, EDS files or drive parameters. Record the Builder version and device firmware alongside the files; this is valuable when returning to the machine months later.

If scanning finds no device, first confirm that the PC reaches the intended controller, then check the field-network address and bit rate. Test the PC connection and the CANopen bus separately to locate the fault before repeatedly reinstalling software.

If a node is visible but values do not change, inspect PDO direction, data length and the mapped CPU area. Watching only one 16-bit word of a 32-bit value can be misleading. Verify a small, known data exchange before extending the network configuration.

For servo tests, distinguish the general CANopen port from the Motion/EtherCAT interface. Match the drive suffix, operating mode and axis assignment. Use low-speed JOG only with a clear movement area and a working stop arrangement. Do not disable limit or safety inputs merely to hide an alarm.

For intermittent communication, inspect cable shielding, terminals, end termination and routing near motor cables. Check for built-in termination before adding resistance. Changing software versions alone may overlook a physical fault behind bus-off or slave-offline errors.

Open old projects in a copy before saving with a newer editor. Compare controller selection and network devices before transfer. Download writes from the PC to the device; do not overwrite the running program while intending to make a backup. Retain the last working project separately.

Related topics

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

Delta PMSoft · Delta DCISoft · Delta DeviceNet Builder · Delta device description files

Delta EDS device description files · Delta DVP PLC series · Delta AS PLC series · Delta AH PLC series

Delta DVP-MC · Delta DVP10MC11T · Delta DVP15MC11T · Delta DVP50MC11T

Delta AS500 motion controllers · Delta AS524C-B · Delta AS516E-B · Delta DVPCOPM-SL

Delta AH10COPM-5A · Delta AS-FCOPM · Delta AS00SCM-A · Delta IFD6503

Delta Plc Cables

External references

Delta official download centre · Delta Turkey software announcement · DVP10MC versus DVPCOPM-SL

Delta Turkey EDS installation guidance · Historical V2.02 manufacturer announcement