WORKING WITH INSTRUNET DIAGNOSTIC REPORTS TROUBLESHOOTING > REPORT >
There are several ways to create an instruNet Diagnostic report text file, for purposes
of debugging an instruNet system. This text file can easily be emailed to an instruNet
supplier for comment when troubleshooting.
Generating A Diagnositic Report with instruNet World Software
Run instruNet World software and select "Internal Diagnostic Report" under the Help menu to print a diagnostic report. Then, select all of the text (select Select All under the Edit menu or press Control A), copy the text to the clipboard (select Copy under the Edit menu or press Control C),
paste into an email window (select Paste under the Edit menu or Control V) and then email to your instruNet
supplier for comment. Alternatively, one can press the SAVE AS button to save the text to a file on disk (remember where you place it), and then email it as an attachment. If instruNet World crashes
upon launch or you are not working with instruNet World software, then please resort to the methods below.
Generating A Diagnositic Report From other Software
With version ≥ 3.4 of the instruNet software, one can enable the writing of diagnostic text
to a file within the "..Documents\instruNet\End User\Diagnostic_Reports\.." directory. One
enables the generation of this report when any program that works with instruNet
software is executed (e.g. instruNet World, DasyLab, C/C++, Basic, etc) by placing
an empty text file named
"iNet Digitize Log On.txt"
into the "..MyDocuments\instruNet\End User\" directory. The writing of this file occurs when you close the instruNet driver, which typically occurs when you exit your application program. One can turn this
Diagnostics mode off by changing the "iNet Digitize Log On.txt" filename to another
name (e.g. change "..on" to "..OFF"), or by placing the word "off" into the body of the file using
WordPad or NotePad software.
After you generated that one file ("..MyDocuments\instruNet\End User\Diagnostic_Reports\.."), you can email it to your instruNet supplier for comment.
Run software that accesses instrunet and then exit that software. Make sure that only one program that accesses instruNet runs at a time.
File "..MyDocuments\instruNet\End User\Diagnostic_Reports\.." is created and contains diagnostics text. Copy this to another location to capture it (else it might be rewritten if someone else runs instruNet).
Rename filename "..MyDocuments\instruNet\End User\iNet Digitize Log On.txt" to "..MyDocuments\instruNet\End User\iNet Digitize Log OFF.txt" to turn off diagnostics capture.
Generating a Report during a Crash
An an alternative to the above
"iNet Digitize Log On.txt"
trick is to instead use "iNet Diagnostics On.txt". The difference is the later writes to the diagnostics file each time something happens within the instruNet system. The advantage to this is you will have a log file if your program crashes before it closes the instruNet driver. The disadvantage is this feature significantly slows down the launching of your program.
Generating An instruNet Driver LOG file
With version ≥ 3.4 of the instruNet software, one can enable the writing of a log file to the
"..MyDocuments\instruNet\End User\Diagnostic_Reports\.." directory. This file contains one
row of text that is printed each time one calls a subroutine in the iNet32.dll driver DLL. The beginning of
each log row contains the words "LOG INET" and the time in seconds since opening the instruNet driver. This file is updated on disk when
one resets instruNet or when one closes the instruNet driver. This log feature is supported with all instruNet
software (e.g. instruNet World, DasyLab, LabVIEW, C/C++, Basic, etc) and is enabled by placing
an empty text file named "iNet Main Log On.txt" into the "..MyDocuments\instruNet\End User\" directory. One can turn logging off by changing the filename (e.g. change "..On" to "..OFF"). Since the writing to disk only occurs during reset and driver close, logging is quite fast; however it will slow down your software a tiny amount.
Enabling Additional Error checking
With ≥ 3.1.6 instruNet software, one can turn on additional internal error checking with the following steps: create
a text file named "iNetLoad.ibs" and place it inside the "...MyDocuments\instruNet\end user\" directory or place it in the same directory as your application program. This is an instruNet Script file that
is executed when you first open the instruNet driver. Inside this text file place "calibrate checkon" on line 1
and "delete all" on line 2. This will cause the iNet32.dll instruNet interface dll to do extra error checking
and report more information when there is a problem. To see if this error checking is on, open the
instruNet World window from within your program , select "Installed Hardware Report" under the Hardware menu, and look
for "DevOn_" printed at the top of the window. If you see this, then it means that extra error checking is