Re: CANOpen PDO assignment.
Heinz-Jürgen Oertel <[email protected]>
| Newsgroups | gmane.comp.hardware.bus.can |
|---|---|
| Organization | privat |
| Message-ID | <2535349.izGDyJu24j@linux-edhj> |
Am Montag 29 Oktober 2012, 22:19:57 schrieb John Dammeyer:
> In trying to explain this I end up thinking the concept of default
> Transmit and Receive PDOs are redundent and they should have been just
> named PDOs without the Transmit or Receive adjective.
John,
others have explained it already correctly.
See the device PDOs always from the devices point of view.
Each device has 8 pre-defined PDOs it can use without any configuration.
4 Transmit PDOs, where it can send out process data
and 4 Receive PDOs.
The content is defined in the device profile standard.
401 devices for example use there TPDOs for sending its digital inputs and analog inputs.
Received PDOs are mapped to there digital outputs and analog outputs.
The pre-defined get there CAN ID assignment from a simple rule
For TPDOs
180+node-ID
280+node-ID
380+node-ID
480+node-ID
and for Receive PDOs
200+node-ID
300+node-ID
400+node-ID
500+node-ID
The predefined connection set should ensure
that no one of it collides with another one.
Hope this helps too.
Heinz