VH524-0808TP Veichi VH524-0808TP PLC: 8 inputs / 8 outputs, PNP transistor outputs, 24VDC supply, up to 48 motion axes, RS232/485, CANopen, EtherCAT, Ethernet.

VH524-0808TP — the top VH500 tier for 48 axes with PNP outputs: 8 digital inputs, 8 PNP transistor outputs, 24 V DC, RS232/485, USB, CANopen, two Ethernet, EtherCAT. The maximum axis count in the series, in PNP logic that suits most modern drives.

Typical applications:

• A large line or machine on 32–48 servo axes in a PNP cabinet.
• Multi-group coordinated motion with an upper level over two Ethernet ports.
• Projects that need the maximum VH500 axis count without moving to CODESYS.

Note: it differs from VH524-0808TN only in output polarity (PNP vs NPN). If you stay under 32 axes, VH523-0808TP is cheaper; if you need more than 48 axes or CODESYS — that is already VH600. Expand I/O with VH-R modules on the right and a VH-L board on the left.

Veichi VH500 — EtherCAT motion controller in a slim modular body

Reach for VH500 when you need to coordinate many axes over a bus, not just pump pulses to a stepper/servo. It is a slim PLC on a 1 GHz CPU with a built-in EtherCAT master: up to 72 slaves, bus cycle from 250 µs, up to 48 real axes (64 with virtual). It is programmed in AutoStudio using LD/ST/FBD/SFC, holds 200K program steps and up to 1M variables, with firmware loaded from an SD card.

The main reason to pick VH500 over VH300 is the move from pulse positioning to coordinated EtherCAT motion. Instead of routing separate pulse lines to every drive, you run a single bus, keep dozens of axes in sync and scale easily with VH-R modules on the right and a VH-L board on the left.

What VH500 is good for

• Multi-axis machines and automats: cutting, marking, dosing — coordinating 8–48 drives over one bus.
• Filling and packaging lines: synchronous feeds, cut-on-the-fly, rotary tables.
• Winding and conveyor sections: e-cam and e-gear for electronic shaft synchronization without mechanics.
• Assembly machines with servo axes: where VH300, with its 2-axis interpolation, already hits the ceiling.

How VH500 differs from neighbouring series

In practice VH500 is the sweet spot: real EtherCAT motion already, but without moving to CODESYS or paying for the VH600 medium class. If you stay under fifty axes and AutoStudio is enough, VH500 covers the job. Need CODESYS, PLCopen libraries or more than 48 axes — it makes sense to look straight at VH600.

When VH500 is not the right fit

• You need more than 48 real axes or CODESYS with PLCopen — take VH600.
• Motion is not over a bus but simple pulse on 1–2 axes — VH300 works out cheaper.
• The task is pure logic with no motion — look at the compact VC1 or VC3.
• You work inside another vendor's ecosystem — compare with Delta or Fatek.

Our experience with VH500

VH500 is steadily bought by integrators who have outgrown pulse control and build machines on servo axes over EtherCAT. The typical question is "how many drives will it really handle without cycle slip": from our practice, keep an axis margin and do not load the bus right up to 72 slaves. Alongside it, customers often order VH-R/VH-L expansion modules, Veichi VFDs and Veichi operator panels for the same line.