SOURCE: Terminal cannot associate with AP Problem
The terminal's Status LED indicates the state of the 6800's connection to either of the RF
networks:
If you have multiple portable terminals, and this is the only one with issues making a connection to the AP, then the PDT6846 configuration is probably the issue here, as the unit does not associate when within range of the access point. This problem could also be indicative of either an internally defective RF card or simply a weak signal output from the PDT6846 due in large part to a weak battery.
ACTION STEPS
If problem persists, the PDT6846 requires repair attention specific to the internal radio card.
Rebooting the Device
Try rebooting the device using a Warm Boot. If the Warm Boot doesn't fix the problem, try a Cold Boot.
Warm Boot
A warm boot resets the operating system while preserving the program and data on the RAM disk. This process is similar to pressing the keys on a PC, except that it does not clear the system's memory. To perform a warm boot:
For the 35-Key terminal:
For the 46-Key terminal:
The terminal displays configuration information, copyright, RAM size, and expanded memory RAM size. Other information displayed depends on the operating system, installed device drivers, and AUTOEXEC.BAT commands. If this warm boot procedure fails to restart the terminal, use the Cold Boot procedure.
Cold Boot
A cold boot fully resets the system and clears memory, including the RAM disk. Any programs and data stored in memory or on the RAM disk are deleted. Nonvolatile memory (NVM - the Application EEPROM) is not affected. Caution: This procedure permanently erases all data and software in the terminal unless they reside in NVM. Contents of RAM are lost. To perform a cold boot:
For the 35-Key terminal:
For the 46-Key terminal:
The terminal displays version information, copyright, RAM size, and installed expanded memory RAM size. Other information displayed depends on the operating system, installed device drivers, and AUTOEXEC.BAT commands.
Cold-Boot Failure
During a cold boot, the system briefly displays a status line for each driver as it loads in the
format:
0: Driver #.##
The line shows a status value, usually 0, followed by the name and version number of the
driver. If the system halts at one of these lines and displays a status value other than 0, the
displayed device driver failed to load properly.
If such a failure occurs, try cold booting the terminal again. If this does not solve the problem, call the Symbol Support Center.
Here is your User Manual:
http://www.barcodemuseum.com/SymbolTechnologies/Manuals/pdt6800user.pdf
I’m happy to help further over the phone at https://www.6ya.com/expert/jeremy_69f3cc28d95bf514
LED Indicators
The unit has LED activity indicators on the front of the case provide a status display indicating error conditions, transmission, and network activity for the 802.11a (amber) radio or the 802.11b/g (green) radio.
802.11a Activity LED Amber
The amber LED flashes three times per second until firmware is loaded. During boot, 802.11a mobiles cannot associate. After adoption, the amber LED is steady or flashes with 802.11a radio traffic.
The amber LED flashes once per second if an error prevents the 802.11a radio from operating normally.
802.11b/g Activity LED Green
The green LED flashes three times per second until firmware is loaded. During boot, 802.11b/g mobiles cannot associate. After adoption, the green LED is steady or flashes with 802.11b/g radio traffic.
The green LED flashes once per second if an error prevents the 802.11b/g radio from operating normally.
From this, it appears that the 802.11A radio is malfunctioning.
Here is the Motorola support web page for this device.
246 views
Usually answered in minutes!
×