Pico2HP Strange "speed hole"

[consultech]

I've been doing testing with my new Pico 2 HP for deployment in an apartment complex shortly. I've tried many combinations of settings. and it seems in all of them I get the following behavior.

in a 10-15 foot radius from the device I get great speeds and throughput. Connection stays at 24-56 Mbps and I download and upload at 10-12 Megabits per second easy.

in a 15-30 foot radius it fails almost completely. I can barely keep the connection alive it drops down to 1-5.5 mbps connection and I get anywhere from 500 Kbps to 1 meg.

in a 30-400 foot radius it goes back to great. At the 30 foot range I can get good connections again and download at 10-15 meg and hold 24mpbs to 56 mbps connections. out to 400 feet plus I also get good connections and download at 3-5 megabits per second.


I thought at first this could be a signal hole created by the Omni but I verified that my signal was in the low 30Dbi near the device and would slowly decrease down to the 70's as a moved farther and farther away. there was no apparent fade and then comeback as i moved through my 15-30 foot dead zone.

things i have tried.

changed the rate algorithm ( they all do the same except for they react at different speeds to me moving through my different zones.)

changed channels. ( I’m on 9 which is clear, there are access points on 6 and 11 though. but as an additional test point which helps rule out interference I have a Bullet2HP that does not exhibit this behavior at all.)

enabled and disabled noise immunity.

moved to a different building to make sure some weird localized interference was not taking place.

used auto ACK, then tried static ACK set the ack to a low number ( 21) and moved up to 40 60 -100 150) mostly the same behavior on all settings.

no SuperG features enabled at all( figured if it wouldn't work in basic mode, advanced mode won't be any better)

tried it at full power (29dbi) and a lower setting(20Dbi)

tried on original firmware( 3.2.3 or 3.3.2 I think) and the new Beta 3.4

also to make it seem stranger. I have a Bullet2HP that I have in the same environment and it works great.

also it appears that if I move into my deadzone and quickly start a download or a speed test I stay connected at the higher speeds. With actual throughout to prove it(downloading at 16MBps). Then after about 5-10 seconds it falls apart and drops to the lower speeds. It seems that if I choose one of the slower reacting rate algorithms it takes longer to drop the speed down. As if something is falsely forcing the access point to negotiate down, but it takes time, and before that happens it still pushes actually throughput at the higher levels. This pertains to my earlier post when I though I fixed it by switching out of EWMA mode and it worked( I didn’t test very long obviously. Within 30 seconds it drops down to single digit connection speeds.)

Any help or guidance would be very helpful.

Thanks
Derek

here is my config from the last run.

