NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Arendar type mismatch

Hello,

 

I am using Teststand with LV for wafer level testing and writing the results through an Arendar API to a SQL server database.  The Arendar API provides custom step types to access and write data to the database directly from the TS sequence.  The database field properties can be set as double precision, integer, string and date.  I have not been able to write integer or date strings to the database from Teststand.  Double precision and string values written to database double and string fields work fine.  Arendar can accept formatted strings for date entries.  I believe this has something to do with the TS variable formatting as I can write all field types to the Arendar DB using other data import methods.  Below is the type mismatch error I get.  I'm looking for any suggestions on possible staion settings or variable flag settings that might affect this issue.  I know TS does not support native integer or date formats so I think fixing one will fix them both.

 

Error:

The .NET method 'ArendarTS_WriteProductTest' threw an exception.
Value type does not match the property's data type.
Parameter name: value Source:  ArendarClient
  at VITechnology.Arendar.TestData.TestProperty.SetValue(Object value)
  at VITechnology.Arendar.TestData.TestProperty.set_Value(Object value)
  at NiArendarIntegration.NIArendarIntegration.Arendar_SetProductTestProperties(ProductTest pt, String[] productTestPropertyNames, Object[] productTestPropertyValues)
  at TestStandArendar2007.TestStandArendar.ArendarTS_WriteProductTest(SequenceContext seqContext, ProductTest pt, String[] fieldNames, String[] fieldValues)
[Error Code: -17500]

 

Thanks for the help.

Mike

0 Kudos
Message 1 of 4
(3,124 Views)
You'll have much better luck getting your question answered by posting to the TestStand board or contacting Arendar.
0 Kudos
Message 2 of 4
(3,118 Views)
I could have sworn that I saw this post in a different board. Excuse me if I was wrong.
0 Kudos
Message 3 of 4
(3,102 Views)

It turns out this problem exists when using TestStand 4.0 and Arendar 2007 (V4.0).  VI-Tech fixed the problem in Arendar V4.1.  I'm not sure yet if this function works whith TestStand V4.0 and Arendar V4.1.  I posted this as VI-Tech had been working on this awhile as was I.  VI-Tech responded as to the root of the problem just hours after I posted.  Hmmm....

 

Thanks for your input.

Mike

0 Kudos
Message 4 of 4
(3,097 Views)