Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
new to labview
Redoo
Member
05-07-2002 11:07 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hi there. I'm totally a newbie learning labview. Now I'm trying to setup a
simple system measuring the laser pulse from two channels of a tektronix
684B osilliscope with a trigger pulse from another tektronix 520
osilliscope. Till now I have no questions but I'm pretty sure I'll have a
ton of when I start.
So thanks in advance!
redoo
simple system measuring the laser pulse from two channels of a tektronix
684B osilliscope with a trigger pulse from another tektronix 520
osilliscope. Till now I have no questions but I'm pretty sure I'll have a
ton of when I start.
So thanks in advance!
redoo
scraggs99
NI Employee (retired)
05-13-2002 10:44 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
You can definitely use LabVIEW to communicate with your Tektronix devices. Many instrument manufacturers have posted drivers for their instruments written in LabVIEW. I would recommend searching this online library at http://www.ni.com/devzone/idnet/. This will be the best place to start. If drivers exist then you will not have to worry much about lower level code. If LabVIEW drivers for your instrument do not exist then I would recommend beginning by using the examples for Instrument Communication which are shipped with LabVIEW. An understanding of the code in these examples and an understanding of your instruments function set should be sufficient to get you started.
Good luck!!
Good luck!!
-scraggs99
Anonymous
Active Participant
05-14-2002 04:07 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
scraggs99 wrote:
....
> Many instrument manufacturers have posted drivers for their
> instruments written in LabVIEW.
snip
> If drivers exist then you will not have to worry
> much about lower level code.
One of the things that is not very good with LabVIEW is that
in my opinion manufacturers post terrible drivers/documentation.
I someties have to have a look at RS-command level and read the
instrument RS-manual to find out what the vi's actually do.
Often I have to modify the drivers the make them work tolerably,
or the make work at all.
So for any serious project I would consider manufacturers drivers
to be an example to start with.
I think this situation is a big shame. I remember someone saying that
the drivers usually look like somebody's
first LV project. I think this
should not be the case.
Juha
....
> Many instrument manufacturers have posted drivers for their
> instruments written in LabVIEW.
snip
> If drivers exist then you will not have to worry
> much about lower level code.
One of the things that is not very good with LabVIEW is that
in my opinion manufacturers post terrible drivers/documentation.
I someties have to have a look at RS-command level and read the
instrument RS-manual to find out what the vi's actually do.
Often I have to modify the drivers the make them work tolerably,
or the make work at all.
So for any serious project I would consider manufacturers drivers
to be an example to start with.
I think this situation is a big shame. I remember someone saying that
the drivers usually look like somebody's
first LV project. I think this
should not be the case.
Juha
scraggs99
NI Employee (retired)
05-14-2002 09:15 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Admittedly, the instrument drivers are limited and strongly dependent on who coded them. However, some are quite good and I would still suggest it as a starting point for instrument communication. Especially when the applciation is simply to read from two channels on an O-Scope.
Of course, as with any instrument communication, it would help the programmer to understand the communication protocol and the instruments function set. If you want to have functionality beyond what an instrument driver provides, then yes, gaining an understanding of the function set and basic LabVIEW funcitons will be necessary. I would recommend using the VISA functions and examples.
Of course, as with any instrument communication, it would help the programmer to understand the communication protocol and the instruments function set. If you want to have functionality beyond what an instrument driver provides, then yes, gaining an understanding of the function set and basic LabVIEW funcitons will be necessary. I would recommend using the VISA functions and examples.
-scraggs99
Anonymous
Active Participant
05-14-2002 11:07 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
scraggs99 wrote:
> Admittedly, the instrument drivers are limited and strongly dependent
> on who coded them. However, some are quite good and I would still
> suggest it as a starting point for instrument communication.
> Especially when the applciation is simply to read from two channels on
> an O-Scope.
I agree with you. I was more just complaining in general. ( Just worked
with a not so good driver).
Juha
> Admittedly, the instrument drivers are limited and strongly dependent
> on who coded them. However, some are quite good and I would still
> suggest it as a starting point for instrument communication.
> Especially when the applciation is simply to read from two channels on
> an O-Scope.
I agree with you. I was more just complaining in general. ( Just worked
with a not so good driver).
Juha
