Technical Support Guide

for APEX™ Readers

All APEX™ readers can be identified by their product label, which is located on the exterior of the unit, on the bottom right corner of the backplate. APEX is fully interoperable with Ethos and integrates into any access control system that uses Wiegand or OSDP.

APEX and Ethos are trademarks of Wavelynx Technologies, LLC.

1.1 Label Information

The following key pieces of information are located on the APEX label:

1.2 Form Factors and Variants

APEX is offered in four form factors and two functional variants. All variants are interoperable with Ethos credentials and ship with the same metal-cast mounting plate.

Tip: If you are unsure whether a reader is Summit or Ascent, check the Part No. and CPN on the label, or query reader details using the Configure by Wavelynx app.

This section describes the normal operating behavior of an APEX reader, including the LED and buzzer (A/V) sequences and the meaning of each indication.

2.1 Standard A/V Behavior

APEX uses a Red/Green/Blue LED light bar at the top of the reader for visual feedback. If a reader's A/V behavior differs from the table below, the behavior is most likely being driven by the access control panel (in OSDP or Wiegand mode) or the reader is running a custom configuration — see the Custom Configurations section for guidance.

2.2 LED Color Reference

APEX uses an 8-color RGB palette. LED brightness is configurable globally (0–100%) and per-channel (0–10 scale).

2.3 Firmware Update Reader A/V Behavior

APEX uses the 5.X.X.X firmware family. Firmware images are delivered as encrypted, signed binaries (.bin) over OSDP File Transfer, BLE, or NFC config card. During an update the reader follows this sequence:

Solid BLUE LED for ~45 seconds while the new image is being staged in the alternate MCUboot slot.

Flashing LED for ~30 seconds while the firmware is verified and applied.

Normal startup sequence (technology indication followed by communication mode indication) when the new firmware boots.

Important: Firmware images are never transferred alone. Each customer firmware release is delivered as a DCK bundle (firmware + full configuration) so the reader is always left in a fully configured state.

2.4 Wiegand and OSDP Behavior

APEX is a peripheral device (PD) on the access control bus. Most LED and beeper functionality after startup is dictated by the panel. APEX adds an autodetect capability that allows a single installation to upgrade from Wiegand to OSDP without rewiring.

2.4.1 OSDP Auto-Detect

By default, APEX boots in OSDP Auto-Detect. If the panel ever sends a secure OSDP message, the reader establishes a secure channel and remains in OSDP mode until reset. To return a reader from OSDP-only back to Auto-Detect on APEX (5.X.X.X firmware), use a configuration card or apply a Wavelynx-provided token through the Configure by Wavelynx app.

2.4.2 OSDP Defaults

2.4.3 Panel-Controlled Behavior

Wiegand panel:

RED, GREEN, AMBER LEDs: asserted through control lines.

BEEPER: asserted through the buzzer control line.

OSDP panel:

RED, GREEN, AMBER LEDs: controlled through OSDP LED_CNTRL (0x69) messages.

BEEPER: controlled through OSDP BUZ_CNTRL (0x6A) messages.

2.5 MyPass Mobile App Behavior

MyPass credentials on APEX are programmed to look like MIFARE Classic CSNs. They are 32-bit credentials — the bitstream contains 32 bits of badge ID with no parity bits and no facility code. APEX behavior with the MyPass app differs slightly between iOS and Android; refer to the MyPass documentation for OS-specific tap-and-hold behavior.

2.6 NFC Wallet Behavior

APEX supports both Apple Wallet and Google Wallet over NFC. The reader's behavior with both wallets is identical from the user's perspective:

Uses NFC technology — the device screen must be on.

Sends the credential instantly — no app required upon presentation.

On a successful read, the reader emits 1 BEEP and a GREEN flash.

3.1 Reader will not read my card or is not giving the right output

OSDP / Auto-Detect mode check. Power-cycle the reader and listen to the startup beeps: 2 beeps = OSDP only; 4 beeps = Auto-Detect. If the reader is in OSDP-only mode and you need to switch back, follow Section 2.4.1.

Credential compatibility. Confirm the card is on the APEX-supported list — proprietary credentials and non-LEAF smart cards may not authenticate. For LF Prox cards, confirm the reader is a Summit (AX-XX-S) variant; Ascent variants do not include 125 kHz Prox.

