2013/6/10 Ruben Smits <ruben [dot] smits [..] ...>

> Hi Flavian,
>
>
> On Mon, Jun 10, 2013 at 11:20 AM, <f [dot] hautbois [..] ...> wrote:
>
>> I have two EtherCAT slaves: EK1100 and EL3104.
>>
>> I am running the test.ops script inside the soem_master folder. Now I have
>> two issues:
>> 1- the displayAllDrivers command doesn't display anything.
>>
>
> Can you retry by running with the loglevel on Info:
>
> deployer -s test.ops -linfo, this should show you the available drivers,
> including the one for the EL3104
>
> If it still shows nothing make sure you have build the
> soem_beckhoff_drivers package
>
> note that we do not have drivers for all devices yet.
>

OK I seem to need to explicitely build the soem_beckhoff package.
There is something that is bugging me. You have the soem folder which has
the soem_master subfolder, the soem_beckhoff_drivers subfolder, etc.
Do you _really_ need to run rosmake in each folder? I thought the stack.xml
+ CMakeLists + Makefile took care of that for you.
I have to admit I had to build explicitely soem_master before in order for
it to work, so I should have thought of doing the same with the other ones.

Anyway, the drivers are now installed and the service is created.

>
>
> 2- when I run the configure command inside the Master component, this
>> happens:
>> >[Info]2 slaves found and configured
>> >[Info]Request pre-operational state for all slaves
>> >[Master] Could not create driver for EK1100
>>
>
> The EK1100 is the EtherCAT coupler for which we do not have a driver yet
> since noone really needed it.
>

Is there anything interesting you can control on this one anyway?

>
>
>> >[Master] Could not create driver for EL3104
>>
> So for some reason the devices are detected, but the Soem_Driver_Factory
>> class fails at adding them (line 87 of the soem_master_component.cpp file
>> ;
>> can be found here ).
>>
>> Is there something I overlooked? A bug in the source code? An option I
>> haven't set?
>>
>
> Setting the loglevel and make sure you have build the
> soem_beckhoff_drivers package should do it.
>

Interesting you should mention the -linfo option on the deployer. I used
another way to set the loglevel by setting the environment variable
ORO_LEVEL to 6.

>
>>
>> Thank you in advance.
>>
>
> Ruben
>
>>
>> Flavian
>> --
>> Orocos-Users mailing list
>> Orocos-Users [..] ...
>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>>
>
>
>
> --
> Ruben Smits, Phd
> Chief Technology Officer
> Intermodalics BVBA
> +32479511786
> www.intermodalics.eu
>