Identifying a Unit

All Ethos readers can be identified by their label. The product label can be found on the exterior of all units, located in the bottom right corner of the backplate.

The following key pieces of info are located on the label:

Example Label:

Reader Behavior

The following section describes normal operating behavior for each Ethos reader type with associated meanings. Any special features are also documented.

Standard AV Behavior

The following is the standard AV behavior for an Ethos reader. If a reader's AV behavior is behaving differently, it is likely behavior dictated by the controller or it may be a custom reader configuration (see section Identifying a Custom Configuration).

Firmware Update Reader AV Behavior

BLE MCU (3.X.X.X firmware): 

• Solid Amber LED for ~45 seconds.
  
• Single beep denoting success. 

Reader MCU (3.X.X.X firmware): 

• Alternating RED/GREEN LED.
  
• 3-5 BEEPS followed by a reset. 
• Normal startup sequence. 

Reader MCU (4.X.X.X firmware): 

• Solid Blue LED for ~45 seconds.
  
• 3-5 BEEPS followed by a reset. 
• Normal startup sequence. 

Wiegand-OSDP Behavior

Wiegand-OSDP readers are considered a "slave" device when connected to a panel. Most LED and beeper 
functionality is dictated and controlled by the access control panel. Any autonomous behavior performed by the reader is documented in the Operating Behavior section.

Features

Panel Controlled Behavior

Wiegand Access Control Panel

OSDP Access Control Panel

MyPass Mobile App Behavior

	MyPass Bit Format MyPass credentials are programmed to look like MiFare Classic CSN’s. They are 32 bit long credentials. The bitstream contains 32 bits of badge ID, no parity bits and no facility code bits.

MyPass performs differently depending on the operating system of the phone you are using. These differences are shown in the table below.

NFC Wallet Behavior

Common Solvable Issues

1. Issue: Reader won’t read my card, or reader isn’t giving the right output 
   1. Solution A: OSDP/AutoDetect Mode check 
      1. Double check that the reader is in the correct mode (AutoDetect or OSDP). To do this, power cycle their Ethos reader & count how many green beeps (2 = OSDP, 4 = AutoDetect).  
      2. If reader is in OSDP mode & needs to switch back to AutoDetect, refer to Section “Wiegand-OSDP Behavior” of this guide 
   2. Solution B: Credential Compatibility Issue 
      1. Trying to read cards that are not compatible with the reader, generally this is a proprietary credential or some other non-LEAF smartcard  
      2. Refer to the credential compatibility matrix for more details 
   3. Solution C: Reader has the wrong part number 
      1. The reader isn’t set up to be able to read the RF technology they are trying to use. Determine what type of card they are using, check the PN & CPN (on the backplate label or on the box) of the reader, then verify if the reader can read that RF technology  
      2. See Ethos Reader Datasheet for details 
   4. Solution D: Wiring check & setup simplification 
      1. Double check the wiring, there is a chance you need to swap the green & white wires (RS485+ & RS485- respectively), especially if using a Lenel Panel 
      2. Wire the reader directly to the panel to avoid/circumvent any wiring issues that may be experiencing along their run 
   5. Solution E: Try a different Wavelynx reader to see if this issue is specific to a particular reader 
      1. If you have multiple readers on hand, try wiring up a different reader to the same door to see if the issue persists 
      2. If it does, then the issue has to do with the way that particular door is set up 
      3. If it does not, try wiring that problem reader to a door that is otherwise operating fine. If the issue is with the reader itself, then this is likely grounds for an RMA.  
         1. Email rma@wavelynxtech.com to get an RMA 
   6. Solution F: None of the above solutions worked 
      1. If none of the above work, then you likely have a panel setting issue, & should call the tech support line of the panel manufacturer 
2. Issue: You want to update reader FW or configuration 
   1. Solution: 
      1. Download Configure from the app store  
      2. Request a Token from Wavelynx so you can gain access to the correct file 