Wrong part number. Verify the Part No. and CPN on the label match the technology you are presenting (HF/LF/BLE).

Wiring check. Double-check the OSDP wiring; you may need to swap green/white (RS-485+ / RS-485-), particularly with Lenel panels. APEX includes a terminal block for standardized wiring; the traditional pigtail is available as an optional accessory.

Try a different Wavelynx reader. Wire a known-good APEX reader to the same door. If the issue follows the door, it is likely a panel/wiring issue. If it stays with the reader, contact rma@wavelynx.com to begin an RMA.

None of the above. Contact your panel manufacturer's tech support — the problem is most likely a panel configuration issue.

3.2 You want to update reader firmware or configuration

Download Configure by Wavelynx from the App Store or Google Play.

Request a token from Wavelynx for the firmware or profile you need.

Power-cycle the reader and apply the profile within 60 seconds (see Section 6).

3.3 Cannot bring multiple readers online via OSDP multi-drop

Make sure you have OSDP addressing tokens or cards from Wavelynx and the Configure by Wavelynx app.

Remove power from all readers.

Bring one reader online and address it (1–8) using the addressing card or Configure app. Allow the reader to complete startup.

Remove that reader and bring on the next one. Address each reader to a different OSDP address.

Repeat until each reader has a unique address, then bring them online together.

3.4 Trouble entering the correct bit format for MyPass

Use the W32-5 bit format from the Wavelynx Bitstreams Definition document and enter it into your access control system.

3.5 Wallet credentials are not working

Use the W40-2 bit format from the Wavelynx Bitstreams Definition document and enter it into your access control system.

If an issue cannot be resolved in the field or with Tier 2 (reseller) support, gather the following information before contacting Tier 3 / Wavelynx support:

Detailed description of the issue.

Steps already taken to resolve the issue (using the procedures in Sections 3 and 5).

PACS software and panel make/model.

Reader details from the label: Serial Number, Part Number, CPN, Firmware version.

Panel connection: OSDP or Wiegand.

Credential connection: physical, BLE, or NFC.

If a mobile credential issue: phone model, OS version, mobile application name and version.

If a physical credential issue: card type (125 kHz, DESFire, etc.), credential part number, bitstream format, badge ID, and facility code (if known).

Contact: support@wavelynx.com or (720) 248-7069 with all the above information.

The following sections describe a sanity-check procedure for isolating a potential issue with an APEX unit. These steps decouple reader functionality from the panel and PACS software.

5.1 Generic Troubleshooting

5.1.1 Power Up

Remove power from the reader.

(Optional) Remove all other wires connected to the panel to eliminate panel interference.

Re-power the reader and observe its behavior on startup.

Question: Does the reader perform its normal startup sequence and return to the idle state?

5.1.2 Reader Details

Download the Configure by Wavelynx app from the App Store or Google Play.

Register in Configure.

Use the app's Toolkit to query Reader Details.

Question: Do the reader details match what you are expecting (Part No., CPN, Firmware, OSDP address, etc.)?

5.1.3 Credential Read

(Optional) Remove all wires except power (RED) and ground (BLACK) connected to the panel.

Present a supported credential to the reader.

Question: Does the reader perform its normal credential-read behavior (1 beep + GREEN flash)?

5.1.4 Control Lines (Wiegand only)

Remove all control lines from their panel connections.

Ground each control line one by one (assert it to 0 V) and observe the reader.

Question: Does the GREEN LED illuminate when the blue control line is grounded?

Question: Does the RED LED illuminate when the orange control line is grounded?

Question: Does the AMBER LED illuminate when both blue and orange control lines are grounded?

Question: Does the buzzer sound when the yellow control line is grounded?

5.1.5 OSDP Connection

OSDP is easy to use with APEX readers and does not require new wiring. The same wires that carry Wiegand can carry OSDP — APEX Auto-Detect lets the reader switch over once a secure OSDP message is received.

Remove power from the reader.

Connect the green wire to RS-485 A and the white wire to RS-485 B.

Re-power the reader.

Verify the panel is communicating with the reader before reading a credential or pressing a key.

If the reader is not communicating, swap the white and green wires. RS-485 A and RS-485 B are reversed on some panels (commonly Lenel).

5.2 BLE Troubleshooting

