PL/scope

Similar Questions

• With the help of several AC750 extension of scope in the same House?

  Can I use two or more AC750s in the same House for more coverage wifi scope/better?

  Hello JD777

  Yes you can but it is not recommended to connect 2 extensions to the other, you want to make sure you connect both to the main router.

  DarrenM

• The NI PCI-5124 scope with 2 triggers

  Hello

  I would like to ask about the trigger for starting and reference with PCI-5124.

  I found a sample VI on the following link, but it does not work as I expected.

  http://zone.NI.com/DevZone/CDA/EPD/p/ID/2998

  VI 'start_and_reference_trigger.vi' can detect the outbreak starting and reference in my system, and they begin data acquisition.

  He starts data acquisition when both start and reference triggers are entered.

  However, what I would do is:

  1. sampling at 200 MHz with a 1500 with a single channel record length.

  2. receive the signal to start (i.e. 50 Hz)

  3 receive the reference signal (i.e. 50 kHz)

  4. for each trigger reference, I would like to acquire the data, i.e. data of 1500 for each 100 trigger acquisition reference (not with the combination with the shutter release to start)

  Start trigger: _|^|_________________________________________

  Ref   trigger:______|__|__|__|__|__|__|__|__|__|__|__|__|__|__|____

  ^    ^    ^    ^   ^   ^   ^   ^    ^    ^   ^    ^    ^   ^

  hours of relaxing I want to acquire

  Trigger channels I use are:

  Start the trigger: PFI 0

  Trigger for Ref: PFI 1

  With the sample VI 'start_and... '. ", I found that it acquires when the two begin and trigger reference comes and data collection was only after the release of a single reference.

  I hope my explanation is understandable and I can have a solution soon.

  Hi Tom,

  This example configures a trigger starting and reference, but only for a single record. It is inside a loop, so it will continue to require a trigger start and each record. According to your description of the problem, you want to make an acquisition standard multi-record of 100 records, but you want to implement a trigger to start at the beginning of the acquisition. "' To do this, you can simply open the example of shipping"niScope EX Multi Record.vi"found in the example Finder LabVIEW or by browsing in your Start menu programs" National Instruments "NOR-SCOPE ' example. You need to add the property node to define your Trigger source begin to be PFI 0, but other than that, it should work fine. I have advanced and created a simplified with the trigger Start implemented, attached below. I hope this helps!

  

• No data presented on article 'Zoom Horizontal' or-Scope

  Hi all

  I apologize if this is the wrong forum for this question.  Windows XP

  I am a relatively new user of NOR/very inexperienced.    We have a NO-5133 digitizer hooked to an o-scope and NO-Scope.  We are able to see the waveforms and the o-scope OR Scope data.  We are not able to use the "horizontal zoom" function as no data is presented in the window.  What is a question game?  We tried different versions of NOR-Scope without success.  A simulated signal work on the zoom feature, so I guess it's a problem related to the input (digitizer).  I would appreciate anyones help to understand this issue.  Thank you in advance.

  
  

• OR scope Soft Front Panel fails to load

  Hello

  I use the scope Soft Front Panel OR with my USB NI 5132 for some time successfully. However, recently it has stopped working completely - seems to load a bit then fails before you even open the screen. The same thing happens in MAX I did all the updates critical, uninstalled then reinstalled NI Scope, uninstalled Labview (the only thing I had changed after the last time, I know that it worked successfully) and checked the nitaglv.dll library was in the right place according to this post: http://digital.ni.com/public.nsf/allkb/63739991438EC593862579C6007301EC

  So far nothing's worked. I NI SCOPE 4.0 and NI-VISA 5.3.0 installed, and the computer could see successfully the digitizer USB 5132 Max after the relocation OR scope, well that the flexible façade does not always load and making the Panel test Max also does not.

  I have attached a picture of the screen to load before it disappears so that could provide clues.

  Suggestions?

  
  

