Below are several comments on troubleshooting LabVIEW and instruNet.
Make sure you are using instruNet software version ≥ 3.6 (iNet32.dll).
To obtain the latest DLL free of charge, click here.
If Labview crashes when you close the last instruNet.vi window, upgrade to iNet32.dll version ≥ 220.127.116.11.
Older versions of iNet32.dll result in "iir bad" alert on startup when working with LabVIEW ≥ v8.
iNet32.dll version v3.0.17 through v3.0.47 contain a bug that causes "Digitize Channel Example.vi" to return array data set to all 0's.
iNet32.dll version v3.0.0 through v3.0.45 contain a bug that causes some versions of LabVIEW to crash upon
exiting the LabVIEW application, in cases where instruNet showed at least one dialog box.
If LabVIEW cannot find iNetLV_I32.vi or iNetLV_U32.vi,
then refer to Shiretech file "Advanced.llb".
If LabVIEW cannot find iNetLV_Params.vi,
then refer to Shiretech file "~subVIs.llb".
If you are not sure if LabVIEW is loading the instruNet driver and connecting
to instruNet hardware, see Getting Started with LabVIEW & instruNet.
instruNet power-up calibration consumes 1 to 10 seconds, depending on which instruNet
hardware is attached to your computer.
This calibration sequence occurs in all of the following cases:
Load instruNet driver, which occurs when one first runs an instruNet vi.
Clear instruNet Settings
(e.g. write "Network Clear" to "Press Button 2.vi" in "instruNet World.llb").
In some cases when one changes sample rate while working with at least one i100 box
(e.g. write to "Config Timing.vi" in "Configuration.llb").
The "Digitize Channel Example.vi" clears settings and sets sample rate each time it is run, which
results in 1 or 2 calibration sequence (one from clear and possibly another from set sample rate).
If you want instruNet to beep when it does it's calibration sequence, for purposes of monitoring this behavior, click