How-to
Setting Up DOPSoft Modbus RTU for an HMI to Drive Link
Short answer
Select Modbus as the manufacturer in DOPSoft, choose RTU Hex Address Master (ASCII Hex Address Master only on a drive set to ASCII), copy the drive's serial parameters into the COM port — the factory frame is 9600, 8/Even/1 in RTU at station 1 — and prove the link with one read at a hex address such as 2000 (= 8192 decimal).
On this page
- Which Modbus driver do I select in DOPSoft for the drive?
- Should the link run in Modbus RTU or ASCII?
- Which COM-port fields have to match the drive?
- How do I set the COM port up step by step?
- How do I enter the drive's addresses in a Hex Address driver?
- How do I test the link before building the rest of the screens?
- Why does the read fail when every field matches?
- Questions asked
You make this link in DOPSoft by choosing Modbus as the manufacturer, picking the serial master driver that matches the drive's mode and address notation, and then copying the drive's serial parameters into the COM port one field at a time. For a Delta DOP-series panel such as a DOP107EV reading a GMT Micno inverter over RS-485, the usual destination is RTU Hex Address Master at 9600 baud, 8 data bits, Even parity, 1 stop bit, station 1 — which is exactly the driver's factory setting, so most of the job is confirming the drive side and proving one read.
Which Modbus driver do I select in DOPSoft for the drive? #
Select Modbus as the manufacturer in the HMI communication settings, then choose the serial master driver that matches the drive's mode and address notation: RTU Hex Address Master for Modbus RTU, ASCII Hex Address Master for Modbus ASCII.
In this link the panel is the master and the drive is the slave — the panel starts every poll and every write, the same arrangement as connecting an HMI directly to a VFD over Modbus RTU. The manufacturer entry fixes the protocol family; the driver name then carries two separate decisions at once. The leading word, RTU or ASCII, is the serial mode. "Hex Address" is the second decision: it tells DOPSoft to read every number you type into an object as hexadecimal. Both are settled at selection time, because a screen full of addresses entered in one notation cannot be repaired later by changing serial parameters.
Should the link run in Modbus RTU or ASCII? #
Run RTU — RTU Hex Address Master on the 9600 baud, 8 data bit, Even parity, 1 stop bit factory frame — unless the drive's mode parameter is explicitly set to ASCII, because RTU carries one byte per character where ASCII spends two.
That frame is the DOPSoft factory setting for the Modbus serial drivers; the ASCII counterpart drops to 7 data bits at the same 9600, Even, 1, and both default to controller station 1. ASCII mode renders every byte as two hexadecimal characters on the wire and checks the frame with an LRC byte, while RTU sends raw 8-bit characters behind a CRC — faster at the same baud rate, and the mode drives ship and commission in. Read the drive's mode parameter once, commit to it, and never flip between RTU and ASCII afterward to chase an address-entry problem: a wrong address fails in both modes, and switching adds a second unknown to the fault.
Which COM-port fields have to match the drive? #
All of them — baud rate, data bits, parity, stop bits and the station number; a Modbus serial link has no auto-negotiation, so one wrong field yields timeouts rather than degraded data.
- Baud rate — 9600 at the factory setting; enter whatever the drive uses on both ends.
- Data bits — 8 in RTU, 7 in ASCII; the mode decides this, not preference.
- Parity — Even at the factory setting; if the drive is set to no parity, RTU framing requires 2 stop bits.
- Stop bits — 1 alongside parity.
- Station number — the drive's address, 1 by default; Delta's serial Modbus documentation accepts stations K1–K254 while standard Modbus defines valid slaves as 1–247, so stay inside 1–247.
The same pair will carry more slaves later, each on its own station number, with the same trade-offs you meet when choosing the RS-485 protocol for one HMI and multiple PLCs. And when a poll fails on this bus, the settings rather than the copper are almost always the limit — the same conclusion behind RS-485 protocol being the limit rather than the cabling on other controllers.
How do I set the COM port up step by step? #
Match the HMI COM port to the drive in one pass — manufacturer, driver, port, the four serial fields, and the station number, in that order — then download and test with a single read before building any more screens.
- Open the HMI communication settings in DOPSoft and set the manufacturer to Modbus.
- Select RTU Hex Address Master, or ASCII Hex Address Master only on a drive confirmed to ASCII mode.
- Choose the COM port whose terminals are wired to the RS-485 bus.
- Enter the baud rate, data bits, parity and stop bits exactly as the drive's communication parameters read them.
- Enter the drive's station number as the controller station.
- Download the project to the panel.
- Put one read object on a screen at a known address and watch it before adding anything else.
How do I enter the drive's addresses in a Hex Address driver? #
Enter the addresses exactly as the drive manual prints them: an address printed 2000 is typed 2000 in a Hex Address driver, and it equals 8192 in decimal, because 2 × 4096 + 0 × 256 + 0 × 16 + 0 × 1 = 8192.
Suppose the drive's map lists the output-frequency register at hex address 2000 and a monitoring block at 1000. In DOPSoft you type 2000 and 1000 into the read objects, and the driver interprets them as hexadecimal because of its name. Cross-check against a decimal source such as a Modbus scanner: 2 × 4096 = 8192 and 1 × 4096 = 4096, so the same registers appear there as 8192 and 4096. Delta's serial Modbus documentation places register blocks at exactly 1000H and 2000H, which is why those two conversions cover most of what you will type. The trap runs one way only: a decimal 8192 typed into the hex driver addresses 8192 hexadecimal, a different register entirely.
How do I test the link before building the rest of the screens? #
Download the project and put a single read object on a known, harmless address — a drive status or output-frequency register — and treat one stable value that tracks the drive's own display as proof that port, mode, frame, station and notation all agree.
Reads are harmless, so start there and compare the value against the drive's keypad display. The first write is not: a button aimed at the run-command register will start the motor, so isolate the machine or inhibit the drive's output before you test writes. If the value never lands, run the comparison in the next section with the same field-by-field discipline as fixing an HMI PLC communication timeout over serial.
Why does the read fail when every field matches? #
If every serial field matches and the read still fails, the cause is almost always one of three: the mode is not what you think (RTU against ASCII), the notation is not what you think (hex against decimal), or the station targets the wrong device.
Work the suspects in that order:
- Mode — confirm the drive's mode parameter actually says RTU and the selected driver says RTU. A mode mismatch times out on every address, not just some.
- Notation — the driver reads hex, so a decimal value from the manual typed straight in lands on a different register.
- Station — the poll must carry the drive's configured station number, not the panel's own.
- Frame — recheck all four serial fields against the drive, including the extra stop bit that no-parity framing requires.
- Wiring — last, swap the two RS-485 conductors at one end: A and B labels are not standardized between vendors, and a reversed pair reads nothing.
The first two bullets clear most of these faults. Commit to the mode, commit to the hex notation, set the HMI fields to the drive's numbers, and the link carries.
Questions asked
Can one DOPSoft COM port talk to more than one drive?
Yes. RS-485 is a multidrop bus, so several drives share the same conductor pair as long as each has a unique station number inside the 1 to 247 range and the HMI objects target the right station. Wire the pair as a daisy chain from node to node rather than starred home runs, and keep stub lengths short.
Do I need a PLC between the panel and the drive?
No. The HMI is the Modbus master, so it polls and writes the drive's registers directly over RS-485, the same way a Delta panel runs against a Mitsubishi E700 inverter with no PLC in the path. A PLC only enters the picture when the machine sequence needs one for reasons beyond the HMI link.
How can I tell whether the drive's address list is hexadecimal?
Addresses printed with an H suffix, such as 2000H, or containing the letters A to F are hexadecimal, and you enter them unchanged. A digits-only table is decimal unless its header says otherwise, so convert before typing: 8192 decimal is 2000 in hex, and 4096 decimal is 1000.
Can I leave the DOPSoft defaults of 9600 and station 1 in place?
Only if the drive also sits at 9600 baud, 8 data bits, Even parity, 1 stop bit and station 1 in RTU. The committed rule is the reverse: treat the commissioned drive as the reference and move the HMI fields to match it, because the drive's frame is usually already tied to the plant standard.