• Incompatibility of pilot PXI 5105 and unable to be detected by OR-SCOPE FPS with NO-SCOPE installed 14.1

  I am setting up test bench and just add a PXI-5105 card to my chassis SMU-1078.

  I currently have NO-SCOPE 14.1 installed on my PC host and target RT.

  When I try to run the Test panels in MAX, I get the following error:

  

  If I try to launch SFP-OR-Scope, it does not detect the card of the scope:

  

  The map seems to indicate as normal in my remote systems in MAX.

  For the host, the Installation of NOR-SCOPE includes:

  • Configuration support 14.1
  • 14.1 development support
  • 14.1.1 duration

  For the target RT, Installation of range OR watch as 14.1.0.

  I even checked in the feature add/software for the remote system see if a driver incompatibility was actually present:

  

  I have also confirmed in the Readme that PXI-5105 is supported OR-SCOPE 14.1.

  I'm kind of dead in the water on other ideas to investigate on concerning the system is behaving properly with the new card.  Other ways suggested for study?

  I continued to play with setting up more and find my VI has been targeted my Windows host instead of the goal of the RT.  I'm nowable to see my map of scope 5105 now through Labview + RTM.  Thank you for tolerating a newbie.

• OR Scope sets missing in Version 3.8.5

  We have installed OR carried Version 3.8.5 since the last Developer Suite DVD for use in Labview 11.  However, we have an application written in Visual Basic 6 that uses the NI-Scope pilot.  After you have installed the version 3.8.5 all constants in the module niScope_Defines are not defined. For example. Const NISCOPE_ATTR_ACQUISITION_TYPE =?, Const NISCOPE_ATTR_ACQUISITION_START_TIME =?.  This prevents our compilation of VB6 application.  We can not even run the VB6 samples shipped with the pilot scope NOR version 3.8.5 because of this problem.

  In the contract, NEITHER scope version 3.6.2 works very well in our VB6 application.  However, this version is unusable in Labview 11 because she not supported.

  Anyone know what is happening here?  Y at - it a bug with the driver version 3.8.5, or y at - he of the configuration settings that I have to do to make this work?

  Kind regards

  David

  
  

• Card data scope of device to the TDMS file buffer

  How transfer brought data card device buffer to TDMS file directly bye passing buffers LabVIEW and Windows. In the same way as DAQmx configure logging (VI) do we have any function scope?

  The API OR-SCOPE doesn't have the ability to record data acquired directly on the disc like the DAQmx API offers.  All data must be retrieved from the on-board memory, which makes data transfer OR-SCOPE kernel driver via DMA, and a copy must then happen to transfer data from the space of the kernel in user space (LabVIEW), how it can be manipulated.

  The main reason for this flow is because the calibration scale occurs in the NOR-SCOPE driver and not the material.  So if you were to save data directly to the disk as DAQmx, he stock raw ADC codes, without correction calibrated.  The API OR-SCOPE allows to recover the coefficients of scale if you want to apply them at a later date after extraction of the data from the hardware.  To optimize flow of data applications, it is recommended.

  The only exception to the logging directly on the disk would be the Oscilloscope Reconfigurable SMU-5171R.  It is being implemented with LabVIEW FPGA firmware using the design of Instrument libraries, code is open for editing.  With the open nature of this software stack, it is possible to implement "direct to TDMS" functionality with LabVIEW FPGA Read region node.

  I hope this helps!

  -Nathan

• OR-scope disconnect routing BUG?

  I use a synchronized with a 6652 and a 5124 5922.

  runs the task I want to tried get relaxation from start to PFI0 or PFI1, routing, however NO PFI0 or PFI1 does not seem to disconnect the routing.

  I have attached a simple vi for test. An additional cable to monitor the PFI mini DIN output to a scope is necessary

  1. Choose the 5922, run the vi.
  
  
  2. Read success (some samples are taken)
  
  
  3. Press the PFI0 button (START TRIGGER is routed to PFI0)
  
  
  4. to read (see the trigger on the PFI0 pulse)
  
  
  5. disable the PFI0 button (none is routed to PFI0)
  
  
  6. Hit read (uups, always trigger pulse here)

  Is this a BUG or how to disconnect the starting of the PFI trigger signal without losing my sync?

  Henrik,

  I don't see the problem, your code does not work as you described, but how you try to unplugged the lines wrong REIT.  In the niScope export Signal documentation, it says "unprogram a specific line on a device, call this VI with the signal is no longer you want to export, and then set it to any Terminal output .»

  In your code, you write you write Trigger start to PFI0, which allows the export of the trigger PFI0 to start.  To cancel it, you must write Start Trigger None (no PFI0).  You write 'none' to the wrong entrance of the vi.

  Attached is a copy of your VI it properly deactivated the IFP routing.

  I hope this helps!

  Nathan

