Talk:CANopen

From Wikipedia, the free encyclopedia

[edit] other

I think a few examples are extremely helpful. I added the CANOpen master querying a CANopen slave for current values, can someone please add how to configure a Node address?

[edit] 4 TPDO's and 4 RPDO's

It says in the PDO section that there are 4 TPDO's and 4 RPDO's. This needs some clarification. AFAIK 4 is a default value. But what if a device only has one value to produce? Or is it is a device that produces data to many other devices?

My feeling is that this part needs some additions. —Preceding unsigned comment added by Rene.heijma (talk • contribs) 14:38, 2 January 2008 (UTC)

[edit] "Upload/download" ambiguity

In control system parlance (ie PLCs), "download" means to send data away from you to another device - which is the opposite of its more common internet used where "download" means to bring data to you. So the description below is ambiguous and a diagram would be really helpful, if anyone has one.

The SDO protocol is used to set and read values from the object directory of a remote device. The device whose object directory is accessed is the SDO server and the device accessing the remote device is the SDO client. The communication is always initiated by the SDO client. In CANopen terminology, communication is viewed from the SDO server, so that a read from an object directory results in an SDO upload and a write to directory is an SDO download.