PLC Communication Control of Delta VFD-M Drive: Troubleshooting Jog Frequency Issues
When integrating a Delta VFD-M series variable frequency drive with a Siemens S7-200 SMART PLC via communication, a common issue arises: the drive runs at the programmed frequency on the first start, but subsequent starts default to jog frequency. This behavior can disrupt processes and lead to unexpected machine operation. Understanding the root cause and applying the correct solution is essential for reliable automation.
Understanding the Communication Setup
The Delta VFD-M supports Modbus RTU communication over RS-485, which is commonly used with PLCs like the S7-200 SMART. The PLC acts as the master, sending commands to set frequency, start/stop, and read status. The drive’s parameters must be correctly configured for communication control. Key parameters include:
- P00: Source of frequency command (set to 4 for RS-485 communication)
- P01: Source of operation command (set to 3 for RS-485 communication)
- P88: Communication address (1-254, must match PLC program)
- P89: Baud rate (e.g., 9600 bps)
- P92: Communication protocol (set to 1 for Modbus RTU 8,N,1)
The PLC program typically uses the Modbus library (MBUS_CTRL and MBUS_MSG) to write frequency values to the drive’s holding registers. The frequency command is usually written to register 2001H (frequency command) and the run command to register 2000H (operation command).
Why Does the Jog Frequency Appear After the First Start?
The jog frequency issue often stems from how the drive interprets the run command and frequency reference. In many VFDs, including the Delta VFD-M, the jog function has a dedicated terminal or command bit. When using communication, if the jog bit is inadvertently set or the drive’s logic treats a subsequent start as a jog command, the drive will run at the jog frequency (set in P15) instead of the commanded frequency.
Common causes include:
- Incorrect operation command word: The run command register (2000H) uses specific bits for forward run, reverse run, and jog. If the jog bit (bit 2 for forward jog, bit 3 for reverse jog) is set instead of the run bit (bit 0 for forward run, bit 1 for reverse run), the drive will jog.
- PLC program logic: The program may be writing the correct frequency but sending a jog command after the first cycle due to a logic error or one-shot condition.
- Drive parameter retention: Some drives retain the last command mode. If the drive was previously in jog mode (e.g., from keypad testing), it might not clear the jog status when switching to communication control.
- Timing issues: If the frequency write and run command are not synchronized, the drive might start with the default jog frequency before receiving the new frequency setpoint.
Step-by-Step Troubleshooting and Solution
To resolve the issue, follow these steps:
- Verify Drive Parameters: Ensure P00=4, P01=3, and communication settings match the PLC. Check P15 (jog frequency) to confirm it is set to a value different from the intended running frequency, which helps identify if jog is being activated.
- Check the Operation Command Register: In the PLC program, examine the value written to 2000H. For a normal forward run, the value should be 0001H (bit 0 = 1). For jog forward, it would be 0004H (bit 2 = 1). Ensure the program writes the correct bit pattern. A typical Modbus write command in S7-200 SMART would look like:
MBUS_MSG: Slave=1, RW=1, Addr=16#2000, Count=1, DataPtr=&VB100
// VB100 = 16#01 (forward run) or 16#04 (forward jog) - Sequence the Commands Correctly: Write the frequency setpoint to 2001H first, then after a short delay (e.g., 50-100 ms), write the run command to 2000H. This ensures the drive has the correct frequency before starting.
- Use a State Machine in PLC Logic: Implement a state machine that initializes the drive on first scan, sets the frequency, and then issues a run command only when the drive is stopped. Avoid continuous writing of the run command, which can cause unexpected restarts.
- Monitor Drive Status: Read register 2100H (status word) to confirm the drive is in the expected state. Bit 0 indicates run/stop, and bits 2-3 indicate jog status. Use this feedback to condition the PLC logic.
- Clear Jog Mode Explicitly: If the drive enters jog mode, send a stop command (write 0000H to 2000H) and then reissue the run command with the correct bit. Some users find that writing 0000H before each start ensures a clean state.
Example PLC Program Snippet for Reliable Control
Below is a conceptual ladder logic approach for the S7-200 SMART to avoid jog frequency issues:
| Step | Action | Details |
|---|---|---|
| 1 | Initialize Modbus | Use MBUS_CTRL with correct baud rate, parity, and timeout. Trigger on first scan (SM0.1). |
| 2 | Write Frequency | When start is requested, write desired frequency (e.g., 5000 for 50.00 Hz) to 2001H. Use a one-shot to trigger the MBUS_MSG. |
| 3 | Delay | Use a timer (e.g., TON 100 ms) after frequency write is done (M0.0 from MBUS_MSG). |
| 4 | Write Run Command | After timer, write 16#0001 to 2000H for forward run. Ensure jog bits are 0. |
| 5 | Stop Sequence | On stop request, write 16#0000 to 2000H. Optionally read status to confirm stop before allowing next start. |
Additional Tips for Robust VFD Communication
- Use shielded twisted-pair cable for RS-485 to minimize noise. Ground the shield at one end only.
- Set appropriate timeout values in the PLC Modbus configuration to handle communication losses gracefully.
- Implement a watchdog in the PLC that stops the drive if communication fails for a certain period.
- Check drive firmware version: Some older VFD-M firmware may have bugs related to communication jog handling. Upgrading firmware or consulting Delta support can help.
- Test with a Modbus tool: Use a PC-based Modbus master (like Modbus Poll) to send commands directly to the drive. This isolates whether the issue is in the PLC program or the drive itself.
Conclusion
The jog frequency issue when controlling a Delta VFD-M via S7-200 SMART PLC communication is typically caused by incorrect operation command bits or improper sequencing. By carefully setting the drive parameters, writing the correct register values, and implementing a robust PLC program with proper timing and state management, you can achieve consistent frequency control. Always refer to the VFD-M manual for detailed register maps and parameter descriptions. With these adjustments, your automated system will run smoothly without unexpected jog behavior.
