NI-scope labview vi's

Hi,
I installed the NI-5112 scope card today (it was bought a few years ago). I'm using labview 8.0.
I also installed the NI-Scope 3.4 driver.
I can't find any labview VIs. On the installation disk the examples are only for c.
Where can I find the library with the scope VIs (niScope Initialize.vi, niScope Initiate.vi, etc.) ?
Thank you

Hello Eyal,
The NI-SCOPE VIs can be found within LabVIEW, as Dennis mentioned, within the functions palette on the block diagram under Instrument I/O » Instrument Drivers » NI-SCOPE or under Measurement I/O » NI-SCOPE. Additionally, they should appear in a folder under your Windows start menu by navigating to Start » Programs » National Instruments » NI-SCOPE »Examples » LabVIEW 8.0. If the examples are not appearing in this folder, I would be interested in knowing what does appear under the NI-SCOPE folder.
Additionally, you may try going into Measurement and Automation Explorer (MAX), clicking the software button on the left under the Configuration » My System tree, and then clicking the Change/Remove Software button (please see first image below). This will bring up a dialog with a long list of National Instruments software. If you select NI-SCOPE 3.4, you can then select the Modify button to the right and this will bring up a list of what is installed from the driver as far as support for each development environment. Please ensure that LabVIEW 8.0 support has been installed here.
For your particular version of LabVIEW, you will want to stay with NI-SCOPE 3.4 as the newer versions of NI-SCOPE 3.5.x do not contain support for LabVIEW 8.0 (current versions of DAQmx do not support LV 8.0). Hope this helps,
Daniel S.
National Instruments

Similar Messages

5112 Vamplitude -vs- Vp-p

I have a 5401 arb in a pxi chassis dumping a +/- 1.0 V sine wave directly to a 5112 scope in the same pxi chassis through a coax. Using the scope function for Vp-p I see 2.125V, using the function for Vamplitude I see 1.925. What's the difference between the two functions?
[email protected]

Hi Brad,
You can find the difference between these two measurements in the High Speed Digitizers Help under Programming >> Reference >> NI-SCOPE LabVIEW Reference Help >> Scalar Measurements.
The Voltage Peak to Peak measurement is:
"The maximum voltage minus the minimum voltage in volts."
The Voltage Amplitude is:
"The voltage high minus the voltage low in volts. "
Furthermore, you can find the definition for voltage high and voltage low in the same section of the help document.
Voltage High:
"The last-acquisition histogram method is used, where the voltage high result is the voltage of the histogram bin with the maximum number of hits above 60% of the waveform's voltage peak-to-peak value. This calculation is useful for ignoring the overshoot and preshoot on square waves. "
Voltage Low:
"The last-acquisition histogram method is used, where the voltage low result is the voltage of the histogram bin with the maximum number of hits below 40% of the waveform's voltage peak-to-peak value. This calculation is useful for ignoring the overshoot and preshoot on square waves. "
I hope this helps. Please let me know if you have any further questions.
Regards,
Sean Close
Product Support Engineer: High Speed Digitizers

Crosstalk test system

Hello,
I am trying to figure out a way to build crosstalk test system using the following HW/SW:
- 8- HP8133A: pulse gens (upto 8 driven lines)
- TDS8000 scope
- Labview 7.1
- Test vehicle (MoBo+daughter card)
- cables
Obviously, it would be necessary to "de-skew" and confirm both 1)"pulse timing" and 2)rise-time input to DUT. (before actually measure crosstalk)
The final goals are:
- To test both single-ended and differential channel signal(s)
- To have range of 1 to 8 driven lines
- To save instrument state for pulse and test settings
- To display crosstalk plots on scope or screen capture(?)
- To generate automatic crosstalk (NEXT/FEXT) report (for spreadsheet)
I would appreciate your advice/help, sharing similar experience for pointing me into the right direction.
Best regards,

jjlee,
I have never built a system like the one you described, but I did find that there are instrument drivers for the HP8133A, and the TDS8000 on www.ni.com/idnet. They might at least provide a place for you to start, and if you run into problems along the way others might be able to help with the specific problems you encounter.
Shawn B.
National Instruments
Use NI products on Linux? Come join the NI Linux Users Community

Auto Setup a four channel oscilloscope using two NI 5112 boards

