CiA® 460: CANopen profile for service robot control systems
This document specifies the CANopen interface of a service robot controller device, which is compliant to the Robotic Technology Component (RTC) specification. In order to design the robot communication system independent of CANopen, CiA has mapped the RTC specification by OMG to CANopen. The CiA 460 profile describes the service robot controller or any of the sub-system controllers, using a deeply embedded CANopen network. In addition, CiA 318 specifies the integration of CANopen networks into the RTC environment. This allows implementing heterogeneous network technologies. CiA 460 specifies the NMT manager application and its object dictionary with NMT manager parameters as well as CANopen device proxies representing the connected CANopen devices in the service robot controller device.
Title | Details | Published Size |
Status Action |
---|---|---|---|
CiA 460 version 1.0.0 CANopen profile for service robot control systems |
ScopeThis document specifies the CANopen interface of a service robot controller device, which is compliant to the Robotic technology component (RTC) specification. The profile specifies the NMT master application and its object dictionary with NMT master parameter as well as CANopen device proxies representing the connected CANopen devices in the service robot controller device. |
2012-02-10 321 KB | DSP Login |
CiA 318 version 1.0.0 CANopen integration into RTC environments |
ScopeThis document specifies the mapping of the Robotic technology component (RTC) finite state automaton to the CANopen network management (NMT) finite state automaton as well as the mapping of the RTC data types to CANopen data types. In addition, it describes the RTC - CANopen manager and the ProxyRTCs system integration. |
2012-02-10 585 KB | DSP Login |