BLE issues most often originate with the user's mobile device. The steps below address or determine the cause in most cases. Some devices simply will not function correctly with BLE — this is outside the control of the PACS or the mobile application.

5.2.1 Common Procedure

Ensure that Bluetooth and Location Services are enabled on the device.

Ensure the mobile app has permission to use Bluetooth and Location.

Open the associated mobile app.

Hold the phone directly against the reader.

Question: Does the reader LED turn AMBER, indicating a BLE connection?

Wait approximately 3 seconds for the transaction to complete.

Question: After the transaction completes, does the reader blink GREEN and beep once?

Question: Does the app indicate credential-read success?

5.2.2 Common BLE Issues and Solutions

Issue: The reader LED turns amber briefly, returns to idle, and never beeps or flashes green.

Solution: The mobile app and the reader have a key mismatch. Confirm the correct mobile app is being used for the reader's keyset (Wavelynx-issued or third-party custom mobile).

Issue: The reader LED is not turning amber.

Solution: BLE may be disabled in firmware. Use Configure by Wavelynx (Toolkit → TECH) to confirm BLE is enabled, or contact Wavelynx support.

5.3 NFC Troubleshooting

5.3.1 Common Procedure

Ensure the correct mobile credential application is installed, and the credential is active on the device.

Ensure NFC is enabled on the device, and the app has the necessary permissions.

Unlock the device or ensure the screen is on.

Hold the device directly against the reader.

Question: Does the reader blink GREEN and beep once?

5.3.2 Common NFC Issues and Solutions

Issue: The mobile application reports an NFC error.

Solution: Another application on the phone may have registered support for the Wavelynx reader. Uninstall the conflicting application and restart the credential app.

APEX field configuration can be performed using a configuration card, OSDP File Transfer, or the Configure by Wavelynx mobile app over BLE. Field firmware upgrades use the same channels.

6.1 Obtaining Configuration and Firmware Files

Configuration and firmware files are distributed as encrypted and signed binary (.bin) files. They are obtained from Wavelynx upon request — contact your account manager or Wavelynx support.

APEX uses the same encrypted file format and TLV envelope as the rest of the Wavelynx product line. AES-256-CBC is used for transport encryption with a per-session random IV.

6.2 Configuration Card Application (APEX)

Reset reader power and wait for the reader to complete its startup sequence and return to idle.

Within 1 minute, present the desired configuration card to the reader.

The reader will beep and accept the configuration card.

The reader is now configured. (Note: APEX does not require the 3-beep + reset sequence used by Ethos — it accepts the card and applies the configuration in place.)

6.3 OSDP File Transfer

OSDP file transfer does not need to occur within 1 minute of a power cycle and can be performed at any time.

Use the PACS software to push a configuration or firmware file to the panel and the associated reader.

Once the file has been pushed successfully via OSDP File Transfer, the reader will validate, apply, and (if required) reboot. See Section 2.3 for the firmware-update A/V sequence.

When the reader has fully restarted, the new file will be applied.

Implementation note: While a file transfer is in progress, RFID polling is temporarily disabled to keep OSDP responses within the 200 ms deadline. RFID re-enables on successful completion, on transfer error, or after 60 seconds of inactivity in ft_process_chunk.

6.4 Configure by Wavelynx App

6.4.1 How to install a profile

Navigate to Apply Profiles & Cards. Open Configure by Wavelynx and select Apply Profiles & Cards from the main menu.

Power-cycle the reader.

Connect to a reader: place your device near any Wavelynx reader and tap to connect.

Tap the + icon on the upper right (iPhone) or Download (Android).

Enter the token (code) provided by Wavelynx or the customer. Tokens are unique to the customer/vendor.

Once entered correctly, the profile appears under Apply Profiles & Cards.

6.4.2 How to apply a new firmware or profile

Select Apply Profiles & Cards.

Power-cycle the reader. The reader cannot connect until it has finished its startup sequence.

Within 60 seconds of the power cycle, place your device near the reader and tap to connect.

Choose a profile or card from the list and tap Tap to Update. Keep your device within 6 inches of the reader until the process completes.

6.4.3 How to use the Toolkit

Select Toolkit from the main menu.

Power-cycle the reader.

Within 60 seconds of the power cycle, tap to connect.

Choose a setting (Proximity, Baud Rate, OSDP Address, TECH, Tamper Sensitivity, etc.) and tap Apply.

