Collecting SBIGUDrv Logs
SBIGUDrv has the capability of logging all interactions with a calling application, with varying levels of granularity. Enabling it requires the use of SBIG Driver Checker 64.

Enabling Debug Logs

Download, and install the latest version of SBIG Driver Checker 64 from here, and close any applications that can connect to an SBIG camera, closing any active connections as you do. Open SBIG Driver Checker 64, which should appear as it does in the figure below. 

Click the Debug Log button in the bottom-right corner of the window. This will show the Configure Debug Logger window, shown below.

From this window, you’ll need to click the All button, in the Set Checkboxes group, to ensure all driver commands are captured by the log. Next, click the Set Path button, and select a location for your driver log to be saved. We recommend saving it to somewhere easily accessible, such as My Documents. Once you’ve selected a save location for the log, click the OK button to exit the Configure Debug Logger window. Click the Done button on the main SBIG Driver Checker 64 window to finalize the changes.

Logging Best Practice

We advise Deleting logs between imaging sessions to ensure they don’t get unruly. We also advise keeping it off during normal use, since driver logging introduces significant lag in the imaging process.

Submitting Driver Logs

Once you’ve collected a driver log, you’ll need to submit it to us. Since SBIG Driver Logs can get quite largs (being plain text files), we advise zipping the resulting *.txt file prior to submitting it. The files compress very well.

Disabling Driver Logging

Disabling driver logging is done almost the same way enabling it is — except instead of clicking the All button in the Configure Debug Logger window, you click the Clear All button.