SignalExpress IVI acquire issue

Hi,
I've recently upgraded from Signalexpress 3.0 to 3.5. Previously I used IVI acquire to get data from my multimeter, but since the upgrade, the option "IVI acquire" under "Add Step" has dissappeared, and I'm fairly sure (although not certain as I havent used many of the other options) that some other options have dissappeared as well. I've tried re-installing my IVI drivers and re-installing anything else I can think of that could be related, but it hasnt fixed the problem; all I'm left with are steps involving NI-DAQmx, which isnt particularly useful in this case.
Does anyone know if I simply might have missed re-installing something, or if there's something else I need to upgrade to get IVI acquire back?
Thanks

Are you sure you're running a fully licensed/registered version? You may need to check "Show Unlicensed Steps" in the Options window.
SCXI- 1000 Chassis w/ 1346 adapter
PCI 6281 DAQ card
SCXI- 1520 Bridge Board w/ 1314 Terminal Block (x2)
SCXI- 1180 Feedthrough Panel w/ 1302 Block
Signal Express 2014.
Win7 Enterprise

Similar Messages

  • Why doesn't SignalExpress communicate with TDS3054B scope?

    HELP!
    I have a TDS3054B scope with v3.39 firmware installed on it.  I want to communicate with it using SignalExpress but can't!  I can see the instrument in Measurement & Automation Explorer (v4.2.0.3001).  It shows up as GPIB0::1::INSTR.  I have a USB-GPIB cable going from my laptop to the scope.  The laptop is running LabVIEW 8.2.  I have installed the drivers for the scope from NI's website but still can't get it working...
    I can communicate with the scope using Tektronix's OpenChoice Desktop software, but that software is limited in what it can do...
    Any suggestions?

    Thanks again, Kent. 
    The article helped some, but I still don't have it working...
    In MAX, under the IVI Drivers >> Logical Names, I have the name MyScope.  For the General tab, I have the Driver Session listed as tkds30xx & a Description "TDS3054B oscilloscope".
    In MAX, under the IVI Drivers >> Driver Sessions >> tkds30xx >> General tab, I have the following:
    Initialization Options enabled: Cache, Range Check, Query Instrument Status;     Simulate With: Don't Simulate;     Driver Setup: tkds30xx;     Description: TDS 3000 Series
    In MAX, under the IVI Drivers >> Driver Sessions >> tkds30xx >> Hardware tab, I have the following:
    Hardware Assets: Name - TDS3054B (checked); Resource Descriptor - GPIB0::1::INSTR
    In MAX, under the IVI Drivers >> Driver Sessions >> tkds30xx >> Software tab, I have the following:
    Software Module: <None>;  my only choices are <None> or NIDMM.
    In MAX, under the IVI Drivers >> Driver Sessions >> tkds30xx >> Virtual Names tab, I have the following:
    Virtual Name: CHANNEL1, CHANNEL2, CHANNEL3, CHANNEL4;     Physical Name: CH1, CH2, CH3, CH4
    In MAX, under the IVI Drivers >> Driver Sessions >> tkds30xx >> Initial Settings tab, I have nothing.
    In LabVIEW SignalExpress, I go to Add Step >> Acquire Signals >> IVI Acquire >> IVI Scope Acquire.  The Step Setup box is displayed.  On the Configuration tab >> Device section >> IVI session name, I select Create New...  Another dialoge box opens with an IVI session name in it.  I change it to MyScope (same as in MAX), choose the Resource Descriptor GPIB0::1::INSTR (same as in MAX), but can't select an instrument driver.  The only thing available under Instrument driver is a check mark.  I can't select it for some unknown reason.  I hit the OK button & the box closes, returning to the Step Setup screen.  I try to run the step once & get an error stating:
    "ivi_IviScope Initialize With Options.vi<ERR>
    Driver Status: (Hex 0xBFFA1207) Primary Error: (Hex 0xBFFA1207) The item does not exist in the collection.
    Elaboration: tkds30xx"
    Back to square 1...

  • Some Photo's cannot be transferred to computer

    Using a camera connector on my holiday is fantastic, because it creates space on my compact flash cards, once I transferred my photos to the I-pod photo.
    For one of the created 'rolls' it went wrong. Windows doesn't see a number of photo's in that roll. I am sure that these specific photo's are still on my Ipod, but I cannot get them in my computer.
    Does anyone know what I can do to save these pictures?
    Thank you,
    Greetings, Rob

    Hello,
    Actually, you must use the IVI Acquire step. You must also have NI-VISA installed on your PC.
    Try IVI Acquire and let me know if that worked!
    Regards!
    Felipe Flores
    Engenharia de Aplicações
    National Instruments Brasil

  • Charting Function for V2.0?

    Total Newb here,
    I'm looking for some sort of "Charting" function in SignalExpress 2.0.
    I'm using an SCXI-1000 with a 1520 bridge board. I'd like to display real-time historical data over say, 60 seconds. I was told by our field rep months ago that a charting feature was being built in natively in V_2.0. Before that I had a seperate VI written for charting that worked okay but lacked any configuration controls.
    Thanks
    SCXI- 1000 Chassis w/ 1346 adapter
    PCI 6281 DAQ card
    SCXI- 1520 Bridge Board w/ 1314 Terminal Block (x2)
    SCXI- 1180 Feedthrough Panel w/ 1302 Block
    Signal Express 2014.
    Win7 Enterprise

    Hi CabShake,
    It sounds like you would like SignalExpress to show data as it is acquired to the main data view. SignalExpress functions by displaying data by groups of samples, the Samples to Read in fact. What this means is if I configure SignalExpress to Acquire 10 samples at a rate of 1 Sample/Second then it will take 10 seconds to acquire this data.
       Total Sampling Time = Number of Samples to Acquire / Sampling Rate
                                          =  10 samples / 1 samples / sec = 10 sec
    So, try the following experiment and prove this to yourself:
      1. Create a new project.
      2. Add a step: Acquire Signals->DAQmx Acquire->Analog Input->Voltage
      3. Hold Ctrl and select several analog input channels for display
      4. Click Ok
      5. Configure the Acquisition Mode as Continous
      6. Configure the Samples to Read as 10, the Rate as 1 hz.
      7. Run the project
      8. Observe how the graph updates.
      9. Now increase the rate to 10 samples/sec, now the graph will update all 10 samples in 1 second.
    If the total time to acquire the group of samples exceeds 10 seconds then you will need to change the default timeout, this is done in the
     advanced timing Tab.
    Please post back if this isn't sufficient to answer your question of how to display data at a realtime rate on the graph in SignalExpress.
    Scalars: real numbers. Whereas a waveform would have t0, dt and scalar values attached to it.
    Best regards,
    MatthewW
    Applications Engineer
    National Instruments

  • USI encountered an exception (241)

    Hi, I am using SignalExpress to acquire 32 voltages via a NI 9205 card in a CompactDAQ cDAQ-9174. Nothing too complicated really.
    The acquisition goes fine, and creates a folder with 3 files that look like this...
    Voltage                    National Instruments TDMS Importer For Microsoft Excel        504KB
    Voltage.tdms_index  TDMS_INDEX File                                                                242KB
    Voltage_meta           Text Document                                                                       3KB
    When I try to import the data into Excel, I get the following error...
    TDM Importer
    USI Encountered an exception:
    (241): Cannot create bulk: attribute of wf_start_offset does not exist on entity tdm_channel
    I have downloaded the latest TDM add-in for Excel 2007 from the NI web site.
    I have Microsoft Office 2007 running under Windows 7 Enterprise 2009
    I have acquired several data sets and they all come up with this error when I try to import them into Excel.
    If you can solve this for me I will be such a happy bunny!

    Hi, I am using LabVIEW 2010 Signal Express Version 4.0.0
    I have attached the three files from the data folder... If they get stopped then let me know and I'll email them.
    Hang on,... It won't transmit the text file, so I'll try the other two...
    Attachments:
    Voltage_meta.txt ‏3 KB

  • Labview signal express to excel

    Hello,
    I'm using Labview signalexpress to acquire a signal. My problem is that I acquire 20 seconds of my signal (and I see it on the graph), but the problem is that I can export to excel the only 1.35 seconds, whatever the number of samples. How could I export to excel the entire signal?
    Thanks
    Solved!
    Go to Solution.

    I don't have signal express but a quick search found this link.  It states that there is a setable limit on the size fo data sent to the clipboard.  
    "When you export data to Microsoft Excel, LabVIEW SignalExpress copies data samples to a clipboard for export. Use theMaximum Clipboard Data Export Size option on the Data page of the Options dialog box to increase the number of data samples the clipboard can contain. Depending on the amount of memory on a machine, large log files might not export successfully."
    You might be running into that limitation when you try this method.  Even if you increase the limit you will still not be able to paste more than excel's max size as discussed already.  You would have to paste it into a text file or some other program that can handdle that much data.  I would not use this method however.  Seems like it would be to easy to make mistakes that way.
    A .lvm file is just a text file so you should not run into any limits there.  This is what I would use. 
    Lukin
    Certified LabVIEW Developer

  • Not enough memory issue while acquiring data

    Hi all,
    I am trying to acquire audio data @ 50KS/s for 20 sec. using the PXI 4498 card in the PXI system. To acquire data I am using the DAQmx functions.
    Step1 : Created DAQmx channel
    Step2: Set the no. of sample to read as 20X50=1000000 to the DAQmx Timing function
    Step3: DAQmx Read funtion to read the data. (Set the timeout as 20x2=40Seconds)
    PLease find the attached screen shot of the block diagram.
    Issue is sometimes I am facing the memory issue when I run this VI. Popup saying that "Not enough memory to complete this Operation"  is getting popup and the Vi getting stop abruptly. Kinldy look into the screen shot and suggest me the apprapriate method to read the data at mentioned acquisition rate.
    Note: The problem is not consistent. Sometimes I am facing the error and sometimes not.
    Thanks in advance
    Giridhar
    Attachments:
    Block diagram.jpg ‏208 KB

    I think actdi is talking about loading an external database directly from the XML file using the jdbc XML driver, correct? I have not tried this yet, but am curious as to the results.
    http://docs.oracle.com/cd/E17904_01/integrate.1111/e12644/appendix_xml_driver.htm#CHDFIJEH
    Hope this works.
    Enjoy!
    Michael R.

  • Failed to acquire a wave using ivi dmm step with a FlexDMM NI-4070

    I tried to acquire wave with a FlexDMM NI_4070 and a Read Multipoint ivi step from TestStand, it didn't went thru. Configuration step is: DC volts, 0.01 resolution, immediate trigger source, auto once range mode, 0 trigger delay, 100 multipiont sample count, 10 sample interval, 1 trigger count, interval sample trigger, none meas complete dest; Read step is: wave data type, Step.Result.Reading meas dest, 5000 time out, "failed" status on time out. What I get is failed status due time out.

    Try setting your Timeout to 30000. The Timeout is in milliseconds, while the Sample Interval on the Advanced tab of the Configure step is in seconds. You have this interval set to 10. Setting your timeout to 30 seconds will give your Read operation time to complete.
    Regards,
    Eric M.

  • [svn:bz-trunk] 21661: Avoid calling throwNotSubscribedException() from inside synchronized blocks to prevent potential issues acquiring the lock .

    Revision: 21661
    Revision: 21661
    Author:   [email protected]
    Date:     2011-07-21 06:21:07 -0700 (Thu, 21 Jul 2011)
    Log Message:
    Avoid calling throwNotSubscribedException() from inside synchronized blocks to prevent potential issues acquiring the lock.
    Checkin-Tests: Pass
    QA: Yes
    Doc: No
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/client/FlexClient.java

  • Issues with acquiring from multiple GigE cameras

    Hi,
    I'm trying to build a simple app where three cameras are running simultaneously and can optionally record AVIs with timestamped data appended to each frame. I'm not having the recognition issue (all three cameras are seen through either a network bridge on the PXI system I'm using or an external GigE switch), but they seem to be failing during the grab process. When I have more than one running, green noise in the form of horizontal lines appear on the images, and usually all but one of the cameras will eventually drop out. No such problem exists when triggering only one camera. It seems a lot like the frames are colliding somehow; can grabs from multiple cameras not occur in the same loop?
    As for the program set up, it's mainly a modified version of the "write" case in the AVI Read/Write with Data example. The user is prompted to save the avi's and a text file, three camera and IMAQ sessions are opened (with unique names), and then the program loops until the stop is hit, with a true/false case for actually recording the data. Frame/sample rate is controlled by the millisecond timer wait function. The problem happens regardless of acquisition speed (even at 1 frame/sec), and the CPU nor the network link seem to be anywhere near fully taxed. 
    Thanks,
    Brian

    Thanks for the suggestions guys.  I put the packet size back to 8000 on both cameras.  So far, I'm still seeing green horizontal lines.  Here's what I've tried and what I've learned.
    1.  Set Acquisition Mode in VBAI to Continuous - Immediate
    2.  Tried to reduce the bandwidth demand of the cameras by setting Acquisition Frame Rate (Abs) to 3.0
    3.  Checked the Device Max Throughput under Transport Layer in MAX
    a. Color Pilot camera is 30.4 MB/sec
    b. Mono Pilot camera is 11.1 MB/sec
    4.  Checked the Bandwidth Assigned under Transport Layer in MAX, and it is 125 MB/sec
    5.  Add 30.4 to 11.1 and get 41.5 MB/sec so there is 83.5 MB/sec bandwidth available.
    6.  Subtract 5 MB/sec for overhead and 6 MB/sec for each camera for Bandwidth Reserve (set at 5%) and there is still 66.5 MB/sec left over
    7.  Open VBAI, and then open an inspection in which the Mono camera is configured (mad sure to load the defaults that were saved in MAX)
    8.  Launch MAX and try a Grab from the Color camera
    9.  See green lines of death.... 
    So, I've narrowed my experimentation down to just two cameras and I still have acquisition problems.  I've got to be missing something else.  Note that there is no camera attribute section called "Advanced Ethernet" only "Transport Layer".  Perhaps that was camera-specific.
    I think I'm going to have to use dedicated Ethernet ports for each camera.  It is disappointing since this architecture should work given those bandwidth concessions made for frame rate.
     - Dan

  • Acquiring 24-bit sound with a third-party sound card... truncation issues.

    I am having a very strange problem when using LabVIEW to acquire audio
    data via the Windows API from a Creative Professional E-MU 1616m sound
    card.  The goal is to acquire sound in 24-bit resolution. 
    When capturing sound in 16-bit mode (as set in the LabVIEW software),
    the E-MU 1616m behaves as expected, with a 105dB SNR and approximately
    -130dB noise floor, after dithering.  However, when switching to
    24-bit capture mode, a very severe truncation occurs.  This sends
    the harmonic distortion and noise through the roof.  After
    investigating fairly deeply in our LabVIEW code, I am wondering what
    might be the problem.
    I have compiled a number of screenshots which showcase the problem in more detail.
    Here is a background of the experiment:
    For these tests, both the analog and digital audio was generated by an
    Audio Precision System Two system, and was passed directly into the
    respective line-level or digital audio inputs.  Digital audio was
    tested using both coax and optical cable.  In the sound card
    control software, the audio was sent directly from the input channel
    into the WAVE IN L/R (via the Windows API, I assume).  The
    sampling rate for the profile was 96kHz.
    The sampling rate in all LabVIEW functions was set to 96kHz.  The sample rate set in the AP Digital generator was 96kHz.
    ANALOG 20dBu 96kHz 16bit.jpg
    In this test, everything looks fine.  The audio input is at
    Full-scale for the E-mu's ADCs.  It is exhibiting expected 16-bit
    performance (with dithering).
    ANALOG 20dBu 96kHz 24bit.jpg
    Now we instruct the driver to capture sound in 24 bits.  Notice
    that the noise floor and THD+N go up considerably.  Effects of
    truncation become visible on the time-domain display.
    ANALOG -20dBu 96kHz 16bit.jpg
    Now we drop the input level to -20dBu.   The performance
    starts to look a little messy but is still acceptable.  Note,
    however, the high peaks on the odd harmonics.
    ANALOG -20dBu 96kHz 24bit.jpg
    Now we try to capture at 24 bits.  The effects of truncation are extreme at this low signal level.
    ANALOG -60dBu 96kHz 16bit.jpg
    Now we are at extremely low signal levels.  Individual
    quantization levels can be seen on the signal.  Dither is also
    present.  Performance is still good.
    ANALOG -60dBu 96kHz 24bit.jpg
    However, when increasing the resolution to 24 (which should increase
    the number of quantization levels), our signal is reduced to a square
    wave.  Obviously something is wrong.
    DIGITAL 0dB 16bit 96kHz 16bit.jpg
    Now on to the digital tests.  We start with full-scale.  We
    used an AP outputting a properly dithered 16-bit signal over an optical
    cable.  The soundcard is instructed to receive in 16 bit
    mode.  It looks good.
    DIGITAL 0dB 16bit 96kHz 24bit.jpg
    Using the same input, we change to 24 bit receive mode. 
    DIGITAL 0dB 24bit 96kHz 16bit.jpg
    Now we set up the AP to output a properly dithered 24-bit signal at
    full-scale.  The dips in the frequency domain show us that
    something is wrong.
    DIGITAL 0dB 24bit 96kHz 24bit.jpg
    Receiving in 24-bit mode.  Same story as before.
    DIGITAL -90dB 16bit 96kHz 16bit.jpg
    Now we decrease the amplitude to a low level.  Well-implemented dither is shown here clearly.
    DIGITAL -90dB 16bit 96kHz 24bit.jpg
    However, receiving in 24-bit mode reduces the signal to a dithered square wave.
    DIGITAL -90dB 24bit 96kHz 16bit.jpg
    Here is the low-level signal with the AP generating a 24-bit
    signal.  Dither is applied, but vanishes in the e-mu 1616m. 
    It seems the dither level has been changed.  This is the cause of
    our dips from before.
    DIGITAL -90dB 24bit 96kHz 24bit.jpg
    And finally, we transmit and receive in 24-bits.  Here are the results.
    We have achieved similar results using several of your breakout boxes and soundcards.
    Attached are all screenshots, as well as the main VI (AP Test.vi) and
    the dependent vi's.  There are a number of SVT vi's in the
    project, but they can be ignored since they are not related to the
    problem.
    Any help would be greatly appreciated.
    Best Regards,
    Brett Gildersleeve
    Attachments:
    AP Test.zip ‏2381 KB

    Hi Brett,
    I took a look at the code you attached, but it appears that you may have left out the subvi that actually acquires the sound. When you say Windows API, I assume that you are calling a DLL at some point. How are you configuring the inputs (or what function are you using)? It could be (and this is just a guess) that when you specify 24 bits, the DLL returns the data in a very specific format. If you don't interpret the bits that are returned correctly, LabVIEW may not know what to do with them, as LabVIEW does not have a native 24-bit datatype. If there is any documentation for these function calls, our answer might there...
    Just some thoughts -- thanks for posting your solution!
    Charlie S.
    Visit ni.com/gettingstarted for step-by-step help in setting up your system

  • Having issues with WRT54GS router acquiring network address after wireless connection.

    I've been experiencing problems acquiring a network address after making a wireless connection with the WRT54GS wireless router. I have a Comcast cable modem connected to the internet port of the router and after configuring the SSID and the 64 bit WEP key, I can connect to my router's SSID, but since I can't get an IP address, never connect to the Internet. I've already cloned the laptop's mac address to no avail. Even after configuring a static IP address, subnet mask and default gateway, still cannot connect. I can Ping and Traceroute from the router but not the PC. I can ping localhost and host IP address from the laptop but not the default gateway. Any suggestions would be appreciated. Thanks, SJ

    Connect the computer to the router with the Ethernet cable.
    Try to access the internet when you connect the computer to the router with the Ethernet cable.
    Open the setup page of the router and go to Status page. Check the Internet IP address on the status page of the router.
    If you are able to access the Internet with the Wired connection to the router then try to create a new wireless network on your router.
    Open the setup page of the router and go to Wireless tab. Change the wireless network name SSID and change the channel to 11. Save the settings. Go to Wireless security sub tab and check the wireless security settings. Click on Wireless MAC filter sub tab and make sure that it is disabled. Click on Advanced wireless settings sub tab. Change the Beacon Interval to 75, RTS and fragmentation threshold to 2304. Save the settings.
    Try to connect to the new wireless network and see if that works.
    How many wired and wireless computers do you have in the network?

  • IVI DMM step won't connect

    When I try to connect my IVI DMM Acquire step to a 34411A, I get the following error:
    ivi_IviDmm Configure Power Line Frequency [PLF].vi<ERR>
    Primary Error: (Hex 0xBFFA0011) Does not support this class-compliant feature: method %1
    Elaboration: FunctionId: 69, FunctionName: ConfigurePowerLineFrequency
    <b>Complete call chain:</b>
    ivi_IviDmm Configure Power Line Frequency [PLF].vi
    ivi_subDMMPreExecute.vi
    ivi_InstrDMMBlockState.vi:1
    I'm guessing that the IVI Dmm Acquire step is attempting to call the IVI 'ConfigurePowerLineFrequency' function, which is (apparently) not supported by the 34411A driver. Is there any way to work around this?
    Thanks,
    Aaron

    Hi Aaron,
    I currently have not found any resources that allow SignalExpress to ignore initialization errors. However I did find a resource that has the command for the power line frequency for your device (page 8). http://www.home.agilent.com/upload/cmc_upload/All/34410A_Quick_Reference.pdf?&cc=US&lc=eng
    You can modify the 34411A library so that this command is not used during your IVI DMM Acquire Step; however, I was unable to find the subDMMPreExecute.vi in a search of the project. 
    Sam B.
    Applications Engineer
    National Instruments

  • SignalExpress Tektronix Edition with TDS2014C

    I have the full version of SignalExpress Tektronix Edition to use with a Tektronix TDS2014C 4-channel scope.  Unfortunately SignalExpress will only show me Channel 1 and Channel 2.  I have yet to figure out how to get it to display Channels 3 and 4.  Below are the steps I take:
    Add Step -> Tektronix -> Acquire Signals -> Tek TDS1000/2000
    The image below is what SignalExpress gives me.  Any suggestions?

    Hi Viper32,
    Here is a link to the lates version of the driver. Install it and see if this helps the issue. It was updated in 2008.
    Regards,
    Perry S.
    Applications Engineer
    National Instruments

  • DT9837 With LV SignalExpress

    Hi,
    I have a Data Translation unit DT9837, and I would like to use it with LV SignalExpress. I know that it can be use with labview, but is it possible to use it with SignalExpress, with the sound and vibration assistant ?
    Thank you
    Mathieu

    The DT9837 is not directly supported in SignalExpress.  It also does not appear to have IVI instrument support, so using the generic IVI acquisition steps will not work.  You will need to write a user step in LabVIEW using the LV-Link software supplied by Data Translation to get this to work in SignalExpress.  Use the supplied templates so you can get intialization and finalization of the instrument to work correctly.  Let us know if you run into issues.  My apologies for the lack of direct support.
    This account is no longer active. Contact ShadesOfGray for current posts and information.

Maybe you are looking for