[etherlab-users] "Invalid mailbox configuration", how to configure?

[Stefan Löfgren]

Aha!! I'm really new to this and therefor really slow and full of questions.
But I have a feeling you're absolutly right.
So, I took a look at the hexdump and fsm_slave.c again:


root at lablinux:~# hexdump /sys/ethercat/master0/slave000/eeprom
0000000 0009 0400 2710 0000 0000 0000 0000 0063
0000010 0014 0000 06c9 0000 0003 0000 0000 0000
0000020 0000 0000 0000 0000 0000 0000 0000 0000
0000030 0000 0000 0000 0000 0004 0000 0000 0000
0000040 0000 0000 0000 0000 0000 0000 0000 0000
*
0000070 0000 0000 0000 0000 0000 0000 0007 0001
0000080 0028 0001 0201 0029 0004 1800 0014 0026
0000090 0001 0029 0004 1832 0014 0022 0001 0029
00000a0 0004 1000 0008 0024 0001 0029 0004 1100
00000b0 0008 0020 0001 ffff
00000b8


Well, the SM-information is there right? (1800,14,261), (1832,14,22,1)
(1000,8,24,1) and (1100,8,10,1) and should be evaluated by 
ec_fsm_slave_scan_state_eeprom_data in the 
"evaluate category data"-section... But not working?

/S




---------- Original Message -----------
From: Phil Sutter <sutter at informatik.hs-furtwangen.de>
To: etherlab-users at lists.etherlab.org
Sent: Thu, 13 Mar 2008 20:37:06 +0100
Subject: Re: [etherlab-users] "Invalid mailbox configuration", how to configure?

> On Thu, Mar 13, 2008 at 08:08:31PM +0100, Stefan Löfgren wrote:
> > hmm... No, I have not been using TwinCAT at all, yet...
> > I changed the fsm_client.c to fill in the invalid data.
> > After reading the eeprom data I changed the values to the correct ones.
> > But this is not written back to the eeprom in the slave, right?
> > Anyway it still gives the same error: "Invalid mailbox config"...
> > The data needs to be written to the eeprom for the error to go away, right?
> > This error is actually produced in the slave, and therefor the eeprom needs to
> > be written, am I right? You said that there is a possibility to write the
> > eeprom via /sys/ethercat/master0/slave000/eeprom, how? Or do I need TwinCAT to
> > do this?
> 
> My slave works without having the data written back. Actually it 
> isn't possible at all to do that with it (because of size-limitation)
> . But maybe it works for your slave. With TwinCAT it should be 
> possible to save a binary EEPROM image including the data from the 
> XML. You can cat this file to the eeprom-attribute of your slave.
> 
> > "cat /sys/ethercat/master0/slave000/info" now gives:
> > 
> > Name:
> > Vendor ID: 0x00000014
> > Product code: 0x000006C9
> > 
> > State: INIT (PREOP)
> > Flags: online, ERROR
> > Ring position: 0
> > Current consumption: 0 mA
> > 
> > Data link status:
> >   Port 0 (unknown (255)) Link up, Loop open, Signal detected
> >   Port 1 (unknown (255)) Link down, Loop closed, No signal
> >   Port 2 (unknown (255)) Link down, Loop closed, No signal
> >   Port 3 (unknown (255)) Link down, Loop closed, No signal
> > 
> > Mailboxes:
> >   RX mailbox: 0x1832/20, TX mailbox: 0x1800/20
> >   Supported protocols: CoE
> > 
> > Sync managers / PDO mapping:
> >   SM0: addr 0x1100, size 8, control 0x20, enable
> >     No PDOs mapped.
> 
> To me this looks like you forgot to add the sync managers for your
> mailbox. Following an excerpt of of the same file on my system:
> 
> | Mailboxes:
> |   RX: 0x1000/128, TX: 0x1100/128
> |   Supported protocols: CoE
> | 
> | Sync managers / Pdo mapping:
> |   SM0: addr 0x1000, size 128, control 0x26, enable
> |     No Pdos mapped.
> |   SM1: addr 0x1100, size 128, control 0x22, enable
> |     No Pdos mapped.
> 
> I'm quite sure your XML contains Sm-entities for the registers 0x1832
> and 0x1800.
> 
> Greetings, Phil
> _______________________________________________
> etherlab-users mailing list
> etherlab-users at lists.etherlab.org
> http://lists.etherlab.org/mailman/listinfo/etherlab-users
------- End of Original Message -------