aaa.1.br.devname=br0
aaa.1.devname=ath0
aaa.1.driver=madwifi
aaa.1.ssid=ubntpico
aaa.1.status=enabled
aaa.1.wpa.1.pairwise=TKIP CCMP
aaa.1.wpa.key.1.mgmt=WPA-PSK
aaa.1.wpa.psk=ubnt test
aaa.1.wpa=1
aaa.status=enabled
bridge.1.devname=br0
bridge.1.fd=1
bridge.1.port.1.devname=eth0
bridge.1.port.2.devname=ath0
bridge.1.stp.status=disabled
bridge.status=enabled
dhcpc.1.devname=br0
dhcpc.1.status=disabled
dhcpc.status=disabled
dhcpd.1.status=disabled
dhcpd.status=disabled
dnsmasq.1.devname=eth0
dnsmasq.1.status=enabled
dnsmasq.status=disabled
ebtables.1.cmd=-t nat -A PREROUTING --in-interface ath0 -j arpnat --arpnat-target ACCEPT
ebtables.1.status=disabled
ebtables.2.cmd=-t nat -A POSTROUTING --out-interface ath0 -j arpnat --arpnat-target ACCEPT
ebtables.2.status=disabled
ebtables.3.cmd=-t broute -A BROUTING --protocol 0x888e --in-interface ath0 -j DROP
ebtables.3.status=enabled
ebtables.50.status=disabled
ebtables.51.status=disabled
ebtables.52.status=disabled
ebtables.status=enabled
httpd.port=80
httpd.status=enabled
igmpproxy.status=disabled
iptables.3.status=disabled
iptables.status=disabled
netconf.1.alias.1.status=disabled
netconf.1.alias.2.status=disabled
netconf.1.alias.3.status=disabled
netconf.1.alias.4.status=disabled
netconf.1.alias.5.status=disabled
netconf.1.alias.6.status=disabled
netconf.1.alias.7.status=disabled
netconf.1.alias.8.status=disabled
netconf.1.devname=eth0
netconf.1.ip=0.0.0.0
netconf.1.netmask=255.255.255.0
netconf.1.promisc=enabled
netconf.1.status=enabled
netconf.1.up=enabled
netconf.2.alias.1.status=disabled
netconf.2.alias.2.status=disabled
netconf.2.alias.3.status=disabled
netconf.2.alias.4.status=disabled
netconf.2.alias.5.status=disabled
netconf.2.alias.6.status=disabled
netconf.2.alias.7.status=disabled
netconf.2.alias.8.status=disabled
netconf.2.allmulti=disabled
netconf.2.devname=ath0
netconf.2.ip=0.0.0.0
netconf.2.netmask=255.255.255.0
netconf.2.status=enabled
netconf.2.up=enabled
netconf.3.autoip.status=enabled
netconf.3.devname=br0
netconf.3.ip=192.168.1.20
netconf.3.netmask=255.255.255.0
netconf.3.status=enabled
netconf.3.up=enabled
netconf.status=enabled
netmode=bridge
ppp.1.password=
ppp.1.status=disabled
ppp.status=disabled
radio.1.ack.auto=disabled
radio.1.ackdistance=5850
radio.1.acktimeout=60
radio.1.ani.status=disabled
radio.1.channel=9
radio.1.chanshift=0
radio.1.clksel=0
radio.1.countrycode=840
radio.1.devname=ath0
radio.1.dfs.status=
radio.1.frag=off
radio.1.ieee_mode=pureg
radio.1.mcastrate=6M
radio.1.mode=master
radio.1.rate.auto=enabled
radio.1.rate.max=54M
radio.1.rts=off
radio.1.rx_antenna=1
radio.1.rx_antenna_diversity=disabled
radio.1.status=enabled
radio.1.thresh62a=28
radio.1.thresh62b=28
radio.1.thresh62g=28
radio.1.tx_antenna=1
radio.1.tx_antenna_diversity=disabled
radio.1.txpower=10
radio.countrycode=840
radio.ratemodule=ath_rate_minstrel
radio.status=enabled
resolv.nameserver.1.ip=0.0.0.0
resolv.nameserver.1.status=enabled
resolv.nameserver.2.status=disabled
resolv.status=enabled
route.1.devname=br0
route.1.gateway=192.168.1.1
route.1.ip=0.0.0.0
route.1.netmask=0
route.1.status=enabled
route.status=enabled
tshaper.status=disabled
users.1.name=ubnt
users.1.password=
users.1.status=enabled
users.status=enabled
wireless.1.addmtikie=enabled
wireless.1.ap=
wireless.1.authmode=1
wireless.1.compression=disabled
wireless.1.devname=ath0
wireless.1.fastframes=disabled
wireless.1.frameburst=disabled
wireless.1.hide_ssid=disabled
wireless.1.l2_isolation=enabled
wireless.1.mac_acl.1.mac=
wireless.1.mac_acl.1.status=disabled
wireless.1.mac_acl.10.mac=
wireless.1.mac_acl.10.status=disabled
wireless.1.mac_acl.11.mac=
wireless.1.mac_acl.11.status=disabled
wireless.1.mac_acl.12.mac=
wireless.1.mac_acl.12.status=disabled
wireless.1.mac_acl.13.mac=
wireless.1.mac_acl.13.status=disabled
wireless.1.mac_acl.14.mac=
wireless.1.mac_acl.14.status=disabled
wireless.1.mac_acl.15.mac=
wireless.1.mac_acl.15.status=disabled
wireless.1.mac_acl.16.mac=
wireless.1.mac_acl.16.status=disabled
wireless.1.mac_acl.2.mac=
wireless.1.mac_acl.2.status=disabled
wireless.1.mac_acl.3.mac=
wireless.1.mac_acl.3.status=disabled
wireless.1.mac_acl.4.mac=
wireless.1.mac_acl.4.status=disabled
wireless.1.mac_acl.5.mac=
wireless.1.mac_acl.5.status=disabled
wireless.1.mac_acl.6.mac=
wireless.1.mac_acl.6.status=disabled
wireless.1.mac_acl.7.mac=
wireless.1.mac_acl.7.status=disabled
wireless.1.mac_acl.8.mac=
wireless.1.mac_acl.8.status=disabled
wireless.1.mac_acl.9.mac=
wireless.1.mac_acl.9.status=disabled
wireless.1.mac_acl.policy=allow
wireless.1.mac_acl.status=disabled
wireless.1.macclone=disabled
wireless.1.security=none
wireless.1.signal_led1=94
wireless.1.signal_led2=80
wireless.1.signal_led3=73
wireless.1.signal_led4=65
wireless.1.sper=disabled
wireless.1.ssid=ubntpico
wireless.1.status=enabled
wireless.1.wds=disabled
wireless.1.wmm=disabled
wireless.1.wmmlevel=-1
wireless.status=enabled
wpasupplicant.device.1.profile=
wpasupplicant.device.1.status=disabled
wpasupplicant.profile.1.name=
wpasupplicant.profile.1.network.1.bssid=
wpasupplicant.profile.1.network.1.eap.1.status=disabled
wpasupplicant.profile.1.network.1.key_mgmt.1.name=
wpasupplicant.profile.1.network.1.psk=ubnt test
wpasupplicant.status=disabled

