configure device

what to put in my startup scripts

Hi,

I've seen several different instructions about what to put in the startup 
scripts to configure Comedi.  But I'm not sure I understood any of them well 
enough to try them out.  So for the last few weeks I've been doing that 
manually in the terminal.  I'm using RH Linux without RTAI/RTLinux.  I have an 
NI-6036E board.

Here's what I type in my terminal upon startup whenever I'm using Comedi.

# ./sbin/modprobe ni_pcimio
# ./sbin/ldconfig
# cd /usr/local/comedilib-0.7.22
# ./configure --disable-ruby-binding --disable-python-binding
# make
# make install
# cd comedi_config
# ./comedi_config /dev/comedi0 ni_pcimio
# cd ../comedi_calibrate
# ./comedi_calibrate

1) If you can, please tell me exactly, or almost exactly, what I need to put 
in my startup scripts, and where.

2) This is just a general C programming question, but I haven't gotten it to 
work based on the information I have.  How do I run comedi_calibrate from 
within my acquisition code?

Thanks very much.

Heather

what to put in my startup scripts

Hi,

I've seen several different instructions about what to put in the startup 
scripts to configure Comedi.  But I'm not sure I understood any of them well 
enough to try them out.  So for the last few weeks I've been doing that 
manually in the terminal.  I'm using RH Linux without RTAI/RTLinux.  I have an 
NI-6036E board.

Here's what I type in my terminal upon startup whenever I'm using Comedi.

# ./sbin/modprobe ni_pcimio
# ./sbin/ldconfig
# cd /usr/local/comedilib-0.7.22
# ./configure --disable-ruby-binding --disable-python-binding
# make
# make install
# cd comedi_config
# ./comedi_config /dev/comedi0 ni_pcimio
# cd ../comedi_calibrate
# ./comedi_calibrate

1) If you can, please tell me exactly, or almost exactly, what I need to put 
in my startup scripts, and where.

2) This is just a general C programming question, but I haven't gotten it to 
work based on the information I have.  How do I run comedi_calibrate from 
within my acquisition code?

Thanks very much.

Heather

RE: what to put in my startup scripts

Stephen,

Sorry, but I'm a relative newbie to Linux.

1) By "developers", are you referring to the different login names?  All (two) 
of us need to have access to it.

2) What is in the stop part?

3) What files do these (stop & start) belong in?

Do these six lines really have the same effect as my "modprobe", "configure", 
"make", "make install" and "comedi_config"?  If so, that would be really nice.

Thanks,

Heather

>===== Original Message From Stephen Roderick <roderick <at> ssl.umd.edu> =====
>After building and installing the kernel module, we do nothing more
>than the following in a startup script (this is the start part, there
>is a similar stop part)
>
>COMEDI_CONFIG=/path/to/bin/comedi_config
>DEVICE=ni_pcimio
>
>         /sbin/modprobe ${DEVICE}
>         ${COMEDI_CONFIG} /dev/comedi0 ${DEVICE}
>         chmod g+rw /dev/comedi*
>         chgrp ourgroup /dev/comedi*
>
>Where "ourgroup" is the group of developers needing access to the
>device. The node /dev/comedi is already created, but you might have to
>add a 'mknod /dev/comedi' (or similar) line also.
>
>HTH
>S
>
>On Jul 1, 2006, at 10:25, hhumphre wrote:
>
>> Hi,
>>
>> I've seen several different instructions about what to put in the
>> startup
>> scripts to configure Comedi.  But I'm not sure I understood any of
>> them well
>> enough to try them out.  So for the last few weeks I've been doing that
>> manually in the terminal.  I'm using RH Linux without RTAI/RTLinux.  I
>> have an
>> NI-6036E board.
>>
>> Here's what I type in my terminal upon startup whenever I'm using
>> Comedi.
>>
>> # ./sbin/modprobe ni_pcimio
>> # ./sbin/ldconfig
>> # cd /usr/local/comedilib-0.7.22
>> # ./configure --disable-ruby-binding --disable-python-binding
>> # make
>> # make install
>> # cd comedi_config
>> # ./comedi_config /dev/comedi0 ni_pcimio
>> # cd ../comedi_calibrate
>> # ./comedi_calibrate
>>
>> 1) If you can, please tell me exactly, or almost exactly, what I need
>> to put
>> in my startup scripts, and where.
>>
>> 2) This is just a general C programming question, but I haven't gotten
>> it to
>> work based on the information I have.  How do I run comedi_calibrate
>> from
>> within my acquisition code?
>>
>> Thanks very much.
>>
>> Heather

