On Fri, Oct 03, 2008 at 10:30:27AM +0200, Erwin Burgstaller wrote: > The log entries, in case it doesn't work: > > 09:50:44 EtherCAT DEBUG: File opened. > 09:50:44 EtherCAT DEBUG: ioctl(filp = cb094bc0, cmd = 2150671360 (0), arg = > bfa80758) > 09:50:44 EtherCAT DEBUG: ioctl(filp = cb094bc0, cmd = 3241190401 (1), arg = > bfa80788) > 09:50:44 EtherCAT DEBUG: ioctl(filp = cb094bc0, cmd = 3222840332 (12), arg = > bfa80b34) > 09:50:47 EtherCAT DEBUG: Slave 1 did no respond to Sdo upload request. > Retrying after 2944 ms... > 09:50:47 EtherCAT DEBUG: Slave 1 did no respond to Sdo upload request. > Retrying after 2944 ms... > 09:50:47 EtherCAT DEBUG: Slave 1 did no respond to Sdo upload request. > Retrying after 2944 ms...
I just had a look at your logs again: What's really strange is, that the master seems to not even try to send the Sdo request in the first case (no 'Processing Sdo request...'). In the second case > 10:06:18 EtherCAT DEBUG: File opened. > 10:06:18 EtherCAT DEBUG: ioctl(filp = c78768c0, cmd = 2150671360 (0), arg = > bfac0fb8) > 10:06:18 EtherCAT DEBUG: ioctl(filp = c78768c0, cmd = 3241190401 (1), arg = > bfac0fe8) > 10:06:18 EtherCAT DEBUG: ioctl(filp = c78768c0, cmd = 3222840332 (12), arg = > bfac1394) > 10:06:18 EtherCAT DEBUG: Processing Sdo request for slave 1... > 10:06:18 EtherCAT DEBUG: Uploading Sdo 0x1C12:00 from slave 1. the request takes place immediately. Can you reproduce this in every case when 'manually' requesting the Sdos with the ethercat tool? If I understood you right, the only timeout problems happen in context of Sdo requests, is this correct? -- Best regards, Florian Pose http://etherlab.org _______________________________________________ etherlab-users mailing list etherlab-users@etherlab.org http://lists.etherlab.org/mailman/listinfo/etherlab-users