NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW RTE Search Paths Capitalization [LV/TS]

Not sure if this belongs into LV or Ts so I'm posting on both.

I'm getting the following error when I try to run a sequence in TestStand 4.1 with the LabVIEW 8.5 RTE as my adapter.



Is there a flag in the ini config file that I can set to make my paths not case sensitive???

Thanks,

<<-N->>

0 Kudos
Message 1 of 6
(3,684 Views)
Hi <<-N->>,

The problem is that TestStand is trying to load a vi with the same name, and regardless of the differences in the path (whether different folders or even different drives) that you specify, if the vi being called has the same name, then this error will occur. Although there are other workarounds, what I would recommend in this case is to copy the vi that you are trying to load and rename it, so you would have two of the same vi's that are only differentiated by their name. Happy Programming. 
Jonathan F.
National Instruments
Applications Engineer
0 Kudos
Message 2 of 6
(3,658 Views)

Hi Jonathan,

Thanks for your help, I think the problem is more related to the capitalization of one of the folders in the path. My code is trying to load exactly the same VI in memory from the same path (tkwca200 basic setting.vi) but because the first time it was loaded from (...\Common\...) and the second time it is being loaded from (...\common\...) LabVIEW thinks it is a different VI path which to me it is pretty surprising because even the OS recognizes the path as being the same. Is there anything I can do to ignore the capitals in the path?

Thanks,

<<-N->>
0 Kudos
Message 3 of 6
(3,644 Views)
Hi <<-N->>,

Can we see what happens when we put the vi in a directory above the commons folder in the folder hierarchy (i.e. AWG7000)? I just want to see if the problem still occurs above the "common" folder line. Additionally, what happens when you rename the "common" folder to another name? Does the same behavior occur?
 
Jonathan F.
National Instruments
Applications Engineer
0 Kudos
Message 4 of 6
(3,585 Views)
Hi <<-N->>,

I and some of my colleagues have done some more research on the behavior you were experiencing. This was reported to R&D (# 119007) for further investigation. A possible workaround is to make sure the letter casing of the VI Path on the LV step matches the letter casing of the VI on disk.

Jonathan F.
National Instruments
Applications Engineer
0 Kudos
Message 5 of 6
(3,564 Views)

Hi Jonathan,

We found a workaround moving the folders around and that seems to fix the problem. I talked to a support engineer on the phone yesterday and he confirmed that this was a bug in the TS-LV adapter.
This is the procedure we are following to fix the problem:

  • Create a new VI in C:\MyProject\Projects\Component\Everything.vi
  • Add all the VI's within Component as sub-VI's to "Everything.vi"
  • Close LabVIEW
  • Move the whole directory of C:\MyProject\Projects\Component to C:\Component
  • Open Everything.vi.  Help find the VI's it is having a hard time finding.
  • Close LabVIEW
  • Change C:\Component\Product\Common to C:\Component\Product\xxommon
  • Open Everything.vi.  it should automatically find everything without asking you for help
  • Close LabVIEW
  • Change C:\Component\Product\xxxommon to C:\Component\Product\Common
  • Open Everything.vi.  it should automatically find everything without asking you for help
  • Close LabVIEW
  • Move Component back under MyProject directory structure
  • Open Everything.vi.  Help find the VI's it is having a hard time finding.
  • Close LabVIEW
  • Cross your fingers and see if it works this time.
<< - N - >>

0 Kudos
Message 6 of 6
(3,557 Views)