- From: Jan Klostermann <klostermann_at_rhf.de>
- Date: Thu, 14 Oct 2004 14:59:15 +0200
Hi Wee! It sounds that your program is crashing before. What happens if you out-comment the comedi_command() or if you just put in a pause with a printf()-line in front to see if it even reaches your comedi_command_test()? Dragging down to the point where it gets hung is the only way I see. Regarding the allowed command options you do not seem to have much choice. Just the flags mentioned in the output are allowed. To anything else it will respond with an error! Maybe that's the point. You do not check for the error and therefore run directly into the read() without a select() or poll() and this way the read() never comes back because there will no data arrive to be read. Good luck Jan -----Ursprüngliche Nachricht----- Von: comedi-admin_at_comedi.org [mailto:comedi-admin_at_comedi.org] Im Auftrag von Ong Wee Liat Gesendet: Donnerstag, 14. Oktober 2004 13:38 An: Jan Klostermann; comedi_at_comedi.org Betreff: RE: comedi_cmd Hi Jan, Thanks for your reply. I have tried what you said using the cmd.c inside /demo folder. With only the comedi_command_test() command in a program, it returned the following start: now 0 scan_begin: timer 1000000 (ns) convert: timer 5000 (ns) scan_end: count 1 stop: count 200 comedi command test returned 0 (success) The parameters that were returned are reflective of what i have set in the comedi_cmd structure. However, when i run a program with first a comedi_command_test() command followed by a comedi_command() command, my computer hanged once i started running it!!! Even the above output for comedi_command_test() did not appear. I am quite perplexed by this behaviour. Have you experienced anything like this before? I am using comedi-0.7.68 and comedilib-0.7.21 with a measurement computing card pcidas 6034. I suspect that somewhere in the driver is not behaving properly. Thanks wee -----Original Message----- From: Jan Klostermann [mailto:klostermann_at_rhf.de] Sent: Thursday, October 14, 2004 4:37 PM To: Ong Wee Liat; comedi_at_comedi.org Subject: AW: comedi_cmd Hi Wee! First of all, this depends a lot of the card and therefore the driver you use! Second point is that not all cards will support this kind of trigger for the start_src. I guess, if it is implemented in the driver it will probably be a hardware timer, if not otherwise stated in the driver description. To check if the driver supports this trigger send the command to comedi_command_test() and see what it answers - then you know, if it is going to work out at all... Jan -----Ursprüngliche Nachricht----- Von: comedi-admin_at_comedi.org [mailto:comedi-admin_at_comedi.org] Im Auftrag von Ong Wee Liat Gesendet: Donnerstag, 14. Oktober 2004 08:45 An: comedi_at_comedi.org Betreff: comedi_cmd Dear all, I am a little question on comedi_cmd(). I wonder when i put cmd->start_src=TRIG_TIMER and cmd->start_arg=1000000, is this timer a hardware timer or a software timer? Thanks wee _______________________________________________ comedi mailing list comedi_at_comedi.org https://cvs.comedi.org/cgi-bin/mailman/listinfo/comedi _______________________________________________ comedi mailing list comedi_at_comedi.org https://cvs.comedi.org/cgi-bin/mailman/listinfo/comedi
Received on 2004-10-14Z11:59:15