Cannot start Soem Component

Hello,

Today I had some problems with starting the Soem component. Configuring it goes well, but starting gives the following error:

Deployer [S]> loadComponent("Soem","soem_master::SoemMasterComponent")
58.561 [ Info   ][Thread] Creating Thread for scheduler: 0
58.562 [ Info   ][Soem] Thread created with scheduler type '0', priority 0 and period 0.
58.562 [ Info   ][DeploymentComponent::loadComponent] Adding Soem as new peer:  OK.
 = true                
 
Deployer [S]> Soem.configure 
61.769 [ Info   ][Soem] ec_init on eth0 succeeded.
62.066 [ Info   ][Soem] 14 slaves found and configured.
62.068 [ Info   ][Soem] Safe operational state reached for all slaves.
62.068 [ Info   ][Soem] Request operational state for all slaves
62.074 [ Info   ][Soem] Operational state reached for all slaves.
62.074 [ Warning][Soem] Could not create driver for EK1100
62.074 [ Warning][Soem] Could not create driver for EL5101
62.074 [ Warning][Soem] Could not create driver for EL5101
62.074 [ Warning][Soem] Could not create driver for EL5101
62.074 [ Warning][Soem] Could not create driver for EL5101
62.074 [ Warning][Soem] Could not create driver for EL5101
62.074 [ Warning][Soem] Could not create driver for EL5101
62.074 [ Warning][Soem] Could not create driver for EK1100
62.074 [ Info   ][Soem] Created driver for EL1008, with address 4105
62.074 [ Info   ][Soem] Put configured parameters in the slaves.
62.074 [ Info   ][Soem] Created driver for EL1008, with address 4106
62.075 [ Info   ][Soem] Put configured parameters in the slaves.
62.075 [ Info   ][Soem] Created driver for EL2008, with address 4107
62.075 [ Info   ][Soem] Put configured parameters in the slaves.
62.075 [ Info   ][Soem] Created driver for EL2008, with address 4108
62.075 [ Info   ][Soem] Put configured parameters in the slaves.
62.075 [ Info   ][Soem] Created driver for EL4038, with address 4109
62.075 [ Info   ][Soem] Put configured parameters in the slaves.
62.075 [ Warning][Soem] Could not create driver for EL3102
 = true                
 
Deployer [S]> Soem.start
 = true                
 
Deployer [S]> 67.881 [ ERROR  ][Soem] Time:1297947293.211 SDO slave:13 index:1c13.01 error:06090011 Subindex does not exist
 
67.881 [ ERROR  ][Soem] 
quit

The complete log is attached.

Anyone an idea what might be going on here? Also there are no ports created anymore for the slaves.

Thanks,

Tim

AttachmentSize
soem_error.txt14.06 KB
Ruben Smits's picture

Cannot start Soem Component

On Thursday 17 February 2011 13:59:58 t [dot] t [dot] g [dot] clephas [..] ... wrote:
> Hello,
>
> Today I had some problems with starting the Soem component. Configuring it
> goes well, but starting gives the following error:

> 
> Deployer [S]> loadComponent("Soem","soem_master::SoemMasterComponent")
> 58.561 [ Info   ][Thread] Creating Thread for scheduler: 0
> 58.562 [ Info   ][Soem] Thread created with scheduler type '0', priority 0
> and period 0.
 58.562 [ Info   ][DeploymentComponent::loadComponent] Adding
