Tektronix Oscilloscope Save/Recall

First off, I am a total newbie here. I am currently evaluating the Educational version of Multisim. I am sure I will be here a lot asking questions to help me evaluate this as I hope to use it in the classroom for instructional purposes.
My question is, regarding the Tektronix Oscilloscope Save/Recall feature. I want to save a certain sine wave to compare it to other waves as I add devices. I cannot get the Tektronix Oscilloscope Save/Recall to work. I thought I read somewhere that this feature was not supported but I cannot find that statement again. Is it not supported at all or just in the evaluation copy? Or am I doing something wrong?

In Multisim, the Save/Recall function in the Tek scope only works on setups, not waveforms. You can save waveforms when you use the 2/4 channel scopes or the Agilent scope.

Similar Messages

Save/recall error coefficiects of 8510A to/from pc

I know that, these are the error correction coefficiects created during calibration (also called a \cal set"). The error coefficiect arrays can be read from or sent to a computer, by the OUTPCALC and INPUCALC commands. I used the attached vi. for 8510A.
But the output file is not correct.
May you help me.
thanks
yasamin
Attachments:
Save or Read Calibration Data.vi ‏43 KB
Read Calibration 3.vi ‏25 KB

Hi James W,
Thank you for your attention.
I changed vi and attached updated vi.
I can do saving a cal set to a file (save to pc),
but when I want recall a file (the same one that is saved to my pc) from pc and save to a cal set, vi. do not work.
system gives an error : "BLOCK INPUT ERROR"
I do not know why is it?
Regards,
Yasamin
Attachments:
Save or Read Calibration Data.vi ‏39 KB

How to acquire reference waveforms from Tektronix oscilloscopes

Hi,
I want to acquire stored waveforms .wfm from oscilloscope to LabVIEW for analysis purpose.I tried by using Tek scope drivers,but gives error. what is the appropriate way to do it. Plz help...
Thanks in advance.
sayaf.

Use Tektronics Programer Manual. Find All GPIB commands and there find what command to acquire waveforms. Usually, you write GPIB command and read response from Tek.

Save tektronix waveform into csv file

Hello,
I am trying to save the waveform that from tektronix oscilloscope into a csv file by using Write to the Spreadsheet.vi .
But only one data is in the spreadsheet? How should I do this?
Thanks,

tian66 wrote:
I also have some data coming from the multimeter and I would like to save them in one spreadsheet. Thats why I use the write to the spreadsheet.vi
Is that doable?
Thanks
In that case, you just want to get the Y component of the waveform, which is an array of the Y values.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

How to calculate de area of a waveform in LabView with the oscilloscope Tektronix TDS380

I have a question about a mathematical algorithm. I am using the Tektronix oscilloscope model TDS 380 and since now I have been taking measurements peak to peak, putting in the labview program MEASU: MEAS1: VAL?
I am interested in calculating the area of the waveform, and the instruction manual for the Tektronix TDS 8000 found the command MEASU: MEAS1: TYPE AREA. This command is not in the manual for the model TDS 300 and therefore do not know if you can apply FOR IT. When I insert it I get the error code -1073807339.
My question is: would it be possible to calculate the area with my oscilloscope TDS380 somehow and with LabView? Is it possible to apply the algorithm or can be done differently?

Sorry about not posting. I'm on a business trip right now. Here's the VI, though.
Attachments:
get_second_derivative.vi ‏56 KB

Anyone advise me on how to save and recall the satate information of a cluster of combo boxes?

I have a set of combo boxes saving a devices state information. I would like to save and recall all the selections. I know there are properties to access the selected items, but searching about, I'm not sure the technique to do this. I would like to save/recall in XML format. I made an attempt and it saved the combo box data, but not the selections. Thanks for any help.
Solved!
Go to Solution.
Attachments:
TestStateXmlSave.vi ‏22 KB

I'm not sure what you mean by a bool of array. There are no booleans in your program from what I can see. If I understand you correctly, your trying to read the individual elements of your cluster control, is this right? You can do this using Property nodes. This is just and example. Let me know if I'm off base.
Use a For loop to process your elements that you want to save. I would consider using an Event structure for your main VI. This will do what you are trying to do here, and it will be more compact, cleaner, and more scalable.
Reese, (former CLAD, future CLD)
Some people call me the Space Cowboy!
Some call me the gangster of love.
Some people call me MoReese!
...I'm right here baby, right here, right here, right here at home

HP 8753ES 'block input error' when recalling state

I use HP8753 save/recall state.vi to save and recall state with the HP
8753ES network analyzer. I try to recall state back into the analyzer.
Saving is fine, but when recalling state, I get 'Block Input Error'. I
tried changing '1' to '0' at the Exclusive-OR in Write Text to
Screen.vi in HP 8753 save/recall state as Sastry recommended on
Lilach's question, but it doesn't work. I even take the write text to
screen.vi off and modify the vi to run without it, but it still
doesn't work. Can you advice me how to recall state properly? Thanks

Hi,
a post from Paris, with cloudy weather :-(
learn string of HP8753ES is 7656 bytes long. So 5000 bytes used to read
the VISA ressource are not enough and must be increased to 8000. After
that, HP8753 Save/Recall State.vi works fine here. I hope it will be the
same for you...
Daniel
Rung a écrit:
> I use HP8753 save/recall state.vi to save and recall state with the HP
> 8753ES network analyzer. I try to recall state back into the analyzer.
> Saving is fine, but when recalling state, I get 'Block Input Error'. I
> tried changing '1' to '0' at the Exclusive-OR in Write Text to
> Screen.vi in HP 8753 save/recall state as Sastry recommended on
> Lilach's question, but it doesn't work. I even take the write text to
> screen.vi off and modify the vi to run wi
thout it, but it still
> doesn't work. Can you advice me how to recall state properly? Thanks

VISA - unable to queue operation & device reported an input protocol error.

To summarise I have two main questions:
How can I clear the VISA operation queue and what causes an input protocol error during transfer?
I am using a Tektronix AFG3022B Function Generator with latest firmware connected via USB and LabVIEW 2013 SP1 patch 2 (13.0.1f2) 32bit with NI-VISA 5.4.1.
If I have a small timeout, say 100ms, and perform a save operation and op complete query on the device (*SAV 1;OPC?), then do up to 10 VISA reads; the first few reads time out (as expected), but then I frequently get the following error:
-1073807305 (0xBFFF0037) VI_ERROR_INP_PROT_VIOL. "Device reported an input protocol error during transfer."
Once this occurs, the whole VISA session seems to become unstable and lots of the read operations fail returing this error code and not the timeout error (0xBFFF0015 (VI_ERROR_TMO)).
This only seems to happen when I do save/recall operations (either internal or to a mass storage device connected to the instrument), all other commands/queries timeout for the first few reads (as expected) then return the value. Do you think this is probably down to poor instrument firmware/hardware? Or am I using the VISA incorrectly? I would have thought that attempting to read VISA data to soon should only generate a timeout error and not a protocol error.
Reason for small timeouts:
Instead of setting the timeout to 4 seconds and having no way of cancelling the read operation I set the timeout to 100ms and run a for loop up to 40 times ignoring timout errors unless it's the last loop iteration. This means I can the operation within ~100ms.
What causes the VISA protocol error? I can't find much information on it.
Once the protocol error occurs and I keep repeating the *SAV command, I get the following error:
-1073807303 (0xBFFF0039) VI_ERROR_IN_PROGRESS. "Unable to queue the asynchronous operation because there is already an operation in progress."
Once this error occurs, how can I force a clear on the VISA queue without unplugging/power cycling the instrument?
Some NI I/O trace captures attached to show what happens and test VI.
Using LV2014 SP1
Attachments:
VISA problems.zip ‏38 KB

I thought I would try to duplicate your problems, but I only have a Tektronix TDS Scope that has USB.
I am a big fan of using *OCP? to sync instruments control and your problem is of interest to me
This very simple write/read returns the *OPC '1' return char consistently between 175-185 ms. No problem
Trying your short timeout with a loop, I do not get what I or you expected.
If I run this with an adequate timeout (something well longer than the needed 185 ms) it returns in between 175-185 ms with one time through the for loop. As expected. No problem.
BUT! If I try setting the timeout to something below the needed 175 ms like your 100ms...
Sometimes it works but it takes over 2000 ms to return but only goes though the for loop twice.
But sometime it does not work at all, taking well over 10 sec to exit out of the for loop with a timeout error.
I never see the queue error that you are seeing
How long does it take to do a simple *SAV
I don’t think the queue error is coming from the instrument. You would have to send the instruments the SYSTEM:ERROR? Request before the instrument would report any of the instruments errors.
Be sure to set your Termination Char setting. I prefer to turn it off for the Writes so I control when to send it. But turn it on for the Reads
Also I noticed from your trace files that you use the *OPC? after a *IDN?. This is not needed as you will know the *IDN? is complete when your received the string back. In fact my Tektronix scope did not like it if I sent it "*IDN?;*OPC?\n". It would not send me anything back, not even the IDN.
Is the SAV command on your instrument so long that you need to be able to break out of the loop?
Omar

How can I convert output data (string?) from GPIB-read to an 1D array?

Hello all,
I am reading a displayed waveform from my Tektronix Oscilloscope (TDS3032) via the GPIB Read VI. The format of the waveform data is: positive integer data-point representation with the most significant byte transferred first (2 bytes per data point).
The output data of GPIB-Read looks like a string(?) where the integer numbers and a sign like the euro-currency sign are seperated by spaces e.g. #5200004C3 4 4 4 4 3C3C3........ (C represents the euro-currency sign).
How can I convert this waveform data into a 1D/2D array of real double floatingpoint numbers (DBL) so I can handle the waveform data for data-analysis?
It would be very nice if someone know the solution for this.
t
hanks

Hi,
First of all, I'm assuming you are using LabVIEW.
The first you need to do is parse the string returned by the instrument. In this case you need to search for the known symbols in the string (like the euro sign) and chop the string to get the numeric strings. Here are some examples on parsing from www.ni.com:
Keyword Search: parsing
Once you parse the numeric strings you can use the "String/number conversion VIs" in the String pallette.
Hope this helps.
DiegoF.Message Edited by Molly K on 02-18-2005 11:01 PM

GPIB timeout

I'm using a GPIB to collect data from a Tektronix Oscilloscope and everyday when I come in and try to collect it gives me this error HEX 0XBFFF0A6. I'm using windows 7 and LabView 2011. Each time I just restart LabView and it works just fine throughout the day. Opening MAX shows that it is communicating with the instrument. If this error code is simple I apologize but Google is down due to SOPA.
I've also had similiar problems with USB DAQ devices but in that case it is windows disconnecting from the instrument.

Hi TSCline,
These kinds of errors are usually due to GPIB/VISA reads where the message received is larger than the expected amount of bytes. Try programming a routine which will flush the buffer contents and try the collection command again. http://zone.ni.com/reference/en-XX/help/371361H-01/lvinstio/gpib_clear/
In addition, if you are not doing this already, look through our 3rd party drivers page for your Tektronix model and see if you can download proven VIs to control your Oscilloscope (http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/catnav:id/q/Tektronix/)
Hope this helps!
Aldo A
Applications Engineer
National Instruments

Using Switch Excequtive with NI TestStand

Hello
I am beginner in NI teststand & NI switch excequtive.
I have NI SCXI-1001 Chassis with NI SCXI-1130 switching slots.
I need a quick help on how to use switching in NI TestStand. What I am going to do is: generating a signal by a RIGOL Function Generator and switch this signal to excite some piezoelectric sensors and reading the response signals by a Tektronix oscilloscope.
I have read these documents:
NI TestStand 4.0 Quick Start Guide
Getting Started with TestStand
GETTING STARTED GUIDE NI Switch Executive
and so on
But still, I can not switch the signals with my hardware.
Is there any Tutorial to help me in doing my work?
Is there any VI code, NI TestStand Sequence or Example which can help me?
Please help me asap
Thanks in advance,
Mohammad

Hi Mohammad,
The following are a few documents that outline various ways (including with the Switch Executive) to incorporate switches into your TestStand sequence:
http://zone.ni.com/reference/en-XX/help/370404G-01/nise/teststand/
http://www.ni.com/white-paper/10092/en/
Let us know if those are helpful and keep us updated on your progress!
Regards,
David R
Applications Engineer
National Instruments

What is the correct command sequence code in Labview that will take an instrument out of Remote and put it in Local mode?

I am writing a routine in Labview 5.1 that will capture the screen data on a Network Analyzer after configuring the display. The routine to capture the data is working fine but when I try to send the equipment into local to allow me to manually make another change to the data I want to capture, the analyzer will go into a listen mode. The command I am sending to the analyzer using the 488 misc function is "loc". I've notice that is seems to put the anayzer into listen mode which will not respond to the commands to capture the screen data again.

Check the manual for the instrument. Some instruments do not have a specific command to go into local (or remote) mode. Tektronix oscilloscopes use the GTL command to Go To Local. HP and Agilent instruments do not have a command for this.
It's been a while since I used LV5.1, but in LV6, there is a VI under Instrument I/O->488->488.2 that allows you to set instruments into local mode. Hopefully, the same VIs exist in LV5.1.
Rob

Standardise definition & selection method for ALL third party plugin presets!!!

Over at LogicProHelp there is a very useful topic relating to Logic presets - in which many users have spent time saving individual third party plugin settings as LOGIC presets... which is enormously helpful when selecting instruments etc because they can be selected using a keystroke etc and found within the Logic Library browser window - which is of course searchable!
These presets have then been uploaded to the forum for others to download.
http://www.logicprohelp.com/viewtopic.php?p=367267#367267
I posted on the topic recently and thought it worth mentioning over here on the Apple forum.
Here's what I said - does anyone agree/disagree? Is this something that Apple should work on? For me it's a no brainer but I'd like to know what others think....
"MO 3rd party instruments that rely on mouse-clicks or anything more than one button press to change a preset are incredibly badly designed. It's massively frustrating and impedes creative flow to have to use a mouse, or press several keyboard buttons just to move from one sound to another. Native Instruments interfaces are amongst the worst offenders - you even have to MANUALLY specify what presets you want to use with specific MIDI Program Change messages - because the latter are the only way I know of using anything other than the NI interface to change sounds in their plugins.
The Logic Channel Strip settings saved along with 3rd party Plugin settings saved as Logic Presets have proved a recent revelation for me.
Now I can change instrument presets using a keystroke, a midi message, almost anything I want.
And then there's the Logic Library browser - now that so many sounds are saved as Logic Presets, the Logic browser window has become really powerful - being able to search my entire library for "bass" or a particular instrument name - REGARDLESS of which third party plugin is required to play the sound - IT JUST LOADS AND PLAYS!
Maybe I'm in the minority but I think of a sound I want first, NOT which instrument I should load and then browse through - the latter is kind of backwards for me.
I really think that we users should pressure Apple and plugin developers to provide Logic (and indeed other DAWs) presets with ALL of their products because the amount of effort on their part is minimal compared with countless end-users doing this task manually over and over. The current situation is ridiculous.
DAWs are incredibly powerful these days but the lack of a plugin preset/sound library definition standard is quite crippling to work flow.
I mean if there were a STANDARD LIBRARY DEFINITION such as with Native Instrument libraries or Apple loops where sounds are defined universally and supplied as such in a common preset it would revolutionise sound discovery/selection within DAWs.
Kind of like a document management system that applies to ALL plugins, by ALL developers and the installer for a plugin would then add all its presets to the management system/common library"

Sid Merrett wrote:
Can you give me an example of a plugin that doesn't work with the Logic save preset function?
Sure, I could give you lists of plugins for each of those particular scenarios I addressed.
In that specific case, for one example, Spectrasonics instruments for a few years did not support the hosts' save/recall settings function (at least in Logic), and when contacting them and asking why Stylus RMX could not recall settings saved via Logic's preset system I was given the explanation that it wasn't supported for technical reasons.Basically, it only save/recalled a small handful of settings, the rest were lost, meaning it was impossible for quite some time to use the Logic's save/load settings feature to save user presets, you had to use the plugin's own internal save features. (Yes, the instrument's state was saved in the song, but *wasn't* able to be saved via the preset handling, for technical reasons).
A year or so later, and later Logic versions, they finally got round to making it work as the varioous parts of the host and instruments were upgraded to handle larger data requirements. Spectrasonics instruments are examples of instruments with very specific, custom browser features, many of which you lose if you save data using Logic's functionality - not to mention the effort of saving, naming and organising 8000+ patches per instrument. Plus you have many levels of data - you often load a loop into a part, and a part into a group of parts, and they are different types of data. The hosts save/load feature only saves the state of the plugin - it can't be used to load Loop 14 into part 2, for example. It's the whole plugin, or nothing. More workarounds in terms of how you organise your loading/saving of different types of data.
There are other instruments too, and ones I've beta tested where I've got into the technical details and had to have the preset format changed or simplified because hosts had difficulties storing the data correctly. It's quite a complex thing, in the main, and different instruments implentation of preset handling mean that the whole thing is full of workarounds, compromises, or plain failure to use the feature completely.
Other instruments, such as Minimonsta, lose functionality when saving via the host - for example, you only get the meta patches and patch morphing functions when saving via the plugin's own file format, and that stuff doesn't happen when saving via the host.
I could go on and on about this - every develop has different requirements and they mostly all either do it very basically and rely on the host, or bypass the hosts save/load functionality and implement their own which they can be in control of and that will work across hosts and across platforms. For instance, there is little point having a beautifully organised Oddity library if all those sounds are now unavailable to me if I choose to work in Live...
That's why the whole preset thing is a complicated mess and isn't liable to be sorted soon.
There is a developer over on the PC trying to make a system to unify this stuff between plugins - it's PC only right now, and I forget the details this second, but it's acknowledgement that people recognise this whole thing is a mess and looking at ways to improve the situation.
Sid Merrett wrote:
I hadn't spotted that - thanks. You can't use the Logic Library window to search for Plugin Settings, only Channel Strip Settings.
You *can* use it to search for plugin presets, but only within the context of a single plugin. Ie, if I select the ES2, I can see, and search, the ES2 plugin settings. But often I want "a bass sound", I don't necessarily know that I was an "ES2 bass sound", or a "Minimonsta bass sound" or whatever.
The point being, I just want a sound that will work, and I don't know where it will come from. Forcing me to choose and instrument first can be counter productive. How many times have you needed a sound, and you go "Ok, there might be something in pluginX that'll work?" - you load up pluginX, flip through the sounds, don't find anything useful, then go "Ok, let's try pluginY", no... pluginZ etc etc
I miss Soundiver in many ways. *Ideally*, I'd like one central method of storing my presets which will work cross-plugin, cross-host, cross-format and cross-platform that is a standard that all developers and hosts support, and that offers the main core features that developers need, from simple, single patches with names, up to full meta data, cataloging, organising, author and notes tagging and so on. You can still give the users a choice to use the individual plugin and individual plugin's gui for patch selection, but you can get far more standardised if you want, with the advantages that gives - and you don't have to export patches into the system, as it's developer supported, all presets for your instruments would be instantly available in the library, just as they are in the instrument directly.
But it's difficult to get developers to agree on much, these days - the most likely thing to happen is someone somewhere creates a cross-platform standard for this that gains momentum and that developers and hosts want, or *need* to support.

NI VISA USB disconnection events

I am using NI VISA to control and acquire waveforms from a Tektronix oscilloscope in my application and so far everything works well but sometimes the USB connection can easily disconnect (and then connect immediately) and the MessagedBasedSession object then becomes invalid. My question is how can one setup events to know when a VISA device is connected and disconnected from an application so that these events can be captured and possibly notify the user or reconnect to the instrument. I know there are some functions such as Disable or Enable events but there are little documentation about these functions.
Thank you.

Hi falopsy!
Thank you for contacting National Instruments.
From what I understand of your problem you have a Tektronix scope connected to your computer via USB and you're communicating with it with the use of the VISA drivers. When the connection drops (briefly) and reconnects again, your MessageBasedSession expires and is no longer useful. I have found a few links that I think might help:
Firstly, this method here simply detects an error; you can then notify the user of the error and ask them to reconnect.
http://forums.ni.com/t5/LabVIEW/USB-Serial-VISA-problem-when-reset-happens/m-p/1442352
You also mention VISA Events in your post, although I couldn't find a specific event for a connection drop I feel that it may still be of use:
http://zone.ni.com/reference/en-XX/help/371361J-01/lvinstio/visa_events/
Lastly, I have attached an example VI of how to detect a serial break when transmitting data serially, this may also be of use. It might also be a good idea to swap the USB cable in case this is causing the connection drop.
I hope this helps! Let me know how these go and if there's anything else I can do - Have a great day!
Max
NOTE: If the attachement fails to open, it can be found in LabVIEW under Help>>Find Examples... and searching for "detect serial break".
Attachments:
Detect Serial Break Event.vi ‏35 KB

Problems compiling C in XCODE using VISA / NI

Hi,
I'm developing a program in C to communicate with my Tektronix oscilloscope. I inherited this project from a friend (who is currently incommunicado), so I can't talk to him about it.
Basically, my problem is that my program will not build due to a linker problem. I am using functions from the NI-VISA 5.4 package for OS X 10.8. However, the linker cannot seem to find the correct functions for my system:
Undefined symbols for architecture x86_64:
"_viClose", referenced from:
      _setupVI in oscilloscope.o
      _getData in oscilloscope.o
      _closeInstr in oscilloscope.o
"_viOpen", referenced from:
      _setupVI in oscilloscope.o
"_viOpenDefaultRM", referenced from:
      _setupVI in oscilloscope.o
"_viRead", referenced from:
      _setupVI in oscilloscope.o
      _getData in oscilloscope.o
"_viStatusDesc", referenced from:
      _setupVI in oscilloscope.o
      _getData in oscilloscope.o
"_viWrite", referenced from:
      _setupVI in oscilloscope.o
      _getData in oscilloscope.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
These are all pretty basic VISA functions. I struggled in just including the correct header file, as
#include <visa.h>
didn't work. When I went to the verbose form, it worked:
#include "/Library/Frameworks/VISA.framework/Versions/A/Headers/visa.h"
However, then the problem started happening that I'm having now -- the object linker can't find the code for the VISA functions. I've tried changing build architctures from x86_64 to just x86, without avail. I'm currently building in i386 x86. I've also tried (under Build Phases -> Link Binary with Libraries) to link the VISA.framework to the project, but this simply gives the linker error "cannot find VISA".
I feel like I am missing something very obvious. I'm still operating under the notion that either NI-VISA did not install to the correct location, or that my build settings are incorrect.
Does anyone have any insight to lend? I've been searching through different forums for help for almost 2 days now, with no avail.

atucker-hs wrote:
That is a good point that I hadn't thought of--I didn't run any install operations before installing 5.4. I'll try uninstalling all of 5.4 (there's not an uninstaller; just a text file of files to delete) and then doing a clean install after a restart. I'll let you know how it goes.
As far as their included examples, I tried to compile them both when I had 5.3 and 5.4 installed. I used gcc from the command line, and there were tons of errors - far more than I have in my XCODE project.
Did you try the Instruments/NI-VISA/Examples/C/ExamplesProject.pbproj?

Tektronix Oscilloscope Save/Recall

Similar Messages

Maybe you are looking for