Skip to content

INVT GD200A & GD350 Modbus RTU: P14 Setup & Register Map

INVT GD200A & GD350 Modbus RTU: P14 Setup & Register Map

Modbus RTU on INVT GD200A & GD350: Essentials First

To establish reliable RS-485 communication between an INVT Goodrive200A or Goodrive350 variable frequency drive and a PLC, HMI, or PC, complete three steps: wire a shielded twisted pair to terminals 485+ / 485- (grounding the shield to PE at one end only), match bus settings in group P14 (watch out: INVT factory defaults are 19200 bps, Even, 8-E-1, not 9600 8-N-1!), and switch control channels to Modbus via P00.01 = 2, P00.02 = 0, and P00.06 = 8. When a PLC writes function-code parameters cyclically, always set the address MSB to 1 (0x8xxx instead of 0x0xxx) so writes target on-chip RAM instead of wearing out EEPROM.

Engineer Quick Checklist: 1) Wiring: 485+ → A(+), 485- → B(-); enable the 120 Ω terminator on the last drive in the daisy chain via jumper J5 on GD200A (p. 30–31) or DIP switch SW3 on GD350 (p. 46). 2) Control channels: P00.01 = 2 (comm run/stop), P00.02 = 0 (Modbus), P00.06 = 8 (Modbus frequency). 3) Factory bus defaults: P14.00 = 1, P14.01 = 4 (19200 bps), P14.02 = 1 (RTU E,8,1), P14.03 = 5 ms, P14.04 = 0.0 s (set 3.0–5.0 s for disconnect detection). 4) Key registers: 2000H = control command (0001H FWD, 0005H stop), 2001H = frequency in 0.01 Hz steps (40.00 Hz = 0FA0H, 50.00 Hz = 1388H), 2100H = status word 1, 3000H = running output frequency.

1. RS-485 Wiring, Shield Grounding & 120 Ω Termination

Both the general-purpose INVT GD200A-1R5G-4 / GD200A-2R2G-4 series and the high-performance vector INVT GD350-004G-4 / GD350-011G-4 / GD350-015G-4 series include a built-in half-duplex RS-485 port as standard — no option card is needed for Modbus RTU. For power and I/O wiring basics see our INVT VFD setup and wiring guide, and for protocol fundamentals see Modbus RTU & TCP for PLCs.

RS-485 Bus Wiring Rules

  • Polarity: wire the differential pair straight through — 485+ (A) → 485+ (A) and 485- (B) → 485- (B) (GD200A p. 31; GD350 p. 382–383). If the master receives no reply or garbled bytes, check A/B polarity first.
  • Cable & single-ended shield: use shielded twisted-pair cable (0.5–0.75 mm²). As stressed in INVT's official setup video, ground the cable shield to PE at one end only to avoid ground loops that inject noise onto the bus.
  • Signal reference on GD350: the GD350 control block adds a dedicated 485G terminal next to 485+/485- (p. 47), and the EMI troubleshooting section (GD350 p. 373) recommends tying the drive's signal ground GND/485G to the host controller's reference ground to suppress common-mode voltage.
  • Daisy-chain topology & 120 Ω terminator: wire multiple drives in a linear daisy chain without long star stubs. Enable the built-in 120 Ω terminating resistor on the last physical drive: jumper J5 on GD200A (p. 30–31, 135) or DIP switch SW3 on GD350 (p. 46, 383).
  • Maximum bus distance (GD350 p. 383): 1800 m at 2400 bps, 1200 m at 4800 bps, 800 m at 9600 bps, and 600 m at 19200 bps. Keep RS-485 runs at least 20–30 cm away from motor power cables and cross at 90° angles.

2. GD200A vs GD350 on Modbus RTU: Exact Matches & Differences

Core Modbus RTU control (run/stop, frequency setpoint, monitoring registers, and P14.00–P14.05) is nearly identical across GD200A and GD350, so the same PLC logic works on both drives. However, six hardware and firmware differences matter during panel design or drive replacement (see also INVT GD200A vs Veichi AC310).