> Soem as new peer:  OK. = true
> 
> Deployer [S]> Soem.configure 
> 61.769 [ Info   ][Soem] ec_init on eth0 succeeded.
> 62.066 [ Info   ][Soem] 14 slaves found and configured.
> 62.068 [ Info   ][Soem] Safe operational state reached for all slaves.
> 62.068 [ Info   ][Soem] Request operational state for all slaves
> 62.074 [ Info   ][Soem] Operational state reached for all slaves.
> 62.074 [ Warning][Soem] Could not create driver for EK1100
> 62.074 [ Warning][Soem] Could not create driver for EL5101
> 62.074 [ Warning][Soem] Could not create driver for EL5101
> 62.074 [ Warning][Soem] Could not create driver for EL5101
> 62.074 [ Warning][Soem] Could not create driver for EL5101
> 62.074 [ Warning][Soem] Could not create driver for EL5101
> 62.074 [ Warning][Soem] Could not create driver for EL5101
> 62.074 [ Warning][Soem] Could not create driver for EK1100
> 62.074 [ Info   ][Soem] Created driver for EL1008, with address 4105
> 62.074 [ Info   ][Soem] Put configured parameters in the slaves.
> 62.074 [ Info   ][Soem] Created driver for EL1008, with address 4106
> 62.075 [ Info   ][Soem] Put configured parameters in the slaves.
> 62.075 [ Info   ][Soem] Created driver for EL2008, with address 4107
> 62.075 [ Info   ][Soem] Put configured parameters in the slaves.
> 62.075 [ Info   ][Soem] Created driver for EL2008, with address 4108
> 62.075 [ Info   ][Soem] Put configured parameters in the slaves.
> 62.075 [ Info   ][Soem] Created driver for EL4038, with address 4109
> 62.075 [ Info   ][Soem] Put configured parameters in the slaves.
> 62.075 [ Warning][Soem] Could not create driver for EL3102
>  = true                
> 
> Deployer [S]> Soem.start
>  = true                
> 
> Deployer [S]> 67.881 [ ERROR  ][Soem] Time:1297947293.211 SDO slave:13
> index:1c13.01 error:06090011 Subindex does not exist
 
I've seen this error before too, but it never caused the master to not start.


I see you directly quit the application, can you verify if the Master is 
indeed not started?

Is the bottom-left led of your coupler blinking?


> 67.881 [ ERROR  ][Soem] 
> quit
>
>
> The complete log is attached.
>
> Anyone an idea what might be going on here?
> Also there are no ports created anymore for the slaves.

For me everything is still working.

> Thanks,
>
> Tim
>
-- Ruben

Cannot start Soem Component

On Thu, 2011-02-17 at 15:04 +0100, Ruben Smits wrote:
> On Thursday 17 February 2011 13:59:58 t [dot] t [dot] g [dot] clephas [..] ... wrote:
> > Hello,
> >
> > Today I had some problems with starting the Soem component. Configuring it
> > goes well, but starting gives the following error:
>
> > 
> > Deployer [S]> loadComponent("Soem","soem_master::SoemMasterComponent")
> > 58.561 [ Info   ][Thread] Creating Thread for scheduler: 0
> > 58.562 [ Info   ][Soem] Thread created with scheduler type '0', priority 0
> > and period 0.
>  58.562 [ Info   ][DeploymentComponent::loadComponent] Adding
> > Soem as new peer:  OK. = true
> > 
> > Deployer [S]> Soem.configure 
> > 61.769 [ Info   ][Soem] ec_init on eth0 succeeded.
> > 62.066 [ Info   ][Soem] 14 slaves found and configured.
> > 62.068 [ Info   ][Soem] Safe operational state reached for all slaves.
> > 62.068 [ Info   ][Soem] Request operational state for all slaves
> > 62.074 [ Info   ][Soem] Operational state reached for all slaves.
> > 62.074 [ Warning][Soem] Could not create driver for EK1100
> > 62.074 [ Warning][Soem] Could not create driver for EL5101
> > 62.074 [ Warning][Soem] Could not create driver for EL5101
> > 62.074 [ Warning][Soem] Could not create driver for EL5101
> > 62.074 [ Warning][Soem] Could not create driver for EL5101
> > 62.074 [ Warning][Soem] Could not create driver for EL5101
> > 62.074 [ Warning][Soem] Could not create driver for EL5101
> > 62.074 [ Warning][Soem] Could not create driver for EK1100
> > 62.074 [ Info   ][Soem] Created driver for EL1008, with address 4105
> > 62.074 [ Info   ][Soem] Put configured parameters in the slaves.
> > 62.074 [ Info   ][Soem] Created driver for EL1008, with address 4106
> > 62.075 [ Info   ][Soem] Put configured parameters in the slaves.
> > 62.075 [ Info   ][Soem] Created driver for EL2008, with address 4107
> > 62.075 [ Info   ][Soem] Put configured parameters in the slaves.
> > 62.075 [ Info   ][Soem] Created driver for EL2008, with address 4108
> > 62.075 [ Info   ][Soem] Put configured parameters in the slaves.
> > 62.075 [ Info   ][Soem] Created driver for EL4038, with address 4109
> > 62.075 [ Info   ][Soem] Put configured parameters in the slaves.
> > 62.075 [ Warning][Soem] Could not create driver for EL3102
> >  = true                
> > 
> > Deployer [S]> Soem.start
> >  = true                
> > 
> > Deployer [S]> 67.881 [ ERROR  ][Soem] Time:1297947293.211 SDO slave:13
> > index:1c13.01 error:06090011 Subindex does not exist
>  
> I've seen this error before too, but it never caused the master to not start.
> 
> 
> I see you directly quit the application, can you verify if the Master is 
> indeed not started?

