Yaskawa FlexWorks
FlexWorks is associated with Sigma FSP programming and electronic-cam functionality. Its catalog role differs from ordinary SigmaWin drive setup, so it deserves a separate workflow.
Archive the motion program and cam profile alongside the drive’s feedback configuration. Check the MC/MH option and exact FSP frame before reusing another project.
Practical workflow and cautions
An electronic-cam application links master and follower axes, a cam profile and synchronization events. A FlexWorks project may contain machine motion logic beyond an ordinary parameter backup, so preserve the proven file separately before editing it.
The MC/MH feedback choice in the FSP hardware must agree with the axis definition in the project. Even a small timing change can alter collision risk; commissioning belongs in a controlled, low-speed test procedure.
Why the cam profile needs its own backup
An electronic-cam machine depends on the profile and synchronization events that order its mechanical cycle. Even a complete drive-parameter backup may not reproduce that cycle if the motion project is missing. Archive the FlexWorks file together with the FSP option code and a timing record from the known working machine.
Related hardware
Archive a FlexWorks project with the exact FSP drive designation and the role of its application card.
A different software task
Compare the document scope in SERVOPACK drive manuals when matching this tool to the drive generation.