Jump to content
News about the LabVIEW Wiki! Read more... ×

parthabe

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0

About parthabe

  • Rank
    LAVA groupie

LabVIEW Information

  • Version
    LabVIEW 2014
  • Since
    2004

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. parthabe

    Default Conepane

    Eric, Is it because "6x4x4x6" being the first item in the list, and not "4x2x2x4"?! I was facing this issue in LV2016, and it was a nightmare for more than 2 weeks now, until I just stumbled upon this post, esp your reply!
  2. parthabe

    Using LV with SVN

    I think, yes! Is this what you mean?!
  3. parthabe

    Using LV with SVN

    Hi, Am not able to install "vc_redist.x86.exe" on my Win10Pro 64-bit for LV2016 32-bit! It says "Another version of this product is already installed." What should I do now?! Please see to the attached install log & help/guide me. dd_vcredist_x86_20170628181430.log
  4. Hi All, I'm trying to automate the CSI-2 (MIPI D-PHY Compliance Test Application) provided along with the Keysight DSOS404A Infiniium S-Series DSO using LabVIEW. The "Automated DigitalTest App Remote Toolkit" provided by Keysight comes along with an LV project, with a test VI. Steps followed so far... Installed LV 2014 (14.0f1) 64-bit & activated on Windows 7 Pro SP1 64-bit on a NI PXIe-8135 - works fine Installed Keysight Infiniium Scope Application Software & activated the license - works fine Installed IVI drivers compatibile with the Keysight DSOS404A from Keysight website Launched Main Interface VI from inside the project "Example Labview Remote Client" - works fine Filled the correct IP of the Scope & clicked Connect - Connected message popped up Clicked the Refresh Test List button and observed that the list of Available Tests is loaded properly - works fine Select some tests from the list of Available Tests & clicked Run - works fine Clicked the Disconnect button - Disconnected message popped up VI got stopped Now, I clicked the Run button of the VI, and it started throwing .Net error "Object reference not set to an instance of an object" 2 times, and finally threw "Error 1172 occurred at Invoke Node". From now on, the VI wouldn't run properly. Sometimes, closing LV & reopening the VI again is the ONLY way it works properly without throwing the .Net error 1172. Sometimes, waiting for longer time before running the VI is the ONLY way it works without throwing the .Net error 1172. Any help would be highly appreciated, as I'm dumbstruck without having any clue why this behaves so weirdly so far.
×

Important Information

By using this site, you agree to our Terms of Use.