Teststand 2014 freezing when pressing "module"

[ShadowRise]

Hello everyone,

I'm having trouble working with TestStand 2014, loading module.
First of all, I want to make clear that I have all modules placed in the right folders, and I'm using latest versions for TestStand and Labview 2014/2015 (32 bit).

The problem started when i tried to use the "Call executable" function, to call a python file(v3.6). That broke up my TestStand and every other sequence that I have.
Please see the pictures below.

Also I would like to see what other solution i have, before i reinstall everything 😓.

[Oli_Wachno]

Teling from the pictures you posted, TestStand is not able to connect to LabVIEW anymore.

I guess you have tried rebooting the PC 😉

Guess you are working on a development machine, so I'd check if LabVIEW itself starts / if the installation is ok

Next you might want to open the SequenceEditor and check the LabVIEW adapter settings

If this are ok, create a new SequenceFile put in any new step with the LabVIEW Adapter, check if that works

[ShadowRise]

So, i created a new file and i tried to put my project in it, the same issue. This is the company project, which I worked with other sequences until i this one. Also i tried running the "repair" tool from NI package manager and it got this error: 

• The repair operation was not successful due to missing distribution source, user cancellation, or MSI failure. Ensure the source location is accessible or try rebooting and restarting the repair operation. Error code: 1620

[Oli_Wachno]

In order to be better able to help you, we shoul clarify the wording a bit

---

@ShadowRise wrote:

So, i created a new file and i tried to put my project in it, the same issue.

---

Is that: you created a new SequenceFile? What are you referring to as "my project" (.tpj, .lvprj, ?)?

---

@ShadowRise wrote:

[....]
Also i tried running the "repair" tool from NI package manager and it got this error: 

• The repair operation was not successful due to missing distribution source, user cancellation, or MSI failure. Ensure the source location is accessible or try rebooting and restarting the repair operation. Error code: 1620

---

What exactly did you try to repair?

[ShadowRise]

I created a new SequenceFile, where i inserted a new step named "Action" and i tried to use a VI from the project to load it.


I tried to repair TestSTand, see picture below.

[Oli_Wachno]

---

@ShadowRise wrote:

I created a new SequenceFile, where i inserted a new step named "Action" and i tried to use a VI from the project to load it.

---

What do the LabVIEW Adapter Settings on your machine look like? Menu-> Configure-> Adapters-> LabVIEW

Is LabVIEW working standalone without TestStand? Does opening the VI in question directly in LV work? Is it possble to execute?

---

@ShadowRise wrote:

I tried to repair TestSTand, see picture below.

---

IMHO, you get this error because yur TestStand Version is quite old and as such it is NOT installed using NIPM.

You should be able to "repair" the installation using the Windows Control Panel ->  Software (or whatever it is called these days)

Yet I recommend to execute the steps mentioned above BEFORE repairing. Don't panic!

[ShadowRise]

These are the adapter settings 

Also Labview is working alone, and i can run VI's, open projects.

[Oli_Wachno]

Ok, this is good news so far!

What I don't understand yet is, why calling a Python module using a Call Executable Step should screw up the LabVIEW Adapter.

Does it happen to use the TestStand API to configure stuff?

Just to make it clear: you are using the Call Executable due to the lack of Python support in your old TS & LV versions, right?

[ShadowRise]

I tried using a Python script to verfiy a firmware for a DUT.
I don't know if i am using a TestStand API, but i use python because the TS2014 doesn't have a python enviroment like TS2023.

[Oli_Wachno]

One last thing before repairing/ re-installing....

Change the LabVIEW adapter to Runtime, close and restart TestStand and after this switch back to Development Environment to re-chcek
Small hope but worth a try