12-23-2012 09:54 AM
12-26-2012 06:27 AM
I have used TestStand and Labview for testing Bluetooth in the past.
Testing of other interfaces should be similar.
Few advantages of TestStand :
Integrates with Labview,C++,C# ( Visual studio)
Takes care of process task like serial number,generating different reports.
Simple to use.
If you already installed TestStand you can go through the different examples to get a better view of TestStand.
12-26-2012 10:45 AM
Dear SunRS
many thanks for your help. It is great know haven't installed it yet. I may attend TestStand 1 training so I want to wait and install the evaluation version before the training. have you ever used Pytho. Or any other scripting language for performing these tests? if yes , how did you find Teststand Considering that I have to pay for license .
Do you have access to your source files? I greatly appreciate if you could send me some of your source files so I can dig into it them to get more idea about Teststand for Rf test purpose
many thanks
12-26-2012
11:34 PM
- last edited on
05-08-2025
12:22 PM
by
Content Cleaner
I started with TestStand so dont have much idea about other scripting language.
Sorry i no longer work for the company where i was involved in the BT testing.
We had used Unistone BT device from Infineon for the testing.You can have a look.
The base drivers were developed in Labview ( different functions like connect,send data,disconnect).
These functions were called from TestStand.
If the drivers are already present with the BT device that you will use for testing in C++ or C# then it can be called directly from TestStand.
You can also refer to few labview examples :
https://forums.ni.com/t5/LabVIEW/Interfacing-Zigbee-with-Labview-VIA-RS232/td-p/1122013
Please refer Labview forums for different interfaces.
01-10-2013 08:36 AM - edited 01-10-2013 08:38 AM
Hi en99,
I am unsure what you mean by usign LabVIEW instead of Python - what part of the system would LabVIEW replace? Usually if you were using Python in automated test, it would be to handle the test processing, which in this case is done by TestStand.
As for advantages of TestStand over LabVIEW, the main one which SunRS mentioned is that TestStand has a test management engine, which covers result logging and passing test parameters to the various test modules, which can be written in many languages. As I mentioned above, it is Python which is commonly used to write alternative test managament engines. It is possible to write one in LabVIEW, but for good results it must be carefully architected and is typically a very time-consuming task if you want to keep it modular and use it for other applications. TestStand also has a number of built in tools which help to monitor various aspects of the test sequences, as well as provide multithreading optimisations.
I hope this helps