Cannot start Soem Component

Submitted by Tim on Thu, 2011-02-17 12:59

Orocos-users

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

Attachment	Size
soem_error.txt	14.06 KB

Cannot start Soem Component

Submitted by Ruben Smits on Thu, 2011-02-17 14:08.

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

Submitted by Tim on Thu, 2011-02-17 14:28.

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
> >
> >
> > 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

Cannot start Soem Component

Submitted by Ruben Smits on Thu, 2011-02-17 14:44.

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:
> >
> >
> >
> > >

> > > 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.
 
The ports are inside the slave services, because this leads to a much cleaner 
interface. Try e.g. 'ls Slave_1009'
 
> <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)
>

-- Ruben

Cannot start Soem Component

Submitted by Tim on Thu, 2011-04-14 17:40.

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:
>
>

> 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
>

R: Cannot start Soem Component

Submitted by gianni borghesan on Thu, 2011-04-14 18:28.

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

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

> 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
>

Cannot start Soem Component

Submitted by Tim on Thu, 2011-02-17 14:40.

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:
> >
> > >

> > > 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)
>

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
> > >
> > >
> > > 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
>
>

The Orocos Project

Cannot start Soem Component

Cannot start Soem Component

Cannot start Soem Component

Cannot start Soem Component

Cannot start Soem Component

R: Cannot start Soem Component

Cannot start Soem Component