I don't think I'll send just one SM to Paul, but had I known about this, I might have kept others for maybe a batch send. Great to know it's repairable - I'll put it on the shelf. Does this happen with the 450's or is it an FSK only thing?
I'd still like to know what can cause it, if it was something within my control I'd like to avoid doing it again in the future! -Steve D On Thu, Nov 13, 2014 at 8:32 AM, That One Guy via Af <af@afmug.com> wrote: > ALWAYS send to Paul, if nothing else it gets you out of dealing with Ewaste > > On Thu, Nov 13, 2014 at 10:16 AM, Nate Burke via Af <af@afmug.com> wrote: > >> Dang, I think I just threw out 3 or 4 AP's that were stuck in default >> mode because I didn't think they were repairable. Is your workaround a new >> fix? >> >> >> On 11/13/2014 10:13 AM, Paul McCall via Af wrote: >> >>> Matt, >>> >>> There are actually lots of little chips around the CPU area that can >>> cause this and a couple other parts that can as well. >>> >>> We actually have a proprietary workaround that works pretty universally >>> to fix this, but I cant share that secret :) it involve no component swaps. >>> >>> Paul >>> >>> -----Original Message----- >>> From: Af [mailto:af-boun...@afmug.com] On Behalf Of Matt via Af >>> Sent: Thursday, November 13, 2014 9:28 AM >>> To: af@afmug.com >>> Subject: Re: [AFMUG] Phantom Default Plug? >>> >>> Anyone know the component to replace to fix this? Have replaced >>> ethernet controller chips and diodes on P9 units. >>> >>> >>> On Wed, Nov 12, 2014 at 9:07 PM, Ken Hohhof via Af <af@afmug.com> wrote: >>> >>>> I had one do that, Paul at PDMNet said it was a hardware problem and >>>> apparently somewhat common, I sent it in and they fixed it. It was a >>>> pretty old SM and I thought it was just crud or water in the jack or >>>> on the PCB but I cleaned it up really good with alcohol with no success. >>>> >>>> From: Steve D via Af >>>> Sent: Wednesday, November 12, 2014 9:02 PM >>>> To: af >>>> Subject: [AFMUG] Phantom Default Plug? >>>> >>>> I know I've seen this before, but just had an FSK 2.4 SM do this to me >>>> - real bugger too because it was the last in my truck while I was out >>>> doing a site test. >>>> >>>> Any ideas what caused it or how to fix it? I think I was in the >>>> process of changing color codes when it happened. It's just my truck >>>> test unit running >>>> 11.2 firmware. Going to 13.1.3 didn't fix, nor did going back to >>>> 10.5. Put in a real default plug and reset to defaults too. >>>> >>>> -Steve D >>>> >>> >> > > > -- > All parts should go together without forcing. You must remember that the > parts you are reassembling were disassembled by you. Therefore, if you > can't get them together again, there must be a reason. By all means, do not > use a hammer. -- IBM maintenance manual, 1925 >
