Connection Issue: DRS Radar Series Scanner - "The semaphore timeout period has expired" error

[DR Hunter]

Hi everyone,

I am seeking your expertise regarding a technical issue with my DRS Radar Series scanner on Windows 10.

The Bluetooth connection is established correctly (the software detects the scanner on COM6 and the connection light turns green), but the process stops there.

My specific issue:As soon as I click "Start" to begin the scan, nothing happens. The software does not respond, no data is recorded, and the counters (samples, depth) remain stuck at zero. After a few seconds, the software consistently displays this error message: "The semaphore timeout period has expired."

Here is what I have already tested without success:

• Added the software to the Windows Defender exclusion list.
• Verified the COM port settings (I am correctly using COM6, as identified in the Device Manager).
• Performed a complete Bluetooth re-pairing process.
• Disabled all remote desktop tools (like AnyDesk) to prevent port conflicts.

Has anyone encountered this total blockage at the start of a scan, or does anyone have a tip to stabilize the data stream?

I have attached a screenshot of the error message for reference. Thank you in advance for your help and advice!

 

[guest]

Hi everyone,

I am seeking your expertise regarding a technical issue with my DRS Radar Series scanner on Windows 10.

The Bluetooth connection is established correctly (the software detects the scanner on COM6 and the connection light turns green), but the process stops there.

My specific issue:As soon as I click "Start" to begin the scan, nothing happens. The software does not respond, no data is recorded, and the counters (samples, depth) remain stuck at zero. After a few seconds, the software consistently displays this error message: "The semaphore timeout period has expired."

Here is what I have already tested without success:

• Added the software to the Windows Defender exclusion list.
• Verified the COM port settings (I am correctly using COM6, as identified in the Device Manager).
• Performed a complete Bluetooth re-pairing process.
• Disabled all remote desktop tools (like AnyDesk) to prevent port conflicts.

Has anyone encountered this total blockage at the start of a scan, or does anyone have a tip to stabilize the data stream?

I have attached a screenshot of the error message for reference. Thank you in advance for your help and advice!

Hi @DR Hunter .
I do not know what you're talking about. But...
Most things you have checked yourself. So the COMport is correct, decice is powered up and seems to work, etc.
Depending on the eror-message it seems to be a timeout. May be a .dll is corrupt, may be through an update by another software using the same.
What I would do is, uninstall the software and reinstall it. And maybe there is a update available online.
Hope that will help.🤞