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

Create Custom Step Type (CST) using ASAM XIL steps

October 21, 2024, 12:41 pm
$
0
0

I am trying to create a Custom Step Type consisting of multiple (pre, post and custom) ASAM XIL steps.

 

I add a Sub Step (Pre) and set the interface to .NET and select the AsamXilPlugin.dll as the Assembly. I select StepVariables.TargetScript+SetParameterValues (not creatable) as the Root Class.

 

I have no idea how to set the .NET Invocation such that it allows me to select the Create Script (initially set to In Configuration) or how to get the dropdown so that I can enter the strings in the VeriStand sequence to set.

 

I then want to add more pre and post steps to Load Script to Target, Start Script, Get Parameter Values, and Destroy Script on Target (to return it to the In Configuration state).

 

The purpose is to create a CST that allows me to do all of these behaviors without having to have 6 intermediate steps every time I want to call a VeriStand sequence which is the purpose of creating a CST.

 

If I can get the basic functionality described to work, then I want to add another sub step where the data is loaded from Locals for each of the passed parameters to the VeriStand sequence since that data is read out from a YAML file using a Python script.

 

Any help would be greatly appreciated.

 

Thanks

Randy

↧
Search

Re: Error when logging to MySQL database after windows update

October 21, 2024, 2:43 pm
$
0
0

Since the error message did not include any stack information, unclear what operation in the DBLog.dll that is throwing the exception. Some questions that might be of value to help someone from NI to reproduce:
1. What version of MySQL are you using?

2. Are you using the default schema, or have you altered it in some way?

3. Do you have any information on what Windows Update installed that preceded seeing the error?

↧
↧

Re: TS 24 and .Net 8.0, big disapointement

October 21, 2024, 10:20 pm
$
0
0

I haven't gone down this rabbit hole yet, but I'll soon have to...

 

Guess you've seen

 

Oli_Wachno_0-1729574201570.png

 

 

From what I understand, the TestStand development has decided to follow a different .net support strategy than the LabVIEW Team for IMHO the sake of implementation speed.

 

Though I have to admit, that I find it quite confusing and difficult to find intuitive information for non-.net pros.

↧

Re: TS 24 and .Net 8.0, big disapointement

October 22, 2024, 12:57 am
$
0
0

Hi jungledede,

 

TestStand is still in the process of migrating completely to .NET Core. The .NET adapter (which is responsible for loading and executing your code module) is already fully in .NET 8.

The Sequence Editor, built-in step types and tools etc which are also .NET based are not migrated yet and this is being worked on for the next TestStand release. Once done, all these applications will be in .NET 8 as well. Currently they are still in .NET framework 4.8.

 

You should be able to target your code modules to .NET 8 and use them with TestStand 2024 Q4, that is the expected workflow.

 

From the fact that you are able to execute your dll through a .NET 8 executable without issues and that the exception is not a FileNotFound but rather InvalidOperation, i would suspect that the issue might not be related to having dependencies in the GAC.

 

Would you be able to provide a simplified version of your code which shows the error so we can check what's going on. Just based on looking at your code snapshot, i am unsure why an InvalidOperation exception is being thrown.

 

Regards,

Tinu

 

 

↧

Re: Appel d'une .dll qui s'appuie sur la technologie COM (Component Object Model) de Microsoft dans TestStand

October 22, 2024, 2:01 am
$
0
0

Après plusieurs recherche, je commence à avoir un semblant de début de piste. 

 

1. En effet, j'ai essayé de créer un VI LabVIEW, qui fait l'interface entre la DLL et la séquence TestStand, en utilisant le bloque "Ouvrir Automation" de la bibliothèque "Connectivité" de LabVIEW. 

Cela m'a permis d'afficher les classes et les méthode de la DLL. Puis faire appelle à ce VI d'interface depuis TestStand pour accéder aux fonctions et méthodes de la DLL. 

Capture_Automation.PNG

 

Maintenant, lors de l'exécution de ce VI (d'interface), j'ai l'erreur ci-dessous que je ne comprend pas.  

Erreur_Automation.PNG

 

 

2. La deuxième piste, au lieux d'utiliser "automation ouvrir", j'utilise le bloque "Appeler une fonction d'une dll" dans un vi, et pareil des problème lors de l'exécution, et voici le message cette fois-ci : 

Ouvrir_une_fonction_DLL.PNG

 

 

Comme vous pouvez le deviner, j'ai des connaissances très basiques sur tous ce qui est LabVIEW et TestStand. Alors toute aide ou orientation est la bienvenue :). 

 

Bien à vous, 

 

 

↧
↧

Re: Error when logging to MySQL database after windows update

October 22, 2024, 2:06 am
$
0
0

Thank you! After posting here I found where to file bug reports directly to NI. And in that report I included the information you suggest.

 

Actually we have small modifications to the default schema. However, that same modification is applied to all the schemas and it is only the PROP_BINARY that is throwing the error. But I will try running with an unaltered database schema to verify that our modification doesn't introduce this error.

 

