Veichi AC310 Modbus RTU Setup: Key Essentials First
To establish reliable Modbus RTU communication between a Veichi AC310 VFD and a PLC, HMI, or PC, complete three steps: wire the A+ / B- pair (or RJ45 pins 7 and 8), match serial settings in group F12 (factory default 9600 bps, 8-N-1, slave ID 1), and switch control channels to the bus — F01.01 = 2 (run/stop) and F01.02 = 6 (frequency reference). For cyclic PLC writes, always target RAM addresses (leading nibble 0, e.g. 0x3000 / 0x0109) rather than EEPROM (0x1xxx) to prevent premature flash wear.
Quick engineer checklist: 1) RS-485 block: A+ → T/R+, B- → T/R- (RJ45 port: pin 8 brown → T/R+, pin 7 white-brown → T/R-). 2) For the RS-485 block set F01.01 = 2, F01.02 = 6, and F12.00–F12.07; for the RJ45 port set F12.20 = 1, F12.21–F12.27, and option-card channels F01.01 = 3, F01.02 = 10. 3) Main control registers: 0x3000 (frequency, 0.01 Hz step, 50 Hz =0x1388) and 0x3001 (0x0001FWD run,0x0005DEC stop). 4) Enable disconnect protection via F12.06 and F12.07 = 1 (fault E.CE).
1. Two Physical Interfaces: RS-485 Terminals vs RJ45 Port
Every Veichi AC310 drive (such as AC310-T3-2R2G-B and the rest of the Veichi VFD range) includes RS-485 hardware as standard — no option card is needed for Modbus RTU. VEICHI Tech Academy demonstrates two wiring options.
Option 1: Control Terminal Block (A+ / B-)
Locate the A+ and B- terminals on the AC310 control board and wire a shielded twisted pair straight to your USB-to-RS485 converter, Veichi PLC, or HMI panel: T/R+ → A+, T/R- → B-. Wire multi-drive networks in a daisy chain, avoiding star topologies.
Option 2: RJ45 Port Using a Standard Patch Cable
The onboard RJ45 port defaults to external dual-line keypad communication (F12.20 = 0), but can be switched to Modbus RTU. The official VEICHI Tech Academy RJ45 guide shows the exact Ethernet cable pinout for RS-485 adapters:
- Pin 8 (brown) → T/R+ (A+)
- Pin 7 (white-brown) → T/R- (B-)
Critical note from the v1.6 manual (p. 173–174, 354): first, the RJ45 port uses its own independent group F12.20–F12.27 — set F12.20 = 1 for Modbus Slave mode (the RJ45 video's closing slide mistakenly repeats F12.01–F12.03). Second, when Modbus runs over RJ45, the drive routes run/frequency channels as an option card, so you must set F01.01 = 3 (not 2) and F01.02 = 10 (not 6) — otherwise commands are ignored. Third, T3 45 kW and larger models only support an external dual-line keypad on RJ45 (Modbus over RJ45 is not supported). Practical panel tip: if you need a door-mounted keypad, wire Modbus to A+/B- instead.
Option 3: 4G-IoT Expansion Module
For remote cloud monitoring and mobile start/stop, the Veichi 4G-IoT card wires to A+, B-, 24V, and COM (or plugs into expansion Port A) with F01.01 = 2.
2. Mandatory AC310 Parameters for Modbus RTU (F01 and F12)
For general motor commissioning see our Veichi AC310 setup guide and Modbus RTU/TCP PLC primer. Below is the verified AC310 v1.6 communication table.
| Parameter | Function | Default (Range) | Modbus RTU Setting | EN Manual Ref |
|---|---|---|---|---|
| F01.01 | Run command channel | 0 (0~3) | 2 — RS-485 A+/B- terminals; 3 — option card / RJ45 in Modbus mode (p. 354) | p. 119, 354 |
| F01.02 | Frequency source channel A | 0 (0~11) | 6 — RS-485 A+/B- terminals; 10 — option card / RJ45 in Modbus mode | p. 120, 221 |
| F12.00 | Master / Slave selection (RS-485) | 0 (0~1) | 0 — Slave (for PLC/PC master); 1 — Master | p. 171 |
| F12.01 | Modbus station address | 1 (1~247) | Unique node ID per VFD on the bus (1, 2, 3…) | p. 171 |
| F12.02 | Baud rate selection | 3 (0~6) | 0:1200, 1:2400, 2:4800, 3:9600, 4:19200, 5:38400, 6:57600 bps | p. 171 |
| F12.03 | Data format | 0 (0~5) | 0: (N,8,1), 1: (E,8,1), 2: (O,8,1), 3: (N,8,2), 4: (E,8,2), 5: (O,8,2) | p. 171 |
| F12.04 | Write response mode | 0 (0~1) | 0 — write with response (standard Modbus); 1 — no response | p. 171 |
| F12.05 | Response delay | 0 ms (0~5000) | 0–5 ms (raise to 10–20 ms for slow USB converters) | p. 172 |
| F12.06 | Timeout fault time | 1.0 s (0.1~100.0) | 3.0–5.0 s (longer than PLC poll cycle) | p. 172 |
| F12.07 | Disconnection action (E.CE) | 0 (0~3) | 0=ignore; 1=alarm E.CE & free stop; 2=warning & keep running; 3=forced stop | p. 172 |
| F12.20 – F12.27 | RJ45 port Modbus parameters | F12.20 = 0 | F12.20 = 1 (Modbus Slave), F12.21 addr, F12.22 baud (0–5), F12.23 format, F12.26–F12.27 timeout | p. 173–174 |
Retrofit bonus: F12.11 – F12.16 (p. 172–173) let you remap custom PLC register addresses for frequency, FWD, REV, STOP, and RESET so you can drop an AC310 into an existing machine without rewriting PLC logic.
3. First Bench Test via VEICHI Debugger and Raw Hex Frame
Before wiring to a PLC, verify the link quickly using VEICHI Debugger (or Modbus Poll) and a USB-to-RS485 dongle (e.g. Silicon Labs CP210x):
- Check Windows Device Manager → Ports (COM & LPT) to verify the USB-to-UART driver and note the assigned COM port (e.g.
COM5). - Create a project in VEICHI Debugger: Project → New → VFD → AC310, select RS485, your COM port,
9600,8-N-1, address1. - Open Parameter settings → Read all pages. Monitoring groups C00–C07 (
0x2100–0x2800) are strictly read-only. - Test a raw write in Command window (as shown by VEICHI Tech Academy): write 50.00 Hz to
F01.09(hex address0x0109) on Slave01. With 0.01 Hz resolution, 5000 decimal = 0x1388 hex. Function06(Write Single Register) frame:01 06 01 09 13 88(CRC16 appended automatically). Use function03to read registers.
4. Core Modbus RTU Register Map for PLC and SCADA
Use the dedicated communication block 0x3000–0x3003 (or mirrored 0x2000–0x2003) plus monitoring group 0x2100+ (EN manual v1.6, p. 65–66):
| Hex Address | Name | Access | Scaling / Bit Values |
|---|---|---|---|
| 0x3000 (or 0x2000) | Communication frequency reference | R/W | 0.01 Hz step (0.00–320.00 Hz): 25.00 Hz = 0x09C4, 50.00 Hz = 0x1388 |
| 0x3001 (or 0x2001) | Control command word | R/W | 0x0001=FWD run; 0x0002=REV run; 0x0003/0x0004=FWD/REV jog; 0x0005=DEC stop; 0x0006=Free stop; 0x0007=Reset; 0x0008=Run prohibit; 0x0009=Run permit |
| 0x3002 (or 0x2002) | Drive status word | R | Bitmask: Bit0=Run, Bit1=ACC, Bit2=DEC, Bit3=Reverse, Bit4=Fault, Bit5=Locked, Bit6=Warning, Bit7=Ready |
| 0x3003 (or 0x2003) | Active fault code | R | Integer 0–127 (0=no fault; 34=E.CE) |
| 0x2100 / 0x2101 (C00.00 / C00.01) | Given / Output frequency (monitoring) | R | 0.01 Hz step: 0x2100 (C00.00) = given frequency, 0x2101 (C00.01) = actual output frequency (p. 196); C00 continues at 0x2102 (C00.02 current), 0x210B (C00.11 DC bus) |
Ready-to-use command frames (Slave ID = 1, excluding CRC16):
- Set 50.00 Hz reference:
01 06 30 00 13 88 - Start Forward (FWD):
01 06 30 01 00 01 - Deceleration Stop:
01 06 30 01 00 05 - Fault Reset:
01 06 30 01 00 07 - Read Status Word:
01 03 30 02 00 01
5. Preventing EEPROM Wear During Cyclic PLC Writes
The AC310 manual (p. 65) highlights a rule rarely mentioned in short video demos: EEPROM write cycles are finite. Cyclic PLC polling that writes directly to EEPROM will wear out memory over time.
When sending function 06H to a function-code address, the most significant hex digit (nibble) controls storage:
- Leading 0 (e.g.
0x000Efor F00.14 or0x0109for F01.09) — writes to RAM only (safe for continuous PLC updates; cleared on power-off). - Leading 1 (e.g.
0x100Efor F00.14) — writes to EEPROM (retained across power cycles; use only for one-off configuration changes).
6. Troubleshooting E.CE Fault and Modbus Exception Codes
Fault E.CE (code 34) triggers when silence on the bus exceeds F12.06 (or F12.26 for RJ45) with disconnect trip enabled in F12.07. Inspect cable continuity, A+/B- polarity, bus termination on long runs, and PLC poll intervals.
If the drive replies with a Modbus exception frame (function + 0x80), check the official AC310 exception table (v1.6 manual, p. 67–68):
| Exception Code | Meaning | Typical Cause & Fix |
|---|---|---|
| 01 | Incorrect command code | Unsupported Modbus function; AC310 supports 03H (read), 06H (write single), 08H (loop self-test), and 10H (write multiple registers, p. 60) |
| 03 | CRC error | Line noise, swapped A+/B-, or baud/format mismatch in F12.02/F12.03 |
| 04 | Illegal address | Non-existent register or wrong hex parameter address |
| 05 | Illegal data | Malformed frame or write attempt to read-only C00–C07 registers |
| 06 | Parameter cannot change during run | STOP-only parameter — stop the drive before writing |
| 08 | Drive busy (storing to EEPROM) | Too-frequent 0x1xxx writes — switch to RAM addresses 0x0xxx or 0x3000 |
| 09 | Value exceeds limit | Target exceeds min/max parameter bounds (e.g. frequency above F01.10) |
If the drive refuses to start after writing 0x0008 to 0x3001, Run Prohibition is latched (p. 66). Write 0x0009 to 0x3001 or cycle power to re-enable operation.
7. Sources and Verification
- Official manufacturer manuals: Veichi AC310 User Manual v1.6 (EN, 399 pp.) and Ukrainian AC310 full manual.
- Official VEICHI Tech Academy videos (YouTube): RS485 Application Communication for AC310 AC Drive; RJ45 Application for AC310 AC Drive; IOT Expansion Application for AC310 AC Drive.
All register addresses, F01/F12 parameters, and exception codes were verified directly against the official Veichi AC310 v1.6 manual.
Building Your Automation Panel Around Veichi AC310
Our catalog offers Veichi AC310 VFDs (in stock and to order) from 0.75 kW upward, along with matching Veichi PLCs, HMI panels, and VFD accessories. Contact our engineers if you need multi-drive Modbus sizing or custom register remapping for a drop-in retrofit.