[UBNT-Edmundas]

You did tests with Bullet2HP and Pico2HP devices using the same Omni antenna?
Can you provide link or document with antennas specification used with Bullet2HP device?

[consultech]

Unfortunately no. I have a 10 DBi omni on the bullet. (The manufacturer doesn't seem to have specs for it anymore. but it's a 2.4 Ghz 10DBi omni).I don't currently have a Rev SMA to N adapter to try the same antenna.

The Pico was tested using the included 6 Dbi antenna that comes with it as well as a smaller "2dBi Detachable Dipole Antenna" from a Trendnet device i had with a matching connector. Same behavior with both. Not much info on the site other than what I posted above but the device is a trendnet TPL-210AP

I also in desperation tried it with no antenna. The problem seemed to go away but my range was so short that it may have been difficult to fine my "deadzone"

I somewhat ruled out antenna/signal issues since I duplicated it with a similar but weaker antenna and also if I use net stumbler and map out my signal levels the "deadzone" is not evident at all via signal strength. I move 20 feet away my connectivity goes to crap and i have -30 to -40 Dbi of signal. Maybe that was a mistake.

Also I have duplicated the behavior on 4 laptops and all 4 of these laptops have no problems with the bullet or any other access point I have tested.

[consultech]

Update:

I found an adapter to use my large 10 dBI omni that i was using on the bullet on the pico. same behavior.

so in summary.

on the pico it behaves the exact same with:
the included Omni
a little trendnet 2.2 dbi
my Large wi-fi link 10 Dbi Omni.

On the Bullet using the large 10 Dbi omni it works great,as expected.

Again, I have great signal in the "deadzone".
see image link for a picture of the signal with the laptop in the deadzone with tons of signal and a download running at less than 1 meg. which i can run the download at 7-15 meg if i move out of the deadzone( either closer to the AP with more signal or farther away with less).

http://www.consultech.net/downloads/signal.bmp

[WHT]

Two things you might want to change....

Your ACK distance is set to over THREE MILES. Set it to about ten percent more than the actual physical distance you want to go.

Reduce your data speed, its at 54 Mbps. If your interconnection is 10 Mbps, use 24 Mbps data speed. If its 5 Mbsp, use 12 Mbps data speed.

