Audible Beacon Device (ABD) Troubleshooting Guide

Overview

This guide provides troubleshooting procedures for diagnosing common issues with the Audible Beacon Device (ABD). These procedures help technicians identify wiring issues, configuration problems, and operational faults that may prevent the device from functioning correctly.

Before performing troubleshooting procedures, verify that the system has been installed according to the Installation and Wiring Guide and that the device has been properly configured.

Initial System Checks

Before investigating specific symptoms, perform the following basic checks.

1. Verify the Audible Beacon Device is securely mounted and undamaged.
2. Confirm power is present at the device terminals.
3. Inspect wiring connections between the Audible Beacon Device and the Signal Power Interface.
4. Confirm the pedestrian signal head is operating normally.
5. Verify the Signal Power Interface is properly installed inside the signal head.

These checks will resolve many installation-related issues before deeper troubleshooting is required.

Device Does Not Power On

If the Audible Beacon Device does not power on:

Possible causes:

• No power supplied from the Signal Power Interface
• Incorrect wiring connections
• Loose terminal connections
• Damaged wiring

Corrective actions:

1. Verify voltage at the 12VDC terminal on the device.
2. Confirm the ground terminal connection is secure.
3. Inspect the wiring between the Signal Power Interface and the ABD.
4. Check the terminal block connections for loose or disconnected wires.
5. Inspect the field wiring for damage.

If proper voltage is present and the device still does not power on, the device may require service.

Audible Signal Does Not Activate During Walk Phase

If the Audible Beacon Device powers on but does not activate during the pedestrian walk phase:

Possible causes:

• Walk signal not connected
• Incorrect terminal wiring
• Signal Power Interface output issue

Corrective actions:

1. Verify the Walk (W) terminal is connected to the correct Signal Power Interface output.
2. Confirm the pedestrian signal head displays a Walk indication when the push button is activated.
3. Inspect wiring between the SPI and the ABD for proper terminal mapping.
4. Confirm the SPI is connected to the correct signal inputs inside the pedestrian signal head.

If wiring is correct and the issue persists, inspect the SPI wiring and outputs.

Locator Tone Not Audible

If the device operates but the locator tone cannot be heard:

Possible causes:

• Locator audio file removed or replaced
• Locator tone volume set too low
• Night mode active with reduced volume

Corrective actions:

1. Verify locator audio files are present in the configuration.
2. Check locator tone volume settings in the configuration menu.
3. Confirm night mode scheduling is not reducing audio levels.
4. Test audio playback through the configuration interface.

Adjust volume settings as required to ensure the locator tone is clearly audible.

Audio Messages Do Not Play

If audio messages such as Walk or Clearance do not play:

Possible causes:

• Audio files missing
• Corrupted audio file
• Audio configuration not saved to the device

Corrective actions:

1. Verify audio files are installed for each audio category.
2. Replace the audio file if corruption is suspected.
3. Confirm that configuration changes have been saved to the device.
4. Test audio playback using the programming interface.

If the problem persists, reload the audio files and save the configuration.

Unable to Connect Using PedConnex

If the programming application cannot connect to the device:

Possible causes:

• Bluetooth disabled on mobile device
• Device outside communication range
• Device not powered
• Application connection error

Corrective actions:

1. Verify Bluetooth is enabled on the mobile device.
2. Move closer to the device.
3. Confirm the Audible Beacon Device is powered.
4. Restart the PedConnex application.
5. Restart the mobile device if connection problems persist.

If multiple connection attempts fail, verify the device appears in the available station list.

Configuration Changes Not Applied

If configuration changes appear to save but do not affect device behavior:

Possible causes:

• Changes not saved to the station
• Device not properly disconnected from the application
• Communication interruption during configuration

Corrective actions:

1. Verify the configuration has been saved to the station.
2. Confirm all modified settings were written to the device.
3. Disconnect from the device properly through the application.
4. Reconnect to confirm the configuration values.

If necessary, reapply the configuration settings and save again.

Device Stops Playing Audio After Programming

If the device stops playing audio after configuration changes:

Possible causes:

• Device not properly disconnected from the programming application
• Audio configuration not saved

Corrective actions:

1. Reconnect to the device using the programming interface.
2. Properly disconnect from the device through the application.
3. Power cycle the device if necessary.

Properly disconnecting from the device ensures the audio system returns to normal operation.

Lost Passcode

If the station passcode is lost or forgotten:

The Audible Beacon Device must be returned to the manufacturer for passcode reset.

Technicians should store passcodes securely for future maintenance access.

Communication or File Transfer Errors

If file transfers or configuration changes take an unusually long time:

Possible causes:

• Large audio file size
• Bluetooth communication interruption
• Application software error

Corrective actions:

1. Restart the programming application.
2. Attempt the transfer again.
3. Confirm the audio file meets required specifications.
4. Move closer to the device during file transfer.

Preparing for Technical Support

Before contacting technical support, gather the following information:

• Device station identification number
• Device CC number
• Firmware version
• Description of the issue observed
• Steps already taken to troubleshoot the issue

This information will help expedite the troubleshooting process.

When Service Is Required

If troubleshooting procedures do not resolve the issue, the Audible Beacon Device may require repair or replacement.

Contact technical support for additional diagnostic procedures or service instructions.