FeatureINVT GD200A (EN manual, 182 pp.)INVT GD350 (EN manual)
RS-485 terminals & 120 Ω terminator485+, 485-, PE; jumper J5 (p. 30–31, 135)485+, 485-, 485G, PE; DIP switch SW3 (p. 46–47, 383)
Modbus framing in P14.02RTU (0–5) & ASCII (6–17); default 1: E,8,1 RTU (p. 99–100)RTU only (0–5), no ASCII mode; default 1: E,8,1 RTU (p. 246–247)
Comm. channels P00.020: MODBUS, 1–3: Reserved (p. 42)0: Modbus/Modbus TCP, 1–6: PROFIBUS/CANopen/Ethernet/EtherCAT/PROFINET/wireless card (p. 162)
Custom register mapping P14.06–P14.08P14.06 hundreds: 0=GD200A, 1=custom, 2=CHF100A; defaults P14.07=0x1000, P14.08=0x2000 (p. 101)P14.06 hundreds: 0=off, 1=on; defaults P14.07=0x2000, P14.08=0x2001; adds P14.09 (Modbus TCP timeout), P14.10 (RS-485 upgrade), and PZD mapping P14.48–P14.70 (p. 247–248)
Status word 1 (2100H)0001H–0005H (FWD, REV, Stop, Fault, POFF; p. 147 has a print typo for 0002H, actual meaning is REV)0001H–0006H — adds 0006H: Pre-exciting (p. 395)
Drive ID register 2103H0x0107 (p. 147)0x01A0 (high byte 01=GD, low byte A0=GD350; p. 397)

3. Required P00 & P14 Parameters (Manual-Verified)

Pay special attention to P14.01 and P14.02: unlike many drives that ship at 9600, 8-N-1, both INVT series default out of the box to 19200 bps, Even parity, 8 data bits, 1 stop bit.

ParameterNameDefault (Range)Recommended Modbus RTU SettingManual Ref
P00.01Run command channel0 (0–2)2 — Communication (LOCAL/REMOT LED stays solid ON)GD200A p. 41–42; GD350 p. 162
P00.02Communication channel selection0 (GD200A: 0–3; GD350: 0–7)0 — MODBUS (Modbus / Modbus TCP on GD350)GD200A p. 42; GD350 p. 162
P00.06A frequency command source0 (GD200A: 0–11; GD350: 0–16)8 — MODBUS communication (with P00.09 = 0)GD200A p. 44; GD350 p. 163
P14.00Local slave address1 (1–247)Unique ID per drive on the bus (1, 2, 3…; 0 is broadcast-only, no reply)GD200A p. 99; GD350 p. 246
P14.01Communication baud rate4 (0–7)0:1200, 1:2400, 2:4800, 3:9600, 4:19200 (default), 5:38400, 6:57600, 7:115200 bpsGD200A p. 99; GD350 p. 246
P14.02Data format & parity1 (GD200A: 0–17; GD350: 0–5)0: (N,8,1) RTU; 1: (E,8,1) RTU (default); 2: (O,8,1); 3: (N,8,2); 4: (E,8,2); 5: (O,8,2)GD200A p. 99–100; GD350 p. 246–247
P14.03Response delay5 ms (0–200 ms)5 ms suits most PLCs; raise to 10–20 ms for slow USB–RS485 convertersGD200A p. 100; GD350 p. 247
P14.04Communication timeout (CE)0.0 s (0.0–60.0 s)0.0 disables timeout; set 3.0–5.0 s (longer than PLC poll cycle) for bus watchdog protectionGD200A p. 100; GD350 p. 247
P14.05Transmission fault action0 (0–3)0 — alarm CE & coast to stop; 1 — no alarm, keep running; 2 — controlled stop without alarm (comm mode only); 3 — controlled stop in all modesGD200A p. 100; GD350 p. 247
P14.06Comm. processing action (3-digit hex)0x00 (0x000–0x211)Ones: 0 reply to writes, 1 silent writes; tens: 0/1 password P07.00; hundreds: 1 enable custom addresses P14.07/P14.08GD200A p. 100–101; GD350 p. 247–248
P14.07 / P14.08User-defined run / freq addressesGD200A: 0x1000/0x2000; GD350: 0x2000/0x2001Active when P14.06 hundreds = 1; lets INVT drop into legacy PLC register mapsGD200A p. 101; GD350 p. 248

