I still cannot find "TestStand "Assemble VIs" tool " in TS 3. Again this goes back to the fact that it has no activation and there for no way of knowing if the serial you entered was one you own or not. The target machine has only the RTE's on it. LabVIEW 7.1 was also the last version that you could put in a random serial in and as long as it was in the right format it would be content and unlock all the features of LabVIEW. The source machine has the full TS and LV systems on it. In any other combination, on the same machine, with LV 7.1 RTE or DEV, it works. National Instruments makes thousands of device drivers available for download on the NI Instrument. I got rid of any other versions of TS or LV, plus all their folders, re-installed TS 3.1 from scratch, mass compiled etcĪgain, the only time I get the error is when I try to run the vi in TS configured to run with the LV 7.1 RTE. Yet, it is working perfectly from LV dev and as a stand alone executable on the same machine at the same time. If I switch to the LV RTE (configure adaptor) on the same computer (source computer) I get the non-executable error. If I use the same vi (Read Char from File) directly as a specified module it will run in TS as long as I am in the LV DEV environment. exe with just this vi using 7.1 app builder it runs on the source computer, and the target computer (which only has the RTE's on it). ![]() ![]() It definitely has something to do with your "Read Characters from File.vi" and its sub vi's. It does not appear to be anything you have mentioned so far.
0 Comments
Leave a Reply. |