I’m pretty new to the Canopy hardware, so I thought I would ask a few questions regarding what I am seeing. I have a simple test setup right now, a single AP and one SM about 1/4 mile away. I am in pretty rocky mountainous terrain and heavy foliage.
My stats for the local AP Sessions status is as follows:
LUID: 002 : MAC: 0a-00-3e-90-ae-53 State: IDLE
Session Timeout: 0, AirDelay 10 (approximately 0.28 miles (1470 feet))
Session Count: 16, Reg Count 13, Re-Reg Count 3
RSSI (Avg/Last): 1524/1541 Jitter (Avg/Last): 4/4 Power Level (Avg/Last): -68/-67
DnRate(AP): 20000 DnLimit(AP): 500000 UpRate(AP): 20000 UpLimit(AP): 500000 (kbit)
LoUpCIR(D): 0 LoDnCIR(D): 0 (kbps)
Rate : VC 18 Rate 1X/1X
The stats for the remote SM status page are as follows:
The SM’s AP Eval Data is as below:
Current entry index: 0
*********************************************
Index: 0 Frequency: 906.0 MHz ESN: 0a-00-3e-90-43-a2
Jitter: 5 RSSI: 1209 Power Level: -79 Beacon Count: 15 BRcvW: 0 DFS: 0 FEC: 0
Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 1 Range: 441 feet TxBER: 0 EBcast: 0
Session Count: 12 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0
FrameNumber: 469 SectorID: 0 Color Code: 0 BeaconVersion: 1 SectorUserCount: 0
Frequency: 9060 NumULHalfSlots: 12 NumDLHalfSlots: 37 NumULContSlots: 0
The AP status page is as below: (this happened to be a point whem the SM was not registered)
The Spectrum Analyzer output is optimal, nothing shows over -70 db.
If necessary, I can post a screenshot of that. (Anyone know how to get one from a SM remotely?)
AP Config is as follows:
SM Config is as follows:
I am having trouble keeping the connection stable. It will be up for 30 minutes then down for 10, up for 5 down for 5, up for 4 hours then down for 1 hour. The “session count” continues to increase and in a 1 hour timespan it could reach 15-20. The AP is currently mounted at about 40’.
Anyone have any ideas?
Do you run your spectrum analysis from the SM or the AP? If you did not run it from the AP, turn the AP into an SM via the configuration page and do an analysis. The AP could be getting hit by interference while the SM seems to be fine.
Once I change the AP to an SM, I do not have the spectrum analyzer option like I do in a SM. Am I missing something?
Got it. Had to close the window to refresh the sidebar.
Looks like some decent interference…
Does this analysis from the AP tell me that there is not much that I can do?
The 906-910 noise floor is really low. Do you have a SM or something else firing at the AP? If not, go down to 906 and use that, as it doesn’t look bad at all. In fact, what you’re seeing on that graph looks a lot like a Trango or Motorola 900 AP. : :shock:
I currently have the AP set to 906. I have the SM pointing at the AP. Are there any settings I should adjust?
Could the high dbs possibly be from the SM attempting to register with an AP?
mmm… there is RF but your AP is on 906 and the other RF is much higher so you should be ok.
Try deslecting all the other frequencies on the SM and only have the 906 selected.
… when you ran the spectrum scan… was your SM looking to the AP switched on ?
Ok, deselected all but 906 on the SM. Still looks very high. I don’t think there is anyone else out here with APs, I am out in the sticks.
If that’s from the AP, then you should set the AP to 906Mhz because the noise floor is lowest in that region. And there is definitely something nearby which is broadcasting from 911-919 that looks just like a Trango AP to me. 
a couple of more things it may not help you initial problem but we have ours set to fire up in operational mode that way it does not go idle and set the max range to 10 for starters and also put you in a community string other than canopy and stick with it.
also what kind of antennas you using vertical or horizontal and are the sm antennas turned the right way if ther yagis or panels?
how tall is your tower?
can you see the tower or ap?
oh and turn bam off for now set to sm you can fool with bam later
I’ve had the AP set to 906 since the beginning.
I am using integrated antennas on both the SM and AP. My AP is aimed pretty much directly in his direction, but it is not line of site. My tower is about 40’ but does not clear the trees. SM is 1200’ away.
Is there any hope, or should I invest in a higher tower?
Below is a ping output. Are these response times normal? It appears that there is a large lag about every 15 pings (when the SM is responding).
Reply from 192.168.0.30: bytes=32 time=48ms TTL=254
Reply from 192.168.0.30: bytes=32 time=98ms TTL=254
Reply from 192.168.0.30: bytes=32 time=28ms TTL=254
Reply from 192.168.0.30: bytes=32 time=18ms TTL=254
Reply from 192.168.0.30: bytes=32 time=12ms TTL=254
Reply from 192.168.0.30: bytes=32 time=7ms TTL=254
Reply from 192.168.0.30: bytes=32 time=58ms TTL=254
Reply from 192.168.0.30: bytes=32 time=33ms TTL=254
Reply from 192.168.0.30: bytes=32 time=143ms TTL=254
Reply from 192.168.0.30: bytes=32 time=47ms TTL=254
Reply from 192.168.0.30: bytes=32 time=53ms TTL=254
Reply from 192.168.0.30: bytes=32 time=22ms TTL=254
Reply from 192.168.0.30: bytes=32 time=32ms TTL=254
Reply from 192.168.0.30: bytes=32 time=777ms TTL=254
Reply from 192.168.0.30: bytes=32 time=167ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.30: bytes=32 time=41ms TTL=254
Reply from 192.168.0.30: bytes=32 time=249ms TTL=254
Reply from 192.168.0.30: bytes=32 time=600ms TTL=254
Reply from 192.168.0.30: bytes=32 time=475ms TTL=254
Reply from 192.168.0.30: bytes=32 time=97ms TTL=254
Reply from 192.168.0.30: bytes=32 time=388ms TTL=254
Reply from 192.168.0.30: bytes=32 time=17ms TTL=254
Reply from 192.168.0.30: bytes=32 time=162ms TTL=254
Reply from 192.168.0.30: bytes=32 time=486ms TTL=254
Reply from 192.168.0.30: bytes=32 time=119ms TTL=254
Reply from 192.168.0.30: bytes=32 time=58ms TTL=254
Reply from 192.168.0.30: bytes=32 time=8ms TTL=254
Reply from 192.168.0.30: bytes=32 time=32ms TTL=254
Reply from 192.168.0.30: bytes=32 time=247ms TTL=254
Reply from 192.168.0.30: bytes=32 time=301ms TTL=254
Reply from 192.168.0.30: bytes=32 time=702ms TTL=254
Reply from 192.168.0.30: bytes=32 time=47ms TTL=254
Reply from 192.168.0.30: bytes=32 time=7ms TTL=254
Reply from 192.168.0.30: bytes=32 time=12ms TTL=254
Reply from 192.168.0.30: bytes=32 time=1128ms TTL=254
Reply from 192.168.0.30: bytes=32 time=83ms TTL=254
Reply from 192.168.0.30: bytes=32 time=7ms TTL=254
Reply from 192.168.0.30: bytes=32 time=17ms TTL=254
Reply from 192.168.0.30: bytes=32 time=11ms TTL=254
Reply from 192.168.0.30: bytes=32 time=12ms TTL=254
Reply from 192.168.0.30: bytes=32 time=17ms TTL=254
Reply from 192.168.0.30: bytes=32 time=17ms TTL=254
Reply from 192.168.0.30: bytes=32 time=22ms TTL=254
Reply from 192.168.0.30: bytes=32 time=27ms TTL=254
Reply from 192.168.0.30: bytes=32 time=11ms TTL=254
Reply from 192.168.0.30: bytes=32 time=21ms TTL=254
Reply from 192.168.0.30: bytes=32 time=17ms TTL=254
Reply from 192.168.0.30: bytes=32 time=12ms TTL=254
Reply from 192.168.0.30: bytes=32 time=16ms TTL=254
Reply from 192.168.0.30: bytes=32 time=562ms TTL=254
Reply from 192.168.0.30: bytes=32 time=6ms TTL=254
Reply from 192.168.0.30: bytes=32 time=16ms TTL=254
Reply from 192.168.0.30: bytes=32 time=39ms TTL=254
Reply from 192.168.0.30: bytes=32 time=100ms TTL=254
Reply from 192.168.0.30: bytes=32 time=22ms TTL=254
Reply from 192.168.0.30: bytes=32 time=30ms TTL=254
Reply from 192.168.0.30: bytes=32 time=10ms TTL=254
Reply from 192.168.0.30: bytes=32 time=15ms TTL=254
Reply from 192.168.0.30: bytes=32 time=99ms TTL=254
Reply from 192.168.0.30: bytes=32 time=100ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
some kinda sign of Re-Regs… Line of Sight will be a big help… Always mount APs on the highest pole possible…
I guess everybody here is doing 100’-200’ towers.
@mslaga:
Question: Do you only have 1 AP?
Just a couple of things, take your sm out of aiming mode, in your Ap set 1 control slot, increase your milage to 20 or 30 miles and set to sm not bam-sm
well you could get a connectorized sm with about a 14 to 17 db yagi that would help you alot and yes if you can get above the trees i think you will be good to go.
but you still need to do some tweaking on your settings
I live out in the sticks and the only internet service that was available was a T1 or better from the telco. My goal, in a nutshell, is to share the cost of the T1 circuit (~$500) between a few neighbors who are most interested in faster internet access.
The problem: We are on the side of a mountain with 75’ trees all around. All the houses in my neighborhood are on 5 or more acre lots. Now it works out that I am somewhat in the middle of the neighborhood, the furthest neighbor is the one I am trying to accomodate now, he is about 1300’.
I could invest several thousand into a tower, but that would not really help me offset the cost of the T1 for quite a while. This canopy gear has already cost quite a bit as it is.
Right now I only have 1 AP. I did change the BAM to SM. I will also increase the mileage to 25 and see if that helps. I will also set the control slot.
Thanks in advance for your help!
Another quick question. I have my AP currently pole-mounted on the roof of my house. The pole does move very slightly in the wind. Would this also make an impact? Would it be better to be solid mounted about 10-12 feet lower?