[consultech]

I have had my Ack at multiple settings. The config I posted was just the last setting.

I have tried with it set to 21 and auto which is what should be appropriate for a regular access point covering a small set of rooms.

I have also set it to no Auto and used settings of 21, 40,60,100,150. all pretty much displayed the same behavior. some of the higher settings slowed things down everywhere so the dead zone wasn’t as apparent but that's more because it slowed everything else down instead of fix the hole.

I have reduced the data rates and set them to static and that didn't affect the problem either. I have also switched to B only mode and i get the same behavior. 6 meg throughput near the AP and far away but in my 15-30 foot zone i get almost nothing.

[UBNT-Edmundas]

Pico2 device is located inside building? Have you tried to mount your device in different places? The same behaviour?

[consultech]

Yes. the device is currently hanging from the ceiling in my office. I have moved the device to the far end of this building( about 100 yards in length) and seen the exact same behavior

The Bullet2Hp with the same antenna on a different channel works perfectly mounted not more than 5 feet away.

I have also tested with the Bullet off to make 100% sure it wasn't causing a problem.

Also after discussing with some other wireless people we wrapped the pico body in several layers of aluminum foil with the antenna completely sticking out to improve the shielding of the device just in case the was a compromise of the internal shielding. This did not change the problem either.

[WHT]

What happens when you swap the Pico and bullet locations. If the Pico starts working and the Bullet has the dead zone... then welcome to wireless propagation anomalies.

[consultech]

so I went ahead and swapped them just to be completely sure even though the Pico has exhibited the behavior in multiple locations in this building and the bullet( and other waps, wap54g's, ap-600's etc) have not.

I put the Pico where the bullet was. Exact same behavior

I put the Bullet where the Pico was. Bullet continues to operate very well.

I'm about ready to declare without a doubt that I have a bad Pico....

[consultech]

additional Tidbit.

I was running 3.4 RC i just upgraded to 3.4 and i get the same behavior.

currently running
XS2.ar2316.v3.4.4390.090521.1757

[bigdessert]

I have recently purchased a pico and am experiencing the same sort of thing.

actually upon further testing my results are similar but not the same. will make new post.

[montana_357]

Did anyone figure out your problem??? I am having the same issue. I even replaced the access point with an identical model. Same results.

[MontanaDave]

I have a Pico2 HP that is 10 feet away from my laptop that exhibits a very similar behavior: I can't get over 2 mbps on a connection that consistently tests (on a wired PC) at over 4.5 mbps. It's running the "PicoStation2HP-v3.4.build4390.bin" Firmware. I also have another PicoSta2 HP (Same Firmware) in a clients location that is having severe drop off of thru-put as a function of distance even tho' the signal strength is showing "full bars". The second unit was working well just after install, but now is acting up.

Additional Info: a Linksys WRV-210 at the same distance gives a speed test result that nearly matches the wired PC's result (4.4 mbps). I've run the tests many (dozens) times with very consistent results ....

:confused5:

[montana_357]

I also have this problem. 10 feet away I get 9 megs and 25' away I get 1 if I am lucky. I have read the threads there are other people with this issue. But, I have found no solutions yet. I also replaced with an identical unit to make sure the issue wasn't hardware.

[MontanaDave]

Quick Update to this whole deal:
I downgraded one of my PicoSta2 HP's to Firmware Ver XS2.ar2316.v3.2.2.4003.081114.1719 ("PicoStation2HP-v3.2.2.build4003.bin") and it WAS passsing much better thru-put. However, after a few tests it has now slowed back down to under 2 mbps ..... Something is very odd .... (All this time a wired PC and another access point are passing 4 to 5.5 mbps)...

If there are any Ubiquiti support people monitoring this thread, some input would be appreciated ......

I am continuing testing to ascertain more about this issue ....

[c550nelson]

I've been having similar issues with my Pico2 HP (firmware v3.4) and have also tried a large number of tests with changing ack, data rate, output power, rate algorithm and enable extra reporting off. No success. My setup is simple: pico2 HP as access point and three clients with WPA on (no WDS). The Pico connects with the clients at low data rates even with ideal signals (-60db). I've replaced the pico with a Nano2 and it works flawlessly.

