A collection of frequently asked questions about the Yaskawa SRCI interface.
What is SRCI?
SRCI stands for “Standard Robot Command Interface” and is a new standard for PLC controlled robotics. Just as with MotoLogix , this interface allows programming the robot trajectory in the PLC instead of in the robot controller.
The SRCI specification was created by a working group which was founded in 2018 and included a leading PLC vendor and many robot vendors. The specification is now hosted by the PI standardization organization and the working group is still active (and has welcomed many new members).
SRCI is not limited to any particular PLC or fieldbus. It is expected that over time, many PLC vendors will support this interface (and create a PLC library).
How does Yaskawa SRCI work?
The Yaskawa SRCI implementation consists of two parts:
- SRCI activation in the robot system software (paid option function)
- SRCI interpreter app (free download)
SRCI option function
The option function has to be enabled by Yaskawa. You can verify whether it is enabled on your system by looking into the setup of the SRCI
- If the SRCI option function is ordered on a new system, Yaskawa will activate the option as part of the setup process.
- If SRCI needs to be enabled on an existing system it might require a service visit, as this might also require an update of the robot system software. Please contact your Yaskawa sales representative to discuss the options.
SRCI Interpreter app
The interpreter is implemented as a MotoPlus application, meaning that it is written in C-code and runs in the real-time environment of the robot controller.
Updates of the SRCI app are independent of the robot system software and are distributed by Yaskawa Europe.
Which robots/controllers are supported?
| Robot controller | Supported? |
|---|---|
| YRC1000 | Yes |
| YRC1000micro | Yes |
| Manipulator | Supported? |
|---|---|
| GP series | Yes |
| HC series | No (expected: 2024H2) |
| HD series | Yes |
| MotoMINI | Yes |
| PL series | No (expected: 2024H2) |
| SG series | No (expected: 2024H2) |
| SP series | No (expected: 2024H2) |
Which PLC platforms are supported?
From the robot controller perspective, the PLC platform does not matter. The interface is standardized and every PLC vendor can adopt the standard and create a SRCI PLC library.
Which fieldbuses are supported?
Yaskawa SRCI will be available for the following fieldbuses:
| Fieldbus | Optional: safety protocol |
|---|---|
| EtherCAT | - |
| Ethernet/IP | CIP safety |
| POWERLINK | - |
| PROFINET | PROFIsafe |
We have created an overview of the supported setups (and their order numbers) for Yaskawa SRCI.
What are SRCI profiles?
The SRCI specification divides the features in a few function groups. Every vendor can decide which function group it will support.
- Core profile
Contains core functionalities of the interface and basic commands. - Extended profile
Contains all mandatory commands that are not featured by the core profile. - Optional functions
Contains all optional functions.
Below an overview of the functions for each of the SRCI profiles.
Core profile
Read more...
ChangeSpeedOverrideEnableRobotExchangeConfigurationGroupContinueGroupInterruptGroupJogGroupResetGroupStopMoveAxesAbsoluteMoveDirectAbsoluteMoveLinearAbsoluteReadActualPositionReadActualPositionCyclicReadFrameDataReadLoadDataReadMessagesReadRobotDataReadRobotDefaultDynamicsReadRobotReferenceDynamicsReadRobotSWLimitsReadToolDataReturnToPrimaryRobotTaskSecondarySequenceSetSequenceWriteFrameDataWriteLoadDataWriteRobotDefaultDynamicsWriteRobotReferenceDynamicsWriteToolData
Extended profile
Read more...
ActivateNextCommandCalculateCartesianPositionCalculateForwardKinematicCalculateFrameCalculateInverseKinematicCalculateToolCallSubprogramMoveAxesRelativeMoveCircularAbsoluteMoveCircularCamMoveCircularRelativeMoveDirectCamMoveDirectOffsetMoveDirectRelativeMoveLinearAbsoluteJMoveLinearCamMoveLinearOffsetMoveLinearRelativeReactAtTriggerReadCallSubprogramCyclicReadDigitalInputsReadDigitalOutputsReadIntegersReadRealsReadSystemVariableSetTriggerErrorSetTriggerLimitSetTriggerLimitSetTriggerRegisterSetTriggerUserShiftPositionStopSubprogramWaitForTriggerWaitTimeWriteCallSubprogramCyclicWriteDigitalOutputsWriteIntegersWriteRealsWriteSystemVariable
Optional functions
Read more...
AbortMeasuringInputActivateConveyorTrackingActivateWorkAreaAvoidSingularityBrakeTestCollisionDetectionConfigureConveyorCreateSplineDeleteSplineDynamicSplineForceControlForceLimitFreeDriveLoadMeasurementAutomaticLoadMeasurementSequentialMeasuringInputMonitorWorkAreaMoveApproachDirectMoveApproachLinearMoveDepartDirectMoveDepartLinearMovePickPlaceDirectMovePickPlaceLinearMoveSplineMoveSuperImposedMoveSuperImposedDynamicOpenBrakeOperationMode T1 ExternalOperationMode T2 ExternalPathAccuracyModeReadActualForceReadActualTCPVelocityReadAnalogInputReadAnalogOutputReadDHParameterReadWorkAreaRedefineTrackingPosRestartControllerSearchHardStopSearchHardStopJSetOperationModeSetTriggerMotionSoftSwitchTCPSwitchLanguageSyncToConveyorUnitMeasurementUserLoginWriteAnalogOutputWriteRobotSWLimitsWriteWorkArea
Why is SRCI function xx not supported?
The core profile includes the basic functionalities to operate a robot but we understand that some of the functions from the other profiles might be essential for you.
We would like to hear your feedback on which functions which are important for your projects.
This feedback will be helpful for us to schedule future developments on our SRCI interpreter app.
What is the difference between SRCI and MotoLogix?
SRCI is designed to work with all kinds of different PLC- and robot vendors. It has a clever mechanism to work with different data packet sizes. Also, it can dynamically combine command data in the data packet, meaning that multiple commands can be transmitted in a single communication cycle. The additional layers for this data handling, however, do use a bit more CPU resources.
MotoLogix is a proprietary high-performance solution for PLC controlled robotics. It has been on the market since 2015 and is used in many projects worldwide. However, as it is highly optimized for Yaskawa robots, it cannot be used with other vendors.
The table below shows a brief comparison between SRCI and MotoLogix.
| SRCI | MotoLogix | |
|---|---|---|
| PLC library distribution | PLC vendor | Yaskawa Europe |
| PLC library pricing | ask your PLC vendor | Free of charge |
| Robot option function pricing | $$ | $ |
| Feature set | core profile: Lowextended profile: High | Medium |
| Performance | Medium | High |
| Data packet | Flexible (Yaskawa uses 436b and 254b) | Fixed (436b) |
| CPU requirements (PLC) | Medium | Low |
| Integration support | PLC vendor (primarily) | Yaskawa Europe |
Why would I choose SRCI over MotoLogix?
This depends on your needs. Maybe this summary helps with your decision.
- SRCI comes with a bit higher cost, but PLC vendors might offer easy to use PLC- and HMI applications, saving you lots of engineering hours – Perfect for companies who do not want to spend much development effort on the integration.
- MotoLogix has lower cost (both in price per unit and CPU resources) but requires more development effort for the integration – Perfect for companies who work with larger volumes.