Note on YouTube walkthroughs: INVT's official GD350 CommTest video selects 9600 bps, Even, 8-1 on the PC, while the 3-drive GD200A Pro-face HMI tutorial uses 9600 bps, None, 8-1. If you follow either setup, remember to change P14.01 = 3 (9600 bps) and, if needed, P14.02 = 0 (N,8,1) on every drive — leaving factory P14.01 = 4, P14.02 = 1 will result in zero response.

4. First PC Bench Test (Commix / CommTest) & Ready Hex Frames

Before wiring into a PLC, verify the physical bus with a USB–RS485 adapter and Commix, CommTest, or Modbus Poll (GD350 manual p. 403–404):

  1. Open Windows Device Manager → Ports (COM & LPT) and confirm your adapter's virtual port (e.g., COM3).
  2. Configure the terminal for Modbus RTU (Input HEX), automatic CRC16 (Modbus RTU), and exact serial parameters matching P14.01 and P14.02 (default 19200, E, 8, 1).
  3. Set P00.01 = 2, P00.02 = 0, P00.06 = 8 on the VFD (P14.00 = 1) and read status word 2100H first.

Both series support Modbus RTU function codes 03H (Read Holding Registers), 06H (Write Single Register), 08H (Diagnostics loopback), and 10H (Write Multiple Registers; GD200A p. 140–154, GD350 p. 391–403). Verified hex frames for Slave ID 01H:

  • Read VFD status word 1 (2100H, FC 03H): 01 03 21 00 00 01 8E 36 → stopped drive replies 01 03 02 00 03 F8 45 (0003H = Stopped; GD350 p. 400).
  • Set frequency to 40.00 Hz in 2001H (FC 06H): 40.00 × 100 = 4000 = 0FA0H → 01 06 20 01 0F A0 + CRC (for 50.00 Hz = 5000 = 1388H: 01 06 20 01 13 88 + CRC).
  • Run forward (2000H = 0001H, FC 06H): 01 06 20 00 00 01 43 CA (for Slave ID 03H from GD350 p. 404: 03 06 20 00 00 01 42 28).
  • Controlled stop (2000H = 0005H, FC 06H): 01 06 20 00 00 05 42 09.
  • Simultaneous FWD start + 10.00 Hz in one frame (FC 10H, 2000H–2001H): 01 10 20 00 00 02 04 00 01 03 E8 3B 10 → reply 01 10 20 00 00 02 4A 08 (GD350 p. 401–403).
  • Read running output frequency (3000H, FC 03H): 01 03 30 00 00 01 8B 0A (returns 0FA0H at 40.00 Hz).

5. Complete Modbus RTU Register Map (2000H, 2100H, 3000H, 5000H)

On both GD200A (p. 146–148) and GD350 (p. 394–397), frequency reference 2001H and monitoring registers 3000H/3001H use direct engineering units of 0.01 Hz (scale factor 100). Note that one slide in INVT's official video mistakenly prints "0.1 Hz" for 2001H, yet the engineer immediately writes 0FA0H = 4000 for 40.00 Hz, confirming the manual specification of 0.01 Hz.

