Transducer Not Detected or Misidentified – Device Isolation and Port Diagnostics

Product(s): Measure · Primus · Unity
Applies to version: All current versions
Audience: External – Customers
Difficulty: Advanced
Estimated resolution time: 20–40 minutes
Last updated: 2026-06-27
Article type: Troubleshooting guide

Quick summary

A transducer connected to the Measure board is not detected by the software, or is being identified as the wrong device. This guide walks you through device isolation, port testing, firmware checks, and a hardware reset to restore correct detection.

⚙️ Before you begin

Make sure you have a spare transducer and, if possible, a spare Measure board available for cross-testing.
Have a straightened paperclip or SIM ejector pin available in case a hardware reset is needed (Step 9).
Note exactly which transducer is affected and which port it is connected to.

Step 1: Verify device detection

Do the physically connected devices match the ones shown in the software?

✅ Yes → Proceed to Step 2.
❌ No → Take these steps:

Disconnect all transducers and accessories.
Reconnect them one at a time, checking the software after each reconnection.

→ Check if the issue is resolved. If yes - a specific device is causing detection confusion; identify it and contact Auditdata Support. If no - continue to Step 2.

Step 2: Isolate the transducer

Are multiple transducers or accessories connected to the board?

✅ Yes → Disconnect all other transducers and accessories, leaving only the one you are testing. Retry detection.
❌ No → Proceed to Step 3.

→ Check if the issue is resolved. If yes - another connected device was interfering; reconnect them one at a time to identify it. If no - continue to Step 3.

Step 3: Switch to a different AC port

Have you tried the transducer on a different AC port on the board (e.g., AC1 → AC2)?

✅ Yes → Proceed to Step 4.
❌ No → Disconnect the transducer and plug it into an alternate AC port on the board.

→ Check if the issue is resolved. If yes - the original AC port may be faulty; contact Auditdata Support. If no - continue to Step 4.

Step 4: Connect the transducer directly (remove extension cables)

Is the transducer connected via an extension or sound booth cable?

✅ Yes → Disconnect the extension or booth cable and connect the transducer directly to the AC port on the board.
❌ No → Proceed to Step 5.

→ Check if the issue is resolved. If yes - the extension or booth cable is faulty; replace it. If no - continue to Step 5.

Step 5: Check Windows sound settings

Is Measure muted or disabled in Windows Sound settings?

✅ Yes → Take these steps:

Go to Control Panel → Sound.
Right-click Measure → Enable.
Right-click again → Set as Default Device.

→ Check if the issue is resolved. If yes - you're done ✓. If no - continue to Step 6. * ❌ No → Proceed to Step 6.

Step 6: Cross-test with a different transducer and board

Have you tested using a different transducer and/or a different Measure board?

✅ Yes → Proceed to Step 7.
❌ No → Take these steps:

Swap in a different transducer of the same type and test detection.
If still not detected, swap in a different Measure board and test.

→ Check if the issue is resolved. If yes - the original transducer or board is faulty; contact Auditdata Support for a replacement. If no - continue to Step 7.

Step 7: Run hardware diagnostics

Have you run hardware diagnostics for all board ports in the software?

✅ Yes → Proceed to Step 8.
❌ No → Open the hardware diagnostics in the software and run a full test on all AC ports. Note any errors reported.

→ Check if the issue is resolved. If yes - you're done ✓. If no - continue to Step 8.

Step 8: Rewrite the board firmware

Have you attempted to rewrite the firmware on the board?

✅ Yes → Proceed to Step 9.
❌ No → Use the standard firmware rewrite process in the software. Contact Auditdata Support if you are unsure how to do this.

→ Check if the issue is resolved. If yes - you're done ✓. If no - continue to Step 9.

Step 9: Perform a hardware reset

Disconnect all cables from the board: USB, power supply, and transducers.
Locate the reset pinhole on the back of the board.
Insert a straightened paperclip into the pinhole and hold the reset button down.
While holding the button, connect only the USB cable.
Hold for 3 seconds until the LED blinks once per second.
Release the button - the LED should stay on briefly, then turn off.
Open Device Manager (right-click Start → Device Manager) and confirm the board appears.

→ Check if the issue is resolved. If yes - you're done ✓. If no - proceed to the escalation path below.

🔺 Escalation path

If none of the above steps resolved the issue, contact Auditdata Support.

Please have ready:

Product name and version number
Device model and serial number
Firmware version
Which transducer model is affected and which AC port it is connected to
Your account name and contact details
Which steps above you already tried
Error messages or codes shown in diagnostics
Screenshots if available

✅ Expected outcome

After completing these steps, the transducer should appear correctly in the software - listed under the right device type on the expected port. Hardware diagnostics should show no errors on the affected AC port.

📝 Additional notes

If the transducer is detected correctly after a hardware reset but stops being detected again after a few sessions, this can indicate a loose AC port - contact Auditdata Support to arrange a board inspection.
Always run hardware diagnostics (Step 7) before attempting a firmware rewrite or reset, as the diagnostic report helps Auditdata Support understand the failure pattern.
Related articles: PRIMUS - Failed Hardware Diagnostics · Fitting Unit Board Not Detected · No Sound or Transducer Output

Need more help? Visit the Auditdata Help Centre or contact our support team.