After being idle or running for a long time, automatic document reading does not work

Issue

After a long idle period or extended operation, the hardware document presence sensor stops triggering: automatic scanning does not start, while a manual scan via the Document Reader app still works.

Solution 

When the DebugView buffer grows without limit, log display errors occur. As a result, events from the hardware sensor are no longer processed correctly, and auto-start scanning stops.

1. Make sure you are using the current SDK version.

2. If you do not need to save logs, disable the Do reader logging and Do RFID logging options in the application’s settings: open Document Reader → Settings → General, and uncheck the corresponding options:

   

3. If log saving is required, close Document Reader, then locate and launch DebugView:
   • Via the Document Reader icon: open the Start menu, find Document Reader, right-click it and select Open file location. Run DbgView.exe.
   • Directly from the installation folder where Document Reader is installed (by default):
     • x64: C:\Program Files\Regula\Document Reader SDK\DbgView.exe
     • x86: C:\Program Files (x86)\Regula\Document Reader SDK\DbgView.exe
4. Limit DebugView output:

   • Open Options → History Depth… and set a limit, for example, to 5,000–10,000 lines. Do not use 0 (no limit).

     

   • Enable file logging with wrap-around: go to File → Log to File…, select a file, set Maximum file size (e.g., 10–50 MB) and enable the Wrap option.

     

   • Clear the current display: Edit → Clear Display, so the new limits apply to subsequent entries.
5. Close DebugView.
6. Restart the Document Reader app. DebugView should start automatically. Then verify that automatic document detection is functioning correctly.

Verification

1. Confirm that DebugView has line limits enabled and file logging with wrap-around (the Wrap option is checked).
2. Leave the system idle for a significant period, then place a document on the scanner glass.
3. Verify that scanning starts automatically and the log does not grow without bounds.

Prevention

• Keep History Depth and Wrap-around enabled in Log to File.
• For long sessions, use DebugView filters and periodically clear the display.
• Maintain an up-to-date SDK version.

Useful links

• How to save log using DebugView application.