Delta PMSoft
Delta PMSoft: software for DVP-PM and AH motion modules
Delta PMSoft provides programming, parameters, transfer and monitoring for supported DVP-PM motion controllers and AH PM/MC motion modules. The DVP-PM family has model-dependent ladder/instruction, motion-subroutine, G-code and E-CAM functions. Select capabilities against the full CPU/module code.
V2.12 is the latest official PMSoft central record checked on 15 November 2026. Its listed issue date is 18 September 2018, package size 121 MB, and language type multilingual. The official PMSoft V2.12 download follows Delta’s terms/verification flow. The manufacturer specifies using COMMGR for communication.
Hardware differences · COMMGR and connections · G-code and E-CAM · Versions and Windows · PDF manuals
PMSoft, ISPSoft and WPLSoft roles
WPLSoft serves the general DVP programming family, while ISPSoft supports applicable PLC CPUs. DVP-PM logic uses its model-specific PMSoft project structure. A general DVP ladder project is not directly equivalent to a PM project containing G-code. COMMGR manages the engineering communication channel.
AH integration: ISPSoft/HWCONFIG defines the motion module and rack/slot; PMSoft edits its PM/MC motion program. The ISPSoft manual, PDF 47 and 59–61 describes PMSoft V2.05-or-later .ppm projects for this workflow and explicitly excludes DVP-PM projects from that AH import process. Integration does not mean that every PM project can open on every CPU.
DVP and AH hardware differences
DVP10PM / DVP20PM: select DVP10PM00M, DVP20PM00D, DVP20PM00M and DVP20PM00DT by full code. Axis count, pulse terminals, normal digital output types and supported motion instructions differ. Preserve the D, M and DT suffixes when matching projects and hardware.
Do not generalize G-code/E-CAM support to DVP10PM. The historical comparison at PDF 559–560 separates its OX motion-subroutine, G-code and E-CAM capabilities from DVP20PM00D/00M. Single-axis positioning, interpolation and electronic camming are different functions. Use the actual model’s instruction table.
AH PM/MC: AH05PM-5A, AH10PM-5A and AH15PM-5A are pulse-train motion modules. AH20MC-5A is a DMCNET motion module. The AH hardware manual, PDF 28 lists these roles separately. Verify the drive’s pulse inputs or network support, cabling and firmware against the intended module.
Evaluate AHxxEMC separately. For EMC controllers such as AH08EMC-5A, select the ISPSoft project and AH Motion backplane arrangement against their own hardware. PMSoft support for AHxxPM/AHxxMC projects does not automatically extend to every CPU carrying an AH Motion name.
DVP-FPMC: the Ethernet/CANopen function card serves supported DVP-PM hardware. CANopen configuration, Ethernet project transfer and motion programming are different tasks. The device manual determines where CANopen Builder or PMSoft applies; the card name does not make it equivalent to a DVP10MC or AH20MC system.
COMMGR: direct and CPU-mediated connections
Direct connection: connect to the supported DVP-PM controller or the AH motion module’s own port. Create the correct COMMGR channel and set it to Start. In PMSoft, open Communication → Communication Setting, select the same driver and the appropriate Motion Controller option. The selected port/type must be supported by the model.
Indirect AH connection: the PC reaches an AH CPU, which accesses the motion module through the backplane. Match ISPSoft/HWCONFIG, the COMMGR channel and PMSoft rack/slot to the physical location. Reaching the CPU does not independently identify the intended motion module.
Read PM Information and compare model/firmware with the physical label. A mini-USB connector does not establish one universal driver selection; Delta’s AH connection explanation distinguishes CPU-mediated and direct module access. Verify existing IPs, COM numbers and station addresses rather than writing a manual’s example IP into a working installation.
For serial access, check the programming cable, electrical interface, pinout, baud rate, parity and ASCII/RTU together. The USB-converter driver, PC COM port and COMMGR channel are separate components. Confirm device identity and transfer direction before operating on its program.
Projects, model selection and backups
Select the correct PM Type/model when creating a project. Check model availability of ladder/instruction editors, POU, ST/CFC and motion functions. DVP-PM O100 main logic, supported OX motion subroutines and P subroutines have distinct roles; AH POU/task structures should follow their own model rules.
A backup includes more than one program file. Preserve the PMSoft project, symbols/comments, parameters, motion subroutines, G-code/cam data, associated ISPSoft system, HMI files and drive parameters. Do not assume a controller Upload reconstructs every comment or original source file. Preserve authorized access details for protected projects.
Check PC-file saving, controller Download and supported Flash/retentive-data operations separately. Consult the model manual for retained D areas, battery state and power-return behaviour. Keep a recoverable copy of the existing project/settings before writing to a working machine.
G-code, E-CAM and simulation
G-code: edit paths/programs for a supported PM model using its supported G/M commands. Match axis planes, absolute/relative positioning, units, speed and acceleration. Drawing/path tools do not establish compatibility with every CAD/CAM file or CNC postprocessor output.
E-CAM: evaluate the master position source, slave axis, scale, phase and cam curve together. Curve data must agree with program start/synchronization conditions. A curve from another machine may produce different motion with another encoder or mechanical ratio.
Simulation and physical checks: inspect path geometry in software; verify motor direction, electronic gearing, pulse/direction or CW/CCW format, home/limit signals and drive alarms on the machine. Begin permitted commissioning moves at low speed over short distances. Physical stop and limit functions must operate appropriately.
Communication works but motion does not
Check the selected CPU/module and operating state, then the motion command’s conditions. Servo ON, Ready/Alarm, limit, home and emergency states can affect execution. A completed download does not establish that the program has issued an executable axis command.
For pulse systems, verify pulse/sign signals using suitable measurement equipment and match the drive input format. For DMCNET/CANopen/Ethernet systems, verify the actual protocol, node/station settings and supported devices. Different networks and pulse wiring require different diagnostics.
Versions, historical records and Windows
Research tracked V1.03, V1.03.5, V2.0, V2.04, V2.05, V2.08, V2.10, V2.10.10, V2.11 and V2.12. Manufacturer bulletins/manuals and official security/download records provide different evidence types. V2.10.10 is a historical distributor reference whose installer bytes were not verified. This is not claimed to include every historical build or language package.
The previous official PMSoft V2.11 record lists 22 March 2018 / 120 MB. CVE-2018-14824 documents V2.11 and earlier as affected; the old link is retained for historical identification. V2.12 is the current central selection. Track the source/version of old project files; a particular fix record is not a guarantee against all possible issues.
The PMSoft V2.12 OS field lists Windows XP / Vista / 7 (32-bit/64-bit) / 8 (64-bit). Windows 10 and 11 are not explicitly confirmed by this record. Multilingual does not independently establish a Turkish interface. DPMSoft OS/version data must not be assigned to PMSoft: DPMSoft is separate power-meter software.
PDF manuals and edition scope
The following six manufacturer PDFs retain their actual editions. The PMSoft user-manual copy is dated 21 April 2014; the central manual record dated 31 October 2014 is linked separately. These files are not presented as new V2.12-specific manuals or the latest hardware references for every model. The DVP-20PM instruction sheet contains a Turkish section.
PMSoft user manual — 2014-04-21 edition — Projects, editors, COMMGR, direct/indirect links, parameters, G-code and E-CAM. PDF 16/47: V2.04-or-later scope; PDF 61–65: connections. Cover/revision history date this copy to April 2014; it is not claimed identical to the central October 2014 file or specific to V2.12. English; 2014-04-21; 2nd edition; 327 pages; 9.28 MB.
DVP-PM application/programming manual, Revision II — O100/OX/Pn structure, motion and G-code instructions, E-CAM, POU, FPMC and historical model comparisons. PDF 559–560 distinguishes DVP10PM motion-subroutine/G-code/E-CAM capabilities. This historical edition is not a complete current DVP20PM00DT reference. English; 2011-04-15; Revision II on cover; 561 pages; 20.46 MB.
DVP-20PM multilingual installation sheet — Turkish section — Electrical wiring, axis/signal terminals, battery and Flash information. Turkish section: PDF 17–20. Historical edition, distinct from the central installation record dated 2024-02-21. Multilingual; Turkish/English sections; 2012-09-28; 20 pages; 1.02 MB.
DVP-10PM multilingual installation and wiring sheet — DVP10PM wiring, pulse outputs, serial ports, battery and retention. Contains English and Chinese sections; not a Turkish manual or the current 2024 sheet. Multilingual; English/Chinese; 2010-09-28; Rev.01; 16 pages; 0.85 MB.
AH Motion hardware manual: PM/MC modules and EMC context — Module pinouts, wiring, pulse/DMCNET functions, backplanes and maintenance. PDF 28: PM/MC model roles. Inclusion of AHxxEMC hardware does not establish PMSoft programming support for those controllers. Historical hardware edition, not the 2024 Rev.03. English; 2016-07-15; Rev.01; 254 pages; 14.78 MB.
ISPSoft manual: integrating PMSoft into an AH project — Used here as an integration reference rather than a complete ISPSoft software archive. PDF 47, 59–61: PMSoft V2.05+ .ppm projects, rack/slot selection and exclusion of DVP-PM projects from that import workflow. Full original 801-page document preserved; not presented as the latest ISPSoft edition. English; Cover 2016-05-18; 3rd revision table 2016-05-13; 801 pages; 29.77 MB.
Editor’s note
Record the full label first. Do not assume 10PM, 20PM00D, 20PM00M and 20PM00DT have identical instructions or outputs. Match CPU, drive and axis wiring before reusing another machine’s project.
After connecting, identify the device in PM Information and back up its program/settings before downloading. When connecting through an AH CPU, verify rack/slot as well. The wrong slot may belong to another working axis group.
G-code and cam files form part of the operating motion system. Keep drive parameters, encoder/gearing details and HMI files in the same backup. Ladder logic alone may be insufficient to reconstruct the movement.
Verify direction, a short move and home/limit behaviour in sequence when commissioning an axis. An incorrect pulse scale can turn a small command into a large movement. Check physical limits as well as the displayed path.
If the servo does not move, inspect Ready/Alarm, Servo ON, limits and command conditions before erasing logic. Pulse wiring and DMCNET/CANopen need different diagnostics. Establish how far the signal or network data reaches.
Save the PC project, check required retentive data and record software/firmware versions. Investigate BAT.LOW indications according to the model’s memory arrangement. Preserve the last working copy and change one item at a time.
Related topics
Delta DVP-PM · Delta DVP10PM00M · Delta DVP20PM00D · Delta DVP20PM00M
Delta DVP20PM00DT · Delta AH05PM-5A · Delta AH10PM-5A · Delta AH15PM-5A
Delta AH20MC-5A · Delta DVP PLC series · Delta AH PLC series · Delta AH08EMC-5A
Delta AH Motion backplanes · Delta DVP-FPMC · Delta PLC software · Delta ISPSoft
Delta WPLSoft · Delta COMMGR · Delta CANopen Builder · Delta Plc Cables
External references
Official Delta PMSoft download centre · AH Motion connection explanation · Manufacturer PMSoft V2.0 / V1.03.5 bulletin
Delta EMEA V2.08 announcement · NVD CVE-2018-14824 version record