Ah, you're right. The SoemMaster is indeed started and running. Despite
the error.

And if I set a period, it is working as well.

However I still don't get any dataports. Only services.

<code>
Soem [R]> ls

 Listing TaskContext Soem[R] :

 Configuration Properties: 
     string ifname         = eth0                 (interface to which
the ethercat device is connected)

 Provided Interface:
  Attributes   : (none)
  Operations      : activate cleanup configure displayAvailableDrivers
error getPeriod inFatalError inRunTimeError isActive isConfigured
isRunning setPeriod start stop trigger update 

 Data Flow Ports: (none)

 Services: 
      Slave_1002 ( Services for Beckhoff EL5101 Encoder module ) 
      Slave_1003 ( Services for Beckhoff EL5101 Encoder module ) 
      Slave_1004 ( Services for Beckhoff EL5101 Encoder module ) 
      Slave_1005 ( Services for Beckhoff EL5101 Encoder module ) 
      Slave_1006 ( Services for Beckhoff EL5101 Encoder module ) 
      Slave_1007 ( Services for Beckhoff EL5101 Encoder module ) 
      Slave_1009 ( Services for Beckhoff EL1008 Dig. Input module ) 
      Slave_100a ( Services for Beckhoff EL1008 Dig. Input module ) 
      Slave_100b ( Services for Beckhoff EL2008 Dig. Output module ) 
      Slave_100c ( Services for Beckhoff EL2008 Dig. Output module ) 
      Slave_100d ( Services for Beckhoff EL4038 module ) 

 Requires Operations :  (none)
 Requests Services   :  (none)

 Peers        : (none)


>
> Is the bottom-left led of your coupler blinking?
>
>
> > 67.881 [ ERROR ][Soem]
> > quit
> > </code>
> >
> > The complete log is attached.
> >
> > Anyone an idea what might be going on here?
> > Also there are no ports created anymore for the slaves.
>
> For me everything is still working.
>
>
> > Thanks,
> >
> > Tim
> >
> -- Ruben

Tim

Ruben Smits's picture

Cannot start Soem Component

