Delta TPEditor
Delta TPEditor: software for TP panels and supported drive keypads
Delta TPEditor is a Windows editor for creating, compiling and transferring screen projects for supported TP text/graphic panels and compatible VFD-C keypads. It configures text, numeric displays, alarms, keys and communication objects. Select the full device model within the TP panel family and distinguish the screen project from the PLC control program.
The latest record found in Delta’s official centre on 15 November 2026 is TPEditor V1.98.08. Its issue date is 13 February 2023, listed size 60.97 MB, and language field Multilingual. Official TPEditor V1.98.08 download opens Delta’s terms/verification flow. Obtain the installer from the manufacturer; the PDFs below are prepared for the AVM archive.
Supported hardware · USB and communications · VFD-C / KPC-CC01 · Versions and Windows · PDF manuals
Screen editing and PLC programming
TPEditor edits the screen project. Internal PLC logic in suitable TP04P and TP70P models is handled with the supported WPLSoft or ISPSoft tool. TP70P Quick Start, PDF 43 and 56 explains these transfer tasks separately. Editing a screen file does not automatically change the PLC ladder program.
Writing a bit from a key and processing that bit in PLC logic are separate operations. Match each panel object’s address, data type and access mode to the controller. An editor for a DOP or another HMI family is not interchangeable solely because it carries the same manufacturer’s name.
Supported models and hardware distinctions
The V1.98.08 device field lists TP02G-AS1, TP04G-AS2, TP04G-AL-C, TP04G-AL2, TP04G-BL-C, TP08G-BT2, TP04P Series, TP70P Series and VFD-C Keypad. Match the project target to the device label and firmware. Inclusion in an old manual, or omission from a current short metadata list, is insufficient for a compatibility decision across every software release.
TP04P: TP04P-16TP1R, TP04P-32TP1R, TP04P-22XA1R and TP04P-21EX1R must be distinguished by their actual I/O arrangement. The TP04P installation sheet describes a programming port shared by PLC and panel editing tools. A shared port does not make the two project types a single file.
TP70P: check digital/analogue I/O, PLC functions and communication features for TP70P-16TP1R, TP70P-32TP1R, TP70P-22XA1R and TP70P-21EX1R individually. Use the dedicated port sheet for TP70P-RM0. Identical screen size does not establish identical terminals or COM roles.
COM2 / COM3: the TP70P guide distinguishes PLC communication from panel communication for the standard 16TP1R/32TP1R/22XA1R/21EX1R models, and separately describes RM0’s panel-side RS-232/RS-485 ports. Delta’s TP04P example also distinguishes the COM2 PLC and COM3 panel sides. Do not transfer a port number to another model without checking its manual.
USB drivers, cables and two communication paths
PC ↔ TP transfers the screen project between computer and panel. TP ↔ PLC carries field data between panel and PLC or drive. TP70P guide, PDF 40 presents these settings separately. A working PC USB connection does not prove that field communication uses the correct protocol.
For a supported TP with a built-in USB interface, use the official TP USB Driver record, dated 24 August 2015 / 958 KB. Match the port shown in Device Manager to PC COM Port in TPEditor. TP70P PDF 55–56 explains the driver and COM selection.
A USB/serial converter such as UC-PRG020-12A has its own driver; it is a different package from TP USB Driver. Select the programming cable by electrical interface, device port, pinout and supported protocol. A physically fitting connector does not establish RS-232/RS-485 or protocol compatibility.
Match the field-side device driver, station number, baud rate, parity, data bits and stop bits. With Modbus, also verify ASCII/RTU, address area and supported functions. COMMGR is not a universal prerequisite for every TPEditor connection; follow the manual for the actual panel and connection path.
Project setup, transfer direction and backups
Select the device type, panel model and communication driver in the new project. Check each object’s Refer Device, bit/word address, signed/unsigned format, decimal display and data length. Match word order for 32-bit values when applicable. The displayed numeric format and raw device data are different settings.
Write to TP transfers a PC project to the device. Read from TP reads a supported TP target back to the computer. Write Boot Page to TP and Write Menu to TP have separate purposes. The TPEditor user manual and Delta Boot Page explanation describe target-specific procedures; do not apply an old TP model’s setup keys universally.
Keep the original TPEditor project, software version, panel model/firmware, communication settings and any separate PLC project together. Device upload is not supported by every target and should not be assumed to recover every source editing detail. Open an old project in a separate copy before saving it with a different software version.
Firmware updates and factory resets should follow device identification and a recoverable backup. They are not the first response to a communication fault. Successful compilation does not validate field addresses, physical I/O or machine behaviour.
VFD-C Keypad and KPC-CC01 applications
TPEditor can create custom screens for supported drive/keypad combinations. The ME300 KPC-CC01 section, PDF 117 selects Set Device Type: DELTA VFD-C Inverter and TP Type: VFD-C KeyPad. These menu names do not establish compatibility with every Delta drive or keypad.
Read from TP is unsupported for KPC-CC01. PDF 130 / section 7-13-5 also documents restrictions on Local Page Setting, Global Setting and RTC Refer Device. Preserve the original source project; do not assume an editable screen backup can be uploaded from the keypad. Its drive-parameter copy function is separate from a TPEditor source-project backup.
In the documented example, select PC Link on the keypad, enter its waiting state and use Write to TP in TPEditor. The C2000/CP2000 application note, PDF 18–21 presents the optional KPC-CC01 display separately from Modbus master/slave and built-in PLC settings. Select IFD6530 and wiring pinouts for the relevant topology; an RJ45 connector alone does not mean Ethernet.
A connection is present but data is missing
Check the actual port and device driver first, then station and serial settings. Use a single known address with a read-only object to locate the failed communication path. A write object also requires a writable address and controller logic that accepts the command.
Some TP applications communicate according to objects on the active page. Delta’s TP04P–RTU485 example explains the effects of page, address coverage and supported Modbus functions. Its function list should not be generalised to every TP model. Compare timeout errors against the real device register map instead of shifting addresses arbitrarily.
Versions, the update file and Windows
Manufacturer sources document the version names V1.10, V1.30, V1.40.1, V1.60, V1.85, V1.88, V1.89, V1.98.06, V1.98.07 and V1.98.08. Historical distributor/build candidates and their evidence status are listed in the separate research file. This does not claim to recover every intermediate build, language package or installer.
V1.98.07: official previous record, 13 August 2021 / 59.5 MB; V1.98.06: official record, 14 May 2021 / 59.5 MB. The repeated V1.98.07 entries under HMI and drive categories are not counted as three versions. Installer byte identity was not established because the packages were not downloaded.
V1.60 update file is not a standalone installer. The 30 May 2014 / 3 MB patch record requires TPEditor V1.60 already installed and lists TP04G-BL-C V2.00 and later. V2.00 refers to the device version; it is not evidence of a TPEditor V2.00 release.
The V1.98.08 operating-system field reads Windows® XP/Vista/7(32-bit/64-bit)/8/10(64-bit). This wording does not separately clarify Windows 8 bitness, and Windows 11 is not explicitly listed. Multilingual does not prove a Turkish interface. Check the older TP USB driver’s OS list separately; a working editor does not prove driver compatibility.
PDF manuals and actual editions
The following seven manufacturer PDFs retain their original file contents. The general TPEditor manual is the 2016 edition and TP70P Quick Start is the 2020 edition. A newer central hardware record does not change the edition of an archived copy. The TP70P-RM0 sheet includes Turkish; the other documents’ actual languages are identified separately.
TPEditor user manual — 2016-05-03 — 164 pages; English. Projects, objects, PC–TP connections, screen/Boot Page transfers, firmware and USB drivers. 164 pages. PDF 10 scopes its features to V1.88 or later; this is not a new V1.98.08-specific manual.
TPEditor legacy user manual — 2008 archive — 100 pages; English. Legacy interface, communication and examples; 100 pages. Begins with the contents and ends on printed page 3-8. V1.10 in the source filename does not verify an installer build or its bytes.
TP70P quick start: TPEditor and the PLC project — 73 pages; English. 73 pages. PDF 27: example prerequisites TPEditor V1.85+ and WPLSoft V2.36+; PDF 40: PC↔TP versus TP↔PLC; PDF 43: PLC program; PDF 55–56: USB/COM. Not presented as the central 2022 edition.
TP04P installation sheet — 2013-01-07 — 20 pages; Multilingual. 20 pages; English and Chinese sections, no Turkish section. Shows the shared programming port, WPLSoft/TPEditor roles and hardware connections. The source filename’s 20130319 is not used as the publication date.
TP70P-RM0 installation and port sheet — Turkish section — 2 pages; Multilingual. 2 pages; English, Turkish and Chinese sections, plus a French warning. RM0-specific mounting, ports and pinout reference; does not establish identical I/O/COM layouts across TP70P models.
ME300 user manual: KPC-CC01 and TPEditor section — 457 pages; English. Full original 457-page ME300 manual, not a general TPEditor manual. Section 7-13; PDF 117: V1.60+ and VFD-C KeyPad target; PDF 124: PC Link; PDF 130: Read from TP and other unsupported functions.
C2000/CP2000 Modbus and TPEditor application note — 23 pages; English. 23 pages. Manufacturer application note issued by Delta EMEA / DEN, Marcel Dorti. Built-in PLC Modbus master/slave and optional KPC-CC01 display; TPEditor example on PDF 18–21. Parameters/ports belong to that example topology.
Editor’s note
Record the complete panel label first. TP04G, TP04P and TP70P have different project, port and PLC arrangements. Match the target before transferring a file from another machine.
Collect the original screen and PLC projects while the machine is still operational. Keep communication settings with them. KPC-CC01 cannot provide a Read from TP source backup; preserve the original project file.
When USB is missing, check Device Manager before reinstalling the editor repeatedly. Establish whether the TP’s built-in USB driver or the converter cable’s driver is required, then select the actual COM number in TPEditor.
A working display with missing data requires checking the panel-to-controller path separately from PC-to-panel transfer. Start with a single known read address and verify port, station and data type in sequence.
For each new key, identify the bit or parameter it writes and how machine logic processes it. Verify interlocks, access conditions and physical behaviour before enabling normal operation.
Record firmware and keep a recoverable working project before an update. Preserve the last working copy and change one item at a time so that both diagnosis and rollback remain practical.
Related topics
Delta TP panels and remote I/O · Delta TP Text Panels · Delta TP04P · Delta TP04P-16TP1R
Delta TP04P-32TP1R · Delta TP04P-22XA1R · Delta TP04P-21EX1R · Delta TP70P
Delta TP70P-16TP1R · Delta TP70P-32TP1R · Delta TP70P-22XA1R · Delta TP70P-21EX1R
Delta TP70P-RM0 · Delta TP panel files · Delta PLC software · Delta WPLSoft
Delta ISPSoft · Delta Plc Cables
External references
Official Delta TPEditor download centre · Official TPEditor manual record · TP–PLC serial connection checks
Boot Page transfer · TP04P / RTU485 example · Delta EMEA C2000 application
Manufacturer V1.10 bulletin · Manufacturer V1.30 bulletin · Manufacturer V1.40.1 bulletin