This summer, Yaskawa Europe will release the SRCI (Standard Robot Command Interface) option function for the Yaskawa robot controllers. Take a minute to learn what SRCI is about and what it means for MotoLogix users.
What is SRCI?
SRCI 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, which was created by a working group consisting of a leading PLC vendor and many robot vendors, is now hosted by the PI standardization organization .
The goal of SRCI is to standardize both the data packet and the PLC library functions. This enables users to switch between different robot- and/or PLC vendors without having to rewrite all of their PLC code.
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).
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.
For more details check the function overview below.
What is the difference between MotoLogix and SRCI?
MotoLogix is a proprietary high-performance solution for PLC controlled robotics. It has been on the market for over seven years and is used in many projects worldwide. However, as it is highly optimized for Yaskawa robots, it cannot be used with other vendors.
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.
The table below shows a brief comparison between SRCI and MotoLogix.
| MotoLogix | SRCI | |
|---|---|---|
| PLC library distribution | Yaskawa Europe | PLC vendor |
| PLC library pricing | Free of charge | ask your PLC vendor |
| Robot option function pricing | $ | $$ |
| Feature set | Medium | core profile: Lowextended profile: High |
| Performance | High | Medium |
| Data packet | Fixed (436b) | Flexible (Yaskawa plans two packet sizes) |
| CPU requirements (PLC) | Low | Medium |
| Integration support | Yaskawa Europe | PLC vendor (primarily) |
What does this mean for MotoLogix?
MotoLogix and SRCI will live next to each other. This means that:
- SRCI is not replacing MotoLogix.
- MotoLogix development will not be reduced.
We think that both interfaces will complement each other perfectly.
SRCI or MotoLogix - which interface should I choose?
This depends on your needs. Maybe this summary helps with your decision.
- SRCI comes with a bit higher cost, but PLC vendors will most probably offer easy to use PLC- and HMI applications – Perfect for companies who do not want to spend much development effort on the integration.
- MotoLogix has lower cost (both in price and CPU resources) but requires more development effort for the integration – Perfect for companies who work with larger volumes.
Function overview
This list is based on SRCI spec v1.3
Core profile
Read more...
ChangeSpeedOverrideEnableRobotExchangeConfigurationGroupContinueGroupInterruptGroupJogGroupResetGroupStopMoveAxesAbsoluteMoveDirectAbsoluteMoveLinearAbsoluteReadActualPositionReadActualPositionCyclicReadFrameDataReadLoadDataReadMessagesReadRobotDataReadRobotDefaultDynamicsReadRobotReferenceDynamicsReadRobotSWLimitsReadToolDataReturnToPrimaryRobotTaskSecondarySequenceSetSequenceWriteFrameDataWriteLoadDataWriteRobotDefaultDynamicsWriteRobotReferenceDynamicsWriteToolData
Extended profile
Read more...
ActivateNextCommandCalculateCartesianPositionCalculateForwardKinematicCalculateFrameCalculateInverseKinematicCalculateToolCallSubprogramMoveAxesRelativeMoveCircularAbsoluteMoveCircularCamMoveCircularRelativeMoveDirectCamMoveDirectOffsetMoveDirectRelativeMoveLinearAbsoluteJMoveLinearCamMoveLinearOffsetMoveLinearRelativeReactAtTriggerReadCallSubprogramCyclicReadDigitalInputsReadDigitalOutputsReadIntegersReadRealsReadSystemVariableSetTriggerErrorSetTriggerLimitSetTriggerLimitSetTriggerRegisterSetTriggerUserShiftPositionStopSubprogramWaitForTriggerWaitTimeWriteCallSubprogramCyclicWriteDigitalOutputsWriteIntegersWriteRealsWriteSystemVariable
Optional functions
Read more...
AbortMeasuringInputActivateConveyorTrackingActivateWorkAreaAvoidSingularityBrakeTestCollisionDetectionConfigureConveyorCreateSplineDeleteSplineDynamicSplineForceControlForceLimitFreeDriveLoadMeasurementAutomaticLoadMeasurementSequentialMeasuringInputMonitorWorkAreaMoveApproachDirectMoveApproachLinearMoveDepartDirectMoveDepartLinearMovePickPlaceDirectMovePickPlaceLinearMoveSplineMoveSuperImposedMoveSuperImposedDynamicOpenBrakeOperationMode T1 ExternalOperationMode T2 ExternalPathAccuracyModeReadActualForceReadActualTCPVelocityReadAnalogInputReadAnalogOutputReadDHParameterReadWorkAreaRedefineTrackingPosRestartControllerSearchHardStopSearchHardStopJSetOperationModeSetTriggerMotionSoftSwitchTCPSwitchLanguageSyncToConveyorUnitMeasurementUserLoginWriteAnalogOutputWriteRobotSWLimitsWriteWorkArea
I need SRCI function xx
After the initial release with core profile we will schedule the development
for the next release.
We would like to hear your feedback on functions which are important for your projects. Please use the Support & Contact button below to get in touch with us.