3. Issue: You are not able to get multiple readers online via OSDP Multi-drop
   1. Solution: 
      1. Make sure you have  access to the proper OSDP Addressing cards (FEA-OSDPA-P1) or 6WS/7WS readers and Configure 
      2. Remove power from all readers 
      3. Bring one reader online & use the OSDP Addressing card (Addresses are 1-8) or use Configure to address to the address of their choice and let the reader go through its start-up sequence 
      4. Once the reader has finished the start-up sequence, remove that reader from the panel & bring on the next one 
      5. Address this reader to a different OSDP Address than the 1st reader 
      6. Repeat the above steps until all readers are on unique addresses, and then bring them all 
         online together 
4. Issue: Trying to use MyPass, but having trouble entering the correct bit format into the access control system 
   1. Solution: 
      1. Go to the Bitstreams Definition PDF located on our website and look at the W32-5 bit format, enter this into the system (See Below)
         
5. Issue: Struggling to get Wallet to work 
   1. Solution: 
      1. Go to the Bitstreams Definition PDF located on our website and look at the W40-2 bit format, enter this into the system (See Below)
         

Escalation

If an issue cannot be resolved in the field or with Tier 2 support staff (device reseller), the following info can be provided for an escalation to Tier 3/WaveLynx support staff: 

• Detailed description of the issue. 
• Steps taken to resolve the issue (follow common procedures from previous sections). 
• What PACS software and Panel are being used? 
• Reader details, including: 
  • Label details: 
    • Serial Number 
    • Part Number 
    • CPN 
    • Firmware version 
  • Panel Connection (OSDP/Wiegand).
  • Credential connection (physical, BLE, NFC, etc.) 
• Mobile App/Phone Details (if mobile credential issue): 
  • Model 
  • OS Version 
  • Mobile application being used 
  • Mobile application version 
• Physical Credential Details (if physical credential issue): 
  • Card type (125 kHz, DESFire, etc.) 
  • Credential part number 
  • Bitstream format (if known) 
  • Credential badge ID and facility code number (if known) 

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

Advanced Troubleshooting

The following sections detail a "sanity check" procedure for identifying the source of a potential issue with a unit. These steps will attempt to decouple the reader functionality from panel and PACs software configuration.

Generic Troubleshooting

Power Up

1. Remove power from the reader 
2. (Optional) Remove all other wires connected to the panel. This step may be performed to eliminate the panel interference completely when troubleshooting a unit. 
3. Re-power the reader and observe its behavior upon startup. 
4. Does the reader perform its normal startup sequence and then return to the normal idle state? 

Reader Details

1. Download the Configure by Wavelynx app on the app store.
2. Register on Configure.
3. Use the app to check Reader Details. 
4. Do the reader details match what you are expecting? 

Credential Read

1. (Optional) Remove all wires except power(RED) and ground(BLACK) connected to the panel. This step may be performed to eliminate panel interference completely when troubleshooting a unit. 
2. Present a supported credential to the reader. 
3. Does the reader perform its normal credential read behavior?

Control Lines (Wiegand Only)

1. Remove all control lines from their connections to the panel. 
2. Ground each control line (i.e. assert it to 0V) one by one and observe the behavior at the reader. 
3. Does the green LED illuminate when the blue control line is grounded? 
4. Does the red LED illuminate when the orange control line is grounded? 
5. Does the amber LED illuminate when both the blue and orange control lines are grounded? 
6. Does the beeper sound when the yellow control line is grounded? 

OSDP Connection

1. Remove power from the reader 
2. Connect the green wire to RS485A and the white wire to RS485B 
3. Re-power the reader. 
4. Verify that the panel is successfully communicating with the reader prior to reading a credential or pressing a key. 
5. If the reader is still not communicating with the panel, try swapping the white and green wires. (Note: RS485A and RS485B are swapped on some panels. This is specifically common on Lenel panels) 

BLE Troubleshooting

BLE can be difficult to troubleshoot as the issue most often lies with the user’s device/mobile operating system. These steps provide a basic set of procedures which will alleviate or determine the cause of an issue in most cases. There may be instances when a user’s device simply will not function correctly with BLE. In these cases, nothing can be done as it is outside the control of the PACs system and mobile applications. 

Common Procedure

