FSK and OFDM should sync with eachother fine, you just aren't going to see
a 450i AP with an FSK SM.


On Fri, Jul 14, 2017 at 1:49 PM, CBB - Jay Fuller <[email protected]
> wrote:

>
> you can't even run fsk and ofdm on different channels using timing?
> we have not tried this yet....
>
>
> ----- Original Message -----
> *From:* George Skorup <[email protected]>
> *To:* [email protected]
> *Sent:* Friday, July 14, 2017 12:19 PM
> *Subject:* Re: [AFMUG] what kind of device would this be?
>
> FSK vs OFDM. 100% incompatible.
>
> On 7/14/2017 7:03 AM, Jay Weekley wrote:
> > I just assumed that Cambium's old 900 MHz equipment wouldn't see the
> > beacon information from their new stuff.
> >
> > CBB - Jay Fuller wrote:
> >> obviously 900 mhz and obviously cambium (former moto) - but i'm
> >> having a hard time matching up the mac address -
> >> any help?
> >> thanks :)
> >> AP Selection Method used: Optimize for Throughput
> >> Current entry index: 0 Session Status: SCANNING (via Disabled Color
> >> Code 0)
> >>
> >> Index: 2 Frequency: 924.00 MHz
> >> ESN: 0a-00-3e-9c-2d-9b Region: United States
> >> Jitter: 2 Power Level: -45 dBm Beacon Count: 16 BRcvW: 1 FECEn: 0
> >> Type: Multipoint Avail: 0 Age: 4 Lockout: 0 RegFail 0 Range: 0 feet
> >> MaxRange: 25 miles TxBER: 1 EBcast: 0
> >> Session Count: 0 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0
> >> Rescan Req: 0 SMLimitReached: 0
> >> NoVC's: 0 VCRsvFail: 0 VCActFail: 0
> >> FrameNumber: 1068 SectorID: 0 Color Code: 0 BeaconVersion: 0
> >> SectorUserCount: 2
> >> NumULHalfSlots: 12 NumDLHalfSlots: 35 NumULContSlots: 0
> >> WhiteSched: 0 ICC: 0 Authentication: Disabled
> >> SM PPPoE: Supported
> >>
> >> my only guess would be 900 mhz pmp450i?
> >>
> >> <http://www.avg.com/email-signature?utm_medium=email&;
> utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
> >>     Virus-free. www.avg.com
> >> <http://www.avg.com/email-signature?utm_medium=email&;
> utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
> >>
> >>
> >> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >
>
>

Reply via email to