NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Passing 64 bit data type from LabVIEW to TestStand

Hi All,

I have a VI which has 2 terminals, one with "I64" data type and other with "U64" data type. I am not able to use this VI in teststand since teststand shows "Unknown" in the type field of these terminals.

Does TestStand support accessing of 64 bit Data types from TestStand?

I am using LabVIEW 8.5 and TestStand 4.0

Thanks & Regards,
Kaustubh.
0 Kudos
Message 1 of 4
(3,809 Views)
Hi kbsave,
Currently, TestStand does not support 64 bit integers.
 
However, it is something that we are looking at for future releases of TestStand. We are still in the investigatory phase of this, and are looking for feedback to ensure that if we do implement this feature, it is tailored to what our customers actually want/need.
 
Would it be possible for you to answer the following questions to help us better understand the scenarios in which you plan on using 64 bit integers?
  1. What kinds of tests require 64 bit code modules?  Are you storing very large arrays?  Numbers with very high precision? (Assuming this information isn't confidential)
  2. Do you want or need to store these arrays in TestStand's memory space, or can the arrays be used entirely within the code modules?
  3. Do you want or need to be able to pass 64-bit integers to and from the code modules? (I assume from your question that your answer is yes).
  4. For which adapters do you need 64-bit support?
Jervin Justin
NI TestStand Product Manager
0 Kudos
Message 2 of 4
(3,789 Views)
Hi Jervin,

Thanks for the information.
Answers to your questions:

1. We have a Real Time application in PXI which does the time measurements to the extent of 100 microseconds. The VI which does these measurements, stores the timestamps interms of microseconds. This time is stored as real system time (i.e. MM/DD/YYYY HH:MM:SS.mmmmmm converted to a number) Hence to store this, the code needs I64 and U64 data types. Now teststand does the verification of these timestamps and also displays them in report. To access this data I need 64 bit data types.

2. Yes I need to store them in TestStand memory space as well.

3. Yes. I need to exchange the data between TestStand and code modules.

4. I am using only LabVIEW adapter.

As a temporary solution I have modified the VI to store the timestamp as Double and accessed in TestStand. But the original VI is not supposed to process any numbers other than Integers for some reasons. So I have put converters between the data accessed from terminals and actual processing code.

Thanks and Regards,
Kaustubh
0 Kudos
Message 3 of 4
(3,779 Views)

kbsave,

    I've dealt with this issue before. In the end I just added two terminals to act as the upper and lower words of your 64 bit value. (Very easy to see when display mode is set to Hexadecimal) In your case, maybe the MM/DD/YYYY portion goes into the Upper word and the HH:MM:SS into the lower word? It really isn't a big deal. In the LabView realm, you ignore the two 32 bit terminals. When using the VI in Test Stand, the 64bit (Unknown) is ignored and shows up greyed out and only your two 32-bit values are valid parameters . True, like you said, you need to do a little conversion but this will take literally all of a minute to add to your VI with a ‘Split Number’ component found in the  ‘Numeric->Data Manipulation’ pane.

 

Hope this helps.

 

John

Message 4 of 4
(3,758 Views)