Bounty for ROS-free soem components

Dear Orocos Community,

I hereby offer a 100 euro bounty for someone to modify the build
scripts for the soem orocos component(s) such that they do not depend
on ROS.

I believe the mainline repo is hosted here:
http://git.mech.kuleuven.be/robotics/soem.git

It contains four inter-dependent components: soem_core, soem_master,
soem_ebox, and soem_beckhoff_drivers.

Requirements:
* The components build without ROS installed
* The built components can still talk to an ebox (this hardware is
rare; I can help test, but if they build, they probably work.)
* The built components are still hard real-time (i.e. don't add any
printf's or malloc's, etc... to the code)
* Don't change the component interfaces unless necessary (i.e. please
don't break our other components).
* Don't break the build for ROS users

If you are local, I can hand you cash, or if you prefer I can do a
bank transfer. This for airborne wind power research at KULeuven, but
I will pay out of pocket to avoid bureaucracy.

Please let me know if you are interested. Terms are negotiable.

Cheers,
Andrew

Ruben Smits's picture

Bounty for ROS-free soem components

I'll give it a go later tonight

;)

Ruben Smits, Phd
Chief Technology Officer
Intermodalics BVBA
+32479511786
www.intermodalics.eu

On Wed, Feb 20, 2013 at 3:18 PM, Andrew Wagner <drewm1980 [..] ...> wrote:

> Dear Orocos Community,
>
> I hereby offer a 100 euro bounty for someone to modify the build
> scripts for the soem orocos component(s) such that they do not depend
> on ROS.
>
> I believe the mainline repo is hosted here:
> http://git.mech.kuleuven.be/robotics/soem.git
>
> It contains four inter-dependent components: soem_core, soem_master,
> soem_ebox, and soem_beckhoff_drivers.
>
> Requirements:
> * The components build without ROS installed
> * The built components can still talk to an ebox (this hardware is
> rare; I can help test, but if they build, they probably work.)
> * The built components are still hard real-time (i.e. don't add any
> printf's or malloc's, etc... to the code)
> * Don't change the component interfaces unless necessary (i.e. please
> don't break our other components).
> * Don't break the build for ROS users
>
> If you are local, I can hand you cash, or if you prefer I can do a
> bank transfer. This for airborne wind power research at KULeuven, but
> I will pay out of pocket to avoid bureaucracy.
>
> Please let me know if you are interested. Terms are negotiable.
>
> Cheers,
> Andrew
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>

Bounty for ROS-free soem components

Hi Ruben!

Awesome, thanks!

I am username drewm1980 on skype if you want to chat in real time when
you give it a go.

Cheers,
Andrew

On Wed, Feb 20, 2013 at 4:42 PM, Ruben Smits
<ruben [dot] smits [..] ...> wrote:
> I'll give it a go later tonight
>
> ;)
>
> Ruben Smits, Phd
> Chief Technology Officer
> Intermodalics BVBAthat things has been done for all levels.

For instance I do sequentially :
_ the deployment of all components of all levels (hardware, motion
control, localisation).
_ the connection of ports with the rule "each component connects its
inputs, and never its outputs"
_ the configuration of all components.
_ the start of main managers that will start/stop groups of components.

So I have a main deployment script that is calling 4 hooks, one for
each step. Each hooks is calling the differents steps of the different
levels (with a manual dependency management : hardware before the
other,...). This is the "Robots System Builder" point of view.

The 4 hooks of the XXX level are in the same script. So from the "XXX
System Builder" point of view I provide an independant deployment.
This file is calling the hooks of different groups of componen
> +32479511786
> www.intermodalics.eu
>
>
> On Wed, Feb 20, 2013 at 3:18 PM, Andrew Wagner <drewm1980 [..] ...> wrote:
>>
>> Dear Orocos Community,
>>
>> I hereby offer a 100 euro bounty for someone to modify the build
>> scripts for the soem orocos component(s) such that they do not depend
>> on ROS.
>>
>> I believe the mainline repo is hosted here:
>> http://git.mech.kuleuven.be/robotics/soem.git
>>
>> It contains four inter-dependent components: soem_core, soem_master,
>> soem_ebox, and soem_beckhoff_drivers.
>>
>> Requirements:
>> * The components build without ROS installed
>> * The built components can still talk to an ebox (this hardware is
>> rare; I can help test, but if they build, they probably work.)
>> * The built components are still hard real-time (i.e. don't add any
>> printf's or malloc's, etc... to the code)
>> * Don't change the component interfaces unless necessary (i.e. please
>> don't break our other components).
>> * Don't break the build for ROS users
>>
>> If you are local, I can hand you cash, or if you prefer I can do a
>> bank transfer. This for airborne wind power research at KULeuven, but
>> I will pay out of pocket to avoid bureaucracy.
>>
>> Please let me know if you are interested. Terms are negotiable.
>>
>> Cheers,
>> Andrew
>> --
>> Orocos-Users mailing list
>> Orocos-Users [..] ...
>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>
>