![](/images/new-backgrounds/1110282/11028229x1.webp)
Table 1. Troubleshooting Using LEDs (Continued)
Symptom | Problem/Recommended Checks |
|
|
LINK LED | a. Network Names of APs and Remotes do not match. |
not lit. | They must be identical for association to |
| verify that the system has a unique Network Name. |
| b. Remote not yet associated with an Access Point with |
| the same Network Name. |
| Check the “Status” of the unit’s process of associating |
| with the Access Point. Use the Menu System. |
| c. Poor Antenna |
| and connectors. Reflected power should be less than |
| 10% of the forward power reading (SWR 2:1 or lower). |
| d. Wrong Frequency Mode parameters where units need |
| to be time synchronized. Frequency Mode parameters |
| are channel, bandwidth and pattern offset. |
| e. Wrong encryption |
| and Encryption Phrase must match on the AP and |
| Remote. |
| f. Wrong device authentication |
| match on AP and Remote. |
|
|
LAN LED not | a. Verify the Ethernet cable is connected at both ends. |
lit. | b. Verify that the appropriate type of Ethernet cable is |
| |
| used: |
| c. Verify setting of parameter Eth Port Follows |
| Association if selected or enabled. If enabled, LED |
| does not light when Remote is not associated. |
|
|
GPS LED | Indicates no GPS fix has been obtained. This only applies |
not lit | when GPS operation is desired. |
| a. Check connection of GPS antenna cable and the |
| antenna itself. Is there a clear “view” to satellites? |
| Note: Blinking LED indicates establishing TDD Sync. |
|
|
12 | MDS Mercury Series Startup Guide |