On Thursday 17 February 2011 15:24:15 Tim Clephas wrote:
> On Thu, 2011-02-17 at 15:04 +0100, Ruben Smits wrote:
>
> > On Thursday 17 February 2011 13:59:58 t [dot] t [dot] g [dot] clephas [..] ...
> > wrote:
> >
> > > Hello,
> > >
> > > Today I had some problems with starting the Soem component.
> > > Configuring it
> > >goes well, but starting gives the following error:
> >
> >
> >
> > > &#10;&gt; &gt; &gt; Deployer [S]&gt;&#10;&gt; &gt; &gt; loadComponent(&quot;Soem&quot;,&quot;soem_master::SoemMasterComponent&quot;)&#10;&gt; &gt; &gt; 58.561 [ Info   ][Thread] Creating Thread for scheduler: 0&#10;&gt; &gt; &gt; 58.562 [ Info   ][Soem] Thread created with scheduler type &#039;0&#039;,&#10;&gt; &gt; &gt; priority 0&#10;&gt; &gt; &gt; and period 0.&#10;&gt; &gt;  &#10;&gt; &gt;  58.562 [ Info   ][DeploymentComponent::loadComponent] Adding&#10;&gt; &gt;  &#10;&gt; &gt; &gt; Soem as new peer:  OK. = true&#10;&gt; &gt; &gt; &#10;&gt; &gt; &gt; Deployer [S]&gt; Soem.configure &#10;&gt; &gt; &gt; 61.769 [ Info   ][Soem] ec_init on eth0 succeeded.&#10;&gt; &gt; &gt; 62.066 [ Info   ][Soem] 14 slaves found and configured.&#10;&gt; &gt; &gt; 62.068 [ Info   ][Soem] Safe operational state reached for all&#10;&gt; &gt; &gt; slaves.&#10;&gt; &gt; &gt; 62.068 [ Info   ][Soem] Request operational state for all slaves&#10;&gt; &gt; &gt; 62.074 [ Info   ][Soem] Operational state reached for all slaves.&#10;&gt; &gt; &gt; 62.074 [ Warning][Soem] Could not create driver for EK1100&#10;&gt; &gt; &gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; &gt; &gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; &gt; &gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; &gt; &gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; &gt; &gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; &gt; &gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; &gt; &gt; 62.074 [ Warning][Soem] Could not create driver for EK1100&#10;&gt; &gt; &gt; 62.074 [ Info   ][Soem] Created driver for EL1008, with address&#10;&gt; &gt; &gt; 4105&#10;&gt; &gt; &gt; 62.074 [ Info   ][Soem] Put configured parameters in the slaves.&#10;&gt; &gt; &gt; 62.074 [ Info   ][Soem] Created driver for EL1008, with address&#10;&gt; &gt; &gt; 4106&#10;&gt; &gt; &gt; 62.075 [ Info   ][Soem] Put configured parameters in the slaves.&#10;&gt; &gt; &gt; 62.075 [ Info   ][Soem] Created driver for EL2008, with address&#10;&gt; &gt; &gt; 4107&#10;&gt; &gt; &gt; 62.075 [ Info   ][Soem] Put configured parameters in the slaves.&#10;&gt; &gt; &gt; 62.075 [ Info   ][Soem] Created driver for EL2008, with address&#10;&gt; &gt; &gt; 4108&#10;&gt; &gt; &gt; 62.075 [ Info   ][Soem] Put configured parameters in the slaves.&#10;&gt; &gt; &gt; 62.075 [ Info   ][Soem] Created driver for EL4038, with address&#10;&gt; &gt; &gt; 4109&#10;&gt; &gt; &gt; 62.075 [ Info   ][Soem] Put configured parameters in the slaves.&#10;&gt; &gt; &gt; 62.075 [ Warning][Soem] Could not create driver for EL3102&#10;&gt; &gt; &gt; &#10;&gt; &gt; &gt;  = true                &#10;&gt; &gt; &gt; &#10;&gt; &gt; &gt; &#10;&gt; &gt; &gt; Deployer [S]&gt; Soem.start&#10;&gt; &gt; &gt; &#10;&gt; &gt; &gt;  = true                &#10;&gt; &gt; &gt; &#10;&gt; &gt; &gt; &#10;&gt; &gt; &gt; Deployer [S]&gt; 67.881 [ ERROR  ][Soem] Time:1297947293.211 SDO&#10;&gt; &gt; &gt; slave:13&#10;&gt; &gt; &gt; index:1c13.01 error:06090011 Subindex does not exist&#10;&gt; &gt;  &#10;&gt; &gt;  &#10;&gt; &gt; &#10;&gt; &gt; I&#039;ve seen this error before too, but it never caused the master to not&#10;&gt; &gt; start.&#10; &#10;&gt; &gt; &#10;&gt; &gt; I see you directly quit the application, can you verify if the Master is&#10;&gt; &gt; &#10;&gt; &gt; indeed not started?&#10;&gt; &#10;&gt; &#10;&gt; Ah, you&#039;re right. The SoemMaster is indeed started and running. Despite&#10;&gt; the error.&#10;&gt; &#10;&gt; And if I set a period, it is working as well.&#10;&gt; &#10;&gt; However I still don&#039;t get any dataports. Only services.&#10;&#10;The ports are inside the slave services, because this leads to a much cleaner &#10;interface. Try e.g. &#039;ls Slave_1009&#039;&#10;&#10;&gt; &lt;code&gt;&#10;&gt; Soem [R]&gt; ls&#10;&gt; &#10;&gt;  Listing TaskContext Soem[R] :&#10;&gt; &#10;&gt;  Configuration Properties: &#10;&gt;      string ifname         = eth0                 (interface to which&#10;&gt; the ethercat device is connected)&#10;&gt; &#10;&gt;  Provided Interface:&#10;&gt;   Attributes   : (none)&#10;&gt;   Operations      : activate cleanup configure displayAvailableDrivers&#10;&gt; error getPeriod inFatalError inRunTimeError isActive isConfigured&#10;&gt; isRunning setPeriod start stop trigger update &#10;&gt; &#10;&gt;  Data Flow Ports: (none)&#10;&gt; &#10;&gt;  Services: &#10;&gt;       Slave_1002 ( Services for Beckhoff EL5101 Encoder module ) &#10;&gt;       Slave_1003 ( Services for Beckhoff EL5101 Encoder module ) &#10;&gt;       Slave_1004 ( Services for Beckhoff EL5101 Encoder module ) &#10;&gt;       Slave_1005 ( Services for Beckhoff EL5101 Encoder module ) &#10;&gt;       Slave_1006 ( Services for Beckhoff EL5101 Encoder module ) &#10;&gt;       Slave_1007 ( Services for Beckhoff EL5101 Encoder module ) &#10;&gt;       Slave_1009 ( Services for Beckhoff EL1008 Dig. Input module ) &#10;&gt;       Slave_100a ( Services for Beckhoff EL1008 Dig. Input module ) &#10;&gt;       Slave_100b ( Services for Beckhoff EL2008 Dig. Output module ) &#10;&gt;       Slave_100c ( Services for Beckhoff EL2008 Dig. Output module ) &#10;&gt;       Slave_100d ( Services for Beckhoff EL4038 module ) &#10;&gt; &#10;&gt;  Requires Operations :  (none)&#10;&gt;  Requests Services   :  (none)&#10;&gt; &#10;&gt;  Peers        : (none)&#10;&gt;
>

