Jump to content

RAvirani

S4GRU Staff
  • Posts

    3,455
  • Joined

  • Last visited

  • Days Won

    159

Everything posted by RAvirani

  1. That is what I meant - oops. I guess we’ll see. Verizon just rebuilt that area and it’s looking super nice, especially with the narrowband antennas on eNB 2305. I do wonder why they turned off low/mid CA on that site though.
  2. Sprint eNB 747123 has been outfitted with Sprint equipment. I hope they null the southwest sector on eNB 84598/97496…
  3. Oops - just realized I forgot to copy that PM here. My bad!
  4. This seems similar to the n38/n41 issue. It might also be MFBI.
  5. I cleaned the sectors on the map. @mikejeep would be the one to correct the glitch in app!
  6. No user access to the native 5G RAN in the Washington, Montana or Alaska yet.
  7. I’ve grabbed a good bit of SA on my AT&T iPhone SIM to date, although it’s not fully integrated into the SignalCheck DB yet…
  8. Just saw them! Went ahead and located the ones you mapped. I also confirmed that AT&T is using 1024 cells per site.
  9. Excited to see if AT&T SA NR data will upload now!
  10. I was just about to post this - I drove by there today as well!
  11. Yup - both us and Cellmapper had it wrong. As Mike said, we store the full NCI, not the gNB or sector, so recalculating these values is pretty easy for both of us. I’ve already done so on the map. One of the red flags I’m surprised Cellmapper didn’t pick up on is that there are no odd gNBs when using a 25 bit gNB.
  12. Apologies - T-Mobile is doing 4096 cells per gNB (12 bits per local ID and 24 bits per gNB). Still working on AT&T…
  13. T-Mobile is doing 2048 cells per gNB and AT&T is doing 1024 cells per gNB, I believe. I might need to double check that though.
  14. When you say don’t upload, what do you mean? Can you send me the file the app spits out on failure?
  15. The three big RF planning softwares are Atoll, Planet and Asset. They aren’t cheap or easily accessible; I have access to them because of my industry involvement. Here are links to more info: https://www.forsk.com/atoll-overview https://www.infovista.com/5g-network/planet-rf-planning-software https://www.teoco.com/products-services/ran-solutions/planning/
  16. 505922/506064 improves service along WA-16 (especially on midband). The capacity boost is a plus, too. Using both of these locations also allows the use of narrower antennas (think three 45° antennas spaced at 90°) which tend to have better gain figures. Not 100% sure on the logic here...I'll have to take a look at their plan. 505912/506054 provides much better service along WA-3 going north (almost LoS). I think there were also capacity concerns here. I'll have to take a look at the plan there. From eyeballing it, the Clear site won't improve coverage significantly and keeping both sites would destroy C/(I+N) levels.
  17. Unlikely: https://imgur.com/a/bWKGcPB I don’t have a T-Mobile traffic map to run a Monte-Carlo simulation or anything, but I doubt there’s a capacity need in that area.
  18. Let me pull the azimuths/tilts and take a look when I’m home this evening.
  19. Looks like my info was out of date - checked again this morning and that site is a listed as a conversion site. Interestingly enough, they’re still showing a candidate at Lund & Bethell (47.51765, -122.63022), although it’s not added into the active program…
  20. 746958 and 747190 will both be converted. 745791 doesn’t appear to be slated for conversion…I’ll see if I can figure out why.
  21. Totally missed this. That site is forecasted to be converted Q2 2022. And the site mentioned above. https://imgur.com/a/5yNA0ny I’m hoping they do a good job with the optimization here (unlike what we’re seeing in the Totem Lake area). Lowband RET is separate from midband RET on the antennas they’re deploying, and its range is 2-13 degrees. They can use that and maybe even mechanical tilt to minimize sector overlap. No 2500 small cell plans that I’m aware of.
  22. Non-beta users can feel free to send me their exported web data for import .
×
×
  • Create New...