LogToDatabase custom Step Type

[asafv]

I made my own  Step type based on the Standard NumericLimitTest of NI.

Steps which are based on my steptype does not logToDatabse to table  'MEAS_NUMERICLIMIT'

What do I have to do in order to log those Kind of steps into 'MEAS_NUMERICLIMIT'

from what I see my step type should be a type of 'NI_LimitMeasurement' which is the type that the log to the database .

In other words how do I determine the type of a custom step type to be  'NI_LimitMeasurement' .

Thanks in advance

[markus kossmann]

You have to add that steptype to the "Types to log" field in the STEP_NUMERICLIMIT statement in the database options.  

[asafv]

Thanks for the Quick answer

I already knew that . but We are developing a  significant  amount of custom step types based on the basic numericLimitTest  of NI .

I want to know if there is any way to identify all these custom step type as a group (as a NumericLimitTest group ) thus , every time the logToDatabase identify

a step as a part of a this  group it will log it to the database  as a NumericLimitTest without the need to mark to the database every new step type.

therefore I refered to the MEAS_NUMERICLIMIT table   that  the value  'NI_LimitMeasurement ' in the 'Types To Log' field covers all the types of NumericLimitTest.

If there is no way to Identify a Group of StepTypes then How many StepTypes The 'Types To Log ' field  can contain ?.

[j_dodek]

Hi,

Is it possible to post an example that Forum-members can investigate it ?

Greetings

Juergen

[asafv]

Hello all

I would like to add the callback of 'LogToDatabase' into the sequence in order to pass my parameters to the  'logToDatabase' procedure.

when I'm passing the Databaseoptions cotainer I got this error : 'Type of argument expression 'Locals.ResultList[0]' is incompatible with parameter 'DatabaseOptions'.  Expected Container, Instance of Type 'DatabaseOptions', found Result'

does anyone know how to pass my parameters to the LogToDatabase callback

[RayFarmer]

Hi,

The ResultList is the first parameter of the LogToDatabase sequence.  The DatabaseOptions is the sixth parameter of LogToDatabase. You need to make sure you are passing the parameters in the correct position.

LogToDatabase is called in the ProcessModel or as part of the on the fly mechanism. You dont call this directly from your SequenceFile.

In the default LogToDatabase sequence detailed in the ProcessModel sequencefile is one step which calls Log To Database in the file Database.seq

When you override the sequence callback, you start with with and empty sequence, (unless you have the checkbox set in the preferences). As a minimum you need that step from the default LogToDatabase sequence put in your override LogToDatabase sequence plus your  additional functionality.

Regards

Ray Farmer

[asafv]

Hi Ray.

I'm trying to pass parameters from my sequence to the DatabaseOptions container,

 in order to that I did the following :

1. add the logToDatabase callback into my Sequence

2. I filled the  parameters of the logToDatabase in my sequence with the values that I want.

3. I called  inside the LogToDatabase to the database.seq sequence

4. I made connection between my logToDatabase sequence parameters , to the database.seq parameters.

5. I found out that the parameters of database.seq is not taken from the parameters of my LogToDatabase sequence but from the sequence editor from the station parameters.

attached is my simple test file in TestStand 2.0

Thanks in advance.

[RayFarmer]

Hi,

Had a quick look at your attached sequencefile.

I'm trying to pass parameters from my sequence to the DatabaseOptions container,

 in order to that I did the following :

1. add the logToDatabase callback into my Sequence

2. I filled the  parameters of the logToDatabase in my sequence with the values that I want.

Ok the usual method of filling the DatabaseOptions is to use the DatabaseOptions callback sequence. But filling them in the LogToDatabase as a Local probably would have worked if you had actually used it.

But you are passing Parameter.DatabaseOptions as a parameter to SequenceCall step in LogToDatabase. Change this parameter to use Locals.DatabaseOptions. At the moment you are still using the setting defined in the Configuration menu Database Options....

3. I called  inside the LogToDatabase to the database.seq sequence

4. I made connection between my logToDatabase sequence parameters , to the database.seq parameters.

5. I found out that the parameters of database.seq is not taken from the parameters of my LogToDatabase sequence but from the sequence editor from the station parameters.

attached is my simple test file in TestStand 2.0

See attached picture

Regards

Ray Farmer

Message Edited by Ray Farmer on 01-24-2008 09:56 PM