IMDHMIControls LibraryShop main store

How-to

Control an ATV12 drive from a TM200 PLC over Modbus RTU

Drives and motion Published 5 min read

Short answer

The ATV12 takes start/stop from register 8601 (CMD) and speed from register 8602 (LFRD, in rpm) once you set Fr1 to Mdb in the CtL- menu and match address, baud, parity and stop bits at both ends. The ladder then writes both words cyclically, one request at a time, gated on completion. Start from the TVDA sample project in Machine Expert Basic.

On this page
  1. Switch the ATV12 command and reference to Modbus
  2. Match the serial line at both ends
  3. Start from the TVDA sample project
  4. Structure the ladder around 8601 and 8602
  5. Worked example: turning 30.00 Hz into a value for 8602
  6. Commissioning test
  7. Questions asked

An ATV12 wired to a TM200C16R over RS485 ignores every value the PLC writes until two things change: the drive's command and reference source must be moved off the terminals to Modbus, and the ladder must write a control word and a speed reference cyclically. Set Fr1 to Mdb in the drive's CtL- menu, match the serial line at both ends, and write register 8601 (CMD, start/stop) and register 8602 (LFRD, speed in rpm), one request in flight at a time. The TVDA sample project in Machine Expert Basic already integrates an ATV12 with a TM2xx controller, so start from it rather than from a blank program.

Switch the ATV12 command and reference to Modbus #

Out of the box, Reference Channel 1 (Fr1) is set to AI1, so the drive takes its speed from an analog input and its run command from its own terminals. In the CtL- menu, set Fr1 to Mdb, the built-in Modbus selection: in combined operation Fr1 is the common source for both the command and the reference, so this one setting moves start/stop and speed to the PLC. In separated-channel operation, set the command channel and the reference channel independently, and a drive with only one side moved behaves in a predictable half-working way:

Channel left on terminals What you see Decision
Command Writes to 8601 complete, but the motor runs only from the drive's own inputs Move the command channel to Modbus
Reference Motor starts and stops from the PLC but runs at the AI1 or keypad speed Move the reference channel to Modbus

Read both channels back on the drive keypad after the change. A Modbus write that completes does not prove the channel moved; it only proves the register was written.

Match the serial line at both ends #

Four settings must be identical on the drive's communication menu and on the TM200 serial-line configuration in Machine Expert Basic, with the controller set up as the Modbus master:

Setting ATV12 side TM200 side
Slave address Address in the communication menu Same value in every request
Baud rate Communication menu Serial-line configuration
Parity Communication menu Serial-line configuration
Stop bits Communication menu Serial-line configuration

Commit to one matched set, for example 19200 baud, 8 data bits, even parity, one stop bit; any matched set works and no unmatched set does. On the physical layer, use shielded twisted pair end to end, keep D+ and D- polarity correct at both connectors (a swapped pair produces clean timeouts, never partial responses), terminate only the two physical ends of the line, and ground the shield at one point. Take the serial port pin-out from the TM200C16R hardware guide, not from TM221 drawings.

If every request times out, the cause is address, polarity or format. Fix that before touching the ladder.

Start from the TVDA sample project #

  1. Open the TVDA sample project in Machine Expert Basic: it integrates an ATV12 with a TM2xx controller and is written for the TM221, whose Modbus handling is the same as the TM200's.
  2. Read its serial-line configuration and compare it to your own, setting by setting.
  3. Copy the rungs that build the control word, write the reference and read the status, and note where each request waits for completion before the next one fires.
  4. Retarget the project to your TM200C16R and change only I/O addresses; leave the request gating as written.

Structure the ladder around 8601 and 8602 #

The drive is commanded by two writes and reports through two reads, every cycle:

  1. Read the drive's status word and actual speed into PLC words.
  2. Build the CMD control word for 8601 in one rung from your run, stop and fault-reset bits, using the ATV12's own bit assignments from its Modbus Communication Guide; a control word copied from another drive family will not run this drive.
  3. Scale the operator setpoint into rpm, clamp it between the drive's low and high speed limits, and write it to 8602.
  4. Keep one request in flight: trigger it, wait for done or error, then send the next, throttled on a timer rather than every scan. That discipline is also what keeps the cycle time predictable — see why Modbus RTU drive polling on one serial port is slow for the per-register arithmetic.
  5. Drive the running and fault indications from the status word read back. A PLC run bit does not prove the motor is turning.