For reference, no error on Windows 10 build 19045.4894 but it is present on build 19045.5011

↧

𝕎𝕙𝕖𝕟 𝔸𝕝𝕝 𝔼𝕝𝕤𝕖 𝔽𝕒𝕚𝕝𝕤, ℂ𝕒𝕝𝕝 𝕥𝕙𝕖 ℚ𝕦𝕚𝕔𝕜𝔹𝕠𝕠𝕜𝕤 𝔼𝕟𝕥𝕖𝕣𝕡𝕣𝕚𝕤𝕖 𝕊𝕦𝕡𝕡𝕠𝕣𝕥 ℕ𝕦𝕞𝕓𝕖𝕣: 1-804-635-0107

October 22, 2024, 7:07 am
$
0
0

𝕿𝖍𝖊 𝕼𝖚𝖎𝖈𝖐𝕭𝖔𝖔𝖐𝖘 𝕰𝖓𝖙𝖊𝖗𝖕𝖗𝖎𝖘𝖊 𝖘𝖚𝖕𝖕𝖔𝖗𝖙 𝖓𝖚𝖒𝖇𝖊𝖗 𝖎𝖘 1-804-635-0107. 𝕿𝖍𝖎𝖘 𝖑𝖎𝖓𝖊 𝖕𝖗𝖔𝖛𝖎𝖉𝖊𝖘 𝖉𝖊𝖉𝖎𝖈𝖆𝖙𝖊𝖉 𝖆𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖈𝖊 𝖋𝖔𝖗 𝖚𝖘𝖊𝖗𝖘 𝖊𝖝𝖕𝖊𝖗𝖎𝖊𝖓𝖈𝖎𝖓𝖌 𝖎𝖘𝖘𝖚𝖊𝖘 𝖜𝖎𝖙𝖍 𝖙𝖍𝖊 𝖘𝖔𝖋𝖙𝖜𝖆𝖗𝖊, 𝖔𝖋𝖋𝖊𝖗𝖎𝖓𝖌 𝖍𝖊𝖑𝖕 𝖜𝖎𝖙𝖍 𝖙𝖊𝖈𝖍𝖓𝖎𝖈𝖆𝖑 𝖕𝖗𝖔𝖇𝖑𝖊𝖒𝖘, 𝖆𝖈𝖈𝖔𝖚𝖓𝖙 𝖎𝖓𝖖𝖚𝖎𝖗𝖎𝖊𝖘, 𝖆𝖓𝖉 𝖒𝖔𝖗𝖊. 𝖀𝖘𝖊𝖗𝖘 𝖈𝖆𝖓 𝖗𝖊𝖆𝖈𝖍 𝖔𝖚𝖙 𝖋𝖔𝖗 𝖘𝖚𝖕𝖕𝖔𝖗𝖙 𝖙𝖔 𝖊𝖓𝖘𝖚𝖗𝖊 𝖙𝖍𝖊𝖞 𝖌𝖊𝖙 𝖙𝖍𝖊 𝖒𝖔𝖘𝖙 𝖔𝖚𝖙 𝖔𝖋 𝖙𝖍𝖊𝖎𝖗 𝕼𝖚𝖎𝖈𝖐𝕭𝖔𝖔𝖐𝖘 𝕰𝖓𝖙𝖊𝖗𝖕𝖗𝖎𝖘𝖊 𝖊𝖝𝖕𝖊𝖗𝖎𝖊𝖓𝖈𝖊.

↧

When will we get a new version of ASAM XIL for TestStand 2024 Q4

October 17, 2024, 12:42 pm
$
0
0

I am using TestStand 2023 Q4 and installed the 2024 Q4 and tried to install ASAM XIL.

 

Using NI Package Manager it only gave me option to remove ASAM XIL since it was already installed for 2023 Q4. I removed and reinstalled and it did it for 2023 Q4 version.

 

I tried copying the ASAM XIL files from 2023 to 2024 but that didn't work.

 

How do I make ASAM XIL work for 2024??

 

Thanks

Randy

↧
Search

How can I find what code is modifying a variable?

October 22, 2024, 12:42 pm
$
0
0

I have a weird one.

 

I am using the normal sequential model.

 

Something in my code is adding a property (container + string) to UUT.AdditionalData.  It's not the end of the world, but I can't pinpoint WHEN it's happening.

 

It's getting added between Pre-UUTLoop and Pre-UUT.

 

If I go to the model and put a breakpoint before Pre-UUT, there is no subProperty after PreUUT Loop runs.

 

When I clock STEP INTO on Pre-UUT, it's there.  Instantly.

 

I have searched for the property name in all my sequences, and I have found the code I wrote that creates it.  But that code runs well after this point.  I added a BP to it just to check and sure enough it happens later on.  (That step also creates a bunch of other variables, so that's not the code that's causing this).

It's POSSIBLE that I put this into labview code that's getting called, but there's no way it's running async and waiting for the engine to enter PreUUT.  And I checked the threads, there's two, but one is not running code (just used to launch an external utility and waits for it to exit).

