If the GPIB-ENET is powered off then a call to IBFIND will crunch for 30 seconds (+/- based on my testing) then return an ID of -1. If you test within your code for that -1 unit descriptor then you can either halt your code or skip the GPIB portion until you can verify that the ENET is powered on (ibfind returns valid unit descriptor).
Ryan Mosley National Instruments, Applications Engineer http://www.ni.com/exchange
My experience is that IBFIND will "crunch" for more than 5 minutes! Is this delay configurable within the NI software, or is it some network timeout, outside the NI domain? If so how do I configure this delay?