• SCOPE NI Y waveform versus time

  Hello

  I use NI PXI-5114 scope, how can I get the values of x (increment of time) of the measures I / O-> OR-scope for my chart.

  Thank you

  For niScope read, simply choose the polymorphic case that produces a waveform (or an array of waveforms for multiple channels) and that wire up to your chart.  Waveform type data included the start time and sampling rate for the chart may include the X for you.

• Or-Scope on Linux

  As the information provided by ni.com looking a little outdated, I would like to know the current state of the nor-Scope drivers on linux.

  Specifically, I need to know if:

  (1) I use the GHz sampling rate digitizers (nor 5154 / 5153 / 5152) with no-scope on linux.

  (2) I can develop a C driver for these cards.

  (3) do all on OpenSuse 11.0 >

  Thanks a lot for the useful information ^_^

  Hey kitten,.

  The good news is that we are working on a version of NOR-SCOPE with support of Linux for the PXI-5152. However, it is the only device we will add in favor at this time. I don't have a definitive answer regarding when he will be available, although we try to release him as soon as possible. I'll make sure to post here when it is available. If you need additional assistance, please let us know by filling out a form of suggestion of product here.

  In addition, as mentioned Osamu, we don't officially supported the new SUSE distributions, so this new version will always be compatible with versions of the same distribution. However, there is a chance that if one of the other supported scanners can currently work in OpenSUSE 11.0, and then the PXI-5152 may work, but it will take further work of the user test.

  Kind regards

• Why is relativeInitalX value not taking into account the triggering delay? using scope OR with the PXI-5124

  Hi all

  play with a digitizer PXI-5124 in a case of PXI1042Q with a PXI8110 controller that runs labview 2012 (latest updates) with the latest version of the driver NIScope.

  I put in place an acquisition of off-delay (by assigning the triggering delay, for example 20us) which works very well (I can tell by the signal I get delay control works correctly), but the data returned in the info wfm cluster (using the 2D version of niScope I16 Fetch) does not have this delay.

  Description of the relativeInitialX within this cluster indicator indicates "is the time in seconds between the trigger and the first sample in the acquired waveform" but its never to return something around 1E-9 independent of trigger delay. Surely the relative initial x should reflect the triggering delay?

  I'm doing something wrong?

  Thanks for your help!

  So, I made a screenshot of the image in the section "Trigger Delay" link I sent you.

  

  Meaning of the symbol:

  T0 = original moment of relaxation

  T1 = time to trigger used in the acquired record (t1 = t0 + TriggerDelay)

  T2 = time of first sample in the record of the acquis.

  RX = relativeInitialX = t1 - t2

  Response to previous reviews

  «I understand what you're saying - so basically, if I want to know the delay of my trigger for the first sample in the record, I just add my delay time value to the relativeInitialX.»

  • Close, the delay of the original trigger (t0), for the first sample in the record (t2), would actually be TriggerDelay-relativeInitialX

  «.. . Nowhere does graphically describe where is the relative value of initialX real. »

  • Right, relativeInitialX is not a timestamp, so it is not a place on the timeline, it is the difference between two timestamps (t1 and t2 above), where the relativeInitialX name.

   

  "The trigger"record"is the straight line in the Middle, so expect relative to - 1/2 initialX record length?

  • Almost correct, because the reference trigger is relativeInitialX to the position of 50%, will be the time in seconds for 1/2 the record length. (i.e. If the registration has been long relativeInitialX, 2s = 1 s).  RelativeInitialX will always be the delta time between the trigger (t1) and the first sample returned in the record (t2).
  
  
  • For example using the picture above: If t0 is 10 sec, Trigger Delay = 3 sec, SampleRate = 1 kHz, = 1000 record size.  This means that t1 = 13 s.  Our record is long of 1s (1000 points to 1 DC between each = 1 s), if t2 = 12.5 sec.  If away from all these moments are absolute time, as the timestamps.  So relativeInitialX = t1 - t2 is 13-12, 5 = 0.5 sec.
  
  
  • As a side note, the reference position should not be 50%, you can configure to between 0-100%.

  Time not yet discussed record attributes

  I don't want to make you more confused, but there is another useful attribute in the waveform info that we've not yet discussed and its AbsoluteInitialX.  Starting from the NOR-SCOPE help file:"absoluteInitialX is the timestamp of the first sample of recoveries in seconds..." "So, using the above image, absoluteInitialX = t2.

  I hope this helps.  If a part is still not clear, let me know.

  -Nathan

