Re: What does the "range" variable do in comedi_data_read ?

No, the ranges are board-dependent.  There are some functions in comedilib
for querying what each range actually corresponds to, and how many ranges
the board supports.

Frank

On Fri, 31 May 2002, Nicolas Cottaris wrote:

> Hello Comedi-users,
>
> Can somebody tell me what  does the "range" variable do in the
> comedi_data_read function?
> Does it set the channel gain to pow(10, range)? It only works with
> values 0,1,2,3. After that I get
> an invalid channel range error.
>
>
> Nicolas
>
>
>
> _______________________________________________
> comedi mailing list
> comedi <at> stm.lbl.gov
> http://stm.lbl.gov/cgi-bin/mailman/listinfo/comedi
>

Re: Using comedi_parport to catch interrupts in real-time?

You are talking about using scan_begin_src == TRIG_EXT for the
comedi_parport driver?  Did you register your callback with the
COMEDI_CB_EOS event in the mask?

Frank

On Fri, 31 May 2002, John Sims wrote:

> Has anyone used comedi_parport to catch interrupts via pin 10 of the parallel
> port?  I have the demo ledclock program running un user space, and it catches
> interrupts just fine.  However, if  I take the same command settings, device,
> subdevice settings, etc and put them in a real-time module, and attempt to
> have a callback invoked, nothing happens.
>
> Any thoughts?
>
> John
>
>
> _______________________________________________
> comedi mailing list
> comedi <at> stm.lbl.gov
> http://stm.lbl.gov/cgi-bin/mailman/listinfo/comedi
>

Problems with DAS-16

Looking for ideas.....

I have a system collecting data at 1000 scans per second 
(16000 samples/sec) using a PC104-DAS16jr/16.  It has been
working great since March.  (last check on uptime showed 
42 days).  

I'm trying to get the same set of programs to run on a different
computer with a CIO-DAS16jr.  The system even has a close clone 
of the disk on the other system.  This system does not work.
I've changed the comedi_config command to reflect the change 
in the board. 

If I input say a 30Hz sine wave on channel 0 and ground the 
remaining 15 inputs, I do not get the 30Hz signal on channel 
0 with the CIO-DAS16jr. The signal is scattered over at least 
3 of the 15 other channels.  If I put a PC104-DAS16jr/16 on an
ISA adapter and do the same test with the same cables things 
are fine.  If I try a CIO-DAS16jr/16, the collection hangs during
the setup. ( This board only has a 10MHz master clock going to
the 8254. The Clock parameter is required wiht comedi_config.)

This looks a lot like a problem I had with the PC104-DAS16jr/16 
years ago. With a long cable (5+ feet) the sample clock (cntr 2 out)
would pick up enough ringing to false trigger the MUX counter.  The 
quick fix was to cut the wire at the board end of the cable.  
ComputerBoards/MeasurementComputing claims that it was fixed in 
an later revision of the board.  The cables I'm using have this
line (pin 20 on the DB37) cut.  

RE: What does the "range" variable do in comedi_data_read ?

> Can somebody tell me what  does the "range" variable do in the
> comedi_data_read function?
> Does it set the channel gain to pow(10, range)? It only works with
> values 0,1,2,3. After that I get
> an invalid channel range error.

It depends on your board.  Most boards have multiple voltage ranges that
they read from, and this selects which ranges it uses.  On my PCI-6023
board, it breaks down like this:

Range 0: [-10V to 10V]
Range 1: [-5 V to 5V]
Range 2: [-1 V to 1V]
Range 3: [-.5V to .5V]

At least I think it does - I may be off on those last ranges.   Yours will
vary based on what manufacturer and part # of board you have.  Use the
'info' demo program with comedilib to find out what ranges your analog in is
capable of.

Caleb

PCIM-DDA06/16 Driver?

  Is there a driver for the board PCIM-DDA06/16 from computerboards (6x D/A
at 16 bits) ? I think someone was asking a similar question a short while
ago, but I don't remember the answer. 

    Thanks,

Igal Brener

PCI-DIO-96 problems

Hello -

