Installation of NOR-SCOPE 3.8.7

Similar Questions

• Usability is NOR-SCOPE Soft Front Panel for the PXI-5154?

  I am plans to use the PXI-5154 with his NO-SCOPE Soft Front Panel in a product to test instrumentation. Our past experience, our users need an on-board scope that is easy to use which does not load the CPU. In most cases the scope will be used to check a transitional type of pulses. So, the amplitudes and rise times are essential to ensure compliance with ISO standards. The ability to capture, store and recall traces of reports is important, as well as the ability to perform simple and reproducible follow-up measures. We don't expect our users to have to program the scope; "give me the waveform.

  Does anyone have any comments on the usability of the NOR-SCOPE Soft Front Panel? How to compare with other soft scopes?

  Hello!

  The scope Soft Front Panel is very user friendly and able to load/save waveforms, Load/Save settings and make the scalar measures.  I've attached a screenshot of what the front soft worn looks as well as a link to a help document on the high speed digitizer HELP.  Information on the scope Soft Front Panel lies in this document and can be found under the tab content in the configuration tree (NI - Scope Soft Front Panel help).

  Help of digitizer OR high speed

  http://digital.NI.com/manuals.nsf/WebSearch/2123F564C6DE7B27862574DE006915DE

   

• Cannot find the script of Installation of NOR-KAL check

  Hello

  I'm prompts to install the driver of Base of NIDAQmx. I got the following error: could not find the script of Installation of NOR-KAL check. Abandoned facility.

  Could you please help me with this.

  Thank you.

  ---

  C

  Hello Temp_Var,

  What version of DAQmx Base you trying to install? What operating system (including version number) you are trying to install DAQmx Base in?

  You can try to install NOR-KAL separately, following the instructions in the Readme of NOR-KAL. The latest version of NOR-KAL can be found here.

• 8.6 of LabView and NOR-Scope 4.0 will not work

  I have LabView 8.6 running on a PXI system and am trying to acquire data from a digitizer PXI-5105.  I was already running LabView 8.2 and an older version of NOR-Scope.  I opted for LV 8.6 and also NO-Scope 4.0 and now I cannot use OR-Scope in my VI.  He said search for the file type for each component of NOR-scope that I use in my VI and seeks the .clt files.  I can still use soft Panel OR-Scope, but it will not be displayed on the tab like before measure.

  OR-SCOPE compatibility with LabVIEW

  You need an older version of NOR-Scope or a more recent version of LabVIEW.

• Need the block diagram of NOR-SCOPE Soft front Panel

  
  

  I doubt that the code that is available - it can not even be written in LabVIEW.  Examples of NO-SCOPE that are provided with LabVIEW (look in the Finder example under hardware input and output-> Modular Instruments) illustrate all the available functions, and it can be an example that works as a starting point for you.

• How can I detect the minimum and MAXIMUM values of the inputs to the NOR-Scope channels (NI-SMU-1073)?

  
  

  Hello Philippe,

  Take a look at the example below. Retrieves the Min and Max of table X and also correspondent has the value Y.

  Best regards

  Klas

• 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.

• Installation of NI-VISA and NOR-488. 2 on Mac

  I have a new Mac on which I am trying to install instrumentation OR (VISA and GPIB) pilots, and things don't work any tips would be appreciated. I downloaded the most recent version of these two (14.0 visa) and 3.0.1 for the GPIB, ran the installers (restart the computer between the two installed) and then tried to run the VISA configuration utility and the GPIB configuration utility to verify that the drivers were ok (at this point, no measuring equipment is attached to the machine (ultimately, the material will be a USB-> RS232 adapter and a USB-> adapter GPIB).

  The two configuration utilities crashed running. Config GPIB obtained in what concerns to the top of its window and then crashed a few seconds later; NI-VISA never even managed to finish to display the home screen.

  In reviewing reports of incidents, accidents seem to be in the OR-PAL driver at low altitude. The report indicates that

  / Library/Frameworks/nipalu. Framework/versions/1/nipalu

  Abort() called

  Poking around the list of files mentioned in the uninstall NOR-PAL guide, it seems that the kernel extension nipalk.kekt was not actually installed correctly (it is absent of/Library/Extensions and/System/Library/Extensions, and according to the uninstall folder, it should be present in both. I tried to copy the kext above a machine that does not have a functioning VISA/GPIB install, but OSX refused to load because it has not actually been installed.

  My plan right now is follow the uninstaller for VISA, GPIB and NOR-PAL and then try to run the installers, but I fear that I will end up in the same place. Y at - it something special or something needed to get these drivers to install correctly (i.e. should things be installed in a specific order, should I try to install VISA 5.4 and then do an upgrade installation 14, try to sacrifice a goat, stuff like that)?

  The material is a Mini Mac OSX 10.9.5 running.

  Thanks for any help.

  And just to follow up with a few additional details, I went through the same procedure on a second Mac that was fresh out of the box. When running Setup for NOR-488, one of the things that we tried to install was an "Update" the subsystem NI Core Services of pilots. This was despite the fact that the VISA facility has implemented a much newer version of the kernel drivers.

  Thus, it seems that the problem is that NEITHER-488 Setup does not correct version control before overwriting the subsystem of pilots. He obviously checked that the driver has been installed, since the action has been listed as "update" instead of "install".  At least in principle, running the installer of NOR-488 first, then the VISA installer should work, but for some reason some the only time where I tried in my tests, it did not work. Maybe, I haven't had a full work of sanitation among other failed attempts. Just for the record, is the sequence that seems to work

  (0) remove all traces of any agreement, failed to install. Follow the steps described in the files uninstall.txt for NOR-488. 2, NI-VISA and NOR-PAL. The uninstall for this latter guide is located in/Library/Application Support / National Instruments/NOR-PAL

  (1) perform a standard installation of NI-VISA 14.0. Restart the computer. Check VISA works (just run the config utility)

  (2) perform a standard installation of NOR-488. 2 3.0.1. Restart the computer. The VISA and GPIB crash when access

  (Optional) curse (2A) to the length

  (3) perform a standard installation of NI-VISA 14.0. Restart the computer. The VISA and GPIB should now be functional.

  Tested on a pair of 'Late 2012' Mac mini OSX 10.9.4 running. One machine was Labview 2014 before you install the drivers for the instrumentation, the other had not installed LabVIEW.

• 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.

  
  

• 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 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.

• 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