• or scope is suddenly slow to start.

  Hello

  I was using a USB-5132 with no problems, but I suddenly encounter delays in searching for it when the green light is on.  Simpler than I can describe, it's all of a sudden he takes 20-30 minutes for NOR-Scope start.  More specifically, when I start OR-Scope on my PC, I can see it as a process in the Task Manager for 20 minutes before the NOR-Scope window appears on my screen.  Everything seems to be the best I can streams of data to the disk with the digitizer then see on NO-Scope, etc..  However, these delays are making me nervous.  Is there something I should be updated, for example?  I have made sure my NI-VISA is current.

  Thank you

  Penny

  Great, I'm glad that everything is working again.  Go ahead and mark this topic as a response.

• Strange problem after upgrade OR-Scope

  I noticed a strange problem with niScope Multi Fetch WTD.vi who broke my code that worked for years until that I upgraded to OR-Scope 3.9.6.

  In special circumstances, usually when there is more than 4 channels configured, this VI returns fewer points than asked, finishing ever acquisition. And this happens only when its entry 'channels' is wired! Weird how?

  I enclose you a snippet of my code that show this oddity.

  The jury was PCI-5105, LV 2010 32-bit sp1 version.

  
  

• Installation of NOR-SCOPE 3.8.7

  Hello

  I have to install NO-SCOPE 3.8.7 to use a PCI 5105 high-speed digitizer. However, when I try to do, the summary of installation indicates that some features can be installed either because there is a more recent version installed (but it is not a problem), they are "incompatible with products already installed". In my case, these are the ' media of LabView/LabWindows/CVI real-time ' and the 'NOR configuration system 5.0.0' which includes 'LabView 2010/2009/8.6/8.5.

  I use a computer running Windows XP, and the thing is it is a bit old and a lot of people it used before me. Therefore, it's an incredible waste and many previous versions of LabView are installed (v6.1/v7.1/v8.2.1/v8.5/v8.6/v2009/v2010). I read that earlier versions of LabVie have no impact on the last, but I also read this: http://digital.ni.com/public.nsf/allkb/F41A941BE2AFAC47862574B100736584

  What should I do? I guess I can't bypass the installation of the above mentioned features if I want my camera works well, but how can I solve my problem? Deleting files 'LabVIEW 8.2.1 Run-Time Engine' would fix it? Or do I have to uninstall all previous versions of LabView?

  Future prospects for the answers.

  Hello

  I suspect the incompatibility of functions "LabVIEW/LabWindows/CVI real-time supports" result is that your system has a version of NOR-DAQmx already installed (newer than the version with the NOR-SCOPE 3.8.7 distribution included) and the driver NOR-DAQmx "LabVIEW/LabWindows/CVI real-time supports" has for installation of NOR-existing DAQmx have not been installed. Assuming that you do not intend to develop applications using modules in time real LabVIEW or LabWindows/CVI, is without practical consequence for you.

  Distributions of pilot National Instruments (such as the OR-SCOPE) often include support API (as the ' System Configuration OR ") or infrastructure components (for NOR-SCOPE, NOR-DAQmx is threaded a). For the distribution of NOR-SCOPE, we decided NOT to include the latest revisions of these components in order to minimize changes in system during software updates.

  Concerning

• Options OR Scope Soft Front Panel

  Hey!

  How can I include the "impedance" and "Probe atténuation" options at the front view of NOR-SCOPE? Now, this option run "Edit-online Device Configuration"!

  Thank you

  Patrick

  double post