LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Opening a IEEE-1394 or USB port

Hi all,

I would like to use LABView 6.1 to talk to a flatbed scanner that can be
connected to either a IEEE 1394 or a USB port. I have the programing guide
for the scanner, but can't see how to open the port to communicate with the
device. Any suggestions?

Steve
0 Kudos
Message 1 of 3
(3,356 Views)
Steven,

LabVIEW cannot directly open or close a USB or FireWire port. You will need to call the Windows driver for those ports using the Call Library Function Node in the Advanced palette.
Also see the following KnowledgeBase 18964UWV: Can I Use Third-Party USB or IEEE 1394 (FireWire) Devices with LabVIEW?.

Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask
0 Kudos
Message 2 of 3
(3,356 Views)
Steven:

There are usually ways to work around these problems. I once wrote
some CIN code that let me control SCSI based data acquisition from
LabVIEW for Neff 500/620 and Neff 495 even though LV doesn't natively
support SCSI access.

A good book on USB "USB Complete" - Jan Axelson.

You might want to get a copy of that book. It comes with a CD-ROM
with sample code and it tells a lot about USB programming.

ISBN:0-9650819-3-1

According to this book you should be able to talk to a USB port using
just the Windows API calls in kernel32.dll: ReadFile, WriteFile, and
DeviceIOControl. You can access those from Visual Basic or Visual
C++. (Page 192)

I think you should also be able to access them from LabVIEW. I
haven't read all the way through this bo
ok but I have read some parts
of it and have it on my shelf.

By the way, Jan Axelson also has good books on serial and parallel
port programming called obviously enough "Serial Port Complete" and
"Parallel Port Complete".

Douglas De Clue
LabVIEW programmer
ddeclue@bellsouth.net


Randy H wrote in message news:<50650000000500000078930000-1027480788000@exchange.ni.com>...
> Steven,
>
> LabVIEW cannot directly open or close a USB or FireWire port. You will
> need to call the Windows driver for those ports using the Call Library
> Function Node in the Advanced palette.
> Also see the following
> href="http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/42b604435e3f9604862565e200...

.
>
> Randy Hoskin
> Applications Engineer
> National Instruments
> http://www.ni.com/ask
0 Kudos
Message 3 of 3
(3,356 Views)