Re: Question about digital i/o cmd buffer data format in new driver

From: Berns J. Buenaobra <bbuenaobra_at_nip.upd.edu.ph> · Date: Mon, 31 Jan 2005 12:54:50 +0000 (UTC)

Hello I am new to this list. Recently I moved to LV7 Express Linux version
because of the wanting of Ph.D. surpervisor to Mandrake 10.1.

I followed the instructions in the web site for COMEDI and with the help of
my friend compiled them successfully!

I just want to be enlightened:

Q1: There will be no VIs that will  be added to the pallete with this
drivers?
Q2: Do you have to code in ANSI-C to execute Data Acquisition?
Q3: You have to code the CIN for custom palettes for you to work in LabVIEW?

Are these questions correct?

Berns B.

----- Original Message ----- 
From: "Jan Gukelberger" <g.u.g.i_at_gmx.de>
To: "Bernd Porr" <BerndPorr_at_f2s.com>
Cc: <comedi_at_comedi.org>
Sent: Sunday, January 30, 2005 2:16 PM
Subject: Re: Question about digital i/o cmd buffer data format in new driver

> On Fri, 2005-01-28 at 10:39 +0000, Bernd Porr wrote:
> > How fast do you need it? The DUX board is theoretically able to do it.
> > The endpoint EP1 is suitbale for that. Would be 1kHz under USB 1.1 and
> > 8kHz under 2.0.
>
> 1kHz would be the minimum requirement, faster is welcome but at the
> moment not really needed. The concept looks interesting though we need
> more than 8 + 8 IN lines so we'd have to use several boxes on each
> system.
>
> > Has to run then on a second comedi device because the
> > analogue channels are using streaming already. Would be also possible to
> > do a "soft PWM" with it. I'm just now busy with other stuff but I'll
> > look into it. Has been on my todo list for quite a while.
>
> PWM? (sorry, I'm no daq expert)
>
> Yes, all in all those boxes would really be a consideration worth. How
> much work would it be to setup a second device?
>
> > /Bernd
>
> Thanks,
> Jan
>
>
> _______________________________________________
> comedi mailing list
> comedi_at_comedi.org
> https://cvs.comedi.org/cgi-bin/mailman/listinfo/comedi
>