-- Ruben

Cannot start Soem Component

Yes I did,

I don't have a lot of time right now, but I suggest you take a look at this deployer file:
https://amigo.wtb.tue.nl/svn/amigo/code/tue-ros-pkg/trunk/tue_actuation/...

It makes use of the soem.git from leuven.

The remainder of the components that is loaded in this ops file can be found in this ros-package:
https://amigo.wtb.tue.nl/svn/amigo/code/tue-ros-pkg/trunk/tue_actuation/...

Tim

-----Oorspronkelijk bericht-----
Van: gianni borghesan [mailto:Gianni [dot] Borghesan [..] ...]
Verzonden: donderdag 14 april 2011 19:21
Aan: Clephas, T.T.G.
Onderwerp: Re: [Orocos-users] Cannot start Soem Component

Hello,
Did you get any luck in the end of making use of encoders readers
EL5101?
Gianni.

Il giorno gio, 17/02/2011 alle 13.59 +0100, t [dot] t [dot] g [dot] clephas [..] ...
ha scritto:
> Hello,
>
> Today I had some problems with starting the Soem component. Configuring it goes well, but starting gives the following error:
>
> &#10;&gt; Deployer [S]&gt; loadComponent(&quot;Soem&quot;,&quot;soem_master::SoemMasterComponent&quot;)&#10;&gt; 58.561 [ Info   ][Thread] Creating Thread for scheduler: 0&#10;&gt; 58.562 [ Info   ][Soem] Thread created with scheduler type &#039;0&#039;, priority 0 and period 0.&#10;&gt; 58.562 [ Info   ][DeploymentComponent::loadComponent] Adding Soem as new peer:  OK.&#10;&gt;  = true                &#10;&gt; &#10;&gt; Deployer [S]&gt; Soem.configure &#10;&gt; 61.769 [ Info   ][Soem] ec_init on eth0 succeeded.&#10;&gt; 62.066 [ Info   ][Soem] 14 slaves found and configured.&#10;&gt; 62.068 [ Info   ][Soem] Safe operational state reached for all slaves.&#10;&gt; 62.068 [ Info   ][Soem] Request operational state for all slaves&#10;&gt; 62.074 [ Info   ][Soem] Operational state reached for all slaves.&#10;&gt; 62.074 [ Warning][Soem] Could not create driver for EK1100&#10;&gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; 62.074 [ Warning][Soem] Could not create driver for EK1100&#10;&gt; 62.074 [ Info   ][Soem] Created driver for EL1008, with address 4105&#10;&gt; 62.074 [ Info   ][Soem] Put configured parameters in the slaves.&#10;&gt; 62.074 [ Info   ][Soem] Created driver for EL1008, with address 4106&#10;&gt; 62.075 [ Info   ][Soem] Put configured parameters in the slaves.&#10;&gt; 62.075 [ Info   ][Soem] Created driver for EL2008, with address 4107&#10;&gt; 62.075 [ Info   ][Soem] Put configured parameters in the slaves.&#10;&gt; 62.075 [ Info   ][Soem] Created driver for EL2008, with address 4108&#10;&gt; 62.075 [ Info   ][Soem] Put configured parameters in the slaves.&#10;&gt; 62.075 [ Info   ][Soem] Created driver for EL4038, with address 4109&#10;&gt; 62.075 [ Info   ][Soem] Put configured parameters in the slaves.&#10;&gt; 62.075 [ Warning][Soem] Could not create driver for EL3102&#10;&gt;  = true                &#10;&gt; &#10;&gt; Deployer [S]&gt; Soem.start&#10;&gt;  = true                &#10;&gt; &#10;&gt; Deployer [S]&gt; 67.881 [ ERROR  ][Soem] Time:1297947293.211 SDO slave:13 index:1c13.01 error:06090011 Subindex does not exist&#10;&gt; &#10;&gt; 67.881 [ ERROR  ][Soem] &#10;&gt; quit&#10;&gt;
>
> The complete log is attached.
>
> Anyone an idea what might be going on here?
> Also there are no ports created anymore for the slaves.
>
> Thanks,
>
> Tim
>