I have two NI 5112 boards and want to design a four channel oscilloscope supporting auto setup.
I refer to the "niScope EX Getting Started.vi". I have studied the "niScope Initialize" and "niScope Auto Setup" in the "NI SCOPE VI Reference Help".
The "niScope Auto Setup" generates no trigger output. Would it still be possible to auto setup a four channel synchronized display using two NI 5112 boards?
How can I using property nodes or by other means find out:
1. If there is a signal present on ch0 and what vertical range "niScope Auto Setup" has setup?
2. If there is a signal present on ch1 and what vertical range "niScope Auto Setup" has setup?
3. If there is no signal on a certain channel?
I
intend to use and modify the �niScope EX 5112 Synchronization.vi�

There are no NI-SCOPE functions to automatically do an autosetup on two synchronized 5112s. However, you can use niScope Auto Setup.vi on each of the 5112s individually, then reset the slave trigger parameters back to digital with the proper source. The other synch parameters (clock out/in, synch pulse, trigger out) should not be effected by the auto setup.
If the autosetup routine cannot find a signal on either channel, it will return a warning. If autosetup cannot detect a signal on a particular channel, it will set the lowest possible vertical range. To find out if there is a signal on a particular channel, take a short data set and look at it. NI-SCOPE does not provide a way to get this information any other way. If you know your signals wi
ll always produce a range greater than the smallest range of the 5112, you can use the vertical range as the way of telling that no signal was detected.
You can query almost any current parameter from the driver using property nodes. The vertical range is channel specific, so first set the Active Channel, then query for Vertical->Vertical Range. A word of warning when querying parameters. NI-SCOPE is IVI compliant, so the values you get from querying the property nodes are based on the IVI specification, not the NI-SCOPE LabVIEW API. Sources will always be strings and some properties have the same format, but different mappings. For example, the trigger slope in the LabVIEW API is mapped 0-positive, 1-negative. If queried from the property node, 0 is negative and 1 is positive due to the IVI spec. There are not many of these. You can easily find them by looking in the block diagram of the set VIs for look-up tables (array constants).
Good luck! If you
still need more help, post a reply
This account is no longer active. Contact ShadesOfGray for current posts and information.

NI-scope driver is not listed in the labview functions!!

Hi everyone,
I’m using High speed digitizer (NI 5922) and I want to take the data programmatically with the Labview 8.5. my problem is that I can NOT find the NI-Scope driver in the function palette of the labview and I found only one driver with “Agilent 34401” which I don’t need, Although everything is OK with the MAX (the driver passed the self test and I can run the SCOPE SOFT FRONT Panel).
Thank you for your kind concern,
Best,
Ibrahim
Solved!
Go to Solution.

Hello Ibrahim,
the current version of NI-SCOPE (3.8.7) does only support Labview 8.6.1 and higher (-> http://joule.ni.com/nidu/cds/view/p/id/2681/lang/en). After a little research the latest supporting version I could find is 3.3.2 ( -> http://joule.ni.com/nidu/cds/view/p/id/883/lang/en), but you may have some problems when using Win7.
Hope I could help,
Oliver

HP/Agilent Infiniium 54831B scope - how to connect with LabView 6.0 by LAN (TCP/IP)

Dear,
I'm looking inf. how to connect Agilent Infiniium 54831B scope with LabView 6.0 by LAN (TCP/IP).
Thanks in advance.
Regards,
Z.Mrowka
mailto:[email protected]

Hello,
If the instrument is capable of being controlled from its TCP/IP port, it will be possible to communicate with the instrument from LabVIEW using VISA.
The VISA resource name input will need to be entered manually and is a little different from the normal Serial or GPIB format. The format is as follows:
For SOCKET connections, this is just like the traditional TCP functionality in LabVIEW. An example string that connects with the NI FTP site is:
"TCPIP::ftp.ni.com::21:OCKET"
For INSTR connection, this requires a device that supports the T&M standard LAN instrument protocol. An example of this (that we have tested with) is the Tektronix 3054 Scope. A string that connects with this scope is: "TCPIP::HostnameOrIP::gpib0,1::INSTR"
I hope this
helps,
Anthony Bacak
National Instruments
Applications Engineering

Is there any concept in LabVIEW that is similar to static local scope variables in C?

I'd like to retain the value between calls to a subVI, as can be done using a static function scoped variable in C. The textbook example of how this is used would be a variable in the function that is a state machine, and knows what state it was in last time it was executed. A simpler example would be just keeping count of how many times the function has been called.
I suppose I could use a global or I could pass values in and out of the subVI, but I'd like to keep the variable known only in the scope of the subVI if at all possible. For example, the outside world has no business knowing (or god forbid) changing what the state information of this function is.

Bmarsh wrote:
> I'd like to retain the value between calls to a subVI, as can be done
> using a static function scoped variable in C. The textbook example of
> how this is used would be a variable in the function that is a state
> machine, and knows what state it was in last time it was executed. A
> simpler example would be just keeping count of how many times the
> function has been called.
>
> I suppose I could use a global or I could pass values in and out of
> the subVI, but I'd like to keep the variable known only in the scope
> of the subVI if at all possible. For example, the outside world has
> no business knowing (or god forbid) changing what the state
> information of this function is.
There is no need to do something "conceptual" or spec
ific to have this
static variable. You already have this in any control or indicator in
your sub-vi while it is in memory. Control/indicator value will remain
in sub-vi data space between calls. Don't forget about make your sub-vi
non-reentrant or keep track of sub-vi data space copies.
If you want to read/write this value from another vi, consider it global
or I'd prefer to suggest using functional global(uninitialized shift
register in 1 iteration while loop). Think of it as about 1 value data
repository.
LabVIEW CIN reference manual is a good place to look at, as well as
LabVIEW course kits, describing LabVIEW memory issues in details.
To simplify: create empty sub-vi with control and indicator connected to
each other and call it wiring indicator in caller vi. Keep sub-vi front
panel open and change control in sub-vi manually. You see what happens.
Sergey Krasnishov
Automated Control Systems
National Instruments Alliance Member
Mos
cow, Russia
[email protected]
http://acs.levsha.ru

