Modifying reportgen_txt.seq

[Have GUI will travel]

I have slightly modified "reportgen_txt.seq" (obtained from "C:\Program Files\National Instruments\TestStand 3.1\Components\NI\Models\TestStandModels") and placed the modified copy in "C:\Program Files\National Instruments\TestStand 3.1\Components\User\Models\TestStandModels".

According to some other posts (eg, http://forums.ni.com/ni/board/message?board.id=330&message.id=9750&view=by_date_ascending&page=1), TestStand should use this modified copy as long as it has the same name as a file in the ...\NI area.  But my ...\User file only gets used if I rename the one in the ...\NI path (so that it isn't recognized).

I can't leave the ...\NI file renamed since it will inevitably be needed by other .seq's.

Now that I think of it, even if I get this working, other .seqs would use the one in the ...\User area. Do I have to go all the way and specify a custom process model for my main sequence file to use, or is there a less drastic solution.

Am I missing an option or doing something else wrong? (I am using on-the-fly reporting and have the "Sequence" Report Configuration option selected).

Thanks for any help.

Jon S.

[Tyler T.]

Jon,

If you are using On The Fly report generation, then different sequences are called in the "reportgen_txt.seq" Sequence File, than the normal calls that are made from TestReport callback.  In fact, the entire TestReport callback is skipped if you use On The Fly reporting.    It may be that your sequences are not being called as expected.  Try placing a breakpoint in the "Initialize OTF" sequence of the "reportgen_txt.seq" in your "Compenents\User" directory.

That being said, however, the "reportgen_txt.seq" in your User directory should be called.  This is because the User directory comes before the NI directory in your Search Directories.  Additionally, the "reportgen_txt.seq" Sequence File is called as a relative path.  That means, that TestStand should search for the "reportgen_txt.seq" and it should find it first in your User directory.  Place a breakpoint in the "reportgen_txt.seq" file that is called in both the NI and User directory to determine which sequence is being called.  If the NI sequence is being called, then you should check your Search Path configuration to be sure that the User directory is higher than the NI directory.

Please let me know if you have questions or are still experiencing a problem.

Thanks,

Tyler Tigue

[Have GUI will travel]

Tyler,

I double-checked by doing what you suggested, and it definitely uses the report_gen.txt from the NI\Models area. The only way I can get it to use the one in the Users\Models is to rename the one in the NI\Models area.

I also looked at the "Edit Search Directories" screen. The "User Components Directory" is above the "NI Components Directory" and both are checked.

Maybe because the Process Model is in the /NI path, it doesn't bother to look elsewhere for reportgen_txt.seq? Anyway, unless I can find another solution, I will probably use a customized process model.

Thanks for your suggestions.

Jon

[Tyler T.]

Jon,

I did a little further investigating and I think I understand what was occuring.  Because the Process Model Sequence File exists in the same directory as the reportgen_txt.seq under the  <Compenents>\NI\Models\TestStandModels directory, the reportgen_txt.seq in the same directory will be used before the reportgen_txt.seq in the User directory.  If you copy your Process Model and place it into the <Compenents>\User\Models directory where your modified reportgen_txt.seq exists, then the modified reportgen_txt.seq will be used.  TestStand will search the directory of the calling SequenceFile before it searches the remainder of the Search Path directories.

Let me know if you have any questions.

Thanks,

Tyler Tigue
Applications Engineer
National Instruments

[Have GUI will travel]

Tyler,

That's what I did and that's how it seems to work (with and without on-the-fly reporting).

Thanks for your replies.

Jon