SyncTwinTECHNOLOGIES
Development cloud

The program is written remotely — and verified on real drives

Development of PLC programs, motions and lines — in the browser, without travel. The test — on our bench with drives or on your equipment.

Development cloud diagram An engineer writes a program in the browser; the cloud checks it with a compiler and a run on virtual axes; then the program goes to the bench with drives or to the customer's equipment, and the drives' response returns to the screen. Browser: program and run Cloud IEC 61131-3 compiler check,run on virtual axes Our benchservo drives andI/O on EtherCAT Yourequipmenton your site
What happens in the cloud

From program text to axis motion

  1. ProgramSFC or ST per IEC 61131-3, a cutting program or a robot motion program.
  2. CheckThe compiler checks the whole text; an error comes with its place in the text.
  3. Run without hardwareVirtual axes: stroke and time are visible, the drives stand still.
  4. Test on drivesOur bench or your equipment; the actual value is taken from the drive.
Cloud boundary

Intent goes to the cloud, control stays with the equipment

  • Across the boundary go the program and the «run» and «stop» commandsJogging and direct drive commands stay with the equipment.
  • A button's reply is not a factThe fact is the position and the drive status word, visible on screen.
  • Cloud or your perimeterThe same platform is installed on your servers.
Test bench with drives

Verification on real hardware — without a trip to site

The cloud version of the platform is in production use: programs for machines, robots and units are written in it. Drive tests run on our test bench or on your equipment through a box inside your perimeter.

Our test bench is mixed: axes, a spindle and an I/O coupler from different manufacturers on one EtherCAT bus. It is a development test bench, not factory operation.

ModeWhat happensWhat it proves
Virtual axesNo bus, drives stand still; blocks, steps and timing are visibleLogic, step order and transitions
Test bench drivesReal servos over EtherCAT; torque only inside a motion stepMotion, following error and axis load
Your equipmentThe same program through the box on siteYour machine’s behaviour — in the implementation test protocol
After the run

What you see on screen

Run log

Which program, when, how it ended: ran to the end, stopped, error or outcome unknown.

Monitor and oscilloscope

Coordinates, state, position, velocity and torque charts; the commissioning oscilloscope — 1 kHz over the bus.

Refusals — in words

An unmapped drive, an unknown channel, a missing profile — a refusal with a reason, no “just make it move” substitution.

  • A test on your equipment needsA box inside your perimeter, drives on an EtherCAT bus with the CiA 402 profile, axis profiles on the test bench.
Next step

Discuss an implementation

Describe the unit or line — we will tell you what we will verify and in what time. Target indicators are fixed in the implementation specification.

Request access

Implementation →

Request access