R: Cannot start Soem Component

Thanks!

________________________________________
Da: Clephas, T.T.G. [t [dot] t [dot] g [dot] clephas [..] ...]
Inviato: giovedì 14 aprile 2011 19.30
A: Gianni Borghesan
Cc: orocos-users [..] ...
Oggetto: RE: [Orocos-users] Cannot start Soem Component

Yes I did,

I don't have a lot of time right now, but I suggest you take a look at this deployer file:
https://amigo.wtb.tue.nl/svn/amigo/code/tue-ros-pkg/trunk/tue_actuation/...

It makes use of the soem.git from leuven.

The remainder of the components that is loaded in this ops file can be found in this ros-package:
https://amigo.wtb.tue.nl/svn/amigo/code/tue-ros-pkg/trunk/tue_actuation/...

Tim

-----Oorspronkelijk bericht-----
Van: gianni borghesan [mailto:Gianni [dot] Borghesan [..] ...]
Verzonden: donderdag 14 april 2011 19:21
Aan: Clephas, T.T.G.
Onderwerp: Re: [Orocos-users] Cannot start Soem Component

Hello,
Did you get any luck in the end of making use of encoders readers
EL5101?
Gianni.

Il giorno gio, 17/02/2011 alle 13.59 +0100, t [dot] t [dot] g [dot] clephas [..] ...
ha scritto:
> Hello,
>
> Today I had some problems with starting the Soem component. Configuring it goes well, but starting gives the following error:
>
> &#10;&gt; Deployer [S]&gt; loadComponent(&quot;Soem&quot;,&quot;soem_master::SoemMasterComponent&quot;)&#10;&gt; 58.561 [ Info   ][Thread] Creating Thread for scheduler: 0&#10;&gt; 58.562 [ Info   ][Soem] Thread created with scheduler type &#039;0&#039;, priority 0 and period 0.&#10;&gt; 58.562 [ Info   ][DeploymentComponent::loadComponent] Adding Soem as new peer:  OK.&#10;&gt;  = true&#10;&gt;&#10;&gt; Deployer [S]&gt; Soem.configure&#10;&gt; 61.769 [ Info   ][Soem] ec_init on eth0 succeeded.&#10;&gt; 62.066 [ Info   ][Soem] 14 slaves found and configured.&#10;&gt; 62.068 [ Info   ][Soem] Safe operational state reached for all slaves.&#10;&gt; 62.068 [ Info   ][Soem] Request operational state for all slaves&#10;&gt; 62.074 [ Info   ][Soem] Operational state reached for all slaves.&#10;&gt; 62.074 [ Warning][Soem] Could not create driver for EK1100&#10;&gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; 62.074 [ Warning][Soem] Could not create driver for EK1100&#10;&gt; 62.074 [ Info   ][Soem] Created driver for EL1008, with address 4105&#10;&gt; 62.074 [ Info   ][Soem] Put configured parameters in the slaves.&#10;&gt; 62.074 [ Info   ][Soem] Created driver for EL1008, with address 4106&#10;&gt; 62.075 [ Info   ][Soem] Put configured parameters in the slaves.&#10;&gt; 62.075 [ Info   ][Soem] Created driver for EL2008, with address 4107&#10;&gt; 62.075 [ Info   ][Soem] Put configured parameters in the slaves.&#10;&gt; 62.075 [ Info   ][Soem] Created driver for EL2008, with address 4108&#10;&gt; 62.075 [ Info   ][Soem] Put configured parameters in the slaves.&#10;&gt; 62.075 [ Info   ][Soem] Created driver for EL4038, with address 4109&#10;&gt; 62.075 [ Info   ][Soem] Put configured parameters in the slaves.&#10;&gt; 62.075 [ Warning][Soem] Could not create driver for EL3102&#10;&gt;  = true&#10;&gt;&#10;&gt; Deployer [S]&gt; Soem.start&#10;&gt;  = true&#10;&gt;&#10;&gt; Deployer [S]&gt; 67.881 [ ERROR  ][Soem] Time:1297947293.211 SDO slave:13 index:1c13.01 error:06090011 Subindex does not exist&#10;&gt;&#10;&gt; 67.881 [ ERROR  ][Soem]&#10;&gt; quit&#10;&gt;
>
> The complete log is attached.
>
> Anyone an idea what might be going on here?
> Also there are no ports created anymore for the slaves.
>
> Thanks,
>
> Tim
>

