Remote Access Point (RAP) Set up Help

Hello Forum Guys, I need help with some set up dilemna’s on a Remote Access Point (RAP).

I am using a 5.2AP to (RAP) SM and rebroadcasting with 5.2AP with seperation of incoming 5275 and RAP outgoing 5325.

I know it is suggested to use a differnet frequency, such as 2.4 or 5.7

We do not have 5325 freq in the area and my thoughts were we could get away with the rebroadcast considering the seperation(both freq & distance between SM & RAP)? SM(@RAP) Spectrum Analysis shows little interference).

Issues we’re having;

1) Unable to pass timing sync. Error, Connected wire with pins 1 and 6 only, no go. Good line. Why wont it pass sync?

Had to set AP to generate timing pulse.

2) Test SM’s feeding off RAP are running slow. They are not in the beampath of other frequency or receiving interference from.

Question, any set up info pertaining to priority uplink and downlink settings would be helpful?

We are using BAM.

Any thoughts or suggestions would be appreciated. If anyone has advice or experience with RAP deployment I’d like to hear about it?

Thank You,

Don’t know about the sync cable but if it was working it seems the RAP would be broadcasting in sync with the distant AP, exactly when the adjacent SM is receiving. Likewise if the AP is free-running it probably drifts relative to the adjacent SM and sometimes is broadcasting when the SM is receiving and sometimes they are broadcasting and receiving simultaneously. Either way, there seems to be a significant possibility of interference between the RAP and SM. I would think it could show up as large jitter in the SM sessions on the RAP. You could run the Spectrum Analyzer separately on the RAP and the SM to determine how much signal they see from each other. If it’s a lot, maybe some rf shielding could help. That’s just a guess tonight.

If the sync cable is good, then you can receive sync from the SM. We often feed a RAP via a SM and then serve customers with an AP. Typically, we will not use the same RF band, but we have deployed one installation where a 906V SM feeds a 924H AP. In general, the numbers are consistent with what we observed with other 900 MHz deployments (i.e. 1-2 short duration outages/day see below) in our area.

I pulled an AP from the field yesterday, however, that failed to receive sync from either the timing port via or power port (connected to CMM Micro) for in house testing and possible RMA.


Local AP:
Device type 900MHz - Multipoint - Access Point - 0a-00-3e-90-04-04
Software Version CANOPY 7.0.7 Mar 02 2005 15:06:58 AP-DES
Software Boot Version CANOPYBOOT 3.0
FPGA Version 021605 (DES Sched)
Uptime 17d, 20:46:01
LUID: 002 : MAC: 0a-00-3e-90-07-6c State: IN SESSION (Encrypt Active)
Site Name : BH - Long Farm
Software Version : CANOPY 7.0.7 Mar 02 2005 15:06:58
Software Boot Version : CANOPYBOOT 3.0
FPGA Version : 021605 (DES Sched)
Session Timeout: 24, AirDelay 46
Session Count: 22, Reg Count 21, Re-Reg Count 4
RSSI (Avg/Last): 1948/1890 Jitter (Avg/Last): 10/6 Power Level (Avg/Last): -61/-62
DnRate: 3500 DnLimit: 10000 UpRate: 3500 UpLimit: 10000 (kbit)
Rate : VC 18 Rate 2X/2X

Remote SM:
Session Status REGISTERED
Registered AP 0a-00-3e-90-04-04
RSSI 1777 (-62 dBm)
Jitter 9
Air Delay 46 (approximately 1.28 miles (6762 feet))
*********************************************
Index: 0 Frequency: 906.0 MHz ESN: 0a-00-3e-90-04-04
Jitter: 3 RSSI: 1736 Power Level: -63 Beacon Count: 16 BRcvW: 0 DFS: 0
Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 0 Range: 2254 feet TxBER: 0 EBcast: 1
Session Count: 19 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0
FrameNumber: 163 SectorID: 0 Color Code: 99 BeaconVersion: 1 SectorUserCount: 0
Frequency: 9060 NumULHalfSlots: 11 NumDLHalfSlots: 36 NumULContSlots: 2

Stats for LUID: 2 Test Duration: 10
Downlink RATE: 3457996 bps
Uplink RATE: 904345 bps
Downlink Efficiency: 100 Percent
Max Downlink Index: 96
Actual Downlink Index: 96
Expected Frag Count: 67539
Actual Frag Count: 67988
Uplink Efficiency: 97 Percent
Expected Frag Count: 17663
Actual Frag Count: 18116