Intel Hyper-Threading Technology conflicts with LabVIEW utilities (VISA, Scope GUI, IO Trace...)

I would like to share a pretty hard-to-troubleshoot issue we are experiencing for the last few months.
Our company used to get DELL T5500 for our engineers. The PCs work just fine with all LabVIEW utilities. But DELL has discontinued T5500 series and replace them with T5600. I got one of them few months ago and after installing LabVIEW, I tried to run VISA console via MAX. It immediately crashes MAX and destroy MAX database. After that I try to run other utilities like NI IO Trace, VISA Interactive Control, Scope Soft Front Panel, ... All of then crashed. I am running 64-bit Windows 7 + 64-bit LabVIEW. And we know that most of NI Utilities are 32-bit.
After a lot of frustration I went down to researching the computer BIOS level. And try to side-by-side compare with T5500. T5600 has much newer CPU and has lot more performance enhancement features. I tried to turn of/on one by one to see if any affect LabVIEW utilities. To my surprise I found that Intel® Hyper-Threading Technology (Intel® HT Technology) is the sinner. After turning it off all LabVIEW utilities start to work just fine. All T5600s are shipped with this feature enabled by default.
We know that DELL Precision PCs are almost industry standard for all engineering department. I think in the next few years a lot of people will be hit by this issue. I already notified NI and DELL R&D so they can find a good solution. But I just would like to make this issue Google-searchable so that anybody see this issue may get some help.
Give me any feedback if you encountered the same problem.
Thanks,

This means that you were on a witch hunt and hyperthreading is not the problem. (I always had doubts).
The original thread was about crashes in the visa console, but your problems seem to be much more generic:
"- The application stalls unpredictably after some time, sometimes a minute, sometimes hours. After clicking into the GUI it starts working again. This repeats in an unpredictable way. Competitive activities on the computer seemed to increase the stalling-frequency.
- Sound Input VI stops unpredictably and has to be restarted."
Are you sure you don't have a general code issues such as race conditions or deadlocks. Maybe you should start a new thread and show us a simplified version of your program that still demonstrates the problem. If there are race conditions, moving to a different CPU can cause slight changes in execution order, exposing them.
Did you repair the LabVIEW and driver installation? What are the power settings of the computer? Did you update other drivers (such as video, power management, etc)
What is the exact CPU you are using? What third party utilities and security software is running on your PC?
LabVIEW Champion . Do more with less code and in less time .

How to display scope plot in Labview GUI?

I am trying to figure out how to show TDS8000 scope output plot in LV GUI(?)
This maybe a two fold question.
1. I suppose it may be necessary to adjust the scope scale with appropriate level so that the plot will show enough details of information. (e.g., finding Max and Min points)
2. how to display scope plot in LV GUI?
It would be a great help if anyone can share an example VI.
Thanks,