6.4.4 Troubleshooting FAQs

Where do I get a token? The vendor (or Wavelynx support) provides it.

What if my code does not work? Double-check the code, ensure a stable Bluetooth connection, and verify internet connectivity.

Why isn't the reader updating? Confirm Bluetooth is enabled and that the reader was power cycled within the last 60 seconds.

I can't see reader details. Reconnect and retry. Full reader-details functionality requires APEX firmware 5.X.X.X or later.

APEX readers can ship with custom configurations for end users that need functionality or security different from the default offering. Custom configurations may include modifications to:

LEAF smart-card keysets.

Mobile credential keysets (custom BLE / mobile).

A/V behavior (LEDs, buzzer, idle/read patterns).

Tamper sensitivity or per-axis tamper enable/disable (X, Y, Z).

Customized Prox Filter (LF Prox bitstream / facility-code filtering).

Modified BLE behavior (admin timeout, advertising, key slots km1/km2/kc1/kc2).

7.1 Identifying a Custom Configuration

Custom configurations are identified by the CPN field on the product label. Records of each custom configuration are kept by Wavelynx and should be referenced when supporting a custom-configured reader. To request a new custom profile, or to convert a reader from one PACS to another, contact your PACS or Wavelynx support.

One of the following identifiers will be present in the CPN to indicate a custom configuration (where '#' indicates a unique number or character sequence):

Examples (custom configuration ID in bold):

AX20-S-U002-LAM2

AX25-S-CWL1

7.2 Common Custom Configuration Features

APEX exposes the same family of common custom configuration features as Ethos. Each is described below.

7.2.1 Custom LEAF DESFire Keyset

APEX readers can be loaded from the factory with a custom DESFire smart-card keyset to support the open LEAF application. A custom keyset gives an end user a higher-security solution because only cards programmed for their readers will function at their facility.

The end user's LEAF DESFire cards will produce a valid read (beep + green flash) on the reader.

When reading other smart cards, CSN reads may be disabled on the product.

Custom keyed solutions only affect the card-reader communication; they have no effect on the panel or PACS connected to the reader.

Any bitstream format can be encoded into a custom-keyed LEAF DESFire application — there is no fixed format tied to a custom-keyed solution.

7.2.2 Custom Mobile Credential Keyset

APEX readers can also be loaded from the factory with a custom mobile credential keyset. This allows third-party app and credential providers to issue customized mobile credentials that integrate with their solutions.

Only the specific provider's mobile applications will work with the readers (beep + green flash on success).

Generic mobile credentials (such as MyPass) may not be compatible with the readers.

Custom keyed solutions only affect the phone-reader communication and have no effect on the panel or PACS connected to the reader.

Any bitstream format can be encoded into a custom-keyed mobile credential — there is no fixed format tied to a custom-keyed solution.

Implementation note: BLE session keys for APEX are stored in the SE051 secure element using key slots km1, km2, kc1, and kc2. There are no hardcoded keys; session keys are derived per connection.

7.2.3 Custom Prox Filter

APEX Summit readers can be configured with a custom Prox Filter that blocks reads from proximity cards containing a specific bitstream format or facility code (customer code). This allows an end user to transition from a legacy proximity card population to a more secure smart-card solution without rebadging or replacing all readers at once.

The main advantage of a Prox Filter is to eliminate "double reads" from a dual-technology card when presented to a multi-technology reader, ensuring the secure smart-card credential is the one authenticated and read.

Prox Filters are configured uniquely for each end user based on their desired bitstream and existing card population. Consult the custom configuration documentation for that end user.

In most cases Prox Filters are set to ignore Prox cards encoded with a specific bitstream and facility code — these cards will NOT be read by the reader.

8.1 Technical Specifications

8.2 APEX vs. Ethos at a Glance

8.3 OSDP Quick Reference

8.4 Useful Links

Wavelynx Knowledge Base: support.wavelynx.com

Configure by Wavelynx Token Sheet: Knowledge Base → Configure → Configure Token Sheet

Bitstreams Definition (W32-5, W40-2): wavelynx.com — published PDF

Credential Compatibility Matrix: wavelynx.com — published PDF

RMA / Returns: rma@wavelynx.com

Tech Support: support@wavelynx.com  | (720) 248-7069