Background
I have two LV2012 created Source Distributions (let's call them V1 and V2). V2 is an update to V1 and includes some additional VIs and some modifications to VIs that were within the V1 distribution. In particular; distribution V2 includes a modification to PWMR_Initialise.vi (a VI that initialises a USB RF Power Meter). NOTE: The modification to PWMR_Initialise is internal, we have not modified the Connector Pane.
We have 25 sets of identical target hardware (including the Power Meter) and currently we are deploying either distribution V1 or V2 to a target depending on requirements. Both V1 and V2 are deployed to identical locations, a folder within C:\Users\Public, and as such cannot be deployed together to the same target.
We are creating TestStand Test Sequences on USB Flash drives that we connect to our target hardware and run to drive the instrumentation. If we call PWMR_Initialise.vi from TestStand using an absolute path to its location in C:\Users\Public the same sequence will run on a target with V1 deployed and on a target with V2 deployed.
Problem
Our problems start when I create a VI on the USB Flash drive that calls PWMR_Initialise.vi (a wrapper around PWMR_Initialise) and call that from our TestStand sequence instead of calling PWMR_Initialise directly. If I do that I get two distinct behaviours.
- If the USB Flash drive wrapper VI is created on a development machine with VIs at the V1 standard the TestStand sequence will only run on target hardware with V1 Source Distribution deployed. If I attempt to run it on a target with V2 Source Distribution deployed TestStand returns a VI Not Executable error.
- If the USB Flash drive wrapper VI is created on a development machine with VIs at the V2 standard the TestStand sequence will only run on target hardware with V2 Source Distribution deployed. If I attempt to run it on a target with V1 Source Distribution deployed TestStand returns a VI Not Executable error.
The problems are introduced when the wrapper VI on the USB drive is introduced. It feels like as we introduce a wrapper VI we introduce something that sees the differences between the V1 and V2 versions of PWMR_initialise.vi that are not seen when we call PWMR_Initialise directly from TestStand (without a wrapper).
Any thoughts, suggestions, random ramblings greatly appreciated.
Steve