1. Ensure that Bluetooth and location services are enabled on the device. 
2. Ensure that the mobile application has permission to use Bluetooth and location services. 
3. Open the associated mobile app. 
4. Hold the phone directly against the reader. 
5. Does the reader LED turn AMBER indicating a BLE connection? 
6. Wait ~3 seconds for the transaction to complete. 
7. After the transaction completes, does the reader blink GREEN and BEEP once? 
8. Does the app indicate credential read success? 
9. If 1 through 8 were completed successfully, then the mobile application and reader are functioning correctly.

Common BLE Issues and Solutions

• Issue: The reader LED is turning amber briefly and then goes back to idle. The reader never beeps or flashes green and the credential is never sent. 
• Solution: The app and the reader have a key mismatch. Verify the correct mobile app is being used for the reader configuration. 
• Issue: The reader LED is not turning amber. 
• Solution: The reader is not BLE capable or has BLE turned off. Check the part number and confirm it is 6WS or 7WS.  

NFC Troubleshooting

Common Procedure

1. Ensure the correct mobile credential application is installed and the credential is active on the device. 
2. Ensure that NFC is enabled on the device and the app has appropriate permissions. 
3. Ensure the mobile application has permission to use NFC and location. 
4. Unlock the device or ensure the screen is on. 
5. Hold the device directly against the reader. 
6. Does the reader blink GREEN and BEEP once? 
7. If 1 through 6 were completed successfully, then the mobile application and reader are functioning correctly. 

Common NFC Issues and Solutions

• Issue: The mobile application says there is an NFC error. 
• Solution: This may occur if there is another application on the phone which has registered support for the WaveLynx reader. Uninstall the other application and attempt to restart the current one.

Configuring and Updating Readers

Field Configuration can be performed on any Ethos reader through the use of a configuration card or by means of OSDP File Transfer. Field firmware upgrades can be performed using OSDP File Transfer. 

Obtaining Configuration and Firmware Files

Configuration and firmware image files are distributed in the form of encrypted and signed binary (.bin) files. These may be obtained from WaveLynx upon request. 

Configuration Card Application

1. Reset reader power, wait for the reader to complete its startup sequence and return to an idle state. 
2. Within 1 minute, present the desired configuration card to the reader. 
3. The reader should beep 3 times, followed by a reset. 
4. When the reader has fully restarted, the new configuration will be applied.

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. 

1. Use the associated PACs software to push a configuration file to the panel and associated reader. 
2. Once the file has been pushed successfully to the reader via OSDP file transfer, it will beep 3 times, followed by a reset. 
3. When the reader has fully restarted, the new file will be applied. Please see the AV section for expected update behaviors.  

Configure App

How to Install a Profile

1. Navigate to "Apply Profiles & Cards":
   • Open Configure on your device. 
   • Select Apply Profiles & Cards from the main menu. 
2. Power Cycle the Reader 
3. Connect to a Reader: 
   • Place your device near any Wavelynx reader. 
   • Tap to Connect to establish a Bluetooth connection. 
4. Select the "+" on the Upper Right of the Screen 
5. Enter a Code Provided by the Customer: 
   • After tapping the “+” icon on iphone or “Download” on Android, you will be prompted to enter a code 
   • Enter a code (also known as token) associated to the profile/firmware update needed 
   • The codes are unique to the customer/vendor, they will provide them as needed 
   • Once code is entered correctly, the profile will now appear under your cards or profiles list under “Apply Profiles & Cards” 

How to Apply a new Firmware or Profile

1. Navigate to "Apply Profiles & Cards":
   • Select Apply Profiles & Cards from the main menu. 
2. Power Cycle the Reader 
   • Disconnect power from the reader and power it back up 
   • Reader will not be able to connect until it finishes flashing its startup sequence 
3. Connect to a Reader (within 60 seconds of powercycle): 
   • Place your device near any Wavelynx reader. 
   • Tap to Connect to establish a Bluetooth connection. 
4. Select and Update: 
   • Choose a profile/card from the list. (Request tokens from vendor/customer) 
   • Tap to Update to begin the transfer. 
   • Keep your device near the reader (within 6 inches) until the process completes.

How to Use the Toolkit 

1. Navigate to "Toolkit": 
   • Select Toolkit from the main menu. 