[Jason O]

I have a Pico2 as an AP and a Loco2 as CPE when hooked up to the Pico wireless or the Loco the speed is like 1-2megs. I hook up to a Router that is feeding the Pico VIA an 8 port switch I get 4-5megs. I am going back to site and replace the Pico with an Loco as AP to fix this issue.

Jason

Pico2 is AirOS 3.4.4 Loco2 is 3.4.4

[UBNT-Mike.Ford]

I have a Pico2 as an AP and a Loco2 as CPE when hooked up to the Pico wireless or the Loco the speed is like 1-2megs. I hook up to a Router that is feeding the Pico VIA an 8 port switch I get 4-5megs. I am going back to site and replace the Pico with an Loco as AP to fix this issue.

Jason

Pico2 is AirOS 3.4.4 Loco2 is 3.4.4

Hey Jason,

Please send you config and support files to mike@ubnt.com

Thanks,

[cinders]

I installed my first Pico2HP today. It was installed outside on a 1st floor balcony with a 360 view of wooden huts. It is installed as a AP in bridge mode with POE15 kit and fully shielded Cat5e ethernet cable with grounded RJ-45 connectors.

The unit looked ideal for the job. I'm afraid it isn't so...

The throughput is awful. I'm seeing terrible rates. The signal is great all round, but the rates are terrible. 1-2mbps throughput. Something isn't right.

I managed to get it a lot better by reducing the transmit power and trying different channels. But it's still not ideal.

I have replaced the Pico2HP with an NS2 and have rock solid rates. I'm not sure what to do with the Pico2HP. This is obviously a problem.

Cinders.

[cinders]

Config File:

aaa.1.status=disabled
aaa.status=disabled
bridge.1.devname=br0
bridge.1.fd=1
bridge.1.port.1.devname=eth0
bridge.1.port.1.status=enabled
bridge.1.port.2.devname=ath0
bridge.1.port.2.status=enabled
bridge.1.stp.status=disabled
bridge.status=enabled
dhcpc.1.devname=br0
dhcpc.1.status=disabled
dhcpc.status=disabled
dhcpd.1.status=disabled
dhcpd.status=disabled
dnsmasq.1.devname=eth0
dnsmasq.1.status=enabled
dnsmasq.status=disabled
ebtables.1.cmd=-t nat -A PREROUTING --in-interface ath0 -j arpnat --arpnat-target ACCEPT
ebtables.1.status=disabled
ebtables.2.cmd=-t nat -A POSTROUTING --out-interface ath0 -j arpnat --arpnat-target ACCEPT
ebtables.2.status=disabled
ebtables.3.cmd=-t broute -A BROUTING --protocol 0x888e --in-interface ath0 -j DROP
ebtables.3.status=disabled
ebtables.50.status=disabled
ebtables.51.status=disabled
ebtables.52.status=disabled
ebtables.status=enabled
httpd.port=80
httpd.status=enabled
igmpproxy.status=disabled
iptables.3.status=disabled
iptables.status=disabled
netconf.1.alias.1.status=disabled
netconf.1.alias.2.status=disabled
netconf.1.alias.3.status=disabled
netconf.1.alias.4.status=disabled
netconf.1.alias.5.status=disabled
netconf.1.alias.6.status=disabled
netconf.1.alias.7.status=disabled
netconf.1.alias.8.status=disabled
netconf.1.devname=eth0
netconf.1.ip=0.0.0.0
netconf.1.netmask=255.255.255.0
netconf.1.promisc=enabled
netconf.1.status=enabled
netconf.1.up=enabled
netconf.2.alias.1.status=disabled
netconf.2.alias.2.status=disabled
netconf.2.alias.3.status=disabled
netconf.2.alias.4.status=disabled
netconf.2.alias.5.status=disabled
netconf.2.alias.6.status=disabled
netconf.2.alias.7.status=disabled
netconf.2.alias.8.status=disabled
netconf.2.allmulti=disabled
netconf.2.devname=ath0
netconf.2.ip=0.0.0.0
netconf.2.netmask=255.255.255.0
netconf.2.status=enabled
netconf.2.up=enabled
netconf.3.autoip.status=enabled
netconf.3.devname=br0
netconf.3.ip=192.168.2.10
netconf.3.netmask=255.255.255.0
netconf.3.status=enabled
netconf.3.up=enabled
netconf.status=enabled
netmode=bridge
ppp.1.password=
ppp.1.status=disabled
ppp.status=disabled
radio.1.ack.auto=disabled
radio.1.ackdistance=750
radio.1.acktimeout=26
radio.1.ani.status=disabled
radio.1.channel=11
radio.1.chanshift=0
radio.1.clksel=0
radio.1.countrycode=840
radio.1.devname=ath0
radio.1.dfs.status=
radio.1.frag=off
radio.1.ieee_mode=pureg
radio.1.mcastrate=1M
radio.1.mode=master
radio.1.rate.auto=enabled
radio.1.rate.max=54M
radio.1.rts=off
radio.1.rx_antenna=1
radio.1.rx_antenna_diversity=disabled
radio.1.status=enabled
radio.1.thresh62a=28
radio.1.thresh62b=28
radio.1.thresh62g=28
radio.1.tx_antenna=1
radio.1.tx_antenna_diversity=disabled
radio.1.txpower=15
radio.countrycode=840
radio.ratemodule=ath_rate_minstrel
radio.status=enabled
resolv.host.1.name=AP1
resolv.host.1.status=enabled
resolv.nameserver.1.ip=192.168.2.1
resolv.nameserver.1.status=enabled
resolv.nameserver.2.ip=192.168.2.1
resolv.nameserver.2.status=enabled
resolv.status=enabled
route.1.devname=br0
route.1.gateway=192.168.2.1
route.1.ip=0.0.0.0
route.1.netmask=0
route.1.status=enabled
route.status=enabled
sshd.status=enabled
tshaper.status=disabled
users.1.name=
users.1.password=
users.1.status=enabled
users.status=enabled
wireless.1.addmtikie=disabled
wireless.1.ap=
wireless.1.authmode=1
wireless.1.compression=disabled
wireless.1.devname=ath0
wireless.1.fastframes=disabled
wireless.1.frameburst=disabled
wireless.1.hide_ssid=disabled
wireless.1.l2_isolation=disabled
wireless.1.mac_acl.1.mac=
wireless.1.mac_acl.1.status=disabled
wireless.1.mac_acl.10.mac=
wireless.1.mac_acl.10.status=disabled
wireless.1.mac_acl.11.mac=
wireless.1.mac_acl.11.status=disabled
wireless.1.mac_acl.12.mac=
wireless.1.mac_acl.12.status=disabled
wireless.1.mac_acl.13.mac=
wireless.1.mac_acl.13.status=disabled
wireless.1.mac_acl.14.mac=
wireless.1.mac_acl.14.status=disabled
wireless.1.mac_acl.15.mac=
wireless.1.mac_acl.15.status=disabled
wireless.1.mac_acl.16.mac=
wireless.1.mac_acl.16.status=disabled
wireless.1.mac_acl.17.mac=
wireless.1.mac_acl.17.status=disabled
wireless.1.mac_acl.18.mac=
wireless.1.mac_acl.18.status=disabled
wireless.1.mac_acl.19.mac=
wireless.1.mac_acl.19.status=disabled
wireless.1.mac_acl.2.mac=
wireless.1.mac_acl.2.status=disabled
wireless.1.mac_acl.20.mac=
wireless.1.mac_acl.20.status=disabled
wireless.1.mac_acl.21.mac=
wireless.1.mac_acl.21.status=disabled
wireless.1.mac_acl.22.mac=
wireless.1.mac_acl.22.status=disabled
wireless.1.mac_acl.23.mac=
wireless.1.mac_acl.23.status=disabled
wireless.1.mac_acl.24.mac=
wireless.1.mac_acl.24.status=disabled
wireless.1.mac_acl.25.mac=
wireless.1.mac_acl.25.status=disabled
wireless.1.mac_acl.26.mac=
wireless.1.mac_acl.26.status=disabled
wireless.1.mac_acl.27.mac=
wireless.1.mac_acl.27.status=disabled
wireless.1.mac_acl.28.mac=
wireless.1.mac_acl.28.status=disabled
wireless.1.mac_acl.29.mac=
wireless.1.mac_acl.29.status=disabled
wireless.1.mac_acl.3.mac=
wireless.1.mac_acl.3.status=disabled
wireless.1.mac_acl.30.mac=
wireless.1.mac_acl.30.status=disabled
wireless.1.mac_acl.31.mac=
wireless.1.mac_acl.31.status=disabled
wireless.1.mac_acl.32.mac=
wireless.1.mac_acl.32.status=disabled
wireless.1.mac_acl.4.mac=
wireless.1.mac_acl.4.status=disabled
wireless.1.mac_acl.5.mac=
wireless.1.mac_acl.5.status=disabled
wireless.1.mac_acl.6.mac=
wireless.1.mac_acl.6.status=disabled
wireless.1.mac_acl.7.mac=
wireless.1.mac_acl.7.status=disabled
wireless.1.mac_acl.8.mac=
wireless.1.mac_acl.8.status=disabled
wireless.1.mac_acl.9.mac=
wireless.1.mac_acl.9.status=disabled
wireless.1.mac_acl.policy=allow
wireless.1.mac_acl.status=disabled
wireless.1.macclone=disabled
wireless.1.security=none
wireless.1.signal_led1=94
wireless.1.signal_led2=80
wireless.1.signal_led3=73
wireless.1.signal_led4=65
wireless.1.sper=disabled
wireless.1.ssid=BluechipWiFiCR
wireless.1.status=enabled
wireless.1.wds=disabled
wireless.1.wmm=disabled
wireless.1.wmmlevel=-1
wireless.status=enabled
wpasupplicant.device.1.status=disabled
wpasupplicant.status=disabled