Is there a way to block changes to a variable at runtime, and then have TS throw an error?  That would at least point me to what's trying to mod it.

↧
↧

NI Teststand Base Deployment Engine - cannot register

October 22, 2024, 7:08 pm
$
0
0

We have a NI Teststand Base Deployment Engine License 

After the PC motherboard is changed, we are now unable to register.

Please check the video from the link below.

https://www.ce.com.hk/doc/ni.mp4

Please help to solve

↧

Re: Support for Git

October 22, 2024, 11:51 pm
$
0
0

While NI is thinking about Git support, I cannot comment on the timeline.

 

I am assuming that you have updated .gitattributes to configure it to use lvcompare tool for *.vi file type. To make it easy to work with sequence files in Git, similar to using lvcompare, you can update .gitattributes to use TestStand File Diff/Merge utility for *.seq files.

 

-Shashidhar

↧

Re: NI Teststand Base Deployment Engine - cannot register

October 23, 2024, 12:24 am
$
0
0

This error is due to the NI License Manager recognizing that the computer hardware identifiers have changed. The disconnected licenses are tied to these identifiers and need to be replaced if the hardware changes

↧

Re: Error when logging to MySQL database after windows update

October 23, 2024, 12:38 am
$
0
0

Hi,

we are facing the same issue since the cumulative Update for Windows 10 21H2 for x64 based Systems (KB5044273) has been rolled out to our new production line's PCs. This turned us crazy for a whole day until we tracked it down to the Windows update. We assume that a change in the .NET framework causes this by a difference in the SQL Client.

We are running it against a MariaDB 10.10 (x64) and are using MySQL ODBC 8.0 Unicode client.

 

Would be great if you could share the reply to your bug report herein also.

 

↧
↧

Re: Error when logging to MySQL database after windows update

October 23, 2024, 12:40 am
$
0
0
@greenferret wrote:

Thank you! After posting here I found where to file bug reports directly to NI. And in that report I included the information you suggest.

 

Actually we have small modifications to the default schema. However, that same modification is applied to all the schemas and it is only the PROP_BINARY that is throwing the error. But I will try running with an unaltered database schema to verify that our modification doesn't introduce this error.

 

For reference, no error on Windows 10 build 19045.4894 but it is present on build 19045.5011

Thanks for the info! It's tricky without the stack trace, but your questions are a great starting point. To add on:

  1. Knowing the MySQL version is crucial since certain versions handle database operations differently, and some may have compatibility issues with DBLog.dll.

  2. The schema changes could definitely play a role. Any customizations or non-standard schema alterations might cause unexpected behaviors, especially if DBLog is assuming a default structure.

  3. The Windows Update part is also key—updates sometimes break compatibility with certain libraries or dependencies. If there's a list of recently installed updates, that could help narrow things down. C4Yourself

Hopefully, someone from NI can weigh in with more insight, but these details should help with troubleshooting!

↧

Re: NI Teststand Base Deployment Engine - cannot register

October 23, 2024, 12:42 am
↧
Search

Re: Error when logging to MySQL database after windows update

October 23, 2024, 1:38 am
$
0
0

Thank you too for your quick reply. We are one step further:

 

We uninstalled the update package KB5044029, then after a reboot Teststand could log into the MariaDB server again without the failure.

 

The description of this package:

October 8, 2024-KB5044029 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 10 Version 21H2 and Windows 10 Version 22H2

 

To us it proves that there was an incompatible change in the .NET framework handling the SQL connection.
Curious now to get the correct answer from NI.

↧

Re: Error when logging to MySQL database after windows update

October 23, 2024, 5:01 am
$
0
0

Interesting, we have also seen that uninstalling a Windows update solves the issue but identified other ones:

Windows 10: KB5044273

Windows 11: KB5044285

If we uninstall them it starts working again.

↧
↧

Re: Unable to load TestStand application and no error message after crash

October 23, 2024, 2:12 pm
$
0
0

An other reason I get this issue was access rights on the folders and content of a 'relocated' configuration (Cfg + Public under a SVN working copy, using registry keys). The folder was created with admin rights, and (I guess) SeqEdit was unable to modify some of the files.

 

For reference, I fixed the issue by adding Modify permission for local users to the folder (working copy) containing the configuration files.

↧

Problems passing arguments from teststand to python

October 23, 2024, 6:12 pm
$
0
0

Hi,

 

I am trying to run a python code with teststand but i am having type errors while executing the step.

 

For example, even the simple code below is throwing an error:

 

<class 'TypeError'>
'float' object is not callable

TypeError: 'float' object is not callable

 

Code:  

deftest (num😞
    num=num+1
    returnnum

 

benjohnk_0-1729732320170.png

 

benjohnk_1-1729732333140.pngbenjohnk_2-1729732356674.png

 

↧

Re: Problems passing arguments from teststand to python

October 23, 2024, 6:14 pm
$
0
0

Please help out on how to solve this issue.

↧
Viewing all 24417 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>