* * *
Welcome, Guest. Please login or register.
Did you miss your activation email?
07-20-2018 -- 12:24:37

Login with username, password and session length

Top 10 Posters

flew-da-coup (1302)
Hawaii596 (994)
USMCPMEL (833)
griff61 (557)
Hoopty (546)
docbyers (544)
MIRCS (535)
PMEL_DEVIL-DOG (509)
Thraxas (498)
CalLabSolutions (484)
Members
Stats
  • Total Posts: 18787
  • Total Topics: 3437
  • Online Today: 119
  • Online Ever: 242
  • (04-19-2014 -- 19:20:34)
Users Online
Users: 0
Guests: 42
Total: 42

Author Topic: LabVIEW 2012 VI's Crash LabVIEW  (Read 1162 times)

Offline Hawaii596

  • 7-level
  • ****
  • Posts: 994
  • Action Taken: +16/-3
LabVIEW 2012 VI's Crash LabVIEW
« on: 04-13-2018 -- 21:04:04 »
Any LabVIEW programmers out there. I've posted in the NI community forums, and haven't gotten much help.  This question is for anyone who is skilled at LabVIEW programming....

Trying to set up a simple VI (Agilent 34420A) to read temperature and log it to a data file.  I am not an expert, but I've done this successfully before.  The problem is not in particulars of writing the program, but a possible corruption in one of my SW installations.  I can pick any unmodified VI from among those available in the standard downloaded driver for the Agilent 34420A, and regardless of which VI I pick, when I press the RUN button, LabVIEW crashes.  I switched over to a Fluke 8508A driver, connected it to the GPIB and the same results.  Either of these, I am able to send *IDN? commands to successfully.  NIMAX works fine.

I also tried editing the INSTRUMENT ASSISTANT, and as soon as I tried editing it, LabVIEW crashed.  I think something is corrupt in my installation. 

Not sure if anyone here may have background to assist.
"I often say that when you can measure what you are speaking about, and express it in numbers, you know something about it; but when you cannot measure it, when you cannot express it in numbers, your knowledge is of a meagre and unsatisfactory kind."
Lord Kelvin (1824-1907)
from lecture to the Institute of Civil Engineers, 3 May 1883

Offline silv3rstr3

  • 5-level
  • ***
  • Posts: 180
  • Action Taken: +3/-2
  • USMC (6492) Precision Measurement Equipment Chief
    • Email
Re: LabVIEW 2012 VI's Crash LabVIEW
« Reply #1 on: 04-16-2018 -- 16:34:04 »
Sounds like a corrupt file would be the cause.  I'd contact NI support on the phone and talk to an engineer.  They've been good in the past at helping me troubleshoot their software. 
“They are in front of us, behind us, and we are flanked on both sides by an enemy that out numbers us 29:1. They can’t get away from us now!!”
-Chesty Puller

Offline Hawaii596

  • 7-level
  • ****
  • Posts: 994
  • Action Taken: +16/-3
Re: LabVIEW 2012 VI's Crash LabVIEW
« Reply #2 on: 04-18-2018 -- 15:12:11 »
What appears to be a difficulty is that on their website, when I try to get official support, it asks for my service agreement information. It is Rev 2012, service agreement has expired.  Cost is about $2495 to get that.  We don't use it enough to justify that cost.  I went to their community forums and posted a query. But not much help.  My latest is that I believe it has to be a corruption in the installation. So I am in the midst of uninstalling and re-installing LabVIEW.  I am trying to run off-the-shelf VI's, not make a custom one. And no matter which one I try to run, whenever I press the RUN button, LabVIEW crashes.  One user said he has been using 2012 SP1 with Windows 7 SP1 for a couple of years, meaning there shouldn't be any compatibility issues. We'll see how the re-install goes.
"I often say that when you can measure what you are speaking about, and express it in numbers, you know something about it; but when you cannot measure it, when you cannot express it in numbers, your knowledge is of a meagre and unsatisfactory kind."
Lord Kelvin (1824-1907)
from lecture to the Institute of Civil Engineers, 3 May 1883

 


DISCLAIMER:  This site is not an official US Air Force site, it is intended for private use only.  It is not endorsed, in any way, by the US Air Force, the DoD, or any other governmental agency.  Additionally, all information found within this site is just that, it is NOT meant to be used in place of authorized publications.


All logos and trademarks in this site are property of their respective owner.

All forum content is the property of the respective poster, all the rest © 2004-2017 by PMEL Forum.