We're working on setting up a small data acquistion system using Comedi,
and we've run into problems that we could use some help with. (comedi
v.0.7.64 and comedilib v0.7.18)

We've purchased two data acquisition cards: a Nat. Inst. PCI-6025E multi
I/O card which (so far) works fine, and a Nat. Inst. PCI-DIO-96 which is
misbehaving quite badly.

Any code that outputs to the PCI-DIO-96 doesn't appear to do anything
physical. All of the bits are stuck high (5V). However, if I write
values to the board, and then switch the channel to an 'input', and read
back, the values read back are the values that were written. It's just
that we don't see that on the actual output of the board.

8255 support is compiled into comedi: we increased the log level to 4
and do not see any problems being reported. In the system log, comedi
outputs "comedi: subdevice 0 does not support commands" for all
subdevices of the PCI-DIO-96 (0,1,2,3: substitute the number in) but
only once per time we run the program (It must happen during the
'comedi_open' routine, but I don't know where...). Anyway, this
shouldn't be a problem since I'm not using commands, just
comedi_dio_write and comedi_dio_read.

I'm including the test code here, followed by as much information as I
could get. If any more is needed, let me know.

=======================================================================
This code is just a framework for trying to figure out if anything is

Re: PCI-DIO-96 problems

On Mon, Jun 03, 2002 at 03:34:08PM -0400, Patrick Allison wrote:
> Hello -
> 
> We're working on setting up a small data acquistion system using Comedi,
> and we've run into problems that we could use some help with. (comedi
> v.0.7.64 and comedilib v0.7.18)
> 
> We've purchased two data acquisition cards: a Nat. Inst. PCI-6025E multi
> I/O card which (so far) works fine, and a Nat. Inst. PCI-DIO-96 which is
> misbehaving quite badly.
> 
> Any code that outputs to the PCI-DIO-96 doesn't appear to do anything
> physical. All of the bits are stuck high (5V). However, if I write
> values to the board, and then switch the channel to an 'input', and read
> back, the values read back are the values that were written. It's just
> that we don't see that on the actual output of the board.

Since the 8255 is working on the PCI-6025E, the likely cause of the
problem is either nidio96_8255_cb() in ni_pcidio.c, or the
initialization code for the board.  nidio96_8255_cb() appears
to be doing the correct thing according to the manual.

Are driven inputs read correctly?

Otherwise, everything appears to be ok.

dave...

RE: PCIM-DDA06/16 Driver?

Igal,
	Calin is developing a driver in the next few weeks for this card. He
also has this card and will post the driver code and place it in CM for all
of us, soon.

> >-----Original Message-----
> >From: Igal Brener [mailto:ibrener <at> tellium.com]
> >Sent: Monday, June 03, 2002 2:21 PM
> >To: comedi <at> stm.lbl.gov
> >Subject: PCIM-DDA06/16 Driver?
> >
> >
> >
> >  Is there a driver for the board PCIM-DDA06/16 from 
> >computerboards (6x D/A
> >at 16 bits) ? I think someone was asking a similar question 
> >a short while
> >ago, but I don't remember the answer. 
> >
> >
> >    Thanks,
> >
> >Igal Brener
> >
> >
> >
> >_______________________________________________
> >comedi mailing list
> >comedi <at> stm.lbl.gov
> >http://stm.lbl.gov/cgi-bin/mailman/listinfo/comedi

Re: PCI-DIO-96 problems

On Mon, 2002-06-03 at 16:14, David Schleef wrote:
> Since the 8255 is working on the PCI-6025E, the likely cause of the
> problem is either nidio96_8255_cb() in ni_pcidio.c, or the
> initialization code for the board.  nidio96_8255_cb() appears
> to be doing the correct thing according to the manual.
> 
> Are driven inputs read correctly?
> 
> Otherwise, everything appears to be ok.

re: driven inputs -

No, not as far as we can tell - driving the inputs to ground causes them
to still read back as "1". Basically it seems that whatever we do to the
external connector on the PCI-DIO-96 doesn't seem to do anything from
Comedi's point of view.

Patrick

Multi channels scanning