Show EOL distros:
Package Summary
sr_external_dependencies package is a "dummy" package used to synchronize the includes for the protocol communication between the host and the PIC for Shadow's EtherCAT hardware. It contains a script that automatically downloads the latest h file from our pic32 svn.
- Author: Ugo Cupcic/ ugo@shadowrobot.com, software@shadowrobot.com
- License: GPL
- Source: bzr lp:sr-ros-interface-ethercat/fuerte (branch: release)
Package Summary
sr_external_dependencies package is a "dummy" package used to synchronize the includes for the protocol communication between the host and the PIC for Shadow's EtherCAT hardware. It contains a script that automatically downloads the latest h file from our pic32 svn.
- Author: Ugo Cupcic/ ugo@shadowrobot.com, software@shadowrobot.com
- License: GPL
- Source: git https://github.com/shadow-robot/sr-ros-interface-ethercat.git (branch: groovy-devel)
Package Summary
sr_external_dependencies package is a "dummy" package used to synchronize the includes for the protocol communication between the host and the PIC for Shadow's EtherCAT hardware. It contains a script that automatically downloads the latest h file from our pic32 svn.
- Maintainer status: maintained
- Maintainer: Shadow Robot's software team <software AT shadowrobot DOT com>
- Author: Ugo Cupcic
- License: GPL
- Bug / feature tracker: https://github.com/shadow-robot/sr-ros-interface-ethercat/issues
- Source: git https://github.com/shadow-robot/sr-ros-interface-ethercat.git (branch: hydro-devel)
Package Summary
sr_external_dependencies package is a "dummy" package used to synchronize the includes for the protocol communication between the host and the PIC for Shadow's EtherCAT hardware. It contains a script that automatically downloads the latest h file from our pic32 git.
- Maintainer status: developed
- Maintainer: Shadow Robot's software team <software AT shadowrobot DOT com>
- Author: Ugo Cupcic
- License: GPL
- Bug / feature tracker: https://github.com/shadow-robot/sr-ros-interface-ethercat/issues
- Source: git https://github.com/shadow-robot/sr-ros-interface-ethercat.git (branch: indigo-devel)
Package Summary
sr_external_dependencies package is a "dummy" package used to synchronize the includes for the protocol communication between the host and the PIC for Shadow's EtherCAT hardware. It contains a script that automatically downloads the latest h file from our pic32 git.
- Maintainer status: developed
- Maintainer: Shadow Robot's software team <software AT shadowrobot DOT com>
- Author: Ugo Cupcic
- License: GPL
- Bug / feature tracker: https://github.com/shadow-robot/sr-ros-interface-ethercat/issues
- Source: git https://github.com/shadow-robot/sr-ros-interface-ethercat.git (branch: kinetic-devel)
Package Summary
sr_external_dependencies package is a "dummy" package used to synchronize the includes for the protocol communication between the host and the PIC for Shadow's EtherCAT hardware. It contains a script that automatically downloads the latest h file from our pic32 git.
- Maintainer: Shadow Robot's software team <software AT shadowrobot DOT com>
- Author: Ugo Cupcic
- License: GPL
- Bug / feature tracker: https://github.com/shadow-robot/sr-ros-interface-ethercat/issues
- Source: git https://github.com/shadow-robot/sr-ros-interface-ethercat.git (branch: melodic-devel)
Contents
Overview
When you run make in this package, it simply copies the files from the released directory to the include and compiled_firmware directories. The protocol headers are then used in the sr_edc_ethercat_drivers and sr_robot_lib to interpret the incoming packets.
The compiled firmware can be used in the bootloader plugin of the sr_control_gui to update the firmware of the motors.
Development Use
'NB: For internal use at Shadow only'
If you set the INTERNAL_FIRMWARE environment variable to 1, then we'll download the latest version of the protocol and also the latest compiled firmware from our internal svn (this is only possible if you're working for Shadow).
If you're ready to make a relased firmware, just run make release in the package. This will copy the files to the released directory, write the current versions of the different software in the tested_version.yaml file, and tag the current bzr revision with the revisions as well.