RE: configure device

Re: first timer question

On 30/06/2006 15:28, Adrian T Sindile wrote:
> Hello,
> After compiling Fedora Core 5 kernel-2.6.17, I downloaded comedi and 
> comedilib:
> 
> drwxrwxr-x  7 adrian adrian    4096 Apr  2  2005 comedi-0.7.70
> -rw-rw-r--  1 adrian adrian 3266560 Jun 29 14:16 comedi-0.7.70.tar
> drwxrwxr-x 15 adrian adrian    4096 Oct  2  2004 comedilib-0.7.22
> -rw-rw-r--  1 adrian adrian 4904960 Jun 29 14:16 comedilib-0.7.22.tar

Use the current version of comedi from CVS because comedi-0.7.70 is too 
old for your kernel.  You can follow the instructions for anonymous CVS 
access or download a snapshot from here:
<http://www.comedi.org/cgi-bin/viewcvs.cgi/comedi.tar.gz?view=tar>
The above link was obtained by following the "Browse CVS repository" 
link on the download page, then following the link to the "comedi/" 
directory, then selecting the "Download tarball" link at the bottom.  Do 
not download the "Current Comedi CVS snapshot" link on the main download 
page as it will just screw you up (it needs fixing!).

After unpacking the comedi.tar.gz snapshot (or following the anonymous 
CVS instructions to check it out of the CVS repository), run 
./autogen.sh to generate the configure script and other files.  As 
autogen.sh also runs the configure script it generates, you can pass any 
configure command-line options to autogen.sh.  As you are a first timer, 
it will be better to run ./configure again separately with the correct 
options.  At the moment, you will need at least the --enable-kbuild and 
--disable-pcmcia options:

   ./autogen.sh
   ./configure --enable-kbuild --disable-pcmcia

(Or to do both steps at once:

   ./autogen.sh --enable-kbuild --disable-pcmcia

)

You probably won't need any --with-linuxdir option if you are building 
for the current kernel.  The --enable-kbuild option should take care of it.

You should then be able to run 'make' and 'make install'.

It is possible you may have further problems building, but at least I've 
filtered out the things that I know don't work!  If you have any more 
problems building it, please reply to the list, or at least Cc the list. 
(There's no need to reply to me directly as I'll see it on the list.)

--

-- 
-=( Ian Abbott  <at>  MEV Ltd.    E-mail: <abbotti <at> mev.co.uk>        )=-
-=( Tel: +44 (0)161 477 1898   FAX: +44 (0)161 718 3587         )=-

Re: configure device

On 01/07/2006 12:10, sailendra sethi wrote:
> i have a servo controller card [16 bit] that controls the 6DOF 
> manipulator Arm on serial port.
> i want to write a driver for servo controller in linux2.6 with comedi. i 
> installed Comedi-0.7.70 and comedilib-0.7.22.

If you are planning to write a driver, please base it on the current CVS 
version of Comedi.

> Most of  cards like NI, AD Link,DT etc support PCI /ISA Bus , we can see 
> that by cat /proc/comedi.
> 
> Can i configure the servo controller card with out PCI /ISA in comedi..

In principle, you can use any bus you like. For exanple, there are some 
USB and PCMCIA devices supported by Comedi.

