Deployment utility gives warning: Cannot update VI Path when trying to update vi paths inside FrontEndCallbacks.seq and StationCallbacks.seq

[Roger_C]

Hi,

I'm trying to deploy a teststand based testsystem using the deployment utility.The deployment utility throws the following warning:

---------------------------------------
Warning: Cannot update VI Path:
Step 'Close TestRack', sequence 'MeasureFixtureID', sequence file 'C:\TS Deployment based on HCCP WS\Image\TSPubDocs\Components\Callbacks\FrontEnd\FrontEndCallbacks.seq'
Step 'Measure Fixture ID', sequence 'MeasureFixtureID', sequence file 'C:\TS Deployment based on HCCP WS\Image\TSPubDocs\Components\Callbacks\FrontEnd\FrontEndCallbacks.seq'
Step 'Initialise TestRack', sequence 'MeasureFixtureID', sequence file 'C:\TS Deployment based on HCCP WS\Image\TSPubDocs\Components\Callbacks\FrontEnd\FrontEndCallbacks.seq'
Step 'IdentifyUUT SerialNumber', sequence 'PreUUT', sequence file 'C:\TS Deployment based on HCCP WS\Image\TSPubDocs\Components\Callbacks\Station\StationCallbacks.seq'
+++++++++++++++++++++++++++++++++++++++

I've added a sub-sequence in the FrontEndCallbacks.seq which I call from the operator interface. This sub-sequence uses some labVIEW vi's who are found in a LabVIEW project. These same vi's are used inside other test sequences who are distributed without any problem. I also replaced the standard PreUUT subsequence inside StationCallbacks.seq with a version made in LabVIEW .

If I compare the FrontEndCallbacks.seq with the succcesfull deployed test-sequences I see that the vi-path -links are not replaced with the version of the deployed path  (where the vi's are inside a packed library).

For some reason it's not possible for the deployment utility to replace the links inside  FrontEndCallbacks.seq and StationCallbacks.seq ?

Thanks,

Roger

[Manooch_H]

Roger -

Are there any other Warnings prior to these? For example, do you receive this Warning as well:

Warning: There is no relative path between the following files.  You may need to add a path to your search directories.

I'm trying to reproduce the exact behavior you are seeing.

[Roger_C]

Hi Manooch,

Thanks for the reply.

Indeed there are the following warnings:

Warning: There is no relative path between the following files.  You may need to add a path to your search directories.

From [TestStand Public Documents Directory]\Components\Callbacks\FrontEnd\FrontEndCallbacks.seq to [Installation Directory]\HCCP tester\HCCPTesterCode.lvproj

From [TestStand Public Documents Directory]\Components\Callbacks\FrontEnd\FrontEndCallbacks.seq to [Installation Directory]\VIT\HON00\trunk\Src\TestStand\Components\Callbacks\FrontEnd\frontend.dll

From [TestStand Public Documents Directory]\Components\Callbacks\Station\StationCallbacks.seq to [Installation Directory]\VIT\HON00\trunk\Src\TestStand\Components\Models\TestStandModels\modelsupport2.dll

From [TestStand Public Documents Directory]\Components\Callbacks\Station\StationCallbacks.seq to [Installation Directory]\VIT\HON00\trunk\Src\TestStand\StationCallbacks_PreUUT_IdentifyUUT SerialNumber.seq

From [Installation Directory]\VIT\HON00\trunk\Src\TestStand\TestStand Model & Configuration.tpj to [TestStand Application Data Directory]\Cfg\Users.ini

From [Installation Directory]\VIT\HON00\trunk\Src\TestStand\TestStand Model & Configuration.tpj to [TestStand Public Documents Directory]\Components\Language\English\UIControlStrings.ini

From [Installation Directory]\VIT\HON00\trunk\Src\TestStand\TestStand Model & Configuration.tpj to [TestStand Application Data Directory]\Cfg\TestStandModelReportOptions.ini

From [Installation Directory]\VIT\HON00\trunk\Src\TestStand\TestStand Model & Configuration.tpj to [TestStand Application Data Directory]\Cfg\TestStandModelModelOptions.ini

From [Installation Directory]\VIT\HON00\trunk\Src\TestStand\TestStand Model & Configuration.tpj to [TestStand Application Data Directory]\Cfg\TestStandDatabaseOptions.ini

From [Installation Directory]\VIT\HON00\trunk\Src\TestStand\TestStand Model & Configuration.tpj to [TestStand Application Data Directory]\Cfg\StationGlobals.ini

From [Installation Directory]\VIT\HON00\trunk\Src\TestStand\TestStand Model & Configuration.tpj to [TestStand Public Documents Directory]\Components\Callbacks\Station\StationCallbacks.seq

From [Installation Directory]\VIT\HON00\trunk\Src\TestStand\TestStand Model & Configuration.tpj to [TestStand Public Documents Directory]\Components\Callbacks\FrontEnd\FrontEndCallbacks.seq

From [Installation Directory]\VIT\HON00\trunk\Src\TestStand\TestStand Model & Configuration.tpj to [TestStand Public Documents Directory]\Components\Language\English\CustomStrings.ini

---------------------------------------

Warning: Cannot update VI Path:

Step 'Close TestRack', sequence 'MeasureFixtureID', sequence file 'C:\TS Deployment HCCP\Image\TSPubDocs\Components\Callbacks\FrontEnd\FrontEndCallbacks.seq'

Step 'Measure Fixture ID', sequence 'MeasureFixtureID', sequence file 'C:\TS Deployment HCCP\Image\TSPubDocs\Components\Callbacks\FrontEnd\FrontEndCallbacks.seq'

Step 'Initialise TestRack', sequence 'MeasureFixtureID', sequence file 'C:\TS Deployment HCCP\Image\TSPubDocs\Components\Callbacks\FrontEnd\FrontEndCallbacks.seq'

+++++++++++++++++++++++++++++++++++++++

I had to reproduce these warnings again because I've made a workaround by placing a sequence (with the name FrontendCallback_MeasureFixtureID.seq) in the deployed installation directory. FrontendCallback_MeasureFixtureID.seq contains the actual calls to the LabVIEW VI's. In FrontEndCallbacks.seq I call this FrontendCallback_MeasureFixtureID.seq using a SequenceCall adapter. This works great. But I'm still curious if it's possible to use LabVIEW vi's inside the  FrontEndCallbacks.seq and StationCallbacks.seq.

Roger

[Teds]

I have placed VIs in my FrontEndCallback.seq and it does not have any problems relinking to the VIs after the deployment, using TestStand 4.2 and LV 2010  The location of my VIs are in the <TestStand Public> directory after the deployment so that may make a difference.

Perhaps there is some issue with Packed Project Libraries and TestStand.

Thanks,

PH

[Manooch_H]

Roger -

I have reproduced warnings similar to yours and informed R&D of this issue. I will post back to this forum once I have more information. Thank you for bringing this to our attention.

[Roger_C]

PH, Manooch,

Thanks for the replies.  I'm curious to the cause and sollution.

Roger

[Manooch_H]

Roger -

After looking into this further, the reason that you are seeing this behavior is because the FrontEndCallbacks.seq and StationCallbacks.seq reside in a different base directory than the VIs that they call. Thus the Deployment Utility is unable to resolve a relative path from the sequence file to the VI. We are investigating ways to improve the behavior in these types of situations in the future.

For the time being, you can use your above mentioned workaround or you can add a TestStand Search Directory that provides a base directory for the called VIs, then use a relative path from that directory when calling VIs in your sequence files. When you deploy, you would ensure that the same search directory exists on the target machine such that TestStand can resolve the relative path when calling these VIs.