Understand the difference between real-time data exchange with PDOs and periodic service channel messages with SDOs in EtherCAT, and learn how to read, write, and configure these using RapidSetup and the RapidCode API.
In EtherCAT, values are sent and received from most drives using CANopen PDO’s and SDO’s. In most applications, RapidCode API users need not be aware of these low-level features.
- PDO (Process Data Object) → Real-time data sent to/from the MotionController to each drive/node for every sample period.
- SDO (Service Data Object) → Service Channel messages which are not exchanged every cycle.
🔹 What are PDOs?
PDOs or Process Data Objects are the values exchanged cyclically with every real-time sample of the MotionController (1kHz by default). For servo drives, these are values such as control/status information and position demand/feedback.
- Multi-Threading Note
- → Writing to the same PDO values is not Multi-Threading safe.
→ Writing to different PDO values is Multi-Threading safe.
Reading & Writing
Data Injection
You can inject exchanged information (changing defaults) by creating the CustomNodeInfo.xml.
Let's say we want to read/write from the latch status, control, and positions SDO’s because communicating directly with the SDO takes too much time.
Follow the Example below for a solution.
Using CustomNodeInfo.xml File
In the default NodeInfo.xml file Yaskawa (for example) by default has the following PDO’s configuration:
<PDOs>
<PDOAssignment Index="0x1601" IsOutput="True" Include="False" />
<PDOAssignment Index="0x1a01" IsOutput="False" Include="False" />
<PDOAssignment Index="0x1600" IsOutput="True" Include="True" RemoveContent="0x6060 0x6072" />
<PDOAssignment Index="0x1a00" IsOutput="False" Include="True" />
</PDOs>
Take a look at the Yaskawa-SGD7S.xml ESI file, located in the ESI folder inside the RMP folder:
<Object>
<Index>#x60B8</Index>
<Name>Touch probe function</Name>
<Type>UINT</Type>
<BitSize>16</BitSize>
<Flags>
<Access>rw</Access>
<PdoMapping>RT</PdoMapping>
</Flags>
</Object>
<Object>
<Index>#x60B9</Index>
<Name>Touch probe status</Name>
<Type>UINT</Type>
<BitSize>16</BitSize>
<Flags>
<Access>ro</Access>
<PdoMapping>T</PdoMapping>
</Flags>
</Object>
<Object>
<Index>#x60BA</Index>
<Name>Touch probe 1 position value</Name>
<Type>DINT</Type>
<BitSize>32</BitSize>
<Flags>
<Access>ro</Access>
<PdoMapping>T</PdoMapping>
</Flags>
</Object>
<Object>
<Index>#x60BC</Index>
<Name>Touch probe 2 position value</Name>
<Type>DINT</Type>
<BitSize>32</BitSize>
<Flags>
<Access>ro</Access>
<PdoMapping>T</PdoMapping>
</Flags>
</Object>
You can add multiple AddEntry
by copying the relevant Vendor from NodeInfo.xml and pasting it to CustomNodeInfo.xml and making the following changes:
<PDOs>
<PDOAssignment Index="0x1601" IsOutput="True" Include="False" />
<PDOAssignment Index="0x1a01" IsOutput="False" Include="False" />
<PDOAssignment Index="0x1600" IsOutput="True" Include="True" RemoveContent="0x6060" />
<PDOAssignment Index="0x1a00" IsOutput="False" Include="True" />
<AddEntry Name="Touch probe 1 position value" Index="0x60BA" SubIndex="0" BitLen="32" DataType="DINT" />
<AddEntry Name="Touch probe status" Index="0x60B9" SubIndex="0" BitLen="16" DataType="UINT" />
<AddEntry Name="Touch probe 2 position value" Index="0x60BC" SubIndex="0" BitLen="32" DataType="DINT" />
</PDOAssignment>
</PDOs>
This works well for Inputs:
like Touch probe values and status. But it does not work currently for Outputs:
such as the Touch probe function (0x60B8). Right now if you add an output in, RMP will write 0 into it every cycle. Unless you Override the sent value (see next section).
Output Override
- RapidCode ⚙️
Represents the RMP soft motion controller. This class provides an interface to general controller con...
- RapidSetup 🖥️ Set the value under the OVERRIDE VALUE column and then check the checkbox under the OVERRIDE column. (See image below)
🔹 What are SDOs?
SDOs or Service Data Object are messages in a confirmed service with a kind of handshake. They are used for the access to entries of the object dictionary. Especially the configuration for the requested behavior of the drive adapted to the various possible applications is done by these objects.
- Note
- → SDO’s are not exchanged during every cycle, they are done periodically.
→ Not as fast as PDO’s since they must wait for network response
Reading & Writing
- RapidCode ⚙️
NetworkNode * NetworkNode
Gets the associated NetworkNode object.
Represents a single axis of motion control. This class provides an interface for commanding motion,...
int32_t ServiceChannelRead(int32_t index, int32_t subIndex, int32_t byteCount)
Read a 32-bit integer value from the SDO.
void ServiceChannelWrite(int32_t index, int32_t subIndex, int32_t byteCount, int32_t sdoValue)
Write a number in the SDO.
- RapidSetup 🖥️ The easiest way to read a SDO or write to an SDO is by using our RapidSetup utility then click on your drive node. (see images below)
📜 Sample Code
- C#
for (int i = 0; i < inputCount; i++)
{
}
for (int i = 0; i < outputCount; i++)
{
}