Remote AP (sync via timing port from SM):
Device type 900MHz - Multipoint - Access Point - 0a-00-3e-90-35-58
Software Version CANOPY 7.0.7 Mar 02 2005 15:06:58 AP-DES
Software Boot Version CANOPYBOOT 3.0
FPGA Version 021605 (DES Sched)
Uptime 5d, 17:30:44
Session Status List
LUID: 002 : MAC: 0a-00-3e-90-07-d1 State: IN SESSION (Encrypt Active)
Site Name : Whitney
Software Version : CANOPY 7.0.7 Mar 02 2005 15:06:58
Software Boot Version : CANOPYBOOT 3.0
FPGA Version : 021605 (DES Sched)
Session Timeout: 26, AirDelay 26
Session Count: 3, Reg Count 2, Re-Reg Count 1
RSSI (Avg/Last): 1921/1911 Jitter (Avg/Last): 4/5 Power Level (Avg/Last): -57/-57
DnRate: 3500 DnLimit: 10000 UpRate: 3500 UpLimit: 10000 (kbit)
Rate : VC 18 Rate 2X/2X
LUID: 003 : MAC: 0a-00-3e-90-08-62 State: IN SESSION (Encrypt Active)
Site Name : Shearon
Software Version : CANOPY 7.0.7 Mar 02 2005 15:06:58
Software Boot Version : CANOPYBOOT 3.0
FPGA Version : 021605 (DES Sched)
Session Timeout: 12, AirDelay 33
Session Count: 2, Reg Count 2, Re-Reg Count 1
RSSI (Avg/Last): 2190/2207 Jitter (Avg/Last): 4/1 Power Level (Avg/Last): -51/-50
DnRate: 3500 DnLimit: 10000 UpRate: 3500 UpLimit: 10000 (kbit)
Rate : VC 19 Rate 2X/2X
LUID: 004 : MAC: 0a-00-3e-90-07-f1 State: IN SESSION (Encrypt Active)
Site Name : Hanley
Software Version : CANOPY 7.0.7 Mar 02 2005 15:06:58
Software Boot Version : CANOPYBOOT 3.0
FPGA Version : 021605 (DES Sched)
Session Timeout: 23, AirDelay 12
Session Count: 6, Reg Count 6, Re-Reg Count 0
RSSI (Avg/Last): 1813/1823 Jitter (Avg/Last): 4/4 Power Level (Avg/Last): -59/-58
DnRate: 3500 DnLimit: 10000 UpRate: 3500 UpLimit: 10000 (kbit)
Rate : VC 20 Rate 2X/2X

Status as measured from network operations center:
Device Status
Name: Whitney
Availability: 100 % (of 1 day, 23 hours, 5 minutes)
Packet Loss: 0.09 % (of 8665 total attempts)
Recent Loss: 3 pkts at Apr 08, 17:33:49
Round-trip time: 66 msecCanopy
Recent Outages:
04/08 17:33:55: DOWN for 21 seconds
04/08 09:02:31: DOWN for 21 seconds

Device Status
Name: Shearon
Availability: 99.9 % (of 1 day, 23 hours, 10 minutes)
Packet Loss: 0.17 % (of 8669 total attempts)
Recent Loss: 3 pkts at Apr 08, 17:33:56
Round-trip time: 136 msec
Recent Outages:
04/08 17:34:02: DOWN for 22 seconds
04/08 09:47:46: DOWN for 21 seconds
04/07 20:06:33: DOWN for 55 seconds
04/07 12:18:13: DOWN for 52 seconds

Device Status
SysName: Hanley
Availability: 99.8 % (of 1 day, 23 hours, 1 minute)
Packet Loss: 0.32 % (of 8640 total attempts)
Recent Loss: 3 pkts at Apr 09, 09:40:21
Round-trip time: 141 msec
Recent Outages:
04/09 09:40:27: DOWN for 21 seconds
04/09 07:07:07: DOWN for 22 seconds
04/08 17:34:09: DOWN for 21 seconds
04/08 09:47:21: DOWN for 51 seconds
04/07 20:06:40: DOWN for 55 seconds
04/07 12:17:24: DOWN for 1 minute, 51 seconds

I received a tip regarding “why your AP/SM wont pass sync”.

The suggestion; when deploying a Remote Access Point (RAP) it is necessary to ground the Modules (AP & SM) at the GPS Sync Ports with Ground Wire (from Cat5 Shielded Wire). Doing this allows the Modules to pass sync. Requires soldering Cat5 Shielded Wire “Ground” to GPS port.

I’ve been told that without grounding, no sync. Ap has to be set to generate sync pulse (as I’m currently doing).

In the brief time I’ve found to look at an SM, the port appears plastic. Maybe it’s molded over metal?

I’ll try anything, I’m just trying to find time for the hike up to the RAP. Update to follow.

PS - I have concluded and have been told Shielded RJ12 Plugs are not made. Does anyone know any different?

I made contact with Stewart Connectors. They make all kinds of good stuff. Including “Shielded” RJ11 or RJ12 Plugs;

… the 940-SP-360606 is a shielded 6 position, 6 contact plug but we
call it an RJ11, rightly or wrongly other people call them RJ12s. There is
no difference.

With Thanks and Regards
Sylvia Curtis Applications Engineer
bel Europe Preston UK
01772 556601
01772 888366

I checked and found shielded plugs from their website.

we have never had a problem getting an ap to accept sync thrugh the RJ12 port and have never used shield or grounded the unit pins.
Not sure what that suggestion was about.