LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error "cannot find terminal hotpoint in wire..." during application build.

Hello,
I'm trying to compile a TestStand 2.0.1 Custom LabVIEW Operator Interface with the LabVIEW 6.1 application builder. During the build process I get six(6) error prompts 'cannot find terminal hotpoint in wire...' and the builder stops and prompts another error that says the one of the VI's 'is not executable'. However, I can open the VI and there are no errors on it and no asterisk on the titlebar. There is only one strange thing I noticed in the VI Hierarchy browser, where for this VI and some others, it display an untitled (new) VI not connected to anything (!?) that does not appear in the block diagram. If you reopen the VI, the mysterious VI is gone.
 The interesting thing is that I can successfully build the application if I try it with another Windows XP sp2 computer with the same exact LabVIEW and TestStand versions. Could anyone help me out here and let know what this error means. I can't find any reference to it here or in google. Thanks!
0 Kudos
Message 1 of 2
(5,354 Views)

Thanks  to Kevin in tech support for investigating these errors. I did find after much work one of the VI's that is causing the "terminal hotpoint in wire..." error. It's a GET EXE STRINGS.VI in the custom OI. I have screen shots of it, but I don't know how to load them here... Anyway, it appears to happen on this particular VI because it has more than 20 connector pain terminals, but not all of the connections appear to be setup in the connector pane. However, this does not prevent the VI or the calling VI (TestStand - Execution Display) from running normally or even displaying a broken arrow (Why Not?). I changed the VI and removed the unused connections and the problem seems to be gone. I still need to find one more VI that is doing this. I also don't know why my Laptop is able to build the OI application OK w/o errors and other PC's always stop the application builder because of these errors.

Any other insight on this issue is greatly appreciated. Thanks,

David A. Gaud

Message 2 of 2
(5,338 Views)