[jdcallejas]

I have three complexes already running. On the small complex I tried to use the Pico 2HP, it was imposible to make them work!.. I tried everything, all kinds of configs, nothing worked. I finaly put them in a dumpster!!! Went back to my original setup of NS2 for APs and Loco5 for backhaul. This setup is 100% perfect, one of my complex has been up for a year without any problems, I have not tried the bullet but I am thinking of testing it.
From what I hear they are good!!!

Daniel

[Aveyer]

Just got my Pico2 today, same problem...terrible rates, throughput and sometimes alot of packet loss. Gonna return for a NS Loco2.

[along5664]

Was that a pico2hp or standard pico 2 wisphopefull?

[Aveyer]

Standard Picostation 2.

[deadjimmy]

I've seen the exact same issue w/ the HP.....watch the unit's modulation rates as it's trying to RX/TX data. Then try wrapping only your omni antenna in foil. Or better, attach a small directional and put a coffee can over the top of the antenna, push some data and watch the modulation rates again.

I played with this problem for hours and while I never figured out the actual cause, flipping a coffee can over the directional put me from a very variable and bouncy 1-1.5mbps both ways, to 16mbps both ways. The mod rates seemed to lock solid @ 54/54 with the can over the antenna for some reason.

We've installed some of these in a metro area size wifi network and they act really weird. Throttling and statically setting mod rates isn't really do-able given the RF variability in the environment.

[Jpearl2006]

I am having very similar issues with the picostation HP. I was wondering if anyone has found a solution at this point? I want to purchase the PowerAP N but I do not want to see the same results. Or if I could get the picostation to work correctly I would be happy also.

[dan_kelt]

I've confirmed this exact same behavior on several PicoHPs. I've even sent three of them to Mike Ford on three difference occasions. Each time they seem to get "lost" and now I'm just being ignored. I have a box of a about 150 PicoHP2 that are junk. Mike, would love an explanation.