Cannot start Soem Component

On Thu, 2011-02-17 at 15:24 +0100, Tim Clephas wrote:
> On Thu, 2011-02-17 at 15:04 +0100, Ruben Smits wrote:
> > On Thursday 17 February 2011 13:59:58 t [dot] t [dot] g [dot] clephas [..] ... wrote:
> > > Hello,
> > >
> > > Today I had some problems with starting the Soem component. Configuring it
> > > goes well, but starting gives the following error:
> >
> > > &#10;&gt; &gt; &gt; Deployer [S]&gt; loadComponent(&quot;Soem&quot;,&quot;soem_master::SoemMasterComponent&quot;)&#10;&gt; &gt; &gt; 58.561 [ Info   ][Thread] Creating Thread for scheduler: 0&#10;&gt; &gt; &gt; 58.562 [ Info   ][Soem] Thread created with scheduler type &#039;0&#039;, priority 0&#10;&gt; &gt; &gt; and period 0.&#10;&gt; &gt;  58.562 [ Info   ][DeploymentComponent::loadComponent] Adding&#10;&gt; &gt; &gt; Soem as new peer:  OK. = true&#10;&gt; &gt; &gt; &#10;&gt; &gt; &gt; Deployer [S]&gt; Soem.configure &#10;&gt; &gt; &gt; 61.769 [ Info   ][Soem] ec_init on eth0 succeeded.&#10;&gt; &gt; &gt; 62.066 [ Info   ][Soem] 14 slaves found and configured.&#10;&gt; &gt; &gt; 62.068 [ Info   ][Soem] Safe operational state reached for all slaves.&#10;&gt; &gt; &gt; 62.068 [ Info   ][Soem] Request operational state for all slaves&#10;&gt; &gt; &gt; 62.074 [ Info   ][Soem] Operational state reached for all slaves.&#10;&gt; &gt; &gt; 62.074 [ Warning][Soem] Could not create driver for EK1100&#10;&gt; &gt; &gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; &gt; &gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; &gt; &gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; &gt; &gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; &gt; &gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; &gt; &gt; 62.074 [ Warning][Soem] Could not create driver for EL5101&#10;&gt; &gt; &gt; 62.074 [ Warning][Soem] Could not create driver for EK1100&#10;&gt; &gt; &gt; 62.074 [ Info   ][Soem] Created driver for EL1008, with address 4105&#10;&gt; &gt; &gt; 62.074 [ Info   ][Soem] Put configured parameters in the slaves.&#10;&gt; &gt; &gt; 62.074 [ Info   ][Soem] Created driver for EL1008, with address 4106&#10;&gt; &gt; &gt; 62.075 [ Info   ][Soem] Put configured parameters in the slaves.&#10;&gt; &gt; &gt; 62.075 [ Info   ][Soem] Created driver for EL2008, with address 4107&#10;&gt; &gt; &gt; 62.075 [ Info   ][Soem] Put configured parameters in the slaves.&#10;&gt; &gt; &gt; 62.075 [ Info   ][Soem] Created driver for EL2008, with address 4108&#10;&gt; &gt; &gt; 62.075 [ Info   ][Soem] Put configured parameters in the slaves.&#10;&gt; &gt; &gt; 62.075 [ Info   ][Soem] Created driver for EL4038, with address 4109&#10;&gt; &gt; &gt; 62.075 [ Info   ][Soem] Put configured parameters in the slaves.&#10;&gt; &gt; &gt; 62.075 [ Warning][Soem] Could not create driver for EL3102&#10;&gt; &gt; &gt;  = true                &#10;&gt; &gt; &gt; &#10;&gt; &gt; &gt; Deployer [S]&gt; Soem.start&#10;&gt; &gt; &gt;  = true                &#10;&gt; &gt; &gt; &#10;&gt; &gt; &gt; Deployer [S]&gt; 67.881 [ ERROR  ][Soem] Time:1297947293.211 SDO slave:13&#10;&gt; &gt; &gt; index:1c13.01 error:06090011 Subindex does not exist&#10;&gt; &gt;  &#10;&gt; &gt; I&#039;ve seen this error before too, but it never caused the master to not start.&#10;&gt; &gt; &#10;&gt; &gt; &#10;&gt; &gt; I see you directly quit the application, can you verify if the Master is &#10;&gt; &gt; indeed not started?&#10;&gt; &#10;&gt; Ah, you&#039;re right. The SoemMaster is indeed started and running. Despite&#10;&gt; the error.&#10;&gt; &#10;&gt; And if I set a period, it is working as well.&#10;&gt; &#10;&gt; However I still don&#039;t get any dataports. Only services.&#10;&gt; &#10;&gt; &lt;code&gt;&#10;&gt; Soem [R]&gt; ls&#10;&gt; &#10;&gt;  Listing TaskContext Soem[R] :&#10;&gt; &#10;&gt;  Configuration Properties: &#10;&gt;      string ifname         = eth0                 (interface to which&#10;&gt; the ethercat device is connected)&#10;&gt; &#10;&gt;  Provided Interface:&#10;&gt;   Attributes   : (none)&#10;&gt;   Operations      : activate cleanup configure displayAvailableDrivers&#10;&gt; error getPeriod inFatalError inRunTimeError isActive isConfigured&#10;&gt; isRunning setPeriod start stop trigger update &#10;&gt; &#10;&gt;  Data Flow Ports: (none)&#10;&gt; &#10;&gt;  Services: &#10;&gt;       Slave_1002 ( Services for Beckhoff EL5101 Encoder module ) &#10;&gt;       Slave_1003 ( Services for Beckhoff EL5101 Encoder module ) &#10;&gt;       Slave_1004 ( Services for Beckhoff EL5101 Encoder module ) &#10;&gt;       Slave_1005 ( Services for Beckhoff EL5101 Encoder module ) &#10;&gt;       Slave_1006 ( Services for Beckhoff EL5101 Encoder module ) &#10;&gt;       Slave_1007 ( Services for Beckhoff EL5101 Encoder module ) &#10;&gt;       Slave_1009 ( Services for Beckhoff EL1008 Dig. Input module ) &#10;&gt;       Slave_100a ( Services for Beckhoff EL1008 Dig. Input module ) &#10;&gt;       Slave_100b ( Services for Beckhoff EL2008 Dig. Output module ) &#10;&gt;       Slave_100c ( Services for Beckhoff EL2008 Dig. Output module ) &#10;&gt;       Slave_100d ( Services for Beckhoff EL4038 module ) &#10;&gt; &#10;&gt;  Requires Operations :  (none)&#10;&gt;  Requests Services   :  (none)&#10;&gt; &#10;&gt;  Peers        : (none)&#10;&gt;
>

My bad, they are just not listed. It came down to a typo of mine.

Tim

> >
> > Is the bottom-left led of your coupler blinking?
> >
> >
> > > 67.881 [ ERROR ][Soem]
> > > quit
> > > </code>
> > >
> > > The complete log is attached.
> > >
> > > Anyone an idea what might be going on here?
> > > Also there are no ports created anymore for the slaves.
> >
> > For me everything is still working.
> >
> >
> > > Thanks,
> > >
> > > Tim
> > >
> > -- Ruben
>
> Tim
>
>