<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: surveying for wireless in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/surveying-for-wireless/m-p/5022830#M267122</link>
    <description>&lt;P&gt;Hi, so does the survey software automatically set the 20% overlap for you? do you tell it somewhere in the settings to do that ?&lt;/P&gt;</description>
    <pubDate>Thu, 22 Feb 2024 16:29:08 GMT</pubDate>
    <dc:creator>carl_townshend</dc:creator>
    <dc:date>2024-02-22T16:29:08Z</dc:date>
    <item>
      <title>surveying for wireless</title>
      <link>https://community.cisco.com/t5/wireless/surveying-for-wireless/m-p/5022775#M267114</link>
      <description>&lt;P&gt;Hi Guys&lt;/P&gt;&lt;P&gt;When doing a wireless survey on a site, normally they survey for voice at -67db for the edge of the cell.&lt;/P&gt;&lt;P&gt;I believe typically they look for a 20% overlap, so would that be an overlap be before the edge of the cell I am guessing?&lt;/P&gt;&lt;P&gt;Does software like Airmagnet/Ekahau take this into account when doing a predictive survey?&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;</description>
      <pubDate>Thu, 22 Feb 2024 15:05:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/surveying-for-wireless/m-p/5022775#M267114</guid>
      <dc:creator>carl_townshend</dc:creator>
      <dc:date>2024-02-22T15:05:25Z</dc:date>
    </item>
    <item>
      <title>Re: surveying for wireless</title>
      <link>https://community.cisco.com/t5/wireless/surveying-for-wireless/m-p/5022794#M267119</link>
      <description>&lt;P&gt;That 20% ovelap is a best practice which is very difficult to measure, and that's why all of us use the edge signal level of -67 dBm as a measure to establish when a device should start roaming and hence this is the value we set in survey tools visualizations to validate redundancy (for instance, Intermec/Honeywll barcode scanners do roam at -70 dBm, but iPhones do roam around -67/-68 dBm).&lt;/P&gt;</description>
      <pubDate>Thu, 22 Feb 2024 15:28:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/surveying-for-wireless/m-p/5022794#M267119</guid>
      <dc:creator>JPavonM</dc:creator>
      <dc:date>2024-02-22T15:28:03Z</dc:date>
    </item>
    <item>
      <title>Re: surveying for wireless</title>
      <link>https://community.cisco.com/t5/wireless/surveying-for-wireless/m-p/5022830#M267122</link>
      <description>&lt;P&gt;Hi, so does the survey software automatically set the 20% overlap for you? do you tell it somewhere in the settings to do that ?&lt;/P&gt;</description>
      <pubDate>Thu, 22 Feb 2024 16:29:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/surveying-for-wireless/m-p/5022830#M267122</guid>
      <dc:creator>carl_townshend</dc:creator>
      <dc:date>2024-02-22T16:29:08Z</dc:date>
    </item>
    <item>
      <title>Re: surveying for wireless</title>
      <link>https://community.cisco.com/t5/wireless/surveying-for-wireless/m-p/5023063#M267154</link>
      <description>&lt;P&gt;I use Ekahau and takes the (second) guessing out of the equation.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Feb 2024 21:28:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/surveying-for-wireless/m-p/5023063#M267154</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2024-02-22T21:28:48Z</dc:date>
    </item>
    <item>
      <title>Re: surveying for wireless</title>
      <link>https://community.cisco.com/t5/wireless/surveying-for-wireless/m-p/5023092#M267155</link>
      <description>&lt;P&gt;In what way do you mean ?&lt;/P&gt;</description>
      <pubDate>Thu, 22 Feb 2024 22:04:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/surveying-for-wireless/m-p/5023092#M267155</guid>
      <dc:creator>carl_townshend</dc:creator>
      <dc:date>2024-02-22T22:04:38Z</dc:date>
    </item>
    <item>
      <title>Re: surveying for wireless</title>
      <link>https://community.cisco.com/t5/wireless/surveying-for-wireless/m-p/5023097#M267157</link>
      <description>&lt;P&gt;With Ekahau, I could set up the design for Voice- (2 APs overlapping) or RTLS (3 to 4 APs overlapping) grade with confidence.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Otherwise, I have to "second guess" where the APs will be positioned if I have to make a design without Ekahau.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Feb 2024 22:14:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/surveying-for-wireless/m-p/5023097#M267157</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2024-02-22T22:14:19Z</dc:date>
    </item>
    <item>
      <title>Re: surveying for wireless</title>
      <link>https://community.cisco.com/t5/wireless/surveying-for-wireless/m-p/5023105#M267159</link>
      <description>&lt;P&gt;So are you letting ekahau place the access points for you using a predictive survey here ?&lt;/P&gt;</description>
      <pubDate>Thu, 22 Feb 2024 22:34:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/surveying-for-wireless/m-p/5023105#M267159</guid>
      <dc:creator>carl_townshend</dc:creator>
      <dc:date>2024-02-22T22:34:38Z</dc:date>
    </item>
    <item>
      <title>Re: surveying for wireless</title>
      <link>https://community.cisco.com/t5/wireless/surveying-for-wireless/m-p/5023117#M267162</link>
      <description>&lt;P&gt;Sorry, no.&amp;nbsp; That's not what I meant.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are manually placing the APs in Ekahau design map, however, Ekahau can evaluate if the placements will work in the either one of three scenarios we want.&lt;/P&gt;
&lt;P&gt;For example, we want to design for RTLS, Ekahau will tell us if the design passes (or fails) RTLS because &lt;span class="lia-unicode-emoji" title=":red_heart:"&gt;❤️&lt;/span&gt; APs coverage/overlap.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Feb 2024 23:49:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/surveying-for-wireless/m-p/5023117#M267162</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2024-02-22T23:49:59Z</dc:date>
    </item>
    <item>
      <title>Re: surveying for wireless</title>
      <link>https://community.cisco.com/t5/wireless/surveying-for-wireless/m-p/5023581#M267216</link>
      <description>&lt;P&gt;It's important to remember that Wi-Fi access point (AP) coverage is dynamic and influenced by various factors like transmit power, building materials, and environmental conditions. Designing with a uniform 20% overlap across the entire area might not be feasible/realistic due to these variations.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To address this challenge, I leverage Ekahau's primary and secondary coverage functionalities. Additionally, I adjust AP power levels to closely match the expected client device range to optimize coverage efficiency.&lt;/P&gt;
&lt;P&gt;Jagan Chowdam&lt;/P&gt;
&lt;P&gt;/**Pls rate useful responses**/&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 23 Feb 2024 17:16:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/surveying-for-wireless/m-p/5023581#M267216</guid>
      <dc:creator>jagan.chowdam</dc:creator>
      <dc:date>2024-02-23T17:16:59Z</dc:date>
    </item>
  </channel>
</rss>