Hex AddressDec (0-based)FunctionAccessScaling / Bit Definitions
2000H8192Control command wordR/W0001H FWD run; 0002H REV run; 0003H FWD jog; 0004H REV jog; 0005H Stop; 0006H Coast to stop; 0007H Fault reset; 0008H Jog stop
2001H8193Modbus frequency setpointR/W0–Fmax, unit 0.01 Hz (10.00 Hz = 03E8H, 40.00 Hz = 0FA0H, 50.00 Hz = 1388H)
2002H / 2003H8194 / 8195PID reference / feedbackR/W0–1000 (1000 = 100.0%; requires Modbus selected in P09.00)
2004H8196Torque referenceR/W-3000–3000 (1000 = 100.0% rated motor current)
2100H8448VFD status word 1 (SW 1)R0001H FWD; 0002H REV; 0003H Stopped; 0004H Fault; 0005H POFF; 0006H Pre-exciting (GD350 only)
2101H8449VFD status word 2 (SW 2)RBitmask: Bit0 ready/DC bus; Bit1–2 motor select; Bit3 AM/SM; Bit4 overload pre-alarm; Bit5–6 active channel (00 keypad, 01 terminal, 10 comm)
2102H / 5000H8450 / 20480Active fault codeRInteger matching P07.27 (0 = no fault, 18 = CE, 1 = OUt1, etc.)
2103H8451VFD identification codeRGD200A = 0x0107 (p. 147); GD350 = 0x01A0 (p. 397)
3000H12288Running output frequencyR0–Fmax, unit 0.01 Hz
3001H12289Active set frequencyR0–Fmax, unit 0.01 Hz
3002H12290DC bus voltageRUnit 0.1 V (e.g., 5380 = 538.0 V; not output frequency!)
3003H / 3004H12291 / 12292Output voltage / Output currentR3003H = 0–1200 V (1 V); 3004H = current in 0.1 A
3005H / 3006H / 3007H12293–12295Speed / Power / TorqueR3005H = RPM (1 RPM); 3006H = power -300.0–300.0% (0.1%); 3007H = torque (GD350: 0.1%, -250.0–250.0%)

1-based 4xxxx HMI/PLC addressing tip (Pro-face, Delta, Siemens): convert the hex address to decimal and add 40001. Thus 2000H (8192) becomes 48193, 2001H (8193) becomes 48194, and 3000H (12288) becomes 52289 (or 6-digit 408193 / 412289). In a widely viewed Pro-face HMI tutorial for three GD200A drives, the presenter maps Output Frequency to 3002H by mistake — per the official GD200A manual (p. 147–148), 3002H is DC bus voltage, while actual running frequency lives at 3000H.

6. Critical RAM vs EEPROM Rule (0x8xxx vs 0x0xxx)

Every INVT function code maps directly to a 16-bit Modbus address: high byte = group number in hex, low byte = parameter index in hex (e.g., P05.06 → 0506H, P10.01 → 0A01H, P00.11 → 000BH). Here is a critical trap for engineers migrating from other brands: unlike Veichi AC310, normal 0x0xxx addresses on INVT write straight to EEPROM!

Both official manuals (GD200A p. 146; GD350 p. 394) warn that frequent EEPROM writes degrade memory lifespan. To write function codes to volatile on-chip RAM only:

  • Set the MSB (bit 15) to 1 — add 0x8000 to the parameter's hex address. Manual example: P00.07 is 0007H in EEPROM, so use 8007H for safe cyclic RAM writes (similarly, acceleration time P00.11: 000BH in EEPROM → 800BH in RAM).
  • Write-Only restriction: 0x8xxx addresses are valid only for writing. Reading 8007H with FC 03H returns exception 02H (illegal address) — always read from the base 0007H address.
  • Process registers 2000H–200EH: these always reside in RAM and are safe for continuous cyclic PLC updates.

7. Troubleshooting Fault CE (Code 18), EMI & Modbus Exceptions 01H–09H

