Hello Fadenoid,
Thanks for your post.
Apologies for the long turnaround in replying to your query.
The situation you've described is actually a known issue within LabVIEW 7.1. Corrective action is being investigated. As the issue is integral to LabVIEW there is no setting within v7.1 that will fix this.
A known workaround is to discover your device(s) in the development environment, record the specific device addresses, and feed those explicitly into the rest of your VI before you build it into an executable.
For information on fixes etc in newer versions of LabVIEW please check our website www.ni.com/labview.
Let me know how you get on with this workaround. If you have any further questions on this issue feel free to reply to this post.
Regards,
National Instruments | Northern California