Tune HID Signo Enhanced Tap for the intended opening

Bottom line: DSE recommends evaluating HID Signo Enhanced Tap as the documented opening mode, with its own configuration and test record. Define the intended presentation behavior and representative mobile devices before accepting a range setting for an opening.

Source fact: the connection initiator differs

Section 8.10 of the HID Mobile Access FAQ, PLT-02085 revision C.8, describes Enhanced Tap for HID Signo readers. It contrasts standard Tap, where the mobile device attempts to connect to the reader, with Enhanced Tap, where the reader attempts to connect to the mobile device.

The reading-range note in section 8.8 says device models can behave differently. It calls for testing the reader/mobile-device connection at installation with the devices most commonly used within the organization. The captured revision is dated April 2026; these statements are not a compatibility list for every reader or phone.

What the source does not establish

These sections do not establish a universal dBm setting, guaranteed operating range or opening latency. They also do not make BLE behavior interchangeable with NFC behavior or establish support for an unspecified reader and firmware combination. Confirm those applicability details through the current product documentation before applying the guidance.

Applicability questions

• Is the installed reader a HID Signo model covered by the applicable Enhanced Tap documentation?
• Which opening mode is intended, and what is actually configured?
• Which mobile-device models and application versions represent the users of this opening?
• What presentation position and user behavior should the installation accept?
• Are adjacent openings or readers part of the approved acceptance scenario?

DSE recommendation: test a defined configuration

The following steps are DSE recommendations based on the documented mode and device differences.

Record the reader identity, firmware, chosen mode and relevant configuration reference before adjusting the installation. Define the intended user experience in observable terms: which opening should respond, where the user presents the device and what response the operator should record. Avoid accepting an unspecified “works with phones” requirement.

Choose a representative set of approved mobile devices with the access owner. Record their operating-system and application versions without collecting unnecessary personal information. Have the installer use the applicable manufacturer procedure for the selected reader and mode rather than copying a setting from another door without a documented comparison.

Change one approved setting at a time and preserve the earlier configuration. If a trial produces an unwanted result, record the conditions before moving on. Include an adjacent reader or alternative presentation position only where the test plan authorizes that check. Keep exceptions tied to the affected device and opening rather than silently widening the accepted behavior.

Verification and evidence

Run the agreed test cases with the representative devices. Record the configured mode, device identity, presentation conditions, intended opening and observed response. Use repeated observations agreed with the owner rather than treating one successful presentation as the whole acceptance exercise.

Compare results across the selected device population and investigate inconsistent outcomes before broad rollout. Preserve the configuration that was actually tested and identify any device class excluded from acceptance.

Retain the applicable FAQ revision, product-specific compatibility evidence, approved configuration, test cases and observations. Reopen the assessment after a material reader, firmware, application or user-device change instead of assuming the earlier record covers the new combination.

Official references

• HID Mobile Access Frequently Asked Questions — HID Global; PLT-02085 revision C.8, April 2026; sections 8.8 and 8.10, pages 92–93.

Source review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change.