2. Power Cycle the Reader
   • Disconnect power from the reader and power it back up 
   • Reader will not be able to connect until it finishes flashing its startup sequence 
3. Connect to a Reader (within 60 seconds of powercycle): 
   1. Tap Tap to Connect and ensure proximity to the reader. 
4. Modify Settings: 
   1. Choose a setting (e.g., Proximity, Baud Rate, OSDP Address). 
   2. Tap Apply to update the reader. 

Troubleshooting FAQs 

1. Where do I get a code/token? 
   • The vendor provides it. Contact them or Wavelynx support if needed. 
2. What if my code doesn’t work? 
   • Double-check the code for accuracy. 
   • Ensure a stable Bluetooth connection. 
   • Verify internet connectivity. 
3. Why isn’t the reader updating? 
   • Ensure Bluetooth is enabled. 
   • Confirm the reader has power and was reset within 60 seconds. 
4. Can’t see reader details? 
   • Reconnect and retry. 
   • Contact support if the issue persists. 
   • NOTE: Only firmware 4.2.2.0 and 3.2.1.0 supports the full reader details functionality.

Custom Configurations

Ethos readers are offered with custom configurations for end users that require a product which differs in functionality and/or security from the default offering. Custom configurations can include modifications to any of the following: 

• LEAF smart card keysets. 
• Mobile credential keysets. 
• A/V behavior (LEDs, Beeper, etc.). 
• Disabling tamper 
• Customized “Prox Filter”. 
• Modified BLE behavior

Identifying a Custom Configuration

Custom configurations can be identified by the CPN field included in the product label. Records on the specifics of the configuration are kept by WaveLynx and should be referenced when dealing with a custom configured product. 

One of the following identifiers will be present to indicate a custom configured product (note that “#” indicates a unique number or character sequence denoting the configuration):

Examples (custom config ID bolded):

• ET20-7WS-U002-LAM2 
• ET25-7WS-CWL1 

Common Custom Configuration Features

Ethos readers offer a few common custom configuration features to enable higher security for an end user and allow them to transition their card holders from legacy technologies and systems. The details of these features are outlined below. 

Custom LEAF DESfire Keyset

Ethos readers can be loaded from the factory with a custom DESFire smart card keyset to support the open LEAF application. A custom keyset provides an end user a higher security solution, as only cards programmed/encoded for their readers will function at their facility. 

When supporting a custom keyed solution, the following should be noted: 

• The end user’s LEAF DESFire cards will result in a valid read (indicated by a 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 and have no effect on the panel or PAC system connected to the reader. 
• Any bitstream format can be encoded into a custom keyed LEAF DESFire smart card application, so there is no fixed format tied to a custom keyed solution. 

Custom Mobile Credential Keyset

Just like DESFire keysets, Ethos readers can be loaded from the factory with a custom mobile credential keyset. A custom mobile credential keyset allows third party app/credential providers to issue customized credentials that integrate with their solutions.

When supporting a custom mobile keyed solution, the following should be noted: 

• Only the specific mobile provider’s applications will work with the readers (indicated by a beep/green flash) on the reader. 
• 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 PAC system connected to the reader. 
• Any bitstream format can be encoded into a custom keyed mobile credential, so there is no fixed format tied to a custom keyed solution. 

Custom Prox Filter

Ethos readers can also be configured with a custom “Prox Filter”. A Prox Filter will block reads from Proximity cards which contain a certain bitstream format or facility code (customer code). This allows an end user to transition from a legacy proximity card solution to a more secure smart card solution without rebadging their entire card population or replacing all of their readers at the same time. 

The main advantage of a Prox Filter is to alleviate the issue of “double reads' from a dual-technology card when presented to a multi-technology reader. This also ensures that the secure smart card credential of the dual-technology card is authenticated and read when presented to a reader. 

When supporting a product implementing a Prox Filter, the following should be noted: 

• Prox Filters are configured differently for each end user based on their desired bitstream format and existing card population. Consult the custom configuration documentation for that end user for details on how their Prox Filter is configured. 
• In most cases Prox Filters are set to ignore Prox cards containing a specific bitstream and facility code 
  (customer code). This means that Prox cards encoded with this data will NOT be read by the reader.