NiScope 2.1.4 and niScope 2.5

After ungrading my niScope from 2.1.4 to 2.5 along with other new requirements, I notice my code that synchronizing 5 PXI5112s board stops with this error: Warning 0x3FFA4006 occured-The PLL is not locked. The code works fine with version 2.1.4. I use RTSI clock to sync the 10MHz clock line, RTSI_1 as the sync pulse, and RTSI_0 as the digital trigger source from master to other 4 slave boards. Also, the example code that comes with 2.5 which uses the new scope class (CNiScope) works fine, but the code that comes with the previous version ( uses the niScope_XXXXX functions ) will fails with the above error msg. My question is, is this a new warning msg that NI added in its new version? Or am I missing something in the configuration steps
in the new niScope version? Thanks

That explains a lot. Thanks. I mostly followed the code sample taken out of the 5112Sync example's configureBoard function. If you look at the code (came with 2.1.4, not 2.5), you'll get an idea how I initiate the synchronization. I think I will just use the PXI_CLOCK line for now.
Both sample codes(2.1.4 and 2.5) use the RTSI clock line. When compiled under the new niScope version, the one(2.1.4) with the niScope_XXXXX functions will generate the warning msg while the new one with the new CNiScope class will not. Why? Did you do something with in the class to ignore this non-fatal error?
I've got another question - when you route the RTSI_CLOCK, or the PXI_CLOCK for that matter, what does the third paramete
r, the clockSyncPulseSource, in niScope_configureClock do? I've always thought the first parameter is the PLL source for synchronization.
Again, thanks for the response.