Fault CE on the keypad (numeric fault code 18 in P07.27 and registers 2102H/5000H on both series — GD200A p. 79, 121; GD350 p. 210) indicates an RS-485 timeout: no valid frame arrived within P14.04. For all other drive faults see our INVT VFD error codes diagnostic guide. If communication drops only while the motor accelerates, suspect PWM cable coupling: verify single-ended shield grounding, add a ferrite core to the RS-485 cable (GD350 p. 372–373), or tie signal grounds 485G/GND together.

When the drive replies with the MSB set in the function code (83H for 03H, 86H for 06H), the next byte is the INVT exception code (GD200A p. 150–151; GD350 p. 398–400):

Exception CodeMeaningRoot Cause & Fix
01HIllegal commandUnsupported Modbus function (use 03H, 06H, 08H, 10H) or drive is in fault state
02HIllegal data addressNon-existent register, trying to read a write-only 0x8xxx RAM address, or accessing locked factory group (P29 on GD200A / P99 on GD350)
03HIllegal value / frame structureMalformed Modbus frame structure (byte-count mismatch)
04HOperation failedInvalid parameter value on write (e.g., writing 0003H to P00.01 whose range is 0–2, or duplicate digital input S assignments)
05HIncorrect passwordPassword sent does not match user password P07.00
06HData frame / CRC errorWrong frame length or CRC16 mismatch — inspect EMI, 485+/485- polarity, and P14.01/P14.02
07HWrite not allowed / Read-OnlyWriting to read-only registers (2100H, 3000H, group P17) or out-of-range value
08HCannot modify while runningParameter marked ◎ (e.g., P00.03 or P14.10) — stop the motor first
09HPassword protectedP07.00 ≠ 0 with bus lock enabled in P14.06 tens digit — unlock or clear P07.00 = 0

8. Field Observations & Common Commissioning Mistakes

Across multi-drive panel builds (including the 3× GD200A + Pro-face HMI bench test reviewed above), four practical snags account for most commissioning delays:

  1. Forgetting the 19200 E-8-1 default: engineers configure the PLC for 9600 N-8-1 and spend half an hour checking wiring while the drive waits on 19200 E-8-1 (P14.01 = 4, P14.02 = 1).
  2. Tight P14.04 watchdog on multi-slave buses: when an HMI polls 5–10 drives sequentially, inter-frame gaps per drive easily exceed 1–2 s. Set P14.04 to at least 3× the real poll cycle.
  3. Unshielded wire inside crowded panels: short runs under 10 m often work without the 120 Ω terminator, but unshielded wire routed near contactors triggers intermittent 06H CRC exceptions.
  4. Hardwired emergency stop: even with P00.01 = 2, always wire a physical E-stop to GD350 STO inputs (H1/H2, p. 47) or an external fault EF digital input so the motor stops if the PLC freezes.

9. Sources & Verification

Every P00/P14 parameter, register address, 0x8xxx RAM rule, fault CE code (18), and exception code (01H–09H) was verified directly against the original English GD200A and GD350 manuals.

Sourcing INVT Drives & Industrial Automation Accessories

In our catalog (in stock and to order), you will find INVT variable frequency drives from the GD200A and GD350 lines — including GD200A-1R5G-4 (1.5 kW), GD200A-2R2G-4 (2.2 kW), GD350-004G-4 (4 kW), GD350-011G-4 (11 kW), and GD350-015G-4 (15 kW) — along with communication cards, reactors, and panel accessories. Contact chastotnik.ua engineers if you need help integrating GD200A/GD350 into a Modbus RTU network or matching a legacy PLC register map.

⚡

Need a variable frequency drive for your motor?

We'll find the right solution by power, voltage and load type

Browse catalog Consultation

Поширені запитання

Both series ship with slave address P14.00 = 1, baud rate P14.01 = 4 (19200 bps), and data format P14.02 = 1 (Modbus RTU, Even parity, 8 data bits, 1 stop bit — E,8,1). If your PLC uses 9600 8-N-1, change P14.01 = 3 and P14.02 = 0.