-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to use SDO to configure slave? #240
Comments
The Custom Device does not contain a mechanism to send/receive SDOs. It only interacts with PDOs by exposing VeriStand channels for each PDO defined and enabled in the ESI file. If I recall correctly, you can use the Mailbox > CoE > InitCmd tags to define configuration SDOs to be sent on initialization (during Scan Engine state change which happens on VeriStand deployment). This is handled at the driver level, and VeriStand should not interfere with them. However, it can't be defined, read, or changed from VeriStand. <Mailbox DataLinkLayer="1">
<EoE />
<CoE SdoInfo="true" PdoAssign="true" PdoConfig="true">
<InitCmd>
<Transition>PS</Transition>
<Index>#x6060</Index>
<SubIndex>0</SubIndex>
<Data>08</Data>
<Comment>Op mode</Comment>
</InitCmd>
</CoE>
<FoE />
</Mailbox> |
We use NI Real-Time Controllers (PXIe 8861) as EtherCAT Master for third party (non NI) EtherCAT Slaves.
But how to use SDO to configure slaves?
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YNpoCAG&l=zh-CN
The text was updated successfully, but these errors were encountered: