[Basti]

Hi @all,

I try to start the VI Tester as shown in the getting started thread.
But all I get is the splash screen followed by an error message:

Fehler 1004 ist bei VI-Referenz öffnen in Get Menu Launch Info__jki_lib_application_control__VI Tester Menu Launch.vi->
VI Tester Menu Launch__VI Tester Menu Launch.vi aufgetreten


Mögliche Ursachen:

LabVIEW: Das VI ist nicht im Speicher.

Um ein VI mithilfe der Funktion "VI-Referenz öffnen" in den Speicher zu laden, muss ein Pfad mit dem VI-Pfad-Eingang verbunden sein.

VI Name: GettingStartedWindow.lvlibp:GSW_Main.vi



I try to translate it into english:


Error 1004 occured by opening VI-Reference in Get Menu Launch Info__jki_lib_application_control__VI Tester Menu Launch.vi->
VI Tester Menu Launch__VI Tester Menu Launch.vi


Possible reasons:

LabVIEW: The VI isn't loaded into memory.

To load a VI with the "open VI-Reference" into memory, a path has to be connected to the VI-Path-input.

VI Name: GettingStartedWindow.lvlibp:GSW_Main.vi


Does anybody know how this can be fixed?

Best regards,

Bastian



btw: I use

LV 2010 f4
jki_labs_tool_vi_tester 1.1.2.164-1

[Omar Mussa]

There had been an issue (that seemed to be resolved in LV2009) where it was not possible to launch VI Tester from the Getting Started Window. It's possible that this is what you are seeing. Try opening a new project file or a blank VI and then launching VI Tester and see if that works. It may be a localization issue for German LabVIEW versions. Please reply once you've tested this (even if it works).

[Basti]

Hi Omar,

thanks for your quick reply. I've tried that but without luck.
Now I only see the splash screen quiet short and that's it. No error message this time.

Is there any possibility to debug this?

Omar Mussa, on 17 February 2011 - 03:12 PM, said:

There had been an issue (that seemed to be resolved in LV2009) where it was not possible to launch VI Tester from the Getting Started Window. It's possible that this is what you are seeing. Try opening a new project file or a blank VI and then launching VI Tester and see if that works. It may be a localization issue for German LabVIEW versions. Please reply once you've tested this (even if it works).

[Omar Mussa]

Hi Basti,

Thanks for your patience. I will try to reproduce the problem.

What localization settings are you using (regional settings/language options)?
What version of Windows are you using?

Thanks,
Omar

[Basti]

Hi Omar,

here is my setup:

Windows XP SP3 german
- preset: Deutsch (Deutschland)
- decimal place is comma


LabView 2010 f4 german


if you need any further informations, please let me know.

Thanks,

Bastian

[Omar Mussa]

Thanks Bastian, I'll see if I can reproduce the issue and get back to you.

[Basti]

Thanks for your support

[Omar Mussa]

Hi Bastian,

Here's what I found:

If I run VI Tester from the menu of the Getting Started Window, I get the same error as you (1004, same dialog text) - this only happened when I changed the regional/language settings to German, so I suspect it is a localization issue - I will add this to our known issues shortly.

However, if I open a new project window and press the VI Tester button:



the VI Tester GUI opens up without an issue.

Did you try this?

Also, when it opens the first time, it asks you if you want to recompile the code in LV2010. Select yes. After this, you should be able to open VI Tester faster and more reliably. I still wouldn't recommend opening it from the Getting Started Window though. Let me know if you're still having launch issues.

One other question - in your localization of LabVIEW, is there a folder called:
[Program Files]\LabVIEW 2010\resource

or does it have another name? Can you copy/paste what that full path looks like?

Thanks,
Omar

[Basti]

Omar Mussa, on 23 February 2011 - 11:15 PM, said:

Hi Bastian,

Here's what I found:

If I run VI Tester from the menu of the Getting Started Window, I get the same error as you (1004, same dialog text) - this only happened when I changed the regional/language settings to German, so I suspect it is a localization issue - I will add this to our known issues shortly.

However, if I open a new project window and press the VI Tester button:

VI Tester Toolbar.png

the VI Tester GUI opens up without an issue.

Did you try this?

Also, when it opens the first time, it asks you if you want to recompile the code in LV2010. Select yes. After this, you should be able to open VI Tester faster and more reliably. I still wouldn't recommend opening it from the Getting Started Window though. Let me know if you're still having launch issues.

One other question - in your localization of LabVIEW, is there a folder called:
[Program Files]\LabVIEW 2010\resource

or does it have another name? Can you copy/paste what that full path looks like?

Thanks,
Omar

Hi Omar,

first to your question, yes the folder resource exists.

I've tried the following constellations:

1. On Startup Screen > click on Werkzeuge (Tools) > VI Tester > Test VI
=> doesn't work, shows the splashscreen and that's it

2. In Project Explorer > click on Werkzeuge (Tools) > VI Tester > Test VI
=> doesn't work, same as above

3. in Project Explorer > click on the "open VI Tester" icon
=> works! The VI Tester App starts up just fine

4. in a VI > click on Werkzeuge (Tools) > VI Tester > Test VI
=> works, too. The App starts up without problems

I think I can live with that ;-)
But if you need any further informations to solve this issue, please let me know.

Best regards,

Bastian

[Omar Mussa]

Hi Bastian,

Thanks for investigating and posting this info. I'm glad you are able to open the VI Tester UI (and luckily, the two cases that do run are probably the most common cases). I've added this issue to our known issues list (Case 10911). Let us know if you have any other issues!

Thanks,
Omar

[Rob Calhoun]

I get the same error when trying to open the VI tester from the LabView Getting Started window. (Windows 2008 R2 Server, VI Tester 1.1.2.164-1, LabView 2010 SP 1. If I open a project first, the VI tester opens fine.

There's no actual need to open the VI tester from the Getting Started window. However, the Getting started guide specifically recommends doing exactly that, which is why I encountered it. It might be good to put a note on that page suggestion starting with an empty project.