Quantcast
Channel: All NI TestStand posts
Viewing all 24388 articles
Browse latest View live

Help with Building a Program for a teststand

$
0
0

Hey there i Started labview in August with the courses Core 1 and 2 and By now im quite into labview. Im Building a labview project for a teststand that has a couple of Sensors and actors. Therefore im im using a cDAQ device with some input and Output Modules for my I/O‘s with daqmx. I Build my program with a big state machine so far But from Talking to colleagues they told me to use More Loops for different Occasions (i.e data aquisition, UI and so on). I stumbeled upon QMH, DQMH and Actor Framework. The Problem for me is to how to Communicate between the loops (i know there are queues and notifiers). But When i acquire data in the one Loop i pass it to Another Loop to Analyze and Modify the data?

Also i was told to Not use Event structures for my User Inputs. Is there Another easy and nice way to Process User inputs?

Thanks for any help!


Managing labview VIs

$
0
0

I have a teststand framework that contains two folders that serve as VI "libraries", with several hundred Vis each. 

 

Up until this point, I have not collected the Vis into project or vilib files.

 

In order to be able to run multiple versions of our code on the same machine and not worry about "cross contamination", I collected the Vis into a vilib and then a project file. I updated all teststand calls to point to the projects.

 

This has caused the sequence editor to slow to a crawl during editing. For example, inserting a statement step takes 5-10 seconds, navigation has constant latency, and editing statements is delayed and extremely frustrating.

 

I have found that disabling the search directory containing the VI allows the editor to be responsive.

 

1) I need to keep the Vis in project files, in order to separate the name spaces, correct? Operators open more than one version all the time on our testers.

 

2) is there a way to fix this and keep the search directory?

 

3) do I need to keep the project files, but move to relative paths and not search paths?  If so, is there an easy way to convert the found VI locations to relative paths? Or will I have to adjust each instance? 

Re: Managing labview VIs

$
0
0

I am not aware of lvlibs slowing down load times....which LV version are you using?

 

My preferred way of preventing cross contamination is to use TestStand Environments and saving code modules in project subfolders.

 

How many custom entries do you have in the search paths? 

 

 

 

Re: Help with Building a Program for a teststand

$
0
0

Welocme to this (with regards to your concern not entirely correct) forum

 

IMHO, your questions are basic LabVIEW questions, so it would be best to ask your questions there, this is the forum for a Test Executive Software called "TestStand"

 

BTW... I'd recommend using DQMH. I don#t think you need the complexity of AF yet.

And theres an example for a use case you are describing for DQMH

 

Re: Help with Building a Program for a teststand

Re: Help with Building a Program for a teststand

Re: Managing labview VIs

$
0
0

Oh, yeah. When you point to a VI from an LV proj in a TS Step, TS tries to load the entire project of VIs into memory, which causes TS to slow down.

 

Referring to a VI through a project is suited when the developer/user is susceptible to making edits that result in cross-linking. Unfortunately, this results in a worse developer experience due to TS loading delays.

 

Easy fix is to leave the lvproj empty in the step configuration when loading the VI so TS doesn't load just every VI and only the dependencies of that VI.

Re: Managing labview VIs

$
0
0

Points given for lvprjs, my previous answer was focussed on lvlis, sorry!

Yet you don't use lvprjs to seperate code, since they don't introduce namespaces.

Also lvprjs may introduce application instance issues


Open Workspace automatically on TestStand Startup

$
0
0

Hello Everyone

 

My question is "is it possible to open workspace automatically after running TestStand".

I mean when TestStand Editor is open, it opens automatically the workspace.

I can't open the workspace directy because I need to change the enviroment first.

I found a way how to load the new environement automatically without the need that TestStand restarts.

But this is working only if I open a shortcut of the TestStand Editor and then load a workspace or a sequence file, not opening the file directly.

I hope my question and explanation were clear.

Thank you in advance for your help.

Re: How can I find what code is modifying a variable?

$
0
0

Did you customize your process model at all, or using any specialized model plugins?

Re: How can I find what code is modifying a variable?

$
0
0

Maybe it doesn't exactly help, but if you define a watch for this object, you can define a breakpoint on value change.

 

Sequence editor UI manipulation in TestStand 2024

$
0
0

I have started using TestStand 2024.  When I make the window smaller the variables/sequences pane dissapears rather than scales. This means i have to resize my Steps pane before I can resuze the UI.  Is there a setting i should be using?  The insertion pallet sticks to left. surely variables should stick to right?

 

I would like to move the toolbar back, forward navigation buttons to the right hand end of the toolbar. Even though i have set toolbars as editable I cannot move the buttons around.  Is this possible?

 

Thank you

Michael.

 

Re: Error when logging to MySQL database after windows update

$
0
0

finally we encountered the issue again and could track it down to binary data in a SQL statement (PROP_BINARY).

 

We changed the client ODBC driver from MySQL ODBC connector 8.0.32 (x64) to MariaDB ODBC connector 3.1.20 (x64) which solves the issue (up this date, crossing fingers now...)

 

Re: Managing labview VIs

$
0
0

It sounds like you are calling "source code" in your TestStand sequences instead of code modules which have been thru a build process.

I would build code module in to PPLs and then call the export VIs in the PPLs from TestStand. The PPLs are versioned, so you know exactly which version of the code you are using.

 

Further more it enforces a workflow where you separate the development of code modules from the development of the test sequences. You can build your PPLs with debugging enabled, so that you can step in to them and set breakpoints for debugging, but you cannot change any thing on the spot. You are forced to find the bug, close TestStand, open LabVIEW, fix the bug, build a new version of the PPL, deploy the new PPL and try it in TestStand.

 

I know that many people will consider this extra work, but it will increase the quality of your work and give you less headaches in the long run.

Re: Managing labview VIs

$
0
0

Yet, there is a bit of a lerning curve using PPLs, so if you haven't worked with them already, this might be a wholre different can of worms... 


Re: TestStand cannot locate a LabVIEW Run-Time Engine of version '9.0' and bitness '64-bit'.

$
0
0

Hi,

My old application is missing LabVIEW runtime engine of version 15 32bit. Should I install RTE of year 2015 32 bit to my new computer? I already have installed 2024 Q3  32bit version.

Re: Can't exit TestSTand because of IOConfigurationFramework loading exception

$
0
0

Same situation on my side.

I had TS 2020 64bit installed and then installed 32bit version too.

The 32 bit version has the same behaviour you describe.

No solution found yet.

Re: Can't exit TestSTand because of IOConfigurationFramework loading exception

$
0
0

Hi,

Can you post the error msg you are getting?

Regards,

Anand Jain

NI

Re: Can't exit TestSTand because of IOConfigurationFramework loading exception

Re: TestStand cannot locate a LabVIEW Run-Time Engine of version '9.0' and bitness '64-bit'.

$
0
0

@TarmoP wrote:

Hi,

My old application is missing LabVIEW runtime engine of version 15 32bit. Should I install RTE of year 2015 32 bit to my new computer? I already have installed 2024 Q3  32bit version.


Since you posted here (instead of the LabVIEW forum) can we assume your question is somehow related to NI Teststand? Please clarify.

 

Yes, you can install any runtime version, even if you have LabVIEW installed. Of course there could be problems because 2015 is not tested in windows 11 (details). Does your application just need the runtime or does it also require specific drivers, for example?

Viewing all 24388 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>