Hi jjlee,
It shouldn't be that difficult of a task. Most instrument drivers have
a simple initialize VI, and then some type of waveform measurement VI.
You would connect these two VIs and then take the output from the
waveform measurement (may be waveform acquire or something like that)
to a graph or chart (depending on if you're outside of inside of a
loop). That should be all you need to do for the simplest form of this
application. You would, of course, want to handle errors and close the
connection to the device when you're done collecting the data.
Hope this is of some help,
Regards,
Matt S.
LabVIEW Integration Engineer with experience in LabVIEW Real-Time, LabVIEW FPGA, DAQ, Machine Vision, as well as C/C++. CLAD, working on CLD and CLA.

LabView drivers for Agilent 54830B scope or E4402B Spectrum Analyzer?

Where can I find LabView drivers for the Agilent 54830B scope and the E4402B spectrum analyzer, or at least a driver for another instrument in the same families that I could modify? There are none on the NI site or the Agilent site.

One thing that I have done several times is get a LabWindows CVI
driver from Agilent. You will be provided with a .fp file. LabVIEW
has a link under the Tools>>Instrumentation menu that allows you to
"Import CVI Instrument Driver." This will take the function calls
from CVI and build a set of VI's with the same name. The vi's will be
wrappers for a dll that is used by CVI and other text based languages.

Companies using labview in India and scope of labview in india

HI
This is hari krishna have 1+years experience in labview application development.
I like to know how many companies using labview in India and jobs scope/future of labview developers.
Regards,
Hari Krishna.k
R&D Engineer.

Hi Hari,
The scope of LabVIEW in India is indeed very bright.
You may find the below link useful:
http://forums.ni.com/t5/LabVIEW-Job-Openings/Scope-of-LabVIEW-job-in-India/td-p/1017671
Regards,
Rohan Sood
Applications Engineer
National Instruments
Regards,
Rohan Sood
Applications Engineer
National Instruments

NI Scope Streaming for LabVIEW 8.0

I am currently working on a data streaming project. I have been in touch with an NI rep, and he suggested the ni-scope-streaming-basic/advanced examples from the "NI-SCOPE Stream to Disk Using Win32 File IO" page (http://zone.ni.com/devzone/cda/epd/p/id/5273). Although the recommended software says "LabVIEW 8.0 or above" - I have LabVIEW 8.0 (FDS) and am unable to open the files. I get an error telling me LabVIEW 8.2 is newer than 8.0.
I was wondering if someone has built the project in version 8.0 or older. If so, I could you please post it? If nobody has had this problem before, could you please post a screen shot of the vi in version 8.2 so I can attempt to build it on my own?
Any help would be greatly appreciated.
Eric

Hi Eric,
Thank you for letting us know that the 'basic example' cannot be opened in LabVIEW 8.0 - I will get this fixed. I saved the 'basic example' in LabVIEW 8.0 and attached it below.
David L.
Systems Engineering
National Instruments
Attachments:
ni-scope-streaming-basic (LabVIEW 8).zip ‏461 KB

LABVIEW programming USB communication with TDS2004B scope

Is there anyone who has already programmed USB communication with Tektronix TDS2004B digital scope in LABVIEW?
If that is the case, could it be possible to send me a basic vi that works?
Thanks.
João.

National Instruments has a great library of drivers for various instruments. Most of these include programming examples.
The drivers are searchable at www.ni.com/devzone/idnet
The driver for your instrument is available here.
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness

Labview example for data capture using 5102 scope card

How can I program a Labview Vi to control, and capture a waveform using the 5102 scope card. I need to be able to set it up to continually capture a waveform (Channel 1 and Channel 2) when triggered on a rising edge of channel 1 and then store the data on disk automatically, then wait for the next trigger.
Any help or tips as to how I could do it would be helpful.
Thanks
Allan

Allan,
Please find the attached zip file that has some useful LabVIEW examples with scope 5102
Zvezdana S.
National Instruments
Attachments:
scope.zip ‏181 KB

Using Scope for LabVIEW DSP Module

I have a DSK6416 board and it is supported in my LabVIEW DSP Module on my LabVIEW 8.6 Professional. I want to use two scopes, one for the input audio signal and one for the output audio signal of my board. Which one should I use? NI-SCOPE or Two Channel Oscilloscope? Does NI-SCOPE support any dsk? Does two Channel Oscilloscope work with my real-time project?

Duplicate Post.

NI-scope labview vi's

Similar Messages

Maybe you are looking for