Linux RH 6.2 & Edaq - driver

[Ari Lindroos]

Linux RH 6.2 & Edaq - driver

Few experiences Edaq for Linux installation.

- NationaI Instruments ftp area has latest
driver version 0.9.4
- edaq-0.9.4 turns (make gives some warnings).
- c- test programs ok (my card is 6025e).
- Labview for Linux 5.1 stops when the test
VI-program starts

I got however card operate like this:
I copied file /usr/lib/libedaq.so same
directory name /usr/lib/libnidaq.so
(some reason Labview VI's use this libnidaq.so file)

- after this Labview test programs operate
(fixed disk works much when running VI's?!)

- when starting Linux there comes the module depancies
error but programs operate however.


- has anyone same experiences from the installation
of the edaq-driver?
- have anyone find ot
her solutions?


[See first answer for additional information]

[Ari Lindroos]

[Attachment(s) for question]

[Johannes Niess]

Ari Lindroos writes:

> This is a multi-part message in MIME format.
> --------------785E686E5C689FEA7A506214
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> Linux RH 6.2 & Edaq - driver
>
> Few experiences Edaq for Linux installation.
>
> - NationaI Instruments ftp area has latest
> driver version 0.9.4
> - edaq-0.9.4 turns (make gives some warnings).
> - c- test programs ok (my card is 6025e).
> - Labview for Linux 5.1 stops when the test
> VI-program starts

Confirmed.

>
> I got however card operate like this:
> I copied file /usr/lib/libedaq.so same
> directory name /usr/lib/libnidaq.so
> (some reason Labview VI's use this libnidaq.so file)

Nice idea.

>
> - after this Labview test programs operate
> (
fixed disk works much when running VI's?!)

The linux driver sends a lot of syslog messages to
e. g. /var/log/messages.

>
> - when starting Linux there comes the module depancies
> error but programs operate however.
>
>
> - has anyone same experiences from the installation
> of the edaq-driver?
> - have anyone find other solutions?

[...]

[Johannes Niess]

I'm following up to myself as a summary for the archives.


Johannes Niess writes:

> Ari Lindroos writes:
>

[...]

> >
> > Linux RH 6.2 & Edaq - driver
> >
> > Few experiences Edaq for Linux installation.
> >
> > - NationaI Instruments ftp area has latest
> > driver version 0.9.4
> > - edaq-0.9.4 turns (make gives some warnings).
> > - c- test programs ok (my card is 6025e).
> > - Labview for Linux 5.1 stops when the test
> > VI-program starts
>
> Confirmed.
>
> >
> > I got however card operate like this:
> > I copied file /usr/lib/libedaq.so same
> > directory name /usr/lib/libnidaq.so
> > (some reason Labview VI's use this libnidaq.so file)
>
> Nice idea.

A symbolic link is a cleaner solution:

root@box:somedir # ln -s /usr/lib/libedaq.so /usr/lib/libnidaq.so

To get DIO to work you need to symlink (see above) /dev/nidio[0..x] to
/dev/edio[0..x]. Otherwise you get an "error -1" with no further
description. Devices are released after all VI's are closed. A better
solution for this minor issue is to release after each VI run.

It's even possible to get compatibility to DAQ with Windows. Stick to
the VI's that are available on both platforms (Most of their names
don't start with Linux...). Labview finds the VI's when the ni.llb
supplied with the driver is copied to the labview search path
(e. g. to the /usr/local/lv51/user.lib/ directory).

Don't include the ni.llb in the application directory tree. In that
case LV is too dumb: it loads a VI with the correct name but
probably from the wrong OS. This results in non-executable VI's. A
variation of this theme is "Save with Options / Include .llb files".

It looks like edaq 0.9.4 was released in the middle of a transition
between different library names and different device names. Most of
the .c files and some VI's lack commentary.

When these issues are resolved the driver is ready to be version
1.0.0. What about the Linux support for LV 6i? Is there official
support? What about DAQ?

>
> >
> > - after this Labview test programs operate
> > (fixed disk works much when running VI's?!)
>
> The linux driver sends a lot of syslog messages to
> e. g. /var/log/messages.

You can change the Makefile in the driver subdirectory to remove
debugging messages.

>
> >
> > - when starting Linux there comes the module depancies
> > error but programs operate however.
> >
> >
> > - has anyone same experiences from the installation
> > of the edaq-driver?
> > - have anyone find other solutions?
>
> [...]

Johannes Niess