Similar Messages

  • How can I use the pulse train from a 6602 to trigger an niFGEN and niSCOPE on each rising edge of the pulse train?

    Hello,
    Here is my application: I need to use a 6602 counter/timer to generate a pulse train of certain frequency and duty cycle. On each rising edge of this pulse train, I need to output an arbitrary waveform on Ch. 0 of an niFGEN (5422) AND acquire data from CH. 0 of an niSCOPE (5124). I also need to synchronize the niFGEN and the niSCOPE to the same clock used for the pulse train (6602/ctr0). This process needs to continue until the user stops the system.
    I can generate the pulse train using the 6602 just fine using ctr0, but the pulse train shows up on OUT0 by default. When setting up the niFGEN and niSCOPE to trigger on rising/positive slope edge, OUT0 is not an option for either device as a source for the digital rising edge (pulse train). The main options for both are PFI0-3 and RTSI lines.
    Questions:
    1.) Is there a way that I can direct the pulse train to a location (such as an RTSI line) where BOTH the niFGEN and the niSCOPE can use it as a start trigger for each rising edge? I noticed in MAX that a route can be made between ctr0's internal output and a trigger line and others. If this is a solution, could you please explain how to accomplish this?
    2.) Once I configure the niFGEN and niSCOPE to be triggered on a digital rising edge, how can I effectively have this happen for every rising edge from the pulse train? In other words, can I just initiate the FGEN outside of the while loop and it will generate a waveform for each rising edge it sees at the source until the while loop is exitted?
    3.) Is setting a reference clock for the niFGEN and the niSCOPE the same thing as synchronizing both devices using the same clock that generated the pulse train? It is not clear to me the difference, and why it would necessarily be useful.
    Images of my current front panel and block diagram are attached. If you would rather have the actual VI's just let me know. Any help and/or explanation on this is greatly appreciated. Thanks in advance.
    Attachments:
    Front_Panel_Control.jpg ‏278 KB
    Block_Diagram_Control.jpg ‏263 KB

    Hello Cgifford,
    Welcome to National Instruments Forums.
    To output your signal to the PFI lines,
    you can use external connectios between OUT0 and PFI lines. You can also use
    the backplane to do so by routing into the same RTSI line.
    1)
    On the SCOPE and FGEN, the name of the
    terminals are actually “PXI Trigger Line x/RTSIx” but on the 6602 you might
    need to route the signal using the property:
    You can also use the DAQmx route signal which perform the same opperation.
    2)
    This will depend on the frequency of
    your pulse train. If this is lower than about 10 ms, then you can probably
    place this on a loop and start and stop the acquisition every time. If the
    frequency is higher than this, you will have to use:
    -       Scripting on the FGEN side (read more)
    -       MultiRecord Fetch (more information in the scope help file
    section “Acquisition Functions Reading versus Fetching”).
    3)
    The short answer is yes. The longer one
    might depend on how tight you need the synchronization to be (us, ns, ps). For
    very tight synchronization, you should look into here.
    Message Edited by Yardov on 06-18-2007 03:14 PM
    Gerardo O.
    RF Systems Engineering
    National Instruments
    Attachments:
    property.JPG ‏7 KB

  • Differences in NationalInstruments.ModularInstruments.Scope and NationalInstruments.ModularInstruments.NIScope classes

    Hi,
    I am using an old C# code which was built using the NI SCOPE .Net Class libraries version 1.1. I am resusing this code in my new project and I have installed MeasurementStudio2013, NI SCOPE .Net Class Libraries 2.0 and the NI-SCOPE 14.1 with Visual Studio 2013 and working on .Net Framework 4.5.1 (tried changing the version to 4.5 but nothing really changed)
    The old code uses the library NationalInstruments.ModularInstruments.Scope where as I am working with NationalInstruments.ModularInstruments.NIScope (since newer version of .Net Libraries do not support NationalInstruments.ModularInstruments.Scope.)and I have hell lot of errors in my program since the classes used in old code are not supported by NationalInstruments.ModularInstruments.NIScope.
    Example classes not supported by NationalInstruments.ModularInstruments.NIScope:
    ScopeSession
    ScopeSingleRecordMeasurementReader
    ScopeSingleRecordReader
    ScopeMultipleRecordMeasurementReader
    ScopeMultipleRecordReader
    ScopeReferenceTriggerType
    ScopeChannelCoupling
    etc and etc.
    Are there any alternative classes for these in NationalInstruments.ModularInstruments.NIScope ?Please let me know if I am working on something not possible. What is the possible solution I can apply now ? I cannot degrade to 1.1 version because of Operating System and VS compatibility issues. If there is a comparison guide/ user manual that helps me figure out the differences between the two libraries ,that would help.
    Thanks,
    Priyanka

    Hey, Priyanka
    The 2.0 API download page details discusses the API incompatibility between the 1.1.1 and 2.0 .NET API. I have pasted this as follows for convenience:
    Compatibility Notes
    The NI-SCOPE 2.0.0 .NET Class Library is not compatible with the NI-SCOPE 1.1.1 and earlier .NET Class Libraries. To comply with IVI Foundation standards, the class hierarchy has been completely changed and design-time property caching has been removed. To upgrade an application that uses the NI-SCOPE 1.1.1 or earlier .NET Class Libraries to use 2.0.0 requires you to rewrite most of the code that uses the NI-SCOPE .NET Class Library.
    However, you can install  NI-SCOPE .NET Class Library 2.0.0 side-by-side with NI-SCOPE .NET Class Library 1.1.1 and earlier versions. You can continue to use the .NET applications developed using NI-SCOPE .NET Class Library 1.1.1 and earlier on the same machine that has NI-SCOPE .NET Class Library 2.0.0 installed.
    NI's recommendation is to maintain projects previously written using the 1.1.1 API with the 1.1.1 API, and to start new projects using the 2.0 API. Unfortunately, there isn't a direct migration path between 1.1.1 and 2.0 because of significant architectural changes between the two APIs.
    Do you plan to port the old code for use with the 2.0 API or will you build off of the old code using the 1.1.1 API?
    Thanks,

  • Linking errors whlie running C examples of data acquisition using niScope and visual C++

    hello,
    I have an NI PXIe-1071 chassis with 2 PXI 5154 digitizer cards and NI PXIe 8102 controller.
    I am trying to acquire data using the same. Right now I am trying to compile some of the C based examples given in the documentation of niScope. But I am unable to do so. for instance when I tried to run "ConfigureAcquisition.c ". I am having many errors like the one given below.
    error LNK2019: unresolved external symbols _niScope_init@16 referenced in function _niScope_GenericConfiguredAcquisition@0
    for every niScope based function used in the example it is showing the same error. 
    I have only 2 files niScope.h and niScope.lib. In niScope.h there are declarations for each function but their definition is not there and I came to know that I also require source file of the same to avoid the error. Is this true????
    if I dont reqire source file please suggest me how to avoid such errors. and if I require source file from where I could find it as I talked with NI people and one of the application engineer told me that this is not available with them. 
    Please help me with the same.
    regards
    Sagar

    Try adding the appropriate source files from C:\Users\Public\Documents\National Instruments\NI-SCOPE\examples\c\common. With the errors posted by vijay, I would suggest adding asciiplot.c and GenericMultiRecord.c.
    National Instruments
    Product Support Engineer

  • NIScope 2.7: SW Trig and PXI5112

    Dear experts,
    I want to generate a simultaneous trigger on four PXI5112 to determine the timestamp counter offsets. My application looks quite similar to the Synchronisation example except that I want to trigger the master card by software. So I configured the master to trigger by software.
    This piece used to run on earlier NIScope versions. Now I've changed to 2.7 and I'm encountering an error on the SW Trig VI "Function or method not supported". I discovered that this VI now has an additional input parameter (called "which trigger") where earlier versions didn't have.
    So this VI doesn't seem to be downward compatible to earlier versions.
    1) What happened to this VI ?
    2) Waht does this parameter mean?
    3) How can I resolve this error?
    Thanks for your help
    Oliver Friedrich

    The original VI is called "niScope Send Software Trigger.vi." This VI still exists, and can be found under \instr.lib\niScope\niScopeObsolete.llb.
    However, the simpler solution is to use the new VI (niScope Send Software Trigger Edge.vi). You need to wire a constant to the "which trigger" terminal. Right-click on that terminal and select Create>>Constant. Then choose the constant value as "ReferenceTrigger". Then this VI will work for the PXI-5112.
    The newer VI supports several different types of triggers. While only the ReferenceTrigger can be used on the 5112, the default for that VI is StartTrigger. You are getting this error because you are not wiring a value to this terminal (so StartTrigger is used by default, which is not supported on the 5112).
    Hope this helps,
    Patrick

  • Synchronisation of Data from Vision IMAQ and niScope

    Hi!
    My task:
    - Take images with a Camera (Photonfocus MV-D1024E-160) connected to a NI-Framegrabber PCIe-1427) at speeds around 300 fps at freerunning mode
    - Measure Signals with a PCI-5922 Digitizer at 500 kS per second
    - Store all the data on the disk
    Now I have to find the time window of the Digitizer Signal exactly at the time the image was taken.
    What would be your concept doing something like that. (I use Vision and niScope)
    I did some first tries using:
    - Synchronize Timed Structures Starts VI
    - Use the Global Start/End Time of a Timed Loop as time stamps
    - There is also a micro-second status line stored in every picture (i could use for timing)
    Last but not least important:
    - How would you realize the datastorage
    - I did tryes with safing the image data and the digitizer data in seperate binary files (would TDMS be the better option?)
    - Would you use queues?
    I´m happy for every concept hint! Just write if you need more detailed information!
    Thanks
    Tobi
    Solved!
    Go to Solution.

    Hi Suse
    Thanks a lot for the hints. After a lot of effort I got to the following solution:
    I´m happy if you or someone else has comments on it (This stuff is pretty advanced for me):
    Two independend VI´s running at the same time (See Attachments)
    A) image consumer/producer
    B) Digitizer consumer/producer
    Additionally to the data I also safe the Global Start Time from the timed loop for each dataset (afterwords I can relate the Images to the Digitizer Signals using that timestamp)
    A) Image Consumer/Producer
    Attachment A: After initialisation of the image acquisition (left, upper corner). I have a Producer Loop (on top) which builds an array of 8-bit image data and the Global time stamp of the timed loop). The Consumer Loop (bottom) dequeues the cluster and saves every image as binary file with the nanosecond time stamp as filename. Like this i´m able to stream images from the camera to the harddisk at about 150 fps at full resolution (1024*1024 pixel) and even faster at low resolution (with a ROI)
    B) Digitizer Consumer/Producer
    Attachment B1: After initialisation of the NI-SCOPE I fetch (Points per fetch=2000 at the moment) the digitizer data and build again (similar to A) a cluster with the Global Start Time (and Global End Time for testing aswell). I enqueue in the Producer Loop
    Attachment B2: I Dequeue the data in the Consumer loop and Write (stream) it to a TDMS file
    To stopp all the loops after Acquisition and Storage I use a notifier.
    Questions:
    - Where do you see bottlenecks in this design (what could slow down?)
    - What could be done in a more efficient way?
    - How precise is the Global End Time Stamp (i want do find out exactely which image belongs to which digitizer signal). I didn´t find a lot of info about this Global Times (how are they "produced" within LabView?)
    - Other comments, review on it?
    Thanks again!
    Tobi
    Attachments:
    A.jpg ‏323 KB
    B1.jpg ‏302 KB
    B2.jpg ‏257 KB

  • Hysteresis and niScope Fetch Measurement.vi

    Sometimes I get a pulse width measurement in the order of a few microseconds when I'm expecting 30ms.  I'm wondering if this isn't a result of noise.  I have niScope Fetch Measurement.vi set to measure Positive Width.  From what I understand, the default value of hysteresis is 2 per cent of the Vertical Range setting for the digitizer.  Is there a way to calculate the peak-peak level of noise that will result in a false measurement for a given Vertical Range?  This assumes that the noise appears on the rising edge of the waveform.
    Thanks in advance.

    Hey VI Joe,
    What scope model are you using to make this measurement?  Can you post a screen capture of the signal that you are trying measure? 
    How are you using the "niScope Fetch Measurement.vi?"  Is this in an example VI in the Example Finder?  If it is not, try using the niScope Fetch Forever example VI.  Is the same noise experienced when using this example VI?
    Regards,
    Sara Lewandroski
    Applications Engineer | National Instruments
    http://www.ni.com/support

  • Writing waveforms from Ch. 0 of niSCOPE to binary file in a multi-record setup?

    Hello,
    I am not very experienced with niSCOPE and writing waveform records, so I need some expert help here.
    Here is my application:
    I am generating a pulse train using a 6602 counter/timer. Each rising edge of this pulse train triggers an niFGEN to generate a single sawtooth waveform output to another device and, at the same time, acquiring data from Ch. 0 of an niSCOPE. I am fetching one record per rising edge of the pulse train for the niSCOPE (multi-record setup).
    The attached VI is where I am at thus far. All triggering and reading/fetching of the waveforms seems to be working just fine when testing with an oscilloscope. I now need to save each waveform record along with the timestamp of its rising edge trigger to a binary file. The bottom of the VI is where my attempt is at saving the waveforms to a binary file, so the attention should be there when looking at it.
    I am running LabVIEW from a computer connected to the NI PXI-Chassis using a cross-over cable.
    Questions:
    1.) Do I need to convert the data coming in on Ch. 0 of the niSCOPE to digital? Does it come in as analog from an oscilloscope? If I need to do this, how can I accomplish this?
    2.) When I try to run an example VI to write a waveform to a binary file by choosing "My Computer" in the bottom left of the VI window, it works it saves the file just fine. When I change this to run on "PXI2", a file is not even created and I get an error on File Dialog (code# 7, I think) each time the file is attempted to be closed. This may be a stupid question, but why can I not save data to a file on my computer if running the VI on "PXI2"?
    3.) Assuming the saving of each waveform to a binary file is working (read: (2) is successfully addressed), how can I also write the timestamp of the starting trigger for the waveform along with the waveform in the binary file? An example VI of how I can accomplish this would be fantastic, but I haven't been able to find one thus far.
    4.) When I was messing around and trying to accomplish this, it seemed that doing this writing may slow down the entire process too much. I need to record data to the extent of the sawtooth waveform generated by the niFGEN AWG for each trigger. Is there any changes I should make to my acquisition process in the niSCOPE section so that I can read each waveform, along with keeping the timestamp for each, and write this information to a binary file?
    I need to get this working quickly, so any help on this is greatly appreciated. Thanks in advance.
    Attachments:
    5124_update.vi ‏157 KB

    Thank you so much for your reply, David. Let me try and explain my
    situation and setup a little better, as well as discuss the points you
    made in your reply. Beware, you may want to refill your coffee as this
    post is long .
    I am using an embedded controller in a PXI-1044 chassis. I now have the
    chassis hooked up to our local network, and I am deploying my project
    to the chassis over the network as I am also connected to the local
    network. I have an oscilloscope next to me that takes as input the
    pulse train for a trigger and the generated sawtooth from the niFGEN
    for each trigger (rising edge of the pulse train from the 6602
    counter). Just to make sure synchronization is taking place, the
    sawtooth is also fed as input to the niSCOPE for acquisition.
    "PXI2" is what shows up when I choose to run a VI on the PXI chassis
    rather than "My Computer"; not sure why the 2 is there either, but that
    is what it says. I may have tracked down the issue I was having with
    writing, but more about that a little later...
    The attached VI is an update, although not much has changed. My
    application design is like this (keep in mind that some values for VI's
    are still constants in the block diagram while others are controls on
    the front panel): I am using the 6602 to generate a 1 KHz pulse train
    and routing this pulse train to PXI_Trigger0/RTSI0. I am also using the
    PXI_Clock (10) as a sample clock for this, and also using this same
    clock as the reference clock for both the 5422 and the 5124 (as per the
    synchronization help file mentioned for synchronizing multiple
    devices). Both the 5422 and the 5124 are triggered by a digital rising
    edge (from the pulse train) on PXI_Trigger0/RTSI0 (as it was routed
    there). For each trigger, the niFGEN generates a sawtooth waveform
    using a stepped trigger mode and outputs it. For each trigger, the
    niSCOPE acquires data. They are both synchronous, which is tough to see
    since one has its trigger source on the front panel and the other has
    its trigger source on the block diagram. All devices use PXI_Clock so
    they are synchronized.
    The expected behavior is to only generate a single sawtooth waveform
    per trigger with a certain number of sample points. I want to acquire
    the same number of samples using the niSCOPE, which is what I meant by
    "the extent of the waveform" in my previous post. So, should I change
    the 8192 to 1000 for the number of samples for the niSCOPE? What would
    you recommend for the sampling rate? I have been using 5 MHz for the
    niFGEN and 5 MHz for the niSCOPE...this is how it should be done,
    correct? If it is different in the VI, please let me know. For some
    reason, I have to adjust all of the values each time I open it since
    the default values are not the ones I want.
    I want to generate and acquire one waveform per trigger (one waveform
    per record). However, I want to be able to record a large number of
    records so I have enabled the circular buffer-like treatment of the
    acquired waveforms. The 100 or 1000 records is actually just a number I
    am giving it for now to make sure it is working before recording many
    more records.
    As for saving the niSCOPE data, I would like to save all data in a
    single file that is NOT ascii (to save space). I have been looking at
    the HWS file format, and would like to use it. I think the attached VI
    includes this at the bottom of the while loop. For each trigger, I
    would like to save the time (as accurate as possible) that the trigger
    occurred for the record/waveform, which appears to be (absoluteInitialX
    - relativeInitialX) as you said in your post (thanks!). I just need to
    store as much information about the waveform and time information for
    it as possible with the waveform in the file. So it looks like I will
    need to use the wfm info for that information, providing portions of it
    as waveform attributes in the HWS VI's?
    What format of data do you recommend I fetch, and will I be fetching a
    "Single waveform" or "Multiple waveforms"? Should I use I32, DBL, WDT,
    or other for the format? A balance between good precision in values and
    time it takes to fetch/record would be best.
    Given all of the above, I am having one troube with saving data to a
    file. As a reminder, I am deploying the project to the chassis over the
    network. When I choose a location and/or file to save the HWS data to,
    I only get choices that are on the PC's hard disk (such as C:\Documents
    and Settings\cgifford\...) NOT the chassis's hard disk. When I choose
    something other than "C:\" I get an error that the file could not be
    opened. However, when I choose "C:\" everything goes fine. The saved
    data is nowhere to be found on my PC though, so I am assuming that it
    is being stored on the internal 60G hard disk in the chassis that must
    be named "C" by default or something!?
    I have been told by phone support that I should be able to make a
    direct connection with the chassis just like another PC, and should be
    able to access the information on its internal hard disk in a drag and
    drop fashion. I however cannot directly connect to the PXI chassis to
    get the data that has been saved on the hard disk. We are running
    Windows XP on the PC. We did some poking around and noticed that the
    chassis is not running Windows file sharing, and only has ftp and http
    running. We tried to access it using ftp, but we didn't have a username
    and password to supply it. So, how can we enable Windows file sharing
    on the chassis? How can I connect to it to do drag and drop to get
    saved waveform data off of it? This is the main problem I am now
    facing. Eventually we would like to store data to an external hard disk
    connected to the chassis, which assumes that I can have access to the
    internal storage to tell it to save files to the external hard disk.
    For now saving it to the internal hard disk is just fine until
    everything is proven to work, but I would like to get the data off of
    the internal hard drive to put on another computer.
    Any answers/suggestions on my above questions are greatly appreciated.
    I also want to thank you for reading this long post . I eagerly await
    a reply. Thanks again in advance.
    Chris
    Attachments:
    5124_update.vi ‏143 KB

  • How to include niscope library in VB program

    Hi all:
    I have a DAQ: PCI-5922 with the niscope driver. The sample VB program runs well. Now I want to write my own VB program so how to include the niscope library in my VB project? Thanks
    Regards
    Andy

    andycui,
    You will first need to open or create a new VB project and then select Project>>Add Reference.  Make sure that the COM tab is selected and choose NI-SCOPE Library from the list. 
    Thanks,
    Gio L.
    Digital Support - Product Manager
    National Instruments
    Attachments:
    VB_NI-SCOPE.GIF ‏42 KB

  • Splitting data from waveform output from niScope Multi Fetch Cluster

    I am trying to split the data of a 1-D array of clusters.  I am using a PXI-5421 function generator and a PXI-5122 digitizer.  The NiScope Multifetch Cluster.vi retruns output data of the waveform as a 1-D array of cluster of 3 elements.  This array contains information from channels 0 and 1.  I am trying to extract the waveform component information from each of the channels so I can operate on them an re-assemble two waveforms.  Can someone point me in the right direction?  I can't seem to come up with the right tool from the array or cluster tools.  Thanks.
    Jeff
    Solved!
    Go to Solution.

    You just use an Index Array and an Unbundle by Name or Unbundle.
    Message Edited by Dennis Knutson on 04-30-2009 10:41 PM
    Attachments:
    Index and Unbundle.PNG ‏4 KB

  • NiScope EX Multi Record vi program

    Hi,
    I have a question in niScope EX Multi Record.vi program. I was not explaining it well in my previous mail. That is why people can not answer my question. This time, I will explain clear.
    Attached "abc" is my prgram with niScope EX Multi Record.vi prgram.  This is my question. How come I can not get the waveform when I do the same action in the seond time? Here is how my prgram work. First, I press "reset"  push button, the light will go off and press it again the light turn off. The prgram do nothing, just reset the value of the voltmeter and current meter. Second, I press the "enable" button, the voltmeter and current meter get reading since I have a subprgram under timeout in the event structure. Then, I press the "enable button" again to turn on the light. Third, I press the "bark button", my hardware will be shocked and output waveform, since I have a subprogram, niScope EX Multi Record.vi, I set the right parameter, I will get the "shock pulse waveform".
    Everything looks good and working. Then I press the "bark" push button again to turn the light off. I want to do the same action the second time to see if the waveform of niScope EX Multi Record will generate again because normally I tried the same action the second time. the waveform will generate again. Here I am talking about I use the niScope EX Multi Record.vi prgram without anything and event structure and I did the same action as what I said in the above procedure. But, I did the same action in the second time in this "abc" vi program with niScope EX Multi Record. vi prgram, I could not get a new waveform, I don't understand why? could you please tell me what I did wrong? my niscope EX Multi Record.vi prgram is out of the event structure, what I see is like this prgram is alone just like the one I tried without event structure before. I am not sure if this single prgram mixed with event structure, it will be what? will it be different like I put two subprgrams in one block diagram even though I tried two subprgram put it together and it will work what it suppose to do. I am not very sure if ni scope EX Multi Record.vi prgram mixed with other prgrams with event struturem, what will happen? Will it be the same like two subprgram put it together? Could you please tell me exactly what if I put niScope EX multi record.vi with event structure including another program, what will happen? I would like to understand.
    Attachments:
    abc.vi ‏227 KB

    Hi Nyborn,
    The changes of the graph color are controlled by the Waveform Graph property node on your block diagram. In the niScope EX Multi Record.vi  example the Plot.Fill/PtColor value of the waveform graph property node is connected to a random generating number which changes the color on every execution. If you want to assign just one color, remove the random number vi and just wire a acii constant for the color you'd like. You can find listing of all acii color codes here.
    I hope this helps.
    Regards,
    Natasa

  • NiScope Initialize.viThe specific niScopeDAQ or niScopeDMF dll could not be loaded.

    I am getting this error when I try to use both IVI-SCOPE and NI-SCOPE in TestStand.  I make sure to close each reference before I use the next, but it seems like whichever one is called first will not release its reference unless I reboot the PC.  I wrote a LabVIEW VI that initializes the scope using IVI, then closes it and opens it wth NI-SCOPE and this seems to work fine  However, when I try to execute a sequence in TestStand that should effectively do the same thing, I get the following error when calling niscope Initialize. 
    Details: "niScope Initialize.viThe specific niScopeDAQ or niScopeDMF dll could not be loaded."
    Error Code: "-1074118608; User-defined error code."
    I need to use both because the IVI drivers do not support phase measurements.  If anyone has any suggestions to fixing this, I would really appreciate it!  I'm using LabVIEW 2013 and TestStand 2013 and my scope is an NI PXI-5112.
    Thanks

    Hi K_Joy,
    Thanks for the reply.  The TestStand sequence uses the built-in IVI steps to interface with the scope via IVI drivers.  The NI-SCOPE version uses TestStand Action steps with LabVIEW modules that call VI's located in the C:\Program Files\National Instruments\LabVIEW 2013\instr.lib\niScope.  I uninstalled NI-SCOPE version 4.1 and reinstalled version 4.0.5, which seems to have resolved the problem. However, now when I launch the NI-SCOPE Soft Front Panel I get this error: "The Soft Front Panel could not launch because an error occured while trying to open an application reference."  I can live without the Soft Front Panel for now, but on top of that I am now getting this error when using my DAQ module (a PXI-6221 M Series DAQ) : "Driver cannot complete the route, because the only way to make the route requires a trigger bus line, and no trigger bus has been configured in MAX for this device."  I'm currently attempting a repair installation of NI-DAQmx MAX Configuration Support 9.7.5.  Right now, I'm more or less just reinstalling differenct things because I don't know what else to do, so any insight you can offer into any of these problems would be greatly appreciated!  I've included both the TestStand sequence and the LabVIEW VI that I used to test the IVI vs NI-SCOPE problem, in case you're interested.
    Thanks
    Attachments:
    Test Scope IVI.vi ‏26 KB
    TestScope.seq ‏10 KB

  • NiScope: acquire indefinately upon trigger

    Hi all,
    I am getting some headaches with the pxi-5122. I had it working great when I was acquiring a fixed number of samples upon an external trigger. But now, I need to acquire indefinitely upon getting an external trigger.
    On the web, there is a "stream to disk queues" example that is close to what I want. In the example, they use a "software ref trigger" and set "Fetch relative to" = "read pointer" and "min record length" is left as the default of 1000. Then after initiating acquisition, a loop monitors "fetch backlog" until it is bigger than "samples per fetch", then a fetch is performed until the user stops the loop. It acquires indefinately presumably because "min record length" is ignored.
    I tried to adapt the example to use an external trigger by using an "analog edge ref trigger". I set "Fetch relative to"="trigger", I don't set "min record length" to anything.  I then copied from the "fetch in chunks" example, and set and maintained the "fetch offset" in the loop so that it would always grab the next available chunk of samples. After all of this the best I could do was to get the default record length of 1000 samples in the scope memory and it stops after that. I can increase the "min record length" to something arbitrarily long of course, but I would rather not do that. I am supposing that when I use "fetch relative to"="trigger", niscope thinks I am doing fixed length acquisition. Is this the case?
    To sum up my question: How do I correctly configure niscope to acquire indefinitely upon an external trigger?
    Thanks!
    -AT.

    You don't need to use the DAQmx Connect Terminals.
    The NI-Scope property you want is Synchronizationtart Trigger (Acq. Arm)ource
    (This is different from the Arm Reference Trigger)
    I see that you want to use the BNC Trig connector.  This connector cannot be used as the Start Trigger source, because that input is for analog triggers only.  What you really want to use is PFI 0 (or 1), which is exposed as one of the pins in the AUX I/O Connector at the bottom of the front panel.  There is a pinout diagram for this connector in the NI High-Speed Digitizers help file, under Devices>>NI 5122>>Front Panels>>NI PXI-5122 Front Panel.  This help file also has a lot of information you may want.
    You may want to contact an NI internal sales rep to get an adapter for the AUX I/O connector if you don't have one.
    To summarize:
    The property to set is: Synchronizationtart Trigger (Acq. Arm)ource
    The value you should set on this property is: "VAL_PFI_0" or "VAL_PFI_1"
    That will route the PFI 0 pin to the Start Trigger.

  • NiScope EX Multi Record

    Hi:
    I have a question on niScope EX Multi Record. I tried to put 10ohm in the BNC cable. See my attached graph. Then, I press the "Bark" button on my test fixture. It will generate the waveform using the niScopeEX Multi Record vi. But, if I use 100ohm in R1 or 18kohm in R1, The program will not generate the waveform after pressing the "bark" button. But, if i press the "test" button on the fixture, no matter I use 10ohm, 100ohm or 18kohm, the niScope EX Multi Record vi will generate the waveform. What wrong with it? Is there anything wrong in the  niScopeEX Multi Record vi or is there anything that I can set in this program to solve this problem.
    I am also attached the fixture block so that you can see the bark and test push button.
    I am in a very urgent. I need your quick reponse. I appreicate your help
    Attachments:
    NI Scope.doc ‏430 KB
    Current%20Measurement.PNG ‏7 KB
    Block diagram of the fixture.pdf ‏43 KB

    Hi Nyborn,
    The changes of the graph color are controlled by the Waveform Graph property node on your block diagram. In the niScope EX Multi Record.vi  example the Plot.Fill/PtColor value of the waveform graph property node is connected to a random generating number which changes the color on every execution. If you want to assign just one color, remove the random number vi and just wire a acii constant for the color you'd like. You can find listing of all acii color codes here.
    I hope this helps.
    Regards,
    Natasa

  • NiScope for linux 2.6

    Does niScope application software work for linux 2.6? I currently have it running on Red Hat Enterprise 3, but
    that's the 2.4 kernel and this is a rather outdated kernel version.

    Hi Vince,
    Thanks for the reply. I really applaud NI's efforts into Linux for it's products I just hope decisions like which distributions to support get a periodically reexamined.
    In that vain I feel NI almost has to support SUSE 10 if it's going to support SUSE at all. The idea that 6 months from now you would still list SUSE 9.3 as being supported seems questionable since most SUSE users would have switched to 10 and are already eyeing ver 11.
    Cheers,
    --Russ

Maybe you are looking for

  • Export book to PDF doesn't remember previous settings - CS5

    I've just noted a somewhat annoying "bug" in the book export.  When I export book to PDF--which I do a lot--I have to rename the file and reselect the type of PDF I'm exporting every time. It should remember the last settings I used.I believe in the

  • Cache Refresh Problems:J2EE

    Hi I am facing a problem in cache refresh. The XI 3.0 server is at SP10. Now whenever i am doing any changes in directory and activating it,it doesnt give me any error. but when i am cheking the Cache notifiactions it shows me a "GREEN" light for ABA

  • Editing log4j.properties file of ear while deploying ear file.

    Hi, Can i edit log4j.properties file of ear while deploying ear file. ~ Dhiraj.

  • Download accelerator woes

    I downloaded Download Accelerator Plus a while ago. Seeing as it was just a demo, I uninstalled it. Now when i'm using Camino (or any browser for that matter) if i try to download from certain sources such as mac software sites, mirrors or download.c

  • Unsupported Country

    How can I upgrade to the basic plan when I am in an unsupported country? I created a form and after spending hours on it, I not only found out that I could not download it to pdf for free and that I could not upgrade my service in the country I curre