Worked example: turning 30.00 Hz into a value for 8602 #

Register 8602 takes rpm, so the setpoint must be scaled. Illustrative motor data, with the drive's nominal speed set to match the nameplate: 4-pole, 50 Hz, 1450 rpm.

  • rpm per Hz: 1450 rpm ÷ 50 Hz = 29 rpm per Hz
  • 30.00 Hz setpoint: 1450 × 30 ÷ 50 = 870 rpm, so write the decimal value 870 to 8602
  • Two more points from the same scale for commissioning: 12.00 Hz is 29 × 12 = 348, and 40.00 Hz is 29 × 40 = 1160

The general rule is rpm = nameplate rpm × (setpoint Hz ÷ nameplate Hz); on this motor, every Hz entry is worth 29 rpm. Writing the Hz number itself, 30, would command 30 rpm, about 1 Hz, so the scaling step is not optional. Clamp the result to the drive's speed limits before every write.

Commissioning test #

Run the first tests with the motor uncoupled or the load guarded; the first run bit can start the machine.

  1. Write 348 to 8602 and confirm the drive's output-frequency display settles near 12 Hz at no load.
  2. Set the run bit in the control word and confirm the status word read back shows running, with the shaft turning the expected direction.
  3. Step the reference through 348, 870 and 1160, and confirm the speed value read back tracks each step.
  4. Clear the run bit and confirm the status word shows stopped.
  5. Unplug the RS485 cable while running: the drive must reach its configured communication-loss response and the PLC must flag the timeout. Reconnect and confirm normal control resumes.

Questions asked

Can I keep start/stop on the ATV12 terminals and send only the speed over Modbus?

Yes. Put the drive in separated-channel operation, leave the command channel on the terminals and set only the reference channel to Modbus. The drive then starts from its own input while register 8602 sets the speed. Keep the terminal stop path wired and tested, because a PLC writing only the reference can never stop the drive.

Is register 8602 in Hz or rpm?

Rpm. Register 8602 (LFRD) is the frequency reference expressed in rpm: 870 means 30.00 Hz on a 1450 rpm, 50 Hz motor. The keypad's LFr reference is entered in Hz and is a different entry. Never write the Hz number itself: 30 written to 8602 commands 30 rpm, about 1 Hz on that motor.

Does the TM200C16R need an add-on card to talk Modbus RTU?

No add-on is needed for this link: configure the controller's own serial line as a Modbus RTU master in Machine Expert Basic. Take the port's D+ and D- pin-out from the TM200C16R hardware guide rather than from TM221 documentation, and wire the pair to the drive's D+ and D-.

Can one TM200 control several ATV12 drives on the same RS485 line?

Yes. Modbus RTU is multidrop: give each ATV12 a unique address in its communication menu and poll them one at a time from the same master port. The cycle time grows with every register added per drive, so budget the update rate before the speed loop depends on it.

Keep reading

  • Troubleshooting

    Why Modbus RTU drive polling on one serial port is slow

    Modbus RTU carries one request-response transaction at a time, and at 19.2 kbit/s each drive transaction costs 40-60 ms, so 18 drives polled with a read and a write each need about 1.5-2.5 s per cycle no matter how the messages are chained. Cut the transaction count, schedule command writes ahead of status reads, set each drive's communication-loss timeout above the finished cycle, and change networks when the arithmetic cannot meet the update rate.

    Industrial networks

  • How-to

    Bridging a PLC-5/15 DH+ network to a Kinetix 300 servo drive

    Yes, a DH+-to-EtherNet/IP gateway exchanges command and feedback words between a PLC-5/15 and a Kinetix 300, but it only moves data: the drive must execute the motion profile locally. Replace the stepper controller, pulse expander, and encoder-counter functions with an eight-word map that carries a 32-bit position as two 16-bit words behind a data-valid handshake. If the machine needs trajectory points streamed per scan, migrate the controller instead of bridging it.

    Drives and motion

  • How-to

    Control a PowerFlex 525 drive from two PLC controllers

    Yes — add the PowerFlex 525 to the Logix controller's Ethernet tree and its command tags appear, but a cyclic drive connection has exactly one owner. Give the Logix controller that ownership, read the MicroLogix machine's request into it, and let one rung select the command the drive follows. Never let two controllers write the speed reference.

    Drives and motion