All of the old M series, 5GHz & 2.4GHz had an underclocked processor to avoid coming to close to the 2.4GHz frequency and causing interference to co-located 2.4GHz radios. As it turns out, the third harmonic of the 2GHz frequency that they were underclocked to would interfere with Verizon's 700MHz LTE gear. So we have to run special (not underclocked) firmware on sites where we co-locate with Verizon. None of the new radios made in the last few years have this issue, as they have a faster processor. They really didn't need to underclock them anyway. We have 2.4GHz alongside of radios that had that special firmware and they were not affected at all.
On Fri, Sep 1, 2017 at 1:44 PM, George Skorup <george.sko...@cbcast.com> wrote: > Ethernet. Power it up, leave ethernet link down. > > Switching power supply. Try battery power only, leave ethernet link down. > > CPU/SoC. Pretty much the end of the road. I remember a thread from maybe a > couple years ago where an UBNT radio was interfering with VzW's uplink. I > think UBNT did a special firmware that changed the CPU freq. I don't > remember which radio that was. > > I want to say the IF side of the Dish LNB can be between 500-2200MHz. The > cables tied together is obviously not good. > > You're probably better off just moving your radio and cable to just be > done with it. > > > On 9/1/2017 1:05 PM, Jay Weekley wrote: > >> Got a call from a guy in the field that says Dish moved their equipment >> behind our 2.4 Airgrid and whenever our radio is powered up the customer >> loses their high definition channels. Our cable and theirs are tie wrapped >> together so I suggested that they power the radio with their survey rig to >> see if some kind of interference was involved. Any idea on what is causing >> this problem? Other suggestions besides moving our radio? >> > >
