Very strange behavior when restarting my PicoStation2

[MCunha]

Hi all,

I receive my PicoStation2 today. The first thing I did was a firmware update, from 3.2.3 to 3.4, as soon I turn it on.
Right after the firmware was update, I wasn't able to access the device anymore. I did the recovery procedure several times until I notice the problem wasn't the firmware.

This is the problem: most times I start the pico2, only the power led is turned on and the device don't respond to ping command (no activity from network led).
But if I let the device of for some time (a minute or more), when I plug the cable and turn it on, It will work! Both leds are on (network and power).

If I restart by software (restart button @ AirOS or reboot command @ SSH) some times it will work, some time it will brick (only power led will keep on). But, EVERY time I turn it on and off, only the power led will stay on, unless I wait one minute before turn it on again.

This is really unusual in my opinion. I never saw a similar behavior with others APs (including a few bullets I own).

Is my picostation trustful?
Can I do something to fix this?

Thanks in advance.


EDIT

After a few more tests, I notice a few things:

The PicoStation will work ONLY if it is cool when turned on (this is why one minute or more is need every restar).
If the LAN led is off, I can't access the unit wireless. When this occurs, the unit is completely dead (until its temp cool down and I restart it with sucess).

I think I got a bad unit :(

Regards.

[MCunha]

I made several tests since I notice the problem, and discovered a peculiar behavior from my picostation.

Since I notice the LAN led problem is probably related with heat, I test the unit with a 12v PoE supplier (less volts, less heat, right?). In fact, the time to reconnect the unit with success has decreased a little. But this isn't the stranger thing I discovered.

While testing, I discovered that the Picostation has a mediocre performance. Quite different from any other G access point. The upload speed (ex, from Pico2 to a computer) never get the expected 25mpbs ratio.
But what I discover is more like a hardware problem. I've tested, like said above, with a 12v power source and the original 15v. In all tests I use the same network cable, with 5m length and the same notebook. The notebook was placed 2,5m from the PicoStation, at the same room, with, according with AirOS, -25DBm, 54M for TX and RX. And, before anyone ask, I've tried several power settings and all the main channels (1, 6 and 11).

The result has surprised me: the unit has a better (or last mediocre then 15v) performance when using a 12v power source.

The following screenshot was take transferring a single file (1gb) from a wired desktop to the notebook, with 15v power source:
http://img197.imageshack.us/img197/2205/pico215v.th.jpg (http://img197.imageshack.us/my.php?image=pico215v.jpg)
The average speed is 12mbps, with some 20~22mbps spikes.

The following screenshot was take transferring the same file, exactly the same condition, but powered with 12v:
http://img26.imageshack.us/img26/1136/pico212v.th.jpg (http://img26.imageshack.us/my.php?image=pico212v.jpg)
The performance was better, because the spikes are more frequent.

Below is a screenshot showing the signal quality:
http://img3.imageshack.us/img3/4708/stations.th.jpg (http://img3.imageshack.us/my.php?image=stations.jpg)
And here a scresnshot showing the upload from notebook to desktop (client -> pico). As may be notice, the problem affects the upload too, but make no difference here if is powered by 12v or 15v. In both cases, the upload ratio is aboult 16mbps (little better then download speed, but with less 20mpbs spikes)
http://img15.imageshack.us/img15/6038/pico2upload.th.jpg (http://img15.imageshack.us/my.php?image=pico2upload.jpg)

Ok, this 12/15v thing can be a strange coincidence, but to me Is pretty clear that PicoStation has some PoE and/or heat problem. If not a PoE/heat problem, still having some other problem, because 13mbps is really bad to a G device!

Since I'm not the only one complaining from this LAN led issue, I ask if switch my unit will solve the problem... Since I have no word from Ubiquiti, I don't know if I have a bad unit or all Pico2 are crappy like mine.

Regards.

[acedrew]

Brand new PicoStation, just upgraded to 3.4 firmware. Exact same issue, you have to leave power off for several minutes before it will power back up. Unacceptable.
Please advise when you have devised a solution to this issue, I love the form-factor and GUI for this device, it's too bad it doesn't work.

[UBNT-Mike.Ford]

Hey Guys,

I am testing this at the moment in the lab and will let you know the results.

Thanks,

Mike

[along5664]

We had a power outage last night at a hotel we service, and out of my 7 installed pico, 6 of them did not come back up after the power outage. I think the power just went out and came right back on, maybe a 1-2 sec outage. I did power cycle them all again and now they are up.

[along5664]

Was doing some testing in teh office today with a pico, was changing the speed rates and well as the mode b/g and b only. Made a lot of changing to test and when I changed from ewma to optimistic the unit did a reboot, and it did lock up and not come back up, until I did a power cycle. I am trying to reproduce the error, but so far can't. I did have one client associated during all this testing. Maybe this can help find the solution. I have it on 3.2.2 software at this time.

[along5664]

Ok got it to lock up again. Here is what I did, I unplugged the cat 5 from the injector and plugged it back in as quick as possible to simulate a quick power hit. Locked right on up....then did another power cycle, for about 10 secs and rebooted with no issues. Seems that if it takes a quick power hit, lockup. That does not explain the issue from yesterday where I made a bunch of changes and switched it from ewma to optimistic and it did a reboot on the changes and hung.....

[WHT]

I can see a market for delayed power up module.

[along5664]

Just had call from apartment complex where I have a pico setup, it was locked up. No power outages or anything. Juts quit working...A power cycle brought it back to life. these are driving me nuts......

[along5664]

I did a downgrade from 3.4 to 3.3.2 on a pico today and when it rebooted, it hung. Of course a power cycle go it going again....just something else causing these to lock up...

[Alexander]

Thank you very much - this discussion has helped me solve my problem

[along5664]

Did you find a fix for the lockup issue? If so please share...

[MCunha]

Did you find a fix for the lockup issue? If so please share...
I don't think there is a fix... It's look like a hardware issue, since it happens with 3rd party firmware too.
I own 2 pico2. One has this problem, whatever the firmware installed. The other doesn't have it. I can use any firmware and any poe injector.
According with the box, both units I have was tested at the same day by the same engineer and comes with the same AirOS version (3.2.3). In others words, its a lottery!

I can see a market for delayed power up module.

I agree :lol:

Regards.

[bobcopro]

This is definitely an issue with the Pico-2's. We have 6 out of 200 units on our system (all PS2's, NS2's, etc.) 5 of the 6 will not come up after a power disconnect or ping watchdog reboot. They will usually come back on after a soft reset (changing AP, etc.) Some are 3.2, some are 3.4 firmware.

They will often come up if the LAN cable is hooked up to a computer, not another Pico or Nano, but an actual computer. Otherwise I can power cycle them all day and only the 1 LED and not accessible via Lan and not transmitting.

When they will not come back up while hooked to a computer if I disconnect the AC cable from the POE adapter and plug it back it they will come up, not just disconnecting the Ethernet to the unit (old satellite receiver trick - don't know why it works.)

We are pulling them off the system as I type this until a fix can be found. Don't know what to do with the 20 Pico-HP's that just came in today. We're trying one in the field.

[WISPNZ]

Hi peeps!

We are looking into getting 15 Pico2HP units.
Has this issue been resolved? What has UBNT done to address this?

Kind Regards,
Arno

[dvdwalt]

Hi,

Just to mention we also experienced the same behavior with OpenWRT flushed PicoStation2s.

After a power failure some units does not come back on.
These are not a specific one, this week-end two out of three came back, one hanged.
Last night we had the same, but a different one refused to come back this time.

Luckily we are only at the start of this roll-out, but this is a major consideration for future purchasing and roll-outs.
Thanks to the original poster for giving us a heads-up!

Until this issue is solved I'll look at other Ubiquity models to use instead.

Cheers

[WISPNZ]

?? :D

Please let me know, thanks guys!

[UBNT-Mike.Ford]

Hey Guys,

We are aware that short disconnections in power can cause the units to lockup. The best suggestion is to use a UPS or power conditions and also verify that the PoE is properly supplying the voltage to the units.

THanks,

Mike

[yobosangria]

Hey Guys,

We are aware that short disconnections in power can cause the units to lockup. The best suggestion is to use a UPS or power conditions and also verify that the PoE is properly supplying the voltage to the units.

THanks,

Mike

Excuse me for a minute while I rant.

How can you call this crap carrier grade?
I love the interface, the power, and the cost.
The unreliability is driving us crazy. We have these things mounted on poles throughout RV parks. Sometimes the power flickers. Every other manufacturer's units just come back up. Ubiquiti Nanos, Picos, and Bullets are a crapshoot. It's not tenable to put a UPS or line conditioner in a NEMA box on every pole.

Carriers put these things in remote locations. End users can unplug and replug when this obnoxious behavior occurs, but this requires a truck roll or embarrassing "Can you reset the units again?" phone call to the management at the RV parks.

When you combine these problems with the ridiculous production/distribution snafus, UBNT gets harder and harder to recommend. Don't even get me started on the non-grounded POE injectors which killed so many ethernet ports during lightning storms.

Please fix the ethernet problems. How hard can that be?

[bobcopro]

It's been months with this issue. I'm just RMAing them now as I take them down. I can't afford to put a $70 UPS on a $70 unit. Just a function of the age of the product cycle. My PS2's and NS2's never have any issue. My Bullet2-HP's fry and the Pico's won't reboot and now the new BulletM2 likes to stop communicating with all it's clients several times a day. Connect to a different AP and back and it's fine.

[Gareth]

Has this issue been sorted out yet / is there a solution? I bought a new Pico2 last week and I'm having the exact same problem as described by the original poster.

[Gareth]

I'm still struggling with this.

Anyone?