Yaskawa LogicWorks

LogicWorks is associated with the SigmaLogic control solution. A standard SGDV is not automatically a SigmaLogic device; check the appropriate hardware and option identity.

Keep servo parameters and application logic backups distinct. Before changing a program, review I/O behavior, motion conditions and the effect on safe stopping.

Practical workflow and cautions

With SigmaLogic, logic behavior sits close to the servo function. Copying drive parameters without the input conditions, outputs and motion permissives may fail to restore the original machine behavior.

Troubleshooting needs a consistent revision set: software project, drive identity and machine electrical drawing. A LogicWorks record in an archive does not mean every SGDV frame provides this function. Record the operator message and the servo alarm separately.

Why the LogicWorks project needs its own backup

Drive parameters describe motor behavior, while the LogicWorks project can define responses to machine inputs and events. Restoring parameters after an alarm may not restore the application logic. Retain the drive code, I/O map, project release and last known working backup in one maintenance record.

Related hardware

A LogicWorks project belongs to SigmaLogic, not to ordinary Sigma-5 drive setup.

A different software task

Compare the document scope in SERVOPACK drive manuals when matching this tool to the drive generation.