So do you connect to the controller card over a serial port?  If so you 
could base your driver on the serial2002 driver, but that driver has 
been marked with the status "in development" since 2002, so might not be 
much help, especially for 2.6 kernels.

--

-- 
-=( Ian Abbott  <at>  MEV Ltd.    E-mail: <abbotti <at> mev.co.uk>        )=-
-=( Tel: +44 (0)161 477 1898   FAX: +44 (0)161 718 3587         )=-

Re: USBDUX-fast with Matlab

Hi!

qtscope has a simple ASCII export option which can be loaded into MATLAB with 
the "load" command. You can also use the simple program "cmd" in the demo 
directory to load data into MATLAB.

I've cc'ed to Sven who is using the fast board to load data into MATLAB. He's 
modified "cmd" a bit so that it generates a file which can be loaded into 
MATLAB. Contact him for the source code.

Regards
/Bernd Porr

http://www.linux-usb-daq.co.uk/
Mobile: +44 (0)7840 340069
Work:   +44 (0)141 330 5237

Cang Ye wrote:
> Dear Sir/Madam,
> 
> I am interested in USBDUX-fast. I'd like to ask if Matlab (Linux version)
> can use this device to acquire data.
> 
> Thanks,
> 
> -----------------------------------------
> Cang Ye
> Assistant Professor
> Department of Applied Science
> College of Information Science & Systems Engineering 
> University of Arkansas at Little Rock
> 2801 South University Avenue, ETAS 575
> Little Rock, AR 72204
> Ph:  (501) 683-7284 Fax: (501) 569-8020 
> Email: cxye <at> ualr.edu
> Webpage: http://www.ualr.edu/cxye
>  
> 
> 
> 

Re: problem installing cvs comedi

Hello Alessandro,

On 30/06/06 15:44, Alessandro Toso wrote:
> Hi all,
> 
> I'm trying to install the cvs version of comedi and comedilib. While
> with comedilib everything works fine, when I enter in the comedi
> directory and run "sh autogen.sh" I get this error message:
> 
> checking Linux major/minor version... 2.6
> checking for Linux CFLAGS... ./configure: line
> 4499: /usr/local/comedi/./confstatf11072/flags: No such file or
> directory
> 
> I think that the problem is that autogen.sh makes a mistake in
> generating the "configure" script. Line 4499 is:
> 
> ${MAKE-make} -C ${LINUX_DIR} V=1 SUBDIRS=${tmpdir} LINUXDIR=${LINUX_DIR}
> MODVERDIR=${tmpdir} modules >&5 2>&5
>         . ${tmpdir}/flags
> 
> and there shoudn't be a carriage return after 2>&5. The correct
> instruction is:
> 
> ${MAKE-make} -C ${LINUX_DIR} V=1 SUBDIRS=${tmpdir} LINUXDIR=${LINUX_DIR}
> MODVERDIR=${tmpdir} modules >&5 2>&5 . ${tmpdir}/flags
> 
> I hope this is the correct way to avoid the problem (I tryed and it
> works).

No that's wrong.  Could you restore it as it was and post the section of
the config.log file from "checking for Linux CFLAGS" onwards?  That
would show where the error occurred.  It looks like the make command run
by that test failed before it created the ${tmpdir}/flags file.

The test is trying to build a dummy module in the ${tmpdir} directory,
and create the ${tmpdir}/flags file as a side effect.  The following ".
${tmpdir}/flags" command is trying to source the contents of created
${tmpdir}/flags file into the current shell.  The "." command is failing
because ${tmpdir}/flags file doesn't exist, because the preceding make
command failed to create it for some reason.

--

-- 
-=( Ian Abbott  <at>  MEV Ltd.    E-mail: <abbotti <at> mev.co.uk>        )=-
-=( Tel: +44 (0)161 477 1898   FAX: +44 (0)161 718 3587         )=-

Re: using the parallel port