- From: Ian Abbott <abbotti_at_mev.co.uk>
- Date: Mon, 18 Jun 2007 18:37:50 +0100
Paulo André Capellari wrote: > hmmm, so, a command terminates only when the "EOA" signal is sended by > the device?? Sort of. The command is marked as no longer running when the device signals an EOA event, or an error event. However, the subdevice remains "busy" until the data has been read. Looking at the code more closely, I think I was wrong earlier about having to do a final 'read' to complete the command. Still, the 'comedi_cancel' is a sure-fire way to prepare the subdevice to accept another command. > 2007/6/18, Ian Abbott <abbotti_at_mev.co.uk <mailto:abbotti_at_mev.co.uk>>: > > On 14/06/07 17:49, Paulo André Capellari wrote: > > I wont run simultaneously commands, but various in sequence: > > > > ... some configurations... > > comedi_command_test(dev_comedi, &cmd); > > comedi_command(dev_comedi, &cmd); > > > > ... > > some code > > .... > > (at this point, I'm sure that the previous command have been > terminated) > > > > ...another configurations... > > comedi_command_test(dev_comedi, &cmd); > > comedi_command(dev_comedi, &cmd); > > .... > > > > why only the first command executes? > > If it's a command on the 'read' subdevice, it may be waiting for you to > do a final 'read' to complete the command. This should return 0 to > indicate that the acquisition completed without error. > > Rather than do a final 'read', you could use the 'comedi_cancel' > function to terminate the previous command on the subdevice. > > -- > -=( Ian Abbott _at_ MEV Ltd. E-mail: <abbotti_at_mev.co.uk > <mailto:abbotti_at_mev.co.uk>> )=- > -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=- > > > > > -- > Paulo André > Ciência da Computação - Unioeste/PTI -- -=( Ian Abbott _at_ MEV Ltd. E-mail: <abbotti_at_mev.co.uk> )=- -=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
Received on 2007-06-18Z16:37:50