With the AP off (freq=NONE) the SA shows a suitably low noise floor.
I'm thinking some kind of timing problem so it can see the energy but not
lock to the signal and decode the information in the beacons. Kind of like
the old days of analog TV when the vertical hold knob couldn't stop the
picture from rolling.
I hope replacing the SM tomorrow fixes it, otherwise I'm stumped. It was
too far up the customer's TV tower for me. Time to send the young guy. I'm
65 in a week, and I never liked heights anyway. And as you noted, it's too
damn hot. And humid. We're getting ground fog when the temperature drops
below 80.
-----Original Message-----
From: George Skorup
Sent: Tuesday, September 01, 2015 9:01 PM
To: [email protected]
Subject: Re: [AFMUG] FSK SM sees AP on SA but not on AP Eval
Oh. I misread it to mean it just won't register. I'm stupid. And tired.
Probably just a bad SM, but are you sure it's not local interference at
the SM? Maybe like a 40MHz or 80MHz wifi channel?
On 9/1/2015 8:54 PM, Ken Hohhof wrote:
So AP Eval needs xmt to work, it's not just a passive rcv thing?
-----Original Message----- From: George Skorup Sent: Tuesday, September
01, 2015 8:25 PM To: [email protected] Subject: Re: [AFMUG] FSK SM sees AP on
SA but not on AP Eval
Probably dead Tx. I've seen it a few times. Most of the time it's the
Tx/Rx switch, which means both directions lose 20-30dB. But I've
definitely seen only Tx or only Rx die before. The 85+ degrees the past
few days probably contributed to its demise. Pouring sweat working at a
tower today. That sucked.
On 9/1/2015 6:17 PM, Ken Hohhof wrote:
This SM just stopped working after several months. I would say it went
"deaf", but Spectrum Analyzer still works. It sees the AP at the right
frequency and signal level, and if I move the AP frequency around it's
clear that interference is not the problem. And no, it's not a
configuration issue.
I'm sending a field tech to climb the customer's TV tower tomorrow and
change out the SM, but I'm trying to remember if I've ever seen this
before.
Is this a known failure mode - not deaf, but seemingly can't lock onto or
decode beacons?
