VisiWave Blog
https://www.visiwave.com/blog/
News and Tips About VisiWave Softwareenhttps://www.visiwave.com/blog/templates/2k11/img/s9y_banner_small.pngRSS: VisiWave Blog - News and Tips About VisiWave Software
https://www.visiwave.com/blog/
10021VisiWave Site Survey v6.0.9 Released
https://www.visiwave.com/blog/index.php?/archives/47-VisiWave-Site-Survey-v6.0.9-Released.html
A maintenance release of VisiWave (v6.0.9 ) is now available for download. If you already own v6.0 of VisiWave, just download the eval version and install it over-top of your current version. Your existing license will continue to work. If you would like to evaluate VisiWave, just download the eval version and try it out.<br />
<br />
New features in v6.0.9:<br />
<ul><br />
<li>Fixed Installer Issue<br />
<br />
The installer now includes a DLL if your computer doesn't<br />
already have it installed.<br />
<br />
</ul><br />
<br />
New features in v6.0.8:<br />
<ul><br />
<li>Satellite Positioning Now Supports Glosnass<br />
<br />
Devices that support Glosnass satellite positioning now work<br />
the same as GPS-only devices.<br />
<br />
<li>Max Data Rates Updated<br />
<br />
802.11ax max data rates were updated to use max operational<br />
data rates for an AP rather than the max data rate that the<br />
AP is capable of.<br />
<br />
<li>Added Notification About the Release of VisiWave v7.0 <br />
<br />
When you first start VisiWave, a notice pops up informing you<br />
that VisiWave v7.0 is now available and you can upgrade to it.<br />
You are given a chance to upgrade immediately within the<br />
program.<br />
</ul><br />
<br />
New features in v6.0.7:<br />
<ul><br />
<li>AP Numbers in Exported CSV and XML Files Were Off By One<br />
<br />
The numbers that are used to uniquely identify access points<br />
when exporting survey data in CSV or XML files were off by one.<br />
For example, AP #1 was listed as "0" in the exported data.<br />
<br />
<li>Improved Handling of Radios with Half Power Beamwidth Antennas<br />
<br />
For Predictive Surveys, you can select the antenna pattern used<br />
by the access point. Half Power Beamwidth antennas had issues<br />
handling vertical rotations near 90 or -90 degrees. Also, a<br />
Gain must be specified for the simulation to have any effect.<br />
<br />
<li>Improved Predictive Coverage with Non-Floor-to-Ceiling Barriers <br />
<br />
When using barriers that don't go all the way to the ceiling<br />
and using access points that are mounted high, the predictive<br />
coverage maps weren't showing sufficient signal loss near the<br />
barrier on the side opposite from the access point.<br />
</ul><br />
<br />
New features in v6.0.6:<br />
<ul><br />
<li>Long Data Collection Times<br />
<br />
A wireless adapter that suddenly took a long time to return<br />
AP scan results and then on the next scan quickly returned<br />
scan results could cause VisiWave to get out of sync. This<br />
would then make VisiWave wait about 10 seconds for all<br />
future scan results.<br />
<br />
<li>Memory Leak in Report View<br />
<br />
A memory leak was fixed in Report View. This leak could<br />
have caused stability issues after checking or unchecking<br />
many (hundred+) access points in the AP Filter for a<br />
Heatmap or coverage graph.<br />
<br />
</ul> <br />
<br />
New features in v6.0.5:<br />
<ul><br />
<li>Chanalyzer Not Showing 5GHz DATA<br />
<br />
In some circumstances, VisiWave wasn't showing the 5GHz<br />
spectrum data when you selected "View in Chanalyzer".<br />
<br />
<li>Saving PDF Report Files<br />
<br />
The last version introduced an issue with saving PDF<br />
generated reports. This was fixed with this release.<br />
<br />
</ul><br />
<br />
New features in v6.0.4:<br />
<ul><br />
<li>Performance Issue with Changing "Group By" in AP List<br />
<br />
When a large number of APs are selected in the AP List and then<br />
"Group By" is changed, it can take a long time to switch how<br />
the APs are grouped. This has been fixed.<br />
<br />
<li>Out-of-Memory Error in Large Surveys When Selecting Many Data<br />
Points<br />
<br />
For very large surveys, loading all the discovered access<br />
point readings in the Wi-Fi Details view below the map in the<br />
Survey View could cause out-of-memory errors. VisiWave now<br />
limits the number of rows that are added to this list.<br />
<br />
<li>Generating PDF Reports with Non-ASCII Characters in Filenames<br />
<br />
When generating a PDF report, if the filename you enter contains<br />
non-ASCII characters, images in the report weren't being shown.<br />
This is no longer a restriction. <br />
</ul><br />
<br />
New features in v6.0.3:<br />
<ul><br />
<li>Door & Window Issue With Predictive Surveys<br />
<br />
In some rare cases, the order that doors or windows are<br />
included was causing VisiWave to hang. The ordering is<br />
now changed automatically.<br />
<br />
<li>View in Chanalyzer Issue with Large Datasets<br />
<br />
VisiWave had an issue when using the View in Chanalyzer<br />
feature when the range included too many data points.<br />
Chanalyzer would load but no data would be included. This<br />
situation is now fixed.<br />
<br />
<li>Google Earth Report Default Extension<br />
<br />
If a file extension wasn't provided for the report file,<br />
the file was given the extension of KML. But it needed to be<br />
KMZ for the Google Earth files VisiWave creates. An extension<br />
of KML would cause the embedded images to display as large<br />
X's.<br />
<br />
<li>Google Earth AP Coverage Maps Issue<br />
<br />
If you generated an AP Coverage map for Google Earth and had<br />
both "What to Map" set to "Strongest" and "Highlight Overlaps"<br />
set to anything other than "None", then VisiWave couldn't<br />
generate the Google Earth report. Note that there are never<br />
highlighted overlaps when mapping the strongest APs so usually<br />
this wasn't an issue.<br />
</ul><br />
<br />
New features in v6.0.2:<br />
<ul><br />
<li>Set GPS Location Issue<br />
<br />
If "Get Location from GPS Device" was selected from the "Set<br />
GPS Location" menu item before any data was collected, then<br />
the program would crash.<br />
<br />
<li>Channels Under Noise Can't Be Selected When First Adding<br />
Spectrum Data<br />
<br />
In Survey View in the right pane, the 2.4GHz and 5GHz channels<br />
under "Noise" can't be selected when you collect the first set<br />
of spectrum data points. The channels remained grayed out.<br />
You had to save the survey file and re-load it before you<br />
could access the noise channels.<br />
<br />
<li>Predictive Heatmap Issue with Large Survey Areas<br />
<br />
A large survey area (50m on a side or more) could have had<br />
issues producing accurate predictions when the radio was placed<br />
near the top of barriers. The simulation had a path over the<br />
barriers which was making the signal strengths too generous.<br />
<br />
<li>Channel Maps Weren't Handling Some In-Between Channel Numbers<br />
<br />
Some channels that were "wide" (40MHz, 80MHz, or 160MHz) couldn't<br />
be selected in a Channel map. Now VisiWave handles all common<br />
channel numbers regardless of channel width.<br />
<br />
<li>Rotate Horizontal Wasn't Working for Dipole Antennas<br />
<br />
For predictive surveys with radios set to have dipole antennas,<br />
the Rotate Horizontal setting wasn't affecting the heatmap<br />
pattern. It is now functioning correctly.<br />
<br />
<li>Predictive Heatmaps Had White or Gray Regions<br />
<br />
With a few combinations of Min and Max color legend settings,<br />
some regions of the colored heatmap would show up as white or<br />
gray when they should be a dark red (when using the default<br />
color scheme).<br />
<br />
</ul><br />
<br />
New features in v6.0.1:<br />
<ul><br />
<li>Added Support for Channel Bonding in Predictive Surveys<br />
<br />
When doing a simulation, you can now set a radio's channel<br />
width in addition to just its frequency in the 5GHz band.<br />
You do this by right-clicking on a radio and selecting Edit<br />
Radio. This allows you to simulate the effects of channel<br />
bonding. For example, you can select channel 36 and say that<br />
it is a 40MHz channel to bond channels 36 and 40 together.<br />
<br />
<li>Issue Fixed with Exporting Simulation Data to CSV<br />
<br />
VisiWave was exporting only half the simulated signal values<br />
to the CSV file. Every other value in the X direction was<br />
skipped. Now all the values are exported.<br />
<br />
<li>Performance Improvements When Selecting Radios in Predictive Mode<br />
<br />
There were a few cases where updating the heatmap in Predictive<br />
mode took much longer than needed.<br />
<br />
<li>Allow Merging of Survey Files When Floor Plan Sizes are<br />
Slightly Different<br />
<br />
Due to some rounding issues, some survey files couldn't be<br />
merged even though they used the same floor plan image and<br />
scale.<br />
<br />
<li>Half Power Beamwidth Antenna Types Are More Effective<br />
<br />
For Predictive Surveys, the effect of the horizontal and<br />
vertical rotations for half power beamwidth antennas wasn't<br />
strong enough. And the rotations didn't match the<br />
documentation. These issues have been fixed.<br />
</ul><br />
<br />
<a href="http://www.visiwave.com/wifi/visiwave-v60-features.php">Original new features found in v6.0</a><br />
VisiWave Blognospam@example.com (Administrator)2023-10-05T13:31:00Zhttps://www.visiwave.com/blog/wfwcomment.php?cid=470https://www.visiwave.com/blog/rss.php?version=1.0&type=comments&cid=47VisiWave Site Survey v6.0.8 Released
https://www.visiwave.com/blog/index.php?/archives/46-VisiWave-Site-Survey-v6.0.8-Released.html
A maintenance release of VisiWave (v6.0.8 ) is now available for download. If you already own v6.0 of VisiWave, just download the eval version and install it over-top of your current version. Your existing license will continue to work. If you would like to evaluate VisiWave, just download the eval version and try it out.<br />
<br />
New features in v6.0.8:<br />
<ul><br />
<li>Satellite Positioning Now Supports Glosnass<br />
<br />
Devices that support Glosnass satellite positioning now work<br />
the same as GPS-only devices.<br />
<br />
<li>Max Data Rates Updated<br />
<br />
802.11ax max data rates were updated to use max operational<br />
data rates for an AP rather than the max data rate that the<br />
AP is capable of.<br />
<br />
<li>Added Notification About the Release of VisiWave v7.0 <br />
<br />
When you first start VisiWave, a notice pops up informing you<br />
that VisiWave v7.0 is now available and you can upgrade to it.<br />
You are given a chance to upgrade immediately within the<br />
program.<br />
</ul><br />
<br />
New features in v6.0.7:<br />
<ul><br />
<li>AP Numbers in Exported CSV and XML Files Were Off By One<br />
<br />
The numbers that are used to uniquely identify access points<br />
when exporting survey data in CSV or XML files were off by one.<br />
For example, AP #1 was listed as "0" in the exported data.<br />
<br />
<li>Improved Handling of Radios with Half Power Beamwidth Antennas<br />
<br />
For Predictive Surveys, you can select the antenna pattern used<br />
by the access point. Half Power Beamwidth antennas had issues<br />
handling vertical rotations near 90 or -90 degrees. Also, a<br />
Gain must be specified for the simulation to have any effect.<br />
<br />
<li>Improved Predictive Coverage with Non-Floor-to-Ceiling Barriers <br />
<br />
When using barriers that don't go all the way to the ceiling<br />
and using access points that are mounted high, the predictive<br />
coverage maps weren't showing sufficient signal loss near the<br />
barrier on the side opposite from the access point.<br />
</ul><br />
<br />
New features in v6.0.6:<br />
<ul><br />
<li>Long Data Collection Times<br />
<br />
A wireless adapter that suddenly took a long time to return<br />
AP scan results and then on the next scan quickly returned<br />
scan results could cause VisiWave to get out of sync. This<br />
would then make VisiWave wait about 10 seconds for all<br />
future scan results.<br />
<br />
<li>Memory Leak in Report View<br />
<br />
A memory leak was fixed in Report View. This leak could<br />
have caused stability issues after checking or unchecking<br />
many (hundred+) access points in the AP Filter for a<br />
Heatmap or coverage graph.<br />
<br />
</ul> <br />
<br />
New features in v6.0.5:<br />
<ul><br />
<li>Chanalyzer Not Showing 5GHz DATA<br />
<br />
In some circumstances, VisiWave wasn't showing the 5GHz<br />
spectrum data when you selected "View in Chanalyzer".<br />
<br />
<li>Saving PDF Report Files<br />
<br />
The last version introduced an issue with saving PDF<br />
generated reports. This was fixed with this release.<br />
<br />
</ul><br />
<br />
New features in v6.0.4:<br />
<ul><br />
<li>Performance Issue with Changing "Group By" in AP List<br />
<br />
When a large number of APs are selected in the AP List and then<br />
"Group By" is changed, it can take a long time to switch how<br />
the APs are grouped. This has been fixed.<br />
<br />
<li>Out-of-Memory Error in Large Surveys When Selecting Many Data<br />
Points<br />
<br />
For very large surveys, loading all the discovered access<br />
point readings in the Wi-Fi Details view below the map in the<br />
Survey View could cause out-of-memory errors. VisiWave now<br />
limits the number of rows that are added to this list.<br />
<br />
<li>Generating PDF Reports with Non-ASCII Characters in Filenames<br />
<br />
When generating a PDF report, if the filename you enter contains<br />
non-ASCII characters, images in the report weren't being shown.<br />
This is no longer a restriction. <br />
</ul><br />
<br />
New features in v6.0.3:<br />
<ul><br />
<li>Door & Window Issue With Predictive Surveys<br />
<br />
In some rare cases, the order that doors or windows are<br />
included was causing VisiWave to hang. The ordering is<br />
now changed automatically.<br />
<br />
<li>View in Chanalyzer Issue with Large Datasets<br />
<br />
VisiWave had an issue when using the View in Chanalyzer<br />
feature when the range included too many data points.<br />
Chanalyzer would load but no data would be included. This<br />
situation is now fixed.<br />
<br />
<li>Google Earth Report Default Extension<br />
<br />
If a file extension wasn't provided for the report file,<br />
the file was given the extension of KML. But it needed to be<br />
KMZ for the Google Earth files VisiWave creates. An extension<br />
of KML would cause the embedded images to display as large<br />
X's.<br />
<br />
<li>Google Earth AP Coverage Maps Issue<br />
<br />
If you generated an AP Coverage map for Google Earth and had<br />
both "What to Map" set to "Strongest" and "Highlight Overlaps"<br />
set to anything other than "None", then VisiWave couldn't<br />
generate the Google Earth report. Note that there are never<br />
highlighted overlaps when mapping the strongest APs so usually<br />
this wasn't an issue.<br />
</ul><br />
<br />
New features in v6.0.2:<br />
<ul><br />
<li>Set GPS Location Issue<br />
<br />
If "Get Location from GPS Device" was selected from the "Set<br />
GPS Location" menu item before any data was collected, then<br />
the program would crash.<br />
<br />
<li>Channels Under Noise Can't Be Selected When First Adding<br />
Spectrum Data<br />
<br />
In Survey View in the right pane, the 2.4GHz and 5GHz channels<br />
under "Noise" can't be selected when you collect the first set<br />
of spectrum data points. The channels remained grayed out.<br />
You had to save the survey file and re-load it before you<br />
could access the noise channels.<br />
<br />
<li>Predictive Heatmap Issue with Large Survey Areas<br />
<br />
A large survey area (50m on a side or more) could have had<br />
issues producing accurate predictions when the radio was placed<br />
near the top of barriers. The simulation had a path over the<br />
barriers which was making the signal strengths too generous.<br />
<br />
<li>Channel Maps Weren't Handling Some In-Between Channel Numbers<br />
<br />
Some channels that were "wide" (40MHz, 80MHz, or 160MHz) couldn't<br />
be selected in a Channel map. Now VisiWave handles all common<br />
channel numbers regardless of channel width.<br />
<br />
<li>Rotate Horizontal Wasn't Working for Dipole Antennas<br />
<br />
For predictive surveys with radios set to have dipole antennas,<br />
the Rotate Horizontal setting wasn't affecting the heatmap<br />
pattern. It is now functioning correctly.<br />
<br />
<li>Predictive Heatmaps Had White or Gray Regions<br />
<br />
With a few combinations of Min and Max color legend settings,<br />
some regions of the colored heatmap would show up as white or<br />
gray when they should be a dark red (when using the default<br />
color scheme).<br />
<br />
</ul><br />
<br />
New features in v6.0.1:<br />
<ul><br />
<li>Added Support for Channel Bonding in Predictive Surveys<br />
<br />
When doing a simulation, you can now set a radio's channel<br />
width in addition to just its frequency in the 5GHz band.<br />
You do this by right-clicking on a radio and selecting Edit<br />
Radio. This allows you to simulate the effects of channel<br />
bonding. For example, you can select channel 36 and say that<br />
it is a 40MHz channel to bond channels 36 and 40 together.<br />
<br />
<li>Issue Fixed with Exporting Simulation Data to CSV<br />
<br />
VisiWave was exporting only half the simulated signal values<br />
to the CSV file. Every other value in the X direction was<br />
skipped. Now all the values are exported.<br />
<br />
<li>Performance Improvements When Selecting Radios in Predictive Mode<br />
<br />
There were a few cases where updating the heatmap in Predictive<br />
mode took much longer than needed.<br />
<br />
<li>Allow Merging of Survey Files When Floor Plan Sizes are<br />
Slightly Different<br />
<br />
Due to some rounding issues, some survey files couldn't be<br />
merged even though they used the same floor plan image and<br />
scale.<br />
<br />
<li>Half Power Beamwidth Antenna Types Are More Effective<br />
<br />
For Predictive Surveys, the effect of the horizontal and<br />
vertical rotations for half power beamwidth antennas wasn't<br />
strong enough. And the rotations didn't match the<br />
documentation. These issues have been fixed.<br />
</ul><br />
<br />
<a href="http://www.visiwave.com/wifi/visiwave-v60-features.php">Original new features found in v6.0</a><br />
VisiWave Blognospam@example.com (Administrator)2023-08-10T15:31:00Zhttps://www.visiwave.com/blog/wfwcomment.php?cid=460https://www.visiwave.com/blog/rss.php?version=1.0&type=comments&cid=46VisiWave Site Survey v6.0.7 Released
https://www.visiwave.com/blog/index.php?/archives/45-VisiWave-Site-Survey-v6.0.7-Released.html
A maintenance release of VisiWave (v6.0.7 ) is now available for download. If you already own v6.0 of VisiWave, just download the eval version and install it over-top of your current version. Your existing license will continue to work. If you would like to evaluate VisiWave, just download the eval version and try it out.<br />
<br />
New features in v6.0.7:<br />
<ul><br />
<li>AP Numbers in Exported CSV and XML Files Were Off By One<br />
<br />
The numbers that are used to uniquely identify access points<br />
when exporting survey data in CSV or XML files were off by one.<br />
For example, AP #1 was listed as "0" in the exported data.<br />
<br />
<li>Improved Handling of Radios with Half Power Beamwidth Antennas<br />
<br />
For Predictive Surveys, you can select the antenna pattern used<br />
by the access point. Half Power Beamwidth antennas had issues<br />
handling vertical rotations near 90 or -90 degrees. Also, a<br />
Gain must be specified for the simulation to have any effect.<br />
<br />
<li>Improved Predictive Coverage with Non-Floor-to-Ceiling Barriers <br />
<br />
When using barriers that don't go all the way to the ceiling<br />
and using access points that are mounted high, the predictive<br />
coverage maps weren't showing sufficient signal loss near the<br />
barrier on the side opposite from the access point.<br />
</ul><br />
<br />
New features in v6.0.6:<br />
<ul><br />
<li>Long Data Collection Times<br />
<br />
A wireless adapter that suddenly took a long time to return<br />
AP scan results and then on the next scan quickly returned<br />
scan results could cause VisiWave to get out of sync. This<br />
would then make VisiWave wait about 10 seconds for all<br />
future scan results.<br />
<br />
<li>Memory Leak in Report View<br />
<br />
A memory leak was fixed in Report View. This leak could<br />
have caused stability issues after checking or unchecking<br />
many (hundred+) access points in the AP Filter for a<br />
Heatmap or coverage graph.<br />
<br />
</ul> <br />
<br />
New features in v6.0.5:<br />
<ul><br />
<li>Chanalyzer Not Showing 5GHz DATA<br />
<br />
In some circumstances, VisiWave wasn't showing the 5GHz<br />
spectrum data when you selected "View in Chanalyzer".<br />
<br />
<li>Saving PDF Report Files<br />
<br />
The last version introduced an issue with saving PDF<br />
generated reports. This was fixed with this release.<br />
<br />
</ul><br />
<br />
New features in v6.0.4:<br />
<ul><br />
<li>Performance Issue with Changing "Group By" in AP List<br />
<br />
When a large number of APs are selected in the AP List and then<br />
"Group By" is changed, it can take a long time to switch how<br />
the APs are grouped. This has been fixed.<br />
<br />
<li>Out-of-Memory Error in Large Surveys When Selecting Many Data<br />
Points<br />
<br />
For very large surveys, loading all the discovered access<br />
point readings in the Wi-Fi Details view below the map in the<br />
Survey View could cause out-of-memory errors. VisiWave now<br />
limits the number of rows that are added to this list.<br />
<br />
<li>Generating PDF Reports with Non-ASCII Characters in Filenames<br />
<br />
When generating a PDF report, if the filename you enter contains<br />
non-ASCII characters, images in the report weren't being shown.<br />
This is no longer a restriction. <br />
</ul><br />
<br />
New features in v6.0.3:<br />
<ul><br />
<li>Door & Window Issue With Predictive Surveys<br />
<br />
In some rare cases, the order that doors or windows are<br />
included was causing VisiWave to hang. The ordering is<br />
now changed automatically.<br />
<br />
<li>View in Chanalyzer Issue with Large Datasets<br />
<br />
VisiWave had an issue when using the View in Chanalyzer<br />
feature when the range included too many data points.<br />
Chanalyzer would load but no data would be included. This<br />
situation is now fixed.<br />
<br />
<li>Google Earth Report Default Extension<br />
<br />
If a file extension wasn't provided for the report file,<br />
the file was given the extension of KML. But it needed to be<br />
KMZ for the Google Earth files VisiWave creates. An extension<br />
of KML would cause the embedded images to display as large<br />
X's.<br />
<br />
<li>Google Earth AP Coverage Maps Issue<br />
<br />
If you generated an AP Coverage map for Google Earth and had<br />
both "What to Map" set to "Strongest" and "Highlight Overlaps"<br />
set to anything other than "None", then VisiWave couldn't<br />
generate the Google Earth report. Note that there are never<br />
highlighted overlaps when mapping the strongest APs so usually<br />
this wasn't an issue.<br />
</ul><br />
<br />
New features in v6.0.2:<br />
<ul><br />
<li>Set GPS Location Issue<br />
<br />
If "Get Location from GPS Device" was selected from the "Set<br />
GPS Location" menu item before any data was collected, then<br />
the program would crash.<br />
<br />
<li>Channels Under Noise Can't Be Selected When First Adding<br />
Spectrum Data<br />
<br />
In Survey View in the right pane, the 2.4GHz and 5GHz channels<br />
under "Noise" can't be selected when you collect the first set<br />
of spectrum data points. The channels remained grayed out.<br />
You had to save the survey file and re-load it before you<br />
could access the noise channels.<br />
<br />
<li>Predictive Heatmap Issue with Large Survey Areas<br />
<br />
A large survey area (50m on a side or more) could have had<br />
issues producing accurate predictions when the radio was placed<br />
near the top of barriers. The simulation had a path over the<br />
barriers which was making the signal strengths too generous.<br />
<br />
<li>Channel Maps Weren't Handling Some In-Between Channel Numbers<br />
<br />
Some channels that were "wide" (40MHz, 80MHz, or 160MHz) couldn't<br />
be selected in a Channel map. Now VisiWave handles all common<br />
channel numbers regardless of channel width.<br />
<br />
<li>Rotate Horizontal Wasn't Working for Dipole Antennas<br />
<br />
For predictive surveys with radios set to have dipole antennas,<br />
the Rotate Horizontal setting wasn't affecting the heatmap<br />
pattern. It is now functioning correctly.<br />
<br />
<li>Predictive Heatmaps Had White or Gray Regions<br />
<br />
With a few combinations of Min and Max color legend settings,<br />
some regions of the colored heatmap would show up as white or<br />
gray when they should be a dark red (when using the default<br />
color scheme).<br />
<br />
</ul><br />
<br />
New features in v6.0.1:<br />
<ul><br />
<li>Added Support for Channel Bonding in Predictive Surveys<br />
<br />
When doing a simulation, you can now set a radio's channel<br />
width in addition to just its frequency in the 5GHz band.<br />
You do this by right-clicking on a radio and selecting Edit<br />
Radio. This allows you to simulate the effects of channel<br />
bonding. For example, you can select channel 36 and say that<br />
it is a 40MHz channel to bond channels 36 and 40 together.<br />
<br />
<li>Issue Fixed with Exporting Simulation Data to CSV<br />
<br />
VisiWave was exporting only half the simulated signal values<br />
to the CSV file. Every other value in the X direction was<br />
skipped. Now all the values are exported.<br />
<br />
<li>Performance Improvements When Selecting Radios in Predictive Mode<br />
<br />
There were a few cases where updating the heatmap in Predictive<br />
mode took much longer than needed.<br />
<br />
<li>Allow Merging of Survey Files When Floor Plan Sizes are<br />
Slightly Different<br />
<br />
Due to some rounding issues, some survey files couldn't be<br />
merged even though they used the same floor plan image and<br />
scale.<br />
<br />
<li>Half Power Beamwidth Antenna Types Are More Effective<br />
<br />
For Predictive Surveys, the effect of the horizontal and<br />
vertical rotations for half power beamwidth antennas wasn't<br />
strong enough. And the rotations didn't match the<br />
documentation. These issues have been fixed.<br />
</ul><br />
<br />
<a href="http://www.visiwave.com/wifi/visiwave-v60-features.php">Original new features found in v6.0</a><br />
VisiWave Blognospam@example.com (Administrator)2022-11-14T21:21:00Zhttps://www.visiwave.com/blog/wfwcomment.php?cid=450https://www.visiwave.com/blog/rss.php?version=1.0&type=comments&cid=45VisiWave Site Survey v6.0.6 Released
https://www.visiwave.com/blog/index.php?/archives/44-VisiWave-Site-Survey-v6.0.6-Released.html
A maintenance release of VisiWave (v6.0.6 ) is now available for download. If you already own v6.0 of VisiWave, just download the eval version and install it over-top of your current version. Your existing license will continue to work. If you would like to evaluate VisiWave, just download the eval version and try it out.<br />
<br />
New features in v6.0.6:<br />
<ul><br />
<li>Long Data Collection Times<br />
<br />
A wireless adapter that suddenly took a long time to return<br />
AP scan results and then on the next scan quickly returned<br />
scan results could cause VisiWave to get out of sync. This<br />
would then make VisiWave wait about 10 seconds for all<br />
future scan results.<br />
<br />
<li>Memory Leak in Report View<br />
<br />
A memory leak was fixed in Report View. This leak could<br />
have caused stability issues after checking or unchecking<br />
many (hundred+) access points in the AP Filter for a<br />
Heatmap or coverage graph.<br />
<br />
</ul> <br />
<br />
New features in v6.0.5:<br />
<ul><br />
<li>Chanalyzer Not Showing 5GHz DATA<br />
<br />
In some circumstances, VisiWave wasn't showing the 5GHz<br />
spectrum data when you selected "View in Chanalyzer".<br />
<br />
<li>Saving PDF Report Files<br />
<br />
The last version introduced an issue with saving PDF<br />
generated reports. This was fixed with this release.<br />
<br />
</ul><br />
<br />
New features in v6.0.4:<br />
<ul><br />
<li>Performance Issue with Changing "Group By" in AP List<br />
<br />
When a large number of APs are selected in the AP List and then<br />
"Group By" is changed, it can take a long time to switch how<br />
the APs are grouped. This has been fixed.<br />
<br />
<li>Out-of-Memory Error in Large Surveys When Selecting Many Data<br />
Points<br />
<br />
For very large surveys, loading all the discovered access<br />
point readings in the Wi-Fi Details view below the map in the<br />
Survey View could cause out-of-memory errors. VisiWave now<br />
limits the number of rows that are added to this list.<br />
<br />
<li>Generating PDF Reports with Non-ASCII Characters in Filenames<br />
<br />
When generating a PDF report, if the filename you enter contains<br />
non-ASCII characters, images in the report weren't being shown.<br />
This is no longer a restriction. <br />
</ul><br />
<br />
New features in v6.0.3:<br />
<ul><br />
<li>Door & Window Issue With Predictive Surveys<br />
<br />
In some rare cases, the order that doors or windows are<br />
included was causing VisiWave to hang. The ordering is<br />
now changed automatically.<br />
<br />
<li>View in Chanalyzer Issue with Large Datasets<br />
<br />
VisiWave had an issue when using the View in Chanalyzer<br />
feature when the range included too many data points.<br />
Chanalyzer would load but no data would be included. This<br />
situation is now fixed.<br />
<br />
<li>Google Earth Report Default Extension<br />
<br />
If a file extension wasn't provided for the report file,<br />
the file was given the extension of KML. But it needed to be<br />
KMZ for the Google Earth files VisiWave creates. An extension<br />
of KML would cause the embedded images to display as large<br />
X's.<br />
<br />
<li>Google Earth AP Coverage Maps Issue<br />
<br />
If you generated an AP Coverage map for Google Earth and had<br />
both "What to Map" set to "Strongest" and "Highlight Overlaps"<br />
set to anything other than "None", then VisiWave couldn't<br />
generate the Google Earth report. Note that there are never<br />
highlighted overlaps when mapping the strongest APs so usually<br />
this wasn't an issue.<br />
</ul><br />
<br />
New features in v6.0.2:<br />
<ul><br />
<li>Set GPS Location Issue<br />
<br />
If "Get Location from GPS Device" was selected from the "Set<br />
GPS Location" menu item before any data was collected, then<br />
the program would crash.<br />
<br />
<li>Channels Under Noise Can't Be Selected When First Adding<br />
Spectrum Data<br />
<br />
In Survey View in the right pane, the 2.4GHz and 5GHz channels<br />
under "Noise" can't be selected when you collect the first set<br />
of spectrum data points. The channels remained grayed out.<br />
You had to save the survey file and re-load it before you<br />
could access the noise channels.<br />
<br />
<li>Predictive Heatmap Issue with Large Survey Areas<br />
<br />
A large survey area (50m on a side or more) could have had<br />
issues producing accurate predictions when the radio was placed<br />
near the top of barriers. The simulation had a path over the<br />
barriers which was making the signal strengths too generous.<br />
<br />
<li>Channel Maps Weren't Handling Some In-Between Channel Numbers<br />
<br />
Some channels that were "wide" (40MHz, 80MHz, or 160MHz) couldn't<br />
be selected in a Channel map. Now VisiWave handles all common<br />
channel numbers regardless of channel width.<br />
<br />
<li>Rotate Horizontal Wasn't Working for Dipole Antennas<br />
<br />
For predictive surveys with radios set to have dipole antennas,<br />
the Rotate Horizontal setting wasn't affecting the heatmap<br />
pattern. It is now functioning correctly.<br />
<br />
<li>Predictive Heatmaps Had White or Gray Regions<br />
<br />
With a few combinations of Min and Max color legend settings,<br />
some regions of the colored heatmap would show up as white or<br />
gray when they should be a dark red (when using the default<br />
color scheme).<br />
<br />
</ul><br />
<br />
New features in v6.0.1:<br />
<ul><br />
<li>Added Support for Channel Bonding in Predictive Surveys<br />
<br />
When doing a simulation, you can now set a radio's channel<br />
width in addition to just its frequency in the 5GHz band.<br />
You do this by right-clicking on a radio and selecting Edit<br />
Radio. This allows you to simulate the effects of channel<br />
bonding. For example, you can select channel 36 and say that<br />
it is a 40MHz channel to bond channels 36 and 40 together.<br />
<br />
<li>Issue Fixed with Exporting Simulation Data to CSV<br />
<br />
VisiWave was exporting only half the simulated signal values<br />
to the CSV file. Every other value in the X direction was<br />
skipped. Now all the values are exported.<br />
<br />
<li>Performance Improvements When Selecting Radios in Predictive Mode<br />
<br />
There were a few cases where updating the heatmap in Predictive<br />
mode took much longer than needed.<br />
<br />
<li>Allow Merging of Survey Files When Floor Plan Sizes are<br />
Slightly Different<br />
<br />
Due to some rounding issues, some survey files couldn't be<br />
merged even though they used the same floor plan image and<br />
scale.<br />
<br />
<li>Half Power Beamwidth Antenna Types Are More Effective<br />
<br />
For Predictive Surveys, the effect of the horizontal and<br />
vertical rotations for half power beamwidth antennas wasn't<br />
strong enough. And the rotations didn't match the<br />
documentation. These issues have been fixed.<br />
</ul><br />
<br />
<a href="http://www.visiwave.com/wifi/visiwave-v60-features.php">Original new features found in v6.0</a><br />
VisiWave Blognospam@example.com (Administrator)2022-06-22T15:57:00Zhttps://www.visiwave.com/blog/wfwcomment.php?cid=440https://www.visiwave.com/blog/rss.php?version=1.0&type=comments&cid=44VisiWave Site Survey v6.0.5 Released
https://www.visiwave.com/blog/index.php?/archives/43-VisiWave-Site-Survey-v6.0.5-Released.html
A maintenance release of VisiWave (v6.0.5 ) is now available for download. If you already own v6.0 of VisiWave, just download the eval version and install it over-top of your current version. Your existing license will continue to work. If you would like to evaluate VisiWave, just download the eval version and try it out.<br />
<br />
New features in v6.0.5:<br />
<ul><br />
<li>Chanalyzer Not Showing 5GHz DATA<br />
<br />
In some circumstances, VisiWave wasn't showing the 5GHz<br />
spectrum data when you selected "View in Chanalyzer".<br />
<br />
<li>Saving PDF Report Files<br />
<br />
The last version introduced an issue with saving PDF<br />
generated reports. This was fixed with this release.<br />
<br />
</ul><br />
<br />
New features in v6.0.4:<br />
<ul><br />
<li>Performance Issue with Changing "Group By" in AP List<br />
<br />
When a large number of APs are selected in the AP List and then<br />
"Group By" is changed, it can take a long time to switch how<br />
the APs are grouped. This has been fixed.<br />
<br />
<li>Out-of-Memory Error in Large Surveys When Selecting Many Data<br />
Points<br />
<br />
For very large surveys, loading all the discovered access<br />
point readings in the Wi-Fi Details view below the map in the<br />
Survey View could cause out-of-memory errors. VisiWave now<br />
limits the number of rows that are added to this list.<br />
<br />
<li>Generating PDF Reports with Non-ASCII Characters in Filenames<br />
<br />
When generating a PDF report, if the filename you enter contains<br />
non-ASCII characters, images in the report weren't being shown.<br />
This is no longer a restriction. <br />
</ul><br />
<br />
New features in v6.0.3:<br />
<ul><br />
<li>Door & Window Issue With Predictive Surveys<br />
<br />
In some rare cases, the order that doors or windows are<br />
included was causing VisiWave to hang. The ordering is<br />
now changed automatically.<br />
<br />
<li>View in Chanalyzer Issue with Large Datasets<br />
<br />
VisiWave had an issue when using the View in Chanalyzer<br />
feature when the range included too many data points.<br />
Chanalyzer would load but no data would be included. This<br />
situation is now fixed.<br />
<br />
<li>Google Earth Report Default Extension<br />
<br />
If a file extension wasn't provided for the report file,<br />
the file was given the extension of KML. But it needed to be<br />
KMZ for the Google Earth files VisiWave creates. An extension<br />
of KML would cause the embedded images to display as large<br />
X's.<br />
<br />
<li>Google Earth AP Coverage Maps Issue<br />
<br />
If you generated an AP Coverage map for Google Earth and had<br />
both "What to Map" set to "Strongest" and "Highlight Overlaps"<br />
set to anything other than "None", then VisiWave couldn't<br />
generate the Google Earth report. Note that there are never<br />
highlighted overlaps when mapping the strongest APs so usually<br />
this wasn't an issue.<br />
</ul><br />
<br />
New features in v6.0.2:<br />
<ul><br />
<li>Set GPS Location Issue<br />
<br />
If "Get Location from GPS Device" was selected from the "Set<br />
GPS Location" menu item before any data was collected, then<br />
the program would crash.<br />
<br />
<li>Channels Under Noise Can't Be Selected When First Adding<br />
Spectrum Data<br />
<br />
In Survey View in the right pane, the 2.4GHz and 5GHz channels<br />
under "Noise" can't be selected when you collect the first set<br />
of spectrum data points. The channels remained grayed out.<br />
You had to save the survey file and re-load it before you<br />
could access the noise channels.<br />
<br />
<li>Predictive Heatmap Issue with Large Survey Areas<br />
<br />
A large survey area (50m on a side or more) could have had<br />
issues producing accurate predictions when the radio was placed<br />
near the top of barriers. The simulation had a path over the<br />
barriers which was making the signal strengths too generous.<br />
<br />
<li>Channel Maps Weren't Handling Some In-Between Channel Numbers<br />
<br />
Some channels that were "wide" (40MHz, 80MHz, or 160MHz) couldn't<br />
be selected in a Channel map. Now VisiWave handles all common<br />
channel numbers regardless of channel width.<br />
<br />
<li>Rotate Horizontal Wasn't Working for Dipole Antennas<br />
<br />
For predictive surveys with radios set to have dipole antennas,<br />
the Rotate Horizontal setting wasn't affecting the heatmap<br />
pattern. It is now functioning correctly.<br />
<br />
<li>Predictive Heatmaps Had White or Gray Regions<br />
<br />
With a few combinations of Min and Max color legend settings,<br />
some regions of the colored heatmap would show up as white or<br />
gray when they should be a dark red (when using the default<br />
color scheme).<br />
<br />
</ul><br />
<br />
New features in v6.0.1:<br />
<ul><br />
<li>Added Support for Channel Bonding in Predictive Surveys<br />
<br />
When doing a simulation, you can now set a radio's channel<br />
width in addition to just its frequency in the 5GHz band.<br />
You do this by right-clicking on a radio and selecting Edit<br />
Radio. This allows you to simulate the effects of channel<br />
bonding. For example, you can select channel 36 and say that<br />
it is a 40MHz channel to bond channels 36 and 40 together.<br />
<br />
<li>Issue Fixed with Exporting Simulation Data to CSV<br />
<br />
VisiWave was exporting only half the simulated signal values<br />
to the CSV file. Every other value in the X direction was<br />
skipped. Now all the values are exported.<br />
<br />
<li>Performance Improvements When Selecting Radios in Predictive Mode<br />
<br />
There were a few cases where updating the heatmap in Predictive<br />
mode took much longer than needed.<br />
<br />
<li>Allow Merging of Survey Files When Floor Plan Sizes are<br />
Slightly Different<br />
<br />
Due to some rounding issues, some survey files couldn't be<br />
merged even though they used the same floor plan image and<br />
scale.<br />
<br />
<li>Half Power Beamwidth Antenna Types Are More Effective<br />
<br />
For Predictive Surveys, the effect of the horizontal and<br />
vertical rotations for half power beamwidth antennas wasn't<br />
strong enough. And the rotations didn't match the<br />
documentation. These issues have been fixed.<br />
</ul><br />
<br />
<a href="http://www.visiwave.com/wifi/visiwave-v60-features.php">Original new features found in v6.0</a><br />
VisiWave Blognospam@example.com (Administrator)2022-02-25T16:19:00Zhttps://www.visiwave.com/blog/wfwcomment.php?cid=430https://www.visiwave.com/blog/rss.php?version=1.0&type=comments&cid=43VisiWave Site Survey v6.0.4 Released
https://www.visiwave.com/blog/index.php?/archives/42-VisiWave-Site-Survey-v6.0.4-Released.html
A maintenance release of VisiWave (v6.0.4 ) is now available for download. If you already own v6.0 of VisiWave, just download the eval version and install it over-top of your current version. Your existing license will continue to work. If you would like to evaluate VisiWave, just download the eval version and try it out.<br />
<br />
New features in v6.0.4:<br />
<ul><br />
<li>Performance Issue with Changing "Group By" in AP List<br />
<br />
When a large number of APs are selected in the AP List and then<br />
"Group By" is changed, it can take a long time to switch how<br />
the APs are grouped. This has been fixed.<br />
<br />
<li>Out-of-Memory Error in Large Surveys When Selecting Many Data<br />
Points<br />
<br />
For very large surveys, loading all the discovered access<br />
point readings in the Wi-Fi Details view below the map in the<br />
Survey View could cause out-of-memory errors. VisiWave now<br />
limits the number of rows that are added to this list.<br />
<br />
<li>Generating PDF Reports with Non-ASCII Characters in Filenames<br />
<br />
When generating a PDF report, if the filename you enter contains<br />
non-ASCII characters, images in the report weren't being shown.<br />
This is no longer a restriction. <br />
</ul><br />
<br />
New features in v6.0.3:<br />
<ul><br />
<li>Door & Window Issue With Predictive Surveys<br />
<br />
In some rare cases, the order that doors or windows are<br />
included was causing VisiWave to hang. The ordering is<br />
now changed automatically.<br />
<br />
<li>View in Chanalyzer Issue with Large Datasets<br />
<br />
VisiWave had an issue when using the View in Chanalyzer<br />
feature when the range included too many data points.<br />
Chanalyzer would load but no data would be included. This<br />
situation is now fixed.<br />
<br />
<li>Google Earth Report Default Extension<br />
<br />
If a file extension wasn't provided for the report file,<br />
the file was given the extension of KML. But it needed to be<br />
KMZ for the Google Earth files VisiWave creates. An extension<br />
of KML would cause the embedded images to display as large<br />
X's.<br />
<br />
<li>Google Earth AP Coverage Maps Issue<br />
<br />
If you generated an AP Coverage map for Google Earth and had<br />
both "What to Map" set to "Strongest" and "Highlight Overlaps"<br />
set to anything other than "None", then VisiWave couldn't<br />
generate the Google Earth report. Note that there are never<br />
highlighted overlaps when mapping the strongest APs so usually<br />
this wasn't an issue.<br />
</ul><br />
<br />
New features in v6.0.2:<br />
<ul><br />
<li>Set GPS Location Issue<br />
<br />
If "Get Location from GPS Device" was selected from the "Set<br />
GPS Location" menu item before any data was collected, then<br />
the program would crash.<br />
<br />
<li>Channels Under Noise Can't Be Selected When First Adding<br />
Spectrum Data<br />
<br />
In Survey View in the right pane, the 2.4GHz and 5GHz channels<br />
under "Noise" can't be selected when you collect the first set<br />
of spectrum data points. The channels remained grayed out.<br />
You had to save the survey file and re-load it before you<br />
could access the noise channels.<br />
<br />
<li>Predictive Heatmap Issue with Large Survey Areas<br />
<br />
A large survey area (50m on a side or more) could have had<br />
issues producing accurate predictions when the radio was placed<br />
near the top of barriers. The simulation had a path over the<br />
barriers which was making the signal strengths too generous.<br />
<br />
<li>Channel Maps Weren't Handling Some In-Between Channel Numbers<br />
<br />
Some channels that were "wide" (40MHz, 80MHz, or 160MHz) couldn't<br />
be selected in a Channel map. Now VisiWave handles all common<br />
channel numbers regardless of channel width.<br />
<br />
<li>Rotate Horizontal Wasn't Working for Dipole Antennas<br />
<br />
For predictive surveys with radios set to have dipole antennas,<br />
the Rotate Horizontal setting wasn't affecting the heatmap<br />
pattern. It is now functioning correctly.<br />
<br />
<li>Predictive Heatmaps Had White or Gray Regions<br />
<br />
With a few combinations of Min and Max color legend settings,<br />
some regions of the colored heatmap would show up as white or<br />
gray when they should be a dark red (when using the default<br />
color scheme).<br />
<br />
</ul><br />
<br />
New features in v6.0.1:<br />
<ul><br />
<li>Added Support for Channel Bonding in Predictive Surveys<br />
<br />
When doing a simulation, you can now set a radio's channel<br />
width in addition to just its frequency in the 5GHz band.<br />
You do this by right-clicking on a radio and selecting Edit<br />
Radio. This allows you to simulate the effects of channel<br />
bonding. For example, you can select channel 36 and say that<br />
it is a 40MHz channel to bond channels 36 and 40 together.<br />
<br />
<li>Issue Fixed with Exporting Simulation Data to CSV<br />
<br />
VisiWave was exporting only half the simulated signal values<br />
to the CSV file. Every other value in the X direction was<br />
skipped. Now all the values are exported.<br />
<br />
<li>Performance Improvements When Selecting Radios in Predictive Mode<br />
<br />
There were a few cases where updating the heatmap in Predictive<br />
mode took much longer than needed.<br />
<br />
<li>Allow Merging of Survey Files When Floor Plan Sizes are<br />
Slightly Different<br />
<br />
Due to some rounding issues, some survey files couldn't be<br />
merged even though they used the same floor plan image and<br />
scale.<br />
<br />
<li>Half Power Beamwidth Antenna Types Are More Effective<br />
<br />
For Predictive Surveys, the effect of the horizontal and<br />
vertical rotations for half power beamwidth antennas wasn't<br />
strong enough. And the rotations didn't match the<br />
documentation. These issues have been fixed.<br />
</ul><br />
<br />
<a href="http://www.visiwave.com/wifi/visiwave-v60-features.php">Original new features found in v6.0</a><br />
VisiWave Blognospam@example.com (Administrator)2022-02-08T16:02:00Zhttps://www.visiwave.com/blog/wfwcomment.php?cid=420https://www.visiwave.com/blog/rss.php?version=1.0&type=comments&cid=42VisiWave Site Survey v6.0.3 Released
https://www.visiwave.com/blog/index.php?/archives/41-VisiWave-Site-Survey-v6.0.3-Released.html
A maintenance release of VisiWave (v6.0.3 ) is now available for download. If you already own v6.0 of VisiWave, just download the eval version and install it over-top of your current version. Your existing license will continue to work. If you would like to evaluate VisiWave, just download the eval version and try it out.<br />
<br />
New features in v6.0.3:<br />
<ul><br />
<li>Door & Window Issue With Predictive Surveys<br />
<br />
In some rare cases, the order that doors or windows are<br />
included was causing VisiWave to hang. The ordering is<br />
now changed automatically.<br />
<br />
<li>View in Chanalyzer Issue with Large Datasets<br />
<br />
VisiWave had an issue when using the View in Chanalyzer<br />
feature when the range included too many data points.<br />
Chanalyzer would load but no data would be included. This<br />
situation is now fixed.<br />
<br />
<li>Google Earth Report Default Extension<br />
<br />
If a file extension wasn't provided for the report file,<br />
the file was given the extension of KML. But it needed to be<br />
KMZ for the Google Earth files VisiWave creates. An extension<br />
of KML would cause the embedded images to display as large<br />
X's.<br />
<br />
<li>Google Earth AP Coverage Maps Issue<br />
<br />
If you generated an AP Coverage map for Google Earth and had<br />
both "What to Map" set to "Strongest" and "Highlight Overlaps"<br />
set to anything other than "None", then VisiWave couldn't<br />
generate the Google Earth report. Note that there are never<br />
highlighted overlaps when mapping the strongest APs so usually<br />
this wasn't an issue.<br />
</ul><br />
<br />
New features in v6.0.2:<br />
<ul><br />
<li>Set GPS Location Issue<br />
<br />
If "Get Location from GPS Device" was selected from the "Set<br />
GPS Location" menu item before any data was collected, then<br />
the program would crash.<br />
<br />
<li>Channels Under Noise Can't Be Selected When First Adding<br />
Spectrum Data<br />
<br />
In Survey View in the right pane, the 2.4GHz and 5GHz channels<br />
under "Noise" can't be selected when you collect the first set<br />
of spectrum data points. The channels remained grayed out.<br />
You had to save the survey file and re-load it before you<br />
could access the noise channels.<br />
<br />
<li>Predictive Heatmap Issue with Large Survey Areas<br />
<br />
A large survey area (50m on a side or more) could have had<br />
issues producing accurate predictions when the radio was placed<br />
near the top of barriers. The simulation had a path over the<br />
barriers which was making the signal strengths too generous.<br />
<br />
<li>Channel Maps Weren't Handling Some In-Between Channel Numbers<br />
<br />
Some channels that were "wide" (40MHz, 80MHz, or 160MHz) couldn't<br />
be selected in a Channel map. Now VisiWave handles all common<br />
channel numbers regardless of channel width.<br />
<br />
<li>Rotate Horizontal Wasn't Working for Dipole Antennas<br />
<br />
For predictive surveys with radios set to have dipole antennas,<br />
the Rotate Horizontal setting wasn't affecting the heatmap<br />
pattern. It is now functioning correctly.<br />
<br />
<li>Predictive Heatmaps Had White or Gray Regions<br />
<br />
With a few combinations of Min and Max color legend settings,<br />
some regions of the colored heatmap would show up as white or<br />
gray when they should be a dark red (when using the default<br />
color scheme).<br />
<br />
</ul><br />
<br />
New features in v6.0.1:<br />
<ul><br />
<li>Added Support for Channel Bonding in Predictive Surveys<br />
<br />
When doing a simulation, you can now set a radio's channel<br />
width in addition to just its frequency in the 5GHz band.<br />
You do this by right-clicking on a radio and selecting Edit<br />
Radio. This allows you to simulate the effects of channel<br />
bonding. For example, you can select channel 36 and say that<br />
it is a 40MHz channel to bond channels 36 and 40 together.<br />
<br />
<li>Issue Fixed with Exporting Simulation Data to CSV<br />
<br />
VisiWave was exporting only half the simulated signal values<br />
to the CSV file. Every other value in the X direction was<br />
skipped. Now all the values are exported.<br />
<br />
<li>Performance Improvements When Selecting Radios in Predictive Mode<br />
<br />
There were a few cases where updating the heatmap in Predictive<br />
mode took much longer than needed.<br />
<br />
<li>Allow Merging of Survey Files When Floor Plan Sizes are<br />
Slightly Different<br />
<br />
Due to some rounding issues, some survey files couldn't be<br />
merged even though they used the same floor plan image and<br />
scale.<br />
<br />
<li>Half Power Beamwidth Antenna Types Are More Effective<br />
<br />
For Predictive Surveys, the effect of the horizontal and<br />
vertical rotations for half power beamwidth antennas wasn't<br />
strong enough. And the rotations didn't match the<br />
documentation. These issues have been fixed.<br />
</ul><br />
<br />
<a href="http://www.visiwave.com/wifi/visiwave-v60-features.php">Original new features found in v6.0</a><br />
VisiWave Blognospam@example.com (Administrator)2021-07-29T19:42:00Zhttps://www.visiwave.com/blog/wfwcomment.php?cid=410https://www.visiwave.com/blog/rss.php?version=1.0&type=comments&cid=41VisiWave Site Survey v6.0.2 Released
https://www.visiwave.com/blog/index.php?/archives/40-VisiWave-Site-Survey-v6.0.2-Released.html
A maintenance release of VisiWave (v6.0.2 ) is now available for download. If you already own v6.0 of VisiWave, just download the eval version and install it over-top of your current version. Your existing license will continue to work. If you would like to evaluate VisiWave, just download the eval version and try it out.<br />
<br />
New features in v6.0.2:<br />
<ul><br />
<li>Set GPS Location Issue<br />
<br />
If "Get Location from GPS Device" was selected from the "Set<br />
GPS Location" menu item before any data was collected, then<br />
the program would crash.<br />
<br />
<li>Channels Under Noise Can't Be Selected When First Adding<br />
Spectrum Data<br />
<br />
In Survey View in the right pane, the 2.4GHz and 5GHz channels<br />
under "Noise" can't be selected when you collect the first set<br />
of spectrum data points. The channels remained grayed out.<br />
You had to save the survey file and re-load it before you<br />
could access the noise channels.<br />
<br />
<li>Predictive Heatmap Issue with Large Survey Areas<br />
<br />
A large survey area (50m on a side or more) could have had<br />
issues producing accurate predictions when the radio was placed<br />
near the top of barriers. The simulation had a path over the<br />
barriers which was making the signal strengths too generous.<br />
<br />
<li>Channel Maps Weren't Handling Some In-Between Channel Numbers<br />
<br />
Some channels that were "wide" (40MHz, 80MHz, or 160MHz) couldn't<br />
be selected in a Channel map. Now VisiWave handles all common<br />
channel numbers regardless of channel width.<br />
<br />
<li>Rotate Horizontal Wasn't Working for Dipole Antennas<br />
<br />
For predictive surveys with radios set to have dipole antennas,<br />
the Rotate Horizontal setting wasn't affecting the heatmap<br />
pattern. It is now functioning correctly.<br />
<br />
<li>Predictive Heatmaps Had White or Gray Regions<br />
<br />
With a few combinations of Min and Max color legend settings,<br />
some regions of the colored heatmap would show up as white or<br />
gray when they should be a dark red (when using the default<br />
color scheme).<br />
<br />
</ul><br />
<br />
New features in v6.0.1:<br />
<ul><br />
<li>Added Support for Channel Bonding in Predictive Surveys<br />
<br />
When doing a simulation, you can now set a radio's channel<br />
width in addition to just its frequency in the 5GHz band.<br />
You do this by right-clicking on a radio and selecting Edit<br />
Radio. This allows you to simulate the effects of channel<br />
bonding. For example, you can select channel 36 and say that<br />
it is a 40MHz channel to bond channels 36 and 40 together.<br />
<br />
<li>Issue Fixed with Exporting Simulation Data to CSV<br />
<br />
VisiWave was exporting only half the simulated signal values<br />
to the CSV file. Every other value in the X direction was<br />
skipped. Now all the values are exported.<br />
<br />
<li>Performance Improvements When Selecting Radios in Predictive Mode<br />
<br />
There were a few cases where updating the heatmap in Predictive<br />
mode took much longer than needed.<br />
<br />
<li>Allow Merging of Survey Files When Floor Plan Sizes are<br />
Slightly Different<br />
<br />
Due to some rounding issues, some survey files couldn't be<br />
merged even though they used the same floor plan image and<br />
scale.<br />
<br />
<li>Half Power Beamwidth Antenna Types Are More Effective<br />
<br />
For Predictive Surveys, the effect of the horizontal and<br />
vertical rotations for half power beamwidth antennas wasn't<br />
strong enough. And the rotations didn't match the<br />
documentation. These issues have been fixed.<br />
</ul><br />
<br />
<a href="http://www.visiwave.com/wifi/visiwave-v60-features.php">Original new features found in v6.0</a><br />
VisiWave Blognospam@example.com (Administrator)2021-02-17T18:38:00Zhttps://www.visiwave.com/blog/wfwcomment.php?cid=400https://www.visiwave.com/blog/rss.php?version=1.0&type=comments&cid=40VisiWave Site Survey v5.0.13 Released
https://www.visiwave.com/blog/index.php?/archives/39-VisiWave-Site-Survey-v5.0.13-Released.html
A maintenance release of VisiWave (v5.0.13 ) is now available for download. If you already own v5.0 of VisiWave, just download the eval version and install it over-top of your current version. Your existing license will continue to work. If you would like to evaluate VisiWave, just download the eval version and try it out.<br />
<br />
New features in v5.0.13:<br />
<ul><br />
<li>Survey Notes Not Saved<br />
<br />
Survey notes entered on the Notes tab on the Survey<br />
Properties window were not being saved in the survey file.<br />
They would show up in the report when initially entered,<br />
but not after the survey had been saved and re-loaded.<br />
<br />
<li>Incorrect Horizontal Surface Material for Predictive Heatmaps<br />
<br />
When creating a barrier that has a horizontal surface (such<br />
as a table, desk, or cabinet) the vertical material was used<br />
instead of using the horizontal material.<br />
<br />
<li>Issue Fixed with Exporting Simulation Data to CSV<br />
<br />
VisiWave was exporting only half the simulated signal values<br />
to the CSV file. Every other value in the X direction was<br />
skipped. Now all the values are exported.<br />
<br />
<li>Performance Improvements When Selecting Radios in Prdictive Mode<br />
<br />
There were a few cases where updating the heatmap in Predictive<br />
mode took much longer than needed.<br />
<br />
<li>Allow Merging of Survey Files When Floor Plan Sizes are<br />
Slightly Different<br />
<br />
Due to some rounding issues, some survey files couldn't be<br />
merged even though they used the same floor plan image and<br />
scale.<br />
</ul><br />
<br />
New features in v5.0.12:<br />
<ul><br />
<li>Clear Data Points Issue Fixed<br />
<br />
The previous version introduced a bug when either Data<br />
Points or All was selected from the Survey->Clear menu and<br />
then new data points were added. This has now been fixed.<br />
<br />
<li>Invalid Automatically Detected AP Names Made Survey Files Unloadable<br />
<br />
If the AP name provided by a Cisco compatible controller<br />
contained invalid data, when that garbage AP name was written<br />
to the survey file, it could cause the survey file to not<br />
properly load in the future. Now these invalid AP names are<br />
skipped so they are not written to the survey file.<br />
</ul><br />
<br />
New features in v5.0.11:<br />
<ul><br />
<li>Inferred AP Readings [New Feature]<br />
<br />
When a wireless adapter performs a scan for all APs in the<br />
area, it tries to hear them all but some are missed due to<br />
interference, timing, or many other issues. VisiWave now has<br />
the ability to examine surrounding data points to try to<br />
detect AP readings that were missed. These are called<br />
"Inferred AP Readings". When VisiWave believes an AP reading<br />
was missed, it adds an inferred AP reading to that data point<br />
and estimates what the signal strength would be for that AP.<br />
In heatmaps, a data point with a green outside ring<br />
indicates an inferred AP reading. Also, in the Wi-Fi Details<br />
table, the AP Name or MAC address is colored green for<br />
inferred AP readings and the tooltip label has "<Inferred>"<br />
added to the end.<br />
<br />
If you are seeing many of these inferred AP readings, then you<br />
might consider trying a different wireless adapter or updating<br />
your wireless adapter's drivers to the latest version released<br />
by the manufacturer.<br />
<br />
<li>In Predictive Mode, APs Appear Too Large in Large Survey Areas<br />
<br />
When doing a predictive survey over a large survey area, the<br />
access points added to the scene could become too big. They<br />
are now a more reasonable sized in large survey areas.<br />
<br />
<li>Merging Predictive Survey Files Caused a Crash<br />
<br />
The Merge Survey Files feature wasn't working when trying to<br />
merge a survey file with predictive data. This has now been<br />
fixed. Note the resulting merged survey file will have an<br />
identical copy of the Main Survey File's predictive data. The<br />
barriers, APs, etc. from the other merged survey files will<br />
not be included in the merged survey file.<br />
<br />
<li>Predictive Heatmaps Were Shifted Right and Down in Large Areas<br />
<br />
When doing a predictive survey over a large area, the heatmap<br />
was shifted to the right and down.<br />
<br />
<li>Linked AP Markers Were Not Included During a Survey File Merge<br />
<br />
When merging survey files using the Merge Survey Files<br />
feature, some AP Markers from the survey files being merged<br />
were not copied over. The AP Markers that were linked to an<br />
AP (colored red) were not included. All the AP Markers from<br />
the main survey file and all the unlinked AP Markers were<br />
correctly included.<br />
<br />
<li>Wireless Adapter Names Could Have Been Wrong After a Merge<br />
<br />
If the merged survey files used different wireless adapters<br />
to collect survey data, the wireless adapter name listed<br />
under the Wi-Fi details for each data point could have<br />
been wrong.<br />
<br />
<li>Predictive Surveys: Only First AP in Configuration was Loaded<br />
<br />
When creating a Predictive Survey, you can create many radios,<br />
access points, and configurations. However, when loading a<br />
survey file with more than one AP under a configuration, only<br />
the first one was successfully loaded. The others were<br />
silently skipped.<br />
</ul><br />
<br />
New features in v5.0.10:<br />
<ul><br />
<li>Set Scale Wasn't Working with Decimal Numbers<br />
<br />
v5.0.9 introduced a change that caused Set Scale to not work<br />
if the scale contained a decimal point. This release fixed<br />
that issue.<br />
</ul><br />
<br />
New features in v5.0.9:<br />
<ul><br />
<li>Running Simulations Failed if Windows Username Contained<br />
non-ASCII Characters<br />
<br />
If your Windows user account name contained non-US ASCII<br />
characters, you would get an error saying "The simulation<br />
could not be run." This has been fixed.<br />
<br />
<li>Check for Supported 3D Graphics Drivers for Predict View<br />
<br />
If your computer doesn't have a supported 3D graphics<br />
system, then you will get an error message and Predict<br />
View will be disabled.<br />
<br />
<li>AP Name Master File Characters Not Case Insensitive<br />
<br />
If the MAC addresses entered into the AP Name Master File<br />
had uppercase characters, then when VisiWave went to update<br />
the list, it wouldn't recognize the addresses with uppercase<br />
characters so it would re-add the edits to the end.<br />
<br />
<li>Updates to AP Name Master File are Immediately Seen in VisiWave<br />
<br />
If the AP Name Master File is updated outside of VisiWave (or<br />
by another running instance of VisiWave), the new names are<br />
immediately shown in VisiWave's AP List.<br />
<br />
<li>Unable to Create Report Templates<br />
<br />
v5.0.8 introduced an issue that prevented Report Templates<br />
from being created.<br />
<br />
<li>Dates and Times Not Formatted According to Local Region<br />
<br />
Dates and times displayed by VisiWave are now formatted<br />
according to the computer's language and region.<br />
<br />
<li>In PDF Report, Text from Long Descriptions Located Below<br />
a Graph Might Have Duplicate Text<br />
<br />
If you have a Description on a report page that is located<br />
below the graph and carries over to a second page, text from<br />
the description might be repeated and placed on extra pages.<br />
<br />
</ul><br />
<br />
New features in v5.0.8:<br />
<ul><br />
<li>Predictive Surveys<br />
<br />
VisiWave Site Survey Pro now supports predictive surveys as<br />
well as traditional surveys. A predictive survey is when you<br />
describe the barriers (walls and other solid objects) in the<br />
survey area and the location and characteristics of one or<br />
more access points and then run a theoretical simulation of<br />
how radio waves would propagate through the survey area.<br />
It is a way of estimating wireless coverage without having to<br />
collect survey measurements in the real world. This is<br />
useful for dealing with buildings that haven't been built yet<br />
or for doing what-if analysis for existing areas that can't be<br />
easily modified.<br />
<br />
<li>Difference Heatmap Legend Issue<br />
<br />
There was an issue where the legend of a difference heatmap<br />
would only allow you to see the positive values. Now the full<br />
range of positive and negative numbers can be seen.<br />
<br />
</ul><br />
<br />
New features in v5.0.5:<br />
<ul><br />
<li>Issue with PDF Floor Plan Image File Names<br />
<br />
If the name of a PDF file with non-ASCII characters was used<br />
as a floor plan image, loading that image might have failed.<br />
Now any characters can be used in the file name.<br />
<br />
<li>Issue with Duplicate AP Names Appearing in AP List<br />
<br />
When capturing survey data, the same APs could appear many<br />
times in the AP List. This might happen if a virtual AP<br />
continuously changes an AP's SSID in between scans. Now the<br />
AP List is updated to show the most recent SSID for the AP.<br />
<br />
<li>Issue Using Left/Right Arrow Keys to Move from Point to Point<br />
<br />
Fixed an issue where VisiWave could randomly crash when<br />
selecting a data point in Survey View and then pressing the<br />
left or right arrow key to move to the previous or next data<br />
point.<br />
</ul><br />
<br />
New features in v5.0.4:<br />
<ul><br />
<li>Support for Large Floor Plan Image Files<br />
<br />
If an image file is too large for the amount of memory your<br />
computer has, VisiWave now automatically reduces the size of<br />
the image so it will work. Typically images that are 4000<br />
pixels on a side or less work fine. Larger images might get<br />
automatically resized to around this width or height. You can<br />
see the final image size by selecting Set Scale.<br />
<br />
<li>Wrong AP#'s Listed in AP List in PDF Reports<br />
<br />
If you generated a PDF report, the numbers listed for each AP#<br />
was off by one on AP List report pages.<br />
<br />
<li>MAC Addresses Given Wrong Name for Locally Administered Names<br />
<br />
If an access point generates a Locally Administered MAC<br />
address, VisiWave would sometimes give this AP the wrong<br />
manufacturer name. Now Locally Administered addresses<br />
start "local:".<br />
</ul><br />
<br />
New features in v5.0.3:<br />
<ul><br />
<li>AP Marker Custom Names in Report View Were Incorrect<br />
<br />
If you set a custom name on an AP Marker, save the survey file<br />
then reload the survey file, the custom names won't be correct<br />
when viewed on any report pages.<br />
<br />
<li>Data Points Where Nothing Was Seen Were Not Contributing to<br />
Heatmaps<br />
<br />
If a data point that was collected but no access points where<br />
seen at that location then that point was just skipped when<br />
calculating a heatmap. Now that point contributes to the<br />
heatmap by saying there is no coverage there.<br />
<br />
<li>Changing the Survey Map Image Could Stretch Report Images<br />
<br />
If you changed the survey map image file on an already<br />
existing survey file, the width or height of a report image<br />
would be wrong if the aspect ratio of the new image didn't<br />
match the aspect ratio of the old image.<br />
</ul><br />
<br />
New features in v5.0.2:<br />
<ul><br />
<li>Failed to Load v4.0 Survey Files With "AP#'s" in Caption<br />
<br />
Trying to load a survey file created with an earlier version<br />
of VisiWave would fail if the string "AP#" occurred in<br />
any caption or text description unless the string was<br />
followed by a number.<br />
<br />
<li>Issue When Generating Report With Legend Tab Outside Range<br />
<br />
There was an issue with generating a report when the legend<br />
for a heatmap had one of the tabs outside of the Min/Max<br />
range of the color legend.<br />
<br />
<li>Generating PDF Report Would Randomly Fail<br />
<br />
An uninitialized variable would cause generating a PDF report<br />
to randomly fail.<br />
<br />
<li>Changing the Survey Map Image Could Stretch Report Images<br />
<br />
If you changed the survey map image file on an already<br />
existing survey file, the width or height of a report image<br />
would be wrong if the aspect ratio of the new image didn't<br />
match the aspect ratio of the old image.<br />
<br />
<li>Loading v3.0 Survey Files Could Cause Data Points to be in the<br />
Wrong Location<br />
<br />
Survey files created using v3.0 or earlier of VisiWave did not<br />
contain the floor plan image file, but rather the filename of<br />
the image file. If that filename is no longer valid, then you<br />
are prompted to pick the right image file. Doing this in v5.0<br />
would cause the data points to not be located in the correct<br />
locations.<br />
</ul><br />
<br />
New features in v5.0.1:<br />
<ul><br />
<li>Can't Add Data Points After Loading an Empty v4.0 Survey File<br />
<br />
If you load a survey file created by v4.0 of VisiWave that<br />
didn't have any data points in it already, then adding a data<br />
point to it would give you the error message "Encountered an<br />
improper argument".<br />
<br />
<li>Issue Selecting Interference Tab After Stopping Continuous Capture<br />
<br />
If you switched to the Interference Details Tab after stopping<br />
a Continuous mode data capture it could cause a crash.<br />
<br />
<li>Issue Setting the Name Property On a New Survey<br />
<br />
On a new survey file, if you selected a floor plan image file<br />
and set the "Name" property on the Name tab, then VisiWave<br />
would show an error or crash.<br />
<br />
<li>AP Names Sent from the AP Controller Were Not Presenting Correctly<br />
<br />
The character conversion of AP Names sent by the AP controller<br />
where not using the correct conversion and could end up<br />
looking like Chinese, Japanese, or Korean characters.<br />
<br />
<li>Issue Loading and Saving Report Templates<br />
<br />
Loading or saving Report Templates by pressing the Templates<br />
button in the Report View wasn't working correctly.<br />
<br />
</ul><br />
<br />
<a href="http://www.visiwave.com/wifi/visiwave-v50-features.php">Original new features found in v5.0</a>
VisiWave Blognospam@example.com (Administrator)2020-08-31T18:58:00Zhttps://www.visiwave.com/blog/wfwcomment.php?cid=390https://www.visiwave.com/blog/rss.php?version=1.0&type=comments&cid=39VisiWave Site Survey v6.0.1 Released
https://www.visiwave.com/blog/index.php?/archives/38-VisiWave-Site-Survey-v6.0.1-Released.html
A maintenance release of VisiWave (v6.0.1 ) is now available for download. If you already own v6.0 of VisiWave, just download the eval version and install it over-top of your current version. Your existing license will continue to work. If you would like to evaluate VisiWave, just download the eval version and try it out.<br />
<br />
New features in v6.0.1:<br />
<ul><br />
<li>Added Support for Channel Bonding in Predictive Surveys<br />
<br />
When doing a simulation, you can now set a radio's channel<br />
width in addition to just its frequency in the 5GHz band.<br />
You do this by right-clicking on a radio and selecting Edit<br />
Radio. This allows you to simulate the effects of channel<br />
bonding. For example, you can select channel 36 and say that<br />
it is a 40MHz channel to bond channels 36 and 40 together.<br />
<br />
<li>Issue Fixed with Exporting Simulation Data to CSV<br />
<br />
VisiWave was exporting only half the simulated signal values<br />
to the CSV file. Every other value in the X direction was<br />
skipped. Now all the values are exported.<br />
<br />
<li>Performance Improvements When Selecting Radios in Predictive Mode<br />
<br />
There were a few cases where updating the heatmap in Predictive<br />
mode took much longer than needed.<br />
<br />
<li>Allow Merging of Survey Files When Floor Plan Sizes are<br />
Slightly Different<br />
<br />
Due to some rounding issues, some survey files couldn't be<br />
merged even though they used the same floor plan image and<br />
scale.<br />
<br />
<li>Half Power Beamwidth Antenna Types Are More Effective<br />
<br />
For Predictive Surveys, the effect of the horizontal and<br />
vertical rotations for half power beamwidth antennas wasn't<br />
strong enough. And the rotations didn't match the<br />
documentation. These issues have been fixed.<br />
</ul><br />
<br />
<a href="http://www.visiwave.com/wifi/visiwave-v60-features.php">Original new features found in v6.0</a><br />
VisiWave Blognospam@example.com (Administrator)2020-08-31T18:32:00Zhttps://www.visiwave.com/blog/wfwcomment.php?cid=380https://www.visiwave.com/blog/rss.php?version=1.0&type=comments&cid=38VisiWave Site Survey v5.0.12 Released
https://www.visiwave.com/blog/index.php?/archives/37-VisiWave-Site-Survey-v5.0.12-Released.html
A maintenance release of VisiWave (v5.0.12 ) is now available for download. If you already own v5.0 of VisiWave, just download the eval version and install it over-top of your current version. Your existing license will continue to work. If you would like to evaluate VisiWave, just download the eval version and try it out.<br />
<br />
New features in v5.0.12:<br />
<ul><br />
<li>Clear Data Points Issue Fixed<br />
<br />
The previous version introduced a bug when either Data<br />
Points or All was selected from the Survey->Clear menu and<br />
then new data points were added. This has now been fixed.<br />
<br />
<li>Invalid Automatically Detected AP Names Made Survey Files Unloadable<br />
<br />
If the AP name provided by a Cisco compatible controller<br />
contained invalid data, when that garbage AP name was written<br />
to the survey file, it could cause the survey file to not<br />
properly load in the future. Now these invalid AP names are<br />
skipped so they are not written to the survey file.<br />
</ul><br />
<br />
New features in v5.0.11:<br />
<ul><br />
<li>Inferred AP Readings [New Feature]<br />
<br />
When a wireless adapter performs a scan for all APs in the<br />
area, it tries to hear them all but some are missed due to<br />
interference, timing, or many other issues. VisiWave now has<br />
the ability to examine surrounding data points to try to<br />
detect AP readings that were missed. These are called<br />
"Inferred AP Readings". When VisiWave believes an AP reading<br />
was missed, it adds an inferred AP reading to that data point<br />
and estimates what the signal strength would be for that AP.<br />
In heatmaps, a data point with a green outside ring<br />
indicates an inferred AP reading. Also, in the Wi-Fi Details<br />
table, the AP Name or MAC address is colored green for<br />
inferred AP readings and the tooltip label has "<Inferred>"<br />
added to the end.<br />
<br />
If you are seeing many of these inferred AP readings, then you<br />
might consider trying a different wireless adapter or updating<br />
your wireless adapter's drivers to the latest version released<br />
by the manufacturer.<br />
<br />
<li>In Predictive Mode, APs Appear Too Large in Large Survey Areas<br />
<br />
When doing a predictive survey over a large survey area, the<br />
access points added to the scene could become too big. They<br />
are now a more reasonable sized in large survey areas.<br />
<br />
<li>Merging Predictive Survey Files Caused a Crash<br />
<br />
The Merge Survey Files feature wasn't working when trying to<br />
merge a survey file with predictive data. This has now been<br />
fixed. Note the resulting merged survey file will have an<br />
identical copy of the Main Survey File's predictive data. The<br />
barriers, APs, etc. from the other merged survey files will<br />
not be included in the merged survey file.<br />
<br />
<li>Predictive Heatmaps Were Shifted Right and Down in Large Areas<br />
<br />
When doing a predictive survey over a large area, the heatmap<br />
was shifted to the right and down.<br />
<br />
<li>Linked AP Markers Were Not Included During a Survey File Merge<br />
<br />
When merging survey files using the Merge Survey Files<br />
feature, some AP Markers from the survey files being merged<br />
were not copied over. The AP Markers that were linked to an<br />
AP (colored red) were not included. All the AP Markers from<br />
the main survey file and all the unlinked AP Markers were<br />
correctly included.<br />
<br />
<li>Wireless Adapter Names Could Have Been Wrong After a Merge<br />
<br />
If the merged survey files used different wireless adapters<br />
to collect survey data, the wireless adapter name listed<br />
under the Wi-Fi details for each data point could have<br />
been wrong.<br />
<br />
<li>Predictive Surveys: Only First AP in Configuration was Loaded<br />
<br />
When creating a Predictive Survey, you can create many radios,<br />
access points, and configurations. However, when loading a<br />
survey file with more than one AP under a configuration, only<br />
the first one was successfully loaded. The others were<br />
silently skipped.<br />
</ul><br />
<br />
New features in v5.0.10:<br />
<ul><br />
<li>Set Scale Wasn't Working with Decimal Numbers<br />
<br />
v5.0.9 introduced a change that caused Set Scale to not work<br />
if the scale contained a decimal point. This release fixed<br />
that issue.<br />
</ul><br />
<br />
New features in v5.0.9:<br />
<ul><br />
<li>Running Simulations Failed if Windows Username Contained<br />
non-ASCII Characters<br />
<br />
If your Windows user account name contained non-US ASCII<br />
characters, you would get an error saying "The simulation<br />
could not be run." This has been fixed.<br />
<br />
<li>Check for Supported 3D Graphics Drivers for Predict View<br />
<br />
If your computer doesn't have a supported 3D graphics<br />
system, then you will get an error message and Predict<br />
View will be disabled.<br />
<br />
<li>AP Name Master File Characters Not Case Insensitive<br />
<br />
If the MAC addresses entered into the AP Name Master File<br />
had uppercase characters, then when VisiWave went to update<br />
the list, it wouldn't recognize the addresses with uppercase<br />
characters so it would re-add the edits to the end.<br />
<br />
<li>Updates to AP Name Master File are Immediately Seen in VisiWave<br />
<br />
If the AP Name Master File is updated outside of VisiWave (or<br />
by another running instance of VisiWave), the new names are<br />
immediately shown in VisiWave's AP List.<br />
<br />
<li>Unable to Create Report Templates<br />
<br />
v5.0.8 introduced an issue that prevented Report Templates<br />
from being created.<br />
<br />
<li>Dates and Times Not Formatted According to Local Region<br />
<br />
Dates and times displayed by VisiWave are now formatted<br />
according to the computer's language and region.<br />
<br />
<li>In PDF Report, Text from Long Descriptions Located Below<br />
a Graph Might Have Duplicate Text<br />
<br />
If you have a Description on a report page that is located<br />
below the graph and carries over to a second page, text from<br />
the description might be repeated and placed on extra pages.<br />
<br />
</ul><br />
<br />
New features in v5.0.8:<br />
<ul><br />
<li>Predictive Surveys<br />
<br />
VisiWave Site Survey Pro now supports predictive surveys as<br />
well as traditional surveys. A predictive survey is when you<br />
describe the barriers (walls and other solid objects) in the<br />
survey area and the location and characteristics of one or<br />
more access points and then run a theoretical simulation of<br />
how radio waves would propagate through the survey area.<br />
It is a way of estimating wireless coverage without having to<br />
collect survey measurements in the real world. This is<br />
useful for dealing with buildings that haven't been built yet<br />
or for doing what-if analysis for existing areas that can't be<br />
easily modified.<br />
<br />
<li>Difference Heatmap Legend Issue<br />
<br />
There was an issue where the legend of a difference heatmap<br />
would only allow you to see the positive values. Now the full<br />
range of positive and negative numbers can be seen.<br />
<br />
</ul><br />
<br />
New features in v5.0.5:<br />
<ul><br />
<li>Issue with PDF Floor Plan Image File Names<br />
<br />
If the name of a PDF file with non-ASCII characters was used<br />
as a floor plan image, loading that image might have failed.<br />
Now any characters can be used in the file name.<br />
<br />
<li>Issue with Duplicate AP Names Appearing in AP List<br />
<br />
When capturing survey data, the same APs could appear many<br />
times in the AP List. This might happen if a virtual AP<br />
continuously changes an AP's SSID in between scans. Now the<br />
AP List is updated to show the most recent SSID for the AP.<br />
<br />
<li>Issue Using Left/Right Arrow Keys to Move from Point to Point<br />
<br />
Fixed an issue where VisiWave could randomly crash when<br />
selecting a data point in Survey View and then pressing the<br />
left or right arrow key to move to the previous or next data<br />
point.<br />
</ul><br />
<br />
New features in v5.0.4:<br />
<ul><br />
<li>Support for Large Floor Plan Image Files<br />
<br />
If an image file is too large for the amount of memory your<br />
computer has, VisiWave now automatically reduces the size of<br />
the image so it will work. Typically images that are 4000<br />
pixels on a side or less work fine. Larger images might get<br />
automatically resized to around this width or height. You can<br />
see the final image size by selecting Set Scale.<br />
<br />
<li>Wrong AP#'s Listed in AP List in PDF Reports<br />
<br />
If you generated a PDF report, the numbers listed for each AP#<br />
was off by one on AP List report pages.<br />
<br />
<li>MAC Addresses Given Wrong Name for Locally Administered Names<br />
<br />
If an access point generates a Locally Administered MAC<br />
address, VisiWave would sometimes give this AP the wrong<br />
manufacturer name. Now Locally Administered addresses<br />
start "local:".<br />
</ul><br />
<br />
New features in v5.0.3:<br />
<ul><br />
<li>AP Marker Custom Names in Report View Were Incorrect<br />
<br />
If you set a custom name on an AP Marker, save the survey file<br />
then reload the survey file, the custom names won't be correct<br />
when viewed on any report pages.<br />
<br />
<li>Data Points Where Nothing Was Seen Were Not Contributing to<br />
Heatmaps<br />
<br />
If a data point that was collected but no access points where<br />
seen at that location then that point was just skipped when<br />
calculating a heatmap. Now that point contributes to the<br />
heatmap by saying there is no coverage there.<br />
<br />
<li>Changing the Survey Map Image Could Stretch Report Images<br />
<br />
If you changed the survey map image file on an already<br />
existing survey file, the width or height of a report image<br />
would be wrong if the aspect ratio of the new image didn't<br />
match the aspect ratio of the old image.<br />
</ul><br />
<br />
New features in v5.0.2:<br />
<ul><br />
<li>Failed to Load v4.0 Survey Files With "AP#'s" in Caption<br />
<br />
Trying to load a survey file created with an earlier version<br />
of VisiWave would fail if the string "AP#" occurred in<br />
any caption or text description unless the string was<br />
followed by a number.<br />
<br />
<li>Issue When Generating Report With Legend Tab Outside Range<br />
<br />
There was an issue with generating a report when the legend<br />
for a heatmap had one of the tabs outside of the Min/Max<br />
range of the color legend.<br />
<br />
<li>Generating PDF Report Would Randomly Fail<br />
<br />
An uninitialized variable would cause generating a PDF report<br />
to randomly fail.<br />
<br />
<li>Changing the Survey Map Image Could Stretch Report Images<br />
<br />
If you changed the survey map image file on an already<br />
existing survey file, the width or height of a report image<br />
would be wrong if the aspect ratio of the new image didn't<br />
match the aspect ratio of the old image.<br />
<br />
<li>Loading v3.0 Survey Files Could Cause Data Points to be in the<br />
Wrong Location<br />
<br />
Survey files created using v3.0 or earlier of VisiWave did not<br />
contain the floor plan image file, but rather the filename of<br />
the image file. If that filename is no longer valid, then you<br />
are prompted to pick the right image file. Doing this in v5.0<br />
would cause the data points to not be located in the correct<br />
locations.<br />
</ul><br />
<br />
New features in v5.0.1:<br />
<ul><br />
<li>Can't Add Data Points After Loading an Empty v4.0 Survey File<br />
<br />
If you load a survey file created by v4.0 of VisiWave that<br />
didn't have any data points in it already, then adding a data<br />
point to it would give you the error message "Encountered an<br />
improper argument".<br />
<br />
<li>Issue Selecting Interference Tab After Stopping Continuous Capture<br />
<br />
If you switched to the Interference Details Tab after stopping<br />
a Continuous mode data capture it could cause a crash.<br />
<br />
<li>Issue Setting the Name Property On a New Survey<br />
<br />
On a new survey file, if you selected a floor plan image file<br />
and set the "Name" property on the Name tab, then VisiWave<br />
would show an error or crash.<br />
<br />
<li>AP Names Sent from the AP Controller Were Not Presenting Correctly<br />
<br />
The character conversion of AP Names sent by the AP controller<br />
where not using the correct conversion and could end up<br />
looking like Chinese, Japanese, or Korean characters.<br />
<br />
<li>Issue Loading and Saving Report Templates<br />
<br />
Loading or saving Report Templates by pressing the Templates<br />
button in the Report View wasn't working correctly.<br />
<br />
</ul><br />
<br />
<a href="http://www.visiwave.com/wifi/visiwave-v50-features.php">Original new features found in v5.0</a>
VisiWave Blognospam@example.com (Administrator)2019-09-25T11:30:00Zhttps://www.visiwave.com/blog/wfwcomment.php?cid=370https://www.visiwave.com/blog/rss.php?version=1.0&type=comments&cid=37VisiWave Site Survey v5.0.11 Released
https://www.visiwave.com/blog/index.php?/archives/36-VisiWave-Site-Survey-v5.0.11-Released.html
A maintenance release of VisiWave (v5.0.11 ) is now available for download. If you already own v5.0 of VisiWave, just download the eval version and install it over-top of your current version. Your existing license will continue to work. If you would like to evaluate VisiWave, just download the eval version and try it out.<br />
<br />
New features in v5.0.11:<br />
<ul><br />
<li>Inferred AP Readings [New Feature]<br />
<br />
When a wireless adapter performs a scan for all APs in the<br />
area, it tries to hear them all but some are missed due to<br />
interference, timing, or many other issues. VisiWave now has<br />
the ability to examine surrounding data points to try to<br />
detect AP readings that were missed. These are called<br />
"Inferred AP Readings". When VisiWave believes an AP reading<br />
was missed, it adds an inferred AP reading to that data point<br />
and estimates what the signal strength would be for that AP.<br />
In heatmaps, a data point with a green outside ring<br />
indicates an inferred AP reading. Also, in the Wi-Fi Details<br />
table, the AP Name or MAC address is colored green for<br />
inferred AP readings and the tooltip label has "<Inferred>"<br />
added to the end.<br />
<br />
If you are seeing many of these inferred AP readings, then you<br />
might consider trying a different wireless adapter or updating<br />
your wireless adapter's drivers to the latest version released<br />
by the manufacturer.<br />
<br />
<li>In Predictive Mode, APs Appear Too Large in Large Survey Areas<br />
<br />
When doing a predictive survey over a large survey area, the<br />
access points added to the scene could become too big. They<br />
are now a more reasonable sized in large survey areas.<br />
<br />
<li>Merging Predictive Survey Files Caused a Crash<br />
<br />
The Merge Survey Files feature wasn't working when trying to<br />
merge a survey file with predictive data. This has now been<br />
fixed. Note the resulting merged survey file will have an<br />
identical copy of the Main Survey File's predictive data. The<br />
barriers, APs, etc. from the other merged survey files will<br />
not be included in the merged survey file.<br />
<br />
<li>Predictive Heatmaps Were Shifted Right and Down in Large Areas<br />
<br />
When doing a predictive survey over a large area, the heatmap<br />
was shifted to the right and down.<br />
<br />
<li>Linked AP Markers Were Not Included During a Survey File Merge<br />
<br />
When merging survey files using the Merge Survey Files<br />
feature, some AP Markers from the survey files being merged<br />
were not copied over. The AP Markers that were linked to an<br />
AP (colored red) were not included. All the AP Markers from<br />
the main survey file and all the unlinked AP Markers were<br />
correctly included.<br />
<br />
<li>Wireless Adapter Names Could Have Been Wrong After a Merge<br />
<br />
If the merged survey files used different wireless adapters<br />
to collect survey data, the wireless adapter name listed<br />
under the Wi-Fi details for each data point could have<br />
been wrong.<br />
<br />
<li>Predictive Surveys: Only First AP in Configuration was Loaded<br />
<br />
When creating a Predictive Survey, you can create many radios,<br />
access points, and configurations. However, when loading a<br />
survey file with more than one AP under a configuration, only<br />
the first one was successfully loaded. The others were<br />
silently skipped.<br />
</ul><br />
<br />
New features in v5.0.10:<br />
<ul><br />
<li>Set Scale Wasn't Working with Decimal Numbers<br />
<br />
v5.0.9 introduced a change that caused Set Scale to not work<br />
if the scale contained a decimal point. This release fixed<br />
that issue.<br />
</ul><br />
<br />
New features in v5.0.9:<br />
<ul><br />
<li>Running Simulations Failed if Windows Username Contained<br />
non-ASCII Characters<br />
<br />
If your Windows user account name contained non-US ASCII<br />
characters, you would get an error saying "The simulation<br />
could not be run." This has been fixed.<br />
<br />
<li>Check for Supported 3D Graphics Drivers for Predict View<br />
<br />
If your computer doesn't have a supported 3D graphics<br />
system, then you will get an error message and Predict<br />
View will be disabled.<br />
<br />
<li>AP Name Master File Characters Not Case Insensitive<br />
<br />
If the MAC addresses entered into the AP Name Master File<br />
had uppercase characters, then when VisiWave went to update<br />
the list, it wouldn't recognize the addresses with uppercase<br />
characters so it would re-add the edits to the end.<br />
<br />
<li>Updates to AP Name Master File are Immediately Seen in VisiWave<br />
<br />
If the AP Name Master File is updated outside of VisiWave (or<br />
by another running instance of VisiWave), the new names are<br />
immediately shown in VisiWave's AP List.<br />
<br />
<li>Unable to Create Report Templates<br />
<br />
v5.0.8 introduced an issue that prevented Report Templates<br />
from being created.<br />
<br />
<li>Dates and Times Not Formatted According to Local Region<br />
<br />
Dates and times displayed by VisiWave are now formatted<br />
according to the computer's language and region.<br />
<br />
<li>In PDF Report, Text from Long Descriptions Located Below<br />
a Graph Might Have Duplicate Text<br />
<br />
If you have a Description on a report page that is located<br />
below the graph and carries over to a second page, text from<br />
the description might be repeated and placed on extra pages.<br />
<br />
</ul><br />
<br />
New features in v5.0.8:<br />
<ul><br />
<li>Predictive Surveys<br />
<br />
VisiWave Site Survey Pro now supports predictive surveys as<br />
well as traditional surveys. A predictive survey is when you<br />
describe the barriers (walls and other solid objects) in the<br />
survey area and the location and characteristics of one or<br />
more access points and then run a theoretical simulation of<br />
how radio waves would propagate through the survey area.<br />
It is a way of estimating wireless coverage without having to<br />
collect survey measurements in the real world. This is<br />
useful for dealing with buildings that haven't been built yet<br />
or for doing what-if analysis for existing areas that can't be<br />
easily modified.<br />
<br />
<li>Difference Heatmap Legend Issue<br />
<br />
There was an issue where the legend of a difference heatmap<br />
would only allow you to see the positive values. Now the full<br />
range of positive and negative numbers can be seen.<br />
<br />
</ul><br />
<br />
New features in v5.0.5:<br />
<ul><br />
<li>Issue with PDF Floor Plan Image File Names<br />
<br />
If the name of a PDF file with non-ASCII characters was used<br />
as a floor plan image, loading that image might have failed.<br />
Now any characters can be used in the file name.<br />
<br />
<li>Issue with Duplicate AP Names Appearing in AP List<br />
<br />
When capturing survey data, the same APs could appear many<br />
times in the AP List. This might happen if a virtual AP<br />
continuously changes an AP's SSID in between scans. Now the<br />
AP List is updated to show the most recent SSID for the AP.<br />
<br />
<li>Issue Using Left/Right Arrow Keys to Move from Point to Point<br />
<br />
Fixed an issue where VisiWave could randomly crash when<br />
selecting a data point in Survey View and then pressing the<br />
left or right arrow key to move to the previous or next data<br />
point.<br />
</ul><br />
<br />
New features in v5.0.4:<br />
<ul><br />
<li>Support for Large Floor Plan Image Files<br />
<br />
If an image file is too large for the amount of memory your<br />
computer has, VisiWave now automatically reduces the size of<br />
the image so it will work. Typically images that are 4000<br />
pixels on a side or less work fine. Larger images might get<br />
automatically resized to around this width or height. You can<br />
see the final image size by selecting Set Scale.<br />
<br />
<li>Wrong AP#'s Listed in AP List in PDF Reports<br />
<br />
If you generated a PDF report, the numbers listed for each AP#<br />
was off by one on AP List report pages.<br />
<br />
<li>MAC Addresses Given Wrong Name for Locally Administered Names<br />
<br />
If an access point generates a Locally Administered MAC<br />
address, VisiWave would sometimes give this AP the wrong<br />
manufacturer name. Now Locally Administered addresses<br />
start "local:".<br />
</ul><br />
<br />
New features in v5.0.3:<br />
<ul><br />
<li>AP Marker Custom Names in Report View Were Incorrect<br />
<br />
If you set a custom name on an AP Marker, save the survey file<br />
then reload the survey file, the custom names won't be correct<br />
when viewed on any report pages.<br />
<br />
<li>Data Points Where Nothing Was Seen Were Not Contributing to<br />
Heatmaps<br />
<br />
If a data point that was collected but no access points where<br />
seen at that location then that point was just skipped when<br />
calculating a heatmap. Now that point contributes to the<br />
heatmap by saying there is no coverage there.<br />
<br />
<li>Changing the Survey Map Image Could Stretch Report Images<br />
<br />
If you changed the survey map image file on an already<br />
existing survey file, the width or height of a report image<br />
would be wrong if the aspect ratio of the new image didn't<br />
match the aspect ratio of the old image.<br />
</ul><br />
<br />
New features in v5.0.2:<br />
<ul><br />
<li>Failed to Load v4.0 Survey Files With "AP#'s" in Caption<br />
<br />
Trying to load a survey file created with an earlier version<br />
of VisiWave would fail if the string "AP#" occurred in<br />
any caption or text description unless the string was<br />
followed by a number.<br />
<br />
<li>Issue When Generating Report With Legend Tab Outside Range<br />
<br />
There was an issue with generating a report when the legend<br />
for a heatmap had one of the tabs outside of the Min/Max<br />
range of the color legend.<br />
<br />
<li>Generating PDF Report Would Randomly Fail<br />
<br />
An uninitialized variable would cause generating a PDF report<br />
to randomly fail.<br />
<br />
<li>Changing the Survey Map Image Could Stretch Report Images<br />
<br />
If you changed the survey map image file on an already<br />
existing survey file, the width or height of a report image<br />
would be wrong if the aspect ratio of the new image didn't<br />
match the aspect ratio of the old image.<br />
<br />
<li>Loading v3.0 Survey Files Could Cause Data Points to be in the<br />
Wrong Location<br />
<br />
Survey files created using v3.0 or earlier of VisiWave did not<br />
contain the floor plan image file, but rather the filename of<br />
the image file. If that filename is no longer valid, then you<br />
are prompted to pick the right image file. Doing this in v5.0<br />
would cause the data points to not be located in the correct<br />
locations.<br />
</ul><br />
<br />
New features in v5.0.1:<br />
<ul><br />
<li>Can't Add Data Points After Loading an Empty v4.0 Survey File<br />
<br />
If you load a survey file created by v4.0 of VisiWave that<br />
didn't have any data points in it already, then adding a data<br />
point to it would give you the error message "Encountered an<br />
improper argument".<br />
<br />
<li>Issue Selecting Interference Tab After Stopping Continuous Capture<br />
<br />
If you switched to the Interference Details Tab after stopping<br />
a Continuous mode data capture it could cause a crash.<br />
<br />
<li>Issue Setting the Name Property On a New Survey<br />
<br />
On a new survey file, if you selected a floor plan image file<br />
and set the "Name" property on the Name tab, then VisiWave<br />
would show an error or crash.<br />
<br />
<li>AP Names Sent from the AP Controller Were Not Presenting Correctly<br />
<br />
The character conversion of AP Names sent by the AP controller<br />
where not using the correct conversion and could end up<br />
looking like Chinese, Japanese, or Korean characters.<br />
<br />
<li>Issue Loading and Saving Report Templates<br />
<br />
Loading or saving Report Templates by pressing the Templates<br />
button in the Report View wasn't working correctly.<br />
<br />
</ul><br />
<br />
<a href="http://www.visiwave.com/wifi/visiwave-v50-features.php">Original new features found in v5.0</a>
VisiWave Blognospam@example.com (Administrator)2019-05-29T16:05:00Zhttps://www.visiwave.com/blog/wfwcomment.php?cid=360https://www.visiwave.com/blog/rss.php?version=1.0&type=comments&cid=36VisiWave Site Survey v5.0.10 Released
https://www.visiwave.com/blog/index.php?/archives/35-VisiWave-Site-Survey-v5.0.10-Released.html
A maintenance release of VisiWave (v5.0.10 ) is now available for download. If you already own v5.0 of VisiWave, just download the eval version and install it over-top of your current version. Your existing license will continue to work. If you would like to evaluate VisiWave, just download the eval version and try it out.<br />
<br />
New features in v5.0.10:<br />
<ul><br />
<li>Set Scale Wasn't Working with Decimal Numbers<br />
<br />
v5.0.9 introduced a change that caused Set Scale to not work<br />
if the scale contained a decimal point. This release fixed<br />
that issue.<br />
</ul><br />
<br />
New features in v5.0.9:<br />
<ul><br />
<li>Running Simulations Failed if Windows Username Contained<br />
non-ASCII Characters<br />
<br />
If your Windows user account name contained non-US ASCII<br />
characters, you would get an error saying "The simulation<br />
could not be run." This has been fixed.<br />
<br />
<li>Check for Supported 3D Graphics Drivers for Predict View<br />
<br />
If your computer doesn't have a supported 3D graphics<br />
system, then you will get an error message and Predict<br />
View will be disabled.<br />
<br />
<li>AP Name Master File Characters Not Case Insensitive<br />
<br />
If the MAC addresses entered into the AP Name Master File<br />
had uppercase characters, then when VisiWave went to update<br />
the list, it wouldn't recognize the addresses with uppercase<br />
characters so it would re-add the edits to the end.<br />
<br />
<li>Updates to AP Name Master File are Immediately Seen in VisiWave<br />
<br />
If the AP Name Master File is updated outside of VisiWave (or<br />
by another running instance of VisiWave), the new names are<br />
immediately shown in VisiWave's AP List.<br />
<br />
<li>Unable to Create Report Templates<br />
<br />
v5.0.8 introduced an issue that prevented Report Templates<br />
from being created.<br />
<br />
<li>Dates and Times Not Formatted According to Local Region<br />
<br />
Dates and times displayed by VisiWave are now formatted<br />
according to the computer's language and region.<br />
<br />
<li>In PDF Report, Text from Long Descriptions Located Below<br />
a Graph Might Have Duplicate Text<br />
<br />
If you have a Description on a report page that is located<br />
below the graph and carries over to a second page, text from<br />
the description might be repeated and placed on extra pages.<br />
<br />
</ul><br />
<br />
New features in v5.0.8:<br />
<ul><br />
<li>Predictive Surveys<br />
<br />
VisiWave Site Survey Pro now supports predictive surveys as<br />
well as traditional surveys. A predictive survey is when you<br />
describe the barriers (walls and other solid objects) in the<br />
survey area and the location and characteristics of one or<br />
more access points and then run a theoretical simulation of<br />
how radio waves would propagate through the survey area.<br />
It is a way of estimating wireless coverage without having to<br />
collect survey measurements in the real world. This is<br />
useful for dealing with buildings that haven't been built yet<br />
or for doing what-if analysis for existing areas that can't be<br />
easily modified.<br />
<br />
<li>Difference Heatmap Legend Issue<br />
<br />
There was an issue where the legend of a difference heatmap<br />
would only allow you to see the positive values. Now the full<br />
range of positive and negative numbers can be seen.<br />
<br />
</ul><br />
<br />
New features in v5.0.5:<br />
<ul><br />
<li>Issue with PDF Floor Plan Image File Names<br />
<br />
If the name of a PDF file with non-ASCII characters was used<br />
as a floor plan image, loading that image might have failed.<br />
Now any characters can be used in the file name.<br />
<br />
<li>Issue with Duplicate AP Names Appearing in AP List<br />
<br />
When capturing survey data, the same APs could appear many<br />
times in the AP List. This might happen if a virtual AP<br />
continuously changes an AP's SSID in between scans. Now the<br />
AP List is updated to show the most recent SSID for the AP.<br />
<br />
<li>Issue Using Left/Right Arrow Keys to Move from Point to Point<br />
<br />
Fixed an issue where VisiWave could randomly crash when<br />
selecting a data point in Survey View and then pressing the<br />
left or right arrow key to move to the previous or next data<br />
point.<br />
</ul><br />
<br />
New features in v5.0.4:<br />
<ul><br />
<li>Support for Large Floor Plan Image Files<br />
<br />
If an image file is too large for the amount of memory your<br />
computer has, VisiWave now automatically reduces the size of<br />
the image so it will work. Typically images that are 4000<br />
pixels on a side or less work fine. Larger images might get<br />
automatically resized to around this width or height. You can<br />
see the final image size by selecting Set Scale.<br />
<br />
<li>Wrong AP#'s Listed in AP List in PDF Reports<br />
<br />
If you generated a PDF report, the numbers listed for each AP#<br />
was off by one on AP List report pages.<br />
<br />
<li>MAC Addresses Given Wrong Name for Locally Administered Names<br />
<br />
If an access point generates a Locally Administered MAC<br />
address, VisiWave would sometimes give this AP the wrong<br />
manufacturer name. Now Locally Administered addresses<br />
start "local:".<br />
</ul><br />
<br />
New features in v5.0.3:<br />
<ul><br />
<li>AP Marker Custom Names in Report View Were Incorrect<br />
<br />
If you set a custom name on an AP Marker, save the survey file<br />
then reload the survey file, the custom names won't be correct<br />
when viewed on any report pages.<br />
<br />
<li>Data Points Where Nothing Was Seen Were Not Contributing to<br />
Heatmaps<br />
<br />
If a data point that was collected but no access points where<br />
seen at that location then that point was just skipped when<br />
calculating a heatmap. Now that point contributes to the<br />
heatmap by saying there is no coverage there.<br />
<br />
<li>Changing the Survey Map Image Could Stretch Report Images<br />
<br />
If you changed the survey map image file on an already<br />
existing survey file, the width or height of a report image<br />
would be wrong if the aspect ratio of the new image didn't<br />
match the aspect ratio of the old image.<br />
</ul><br />
<br />
New features in v5.0.2:<br />
<ul><br />
<li>Failed to Load v4.0 Survey Files With "AP#'s" in Caption<br />
<br />
Trying to load a survey file created with an earlier version<br />
of VisiWave would fail if the string "AP#" occurred in<br />
any caption or text description unless the string was<br />
followed by a number.<br />
<br />
<li>Issue When Generating Report With Legend Tab Outside Range<br />
<br />
There was an issue with generating a report when the legend<br />
for a heatmap had one of the tabs outside of the Min/Max<br />
range of the color legend.<br />
<br />
<li>Generating PDF Report Would Randomly Fail<br />
<br />
An uninitialized variable would cause generating a PDF report<br />
to randomly fail.<br />
<br />
<li>Changing the Survey Map Image Could Stretch Report Images<br />
<br />
If you changed the survey map image file on an already<br />
existing survey file, the width or height of a report image<br />
would be wrong if the aspect ratio of the new image didn't<br />
match the aspect ratio of the old image.<br />
<br />
<li>Loading v3.0 Survey Files Could Cause Data Points to be in the<br />
Wrong Location<br />
<br />
Survey files created using v3.0 or earlier of VisiWave did not<br />
contain the floor plan image file, but rather the filename of<br />
the image file. If that filename is no longer valid, then you<br />
are prompted to pick the right image file. Doing this in v5.0<br />
would cause the data points to not be located in the correct<br />
locations.<br />
</ul><br />
<br />
New features in v5.0.1:<br />
<ul><br />
<li>Can't Add Data Points After Loading an Empty v4.0 Survey File<br />
<br />
If you load a survey file created by v4.0 of VisiWave that<br />
didn't have any data points in it already, then adding a data<br />
point to it would give you the error message "Encountered an<br />
improper argument".<br />
<br />
<li>Issue Selecting Interference Tab After Stopping Continuous Capture<br />
<br />
If you switched to the Interference Details Tab after stopping<br />
a Continuous mode data capture it could cause a crash.<br />
<br />
<li>Issue Setting the Name Property On a New Survey<br />
<br />
On a new survey file, if you selected a floor plan image file<br />
and set the "Name" property on the Name tab, then VisiWave<br />
would show an error or crash.<br />
<br />
<li>AP Names Sent from the AP Controller Were Not Presenting Correctly<br />
<br />
The character conversion of AP Names sent by the AP controller<br />
where not using the correct conversion and could end up<br />
looking like Chinese, Japanese, or Korean characters.<br />
<br />
<li>Issue Loading and Saving Report Templates<br />
<br />
Loading or saving Report Templates by pressing the Templates<br />
button in the Report View wasn't working correctly.<br />
<br />
</ul><br />
<br />
<a href="http://www.visiwave.com/wifi/visiwave-v50-features.php">Original new features found in v5.0</a>
VisiWave Blognospam@example.com (Administrator)2019-01-14T15:57:00Zhttps://www.visiwave.com/blog/wfwcomment.php?cid=350https://www.visiwave.com/blog/rss.php?version=1.0&type=comments&cid=35VisiWave Site Survey v5.0.9 Released
https://www.visiwave.com/blog/index.php?/archives/34-VisiWave-Site-Survey-v5.0.9-Released.html
A maintenance release of VisiWave (v5.0.9 ) is now available for download. If you already own v5.0 of VisiWave, just download the eval version and install it over-top of your current version. Your existing license will continue to work. If you would like to evaluate VisiWave, just download the eval version and try it out.<br />
<br />
New features in v5.0.9:<br />
<ul><br />
<li>Running Simulations Failed if Windows Username Contained<br />
non-ASCII Characters<br />
<br />
If your Windows user account name contained non-US ASCII<br />
characters, you would get an error saying "The simulation<br />
could not be run." This has been fixed.<br />
<br />
<li>Check for Supported 3D Graphics Drivers for Predict View<br />
<br />
If your computer doesn't have a supported 3D graphics<br />
system, then you will get an error message and Predict<br />
View will be disabled.<br />
<br />
<li>AP Name Master File Characters Not Case Insensitive<br />
<br />
If the MAC addresses entered into the AP Name Master File<br />
had uppercase characters, then when VisiWave went to update<br />
the list, it wouldn't recognize the addresses with uppercase<br />
characters so it would re-add the edits to the end.<br />
<br />
<li>Updates to AP Name Master File are Immediately Seen in VisiWave<br />
<br />
If the AP Name Master File is updated outside of VisiWave (or<br />
by another running instance of VisiWave), the new names are<br />
immediately shown in VisiWave's AP List.<br />
<br />
<li>Unable to Create Report Templates<br />
<br />
v5.0.8 introduced an issue that prevented Report Templates<br />
from being created.<br />
<br />
<li>Dates and Times Not Formatted According to Local Region<br />
<br />
Dates and times displayed by VisiWave are now formatted<br />
according to the computer's language and region.<br />
<br />
<li>In PDF Report, Text from Long Descriptions Located Below<br />
a Graph Might Have Duplicate Text<br />
<br />
If you have a Description on a report page that is located<br />
below the graph and carries over to a second page, text from<br />
the description might be repeated and placed on extra pages.<br />
<br />
</ul><br />
<br />
New features in v5.0.8:<br />
<ul><br />
<li>Predictive Surveys<br />
<br />
VisiWave Site Survey Pro now supports predictive surveys as<br />
well as traditional surveys. A predictive survey is when you<br />
describe the barriers (walls and other solid objects) in the<br />
survey area and the location and characteristics of one or<br />
more access points and then run a theoretical simulation of<br />
how radio waves would propagate through the survey area.<br />
It is a way of estimating wireless coverage without having to<br />
collect survey measurements in the real world. This is<br />
useful for dealing with buildings that haven't been built yet<br />
or for doing what-if analysis for existing areas that can't be<br />
easily modified.<br />
<br />
<li>Difference Heatmap Legend Issue<br />
<br />
There was an issue where the legend of a difference heatmap<br />
would only allow you to see the positive values. Now the full<br />
range of positive and negative numbers can be seen.<br />
<br />
</ul><br />
<br />
New features in v5.0.5:<br />
<ul><br />
<li>Issue with PDF Floor Plan Image File Names<br />
<br />
If the name of a PDF file with non-ASCII characters was used<br />
as a floor plan image, loading that image might have failed.<br />
Now any characters can be used in the file name.<br />
<br />
<li>Issue with Duplicate AP Names Appearing in AP List<br />
<br />
When capturing survey data, the same APs could appear many<br />
times in the AP List. This might happen if a virtual AP<br />
continuously changes an AP's SSID in between scans. Now the<br />
AP List is updated to show the most recent SSID for the AP.<br />
<br />
<li>Issue Using Left/Right Arrow Keys to Move from Point to Point<br />
<br />
Fixed an issue where VisiWave could randomly crash when<br />
selecting a data point in Survey View and then pressing the<br />
left or right arrow key to move to the previous or next data<br />
point.<br />
</ul><br />
<br />
New features in v5.0.4:<br />
<ul><br />
<li>Support for Large Floor Plan Image Files<br />
<br />
If an image file is too large for the amount of memory your<br />
computer has, VisiWave now automatically reduces the size of<br />
the image so it will work. Typically images that are 4000<br />
pixels on a side or less work fine. Larger images might get<br />
automatically resized to around this width or height. You can<br />
see the final image size by selecting Set Scale.<br />
<br />
<li>Wrong AP#'s Listed in AP List in PDF Reports<br />
<br />
If you generated a PDF report, the numbers listed for each AP#<br />
was off by one on AP List report pages.<br />
<br />
<li>MAC Addresses Given Wrong Name for Locally Administered Names<br />
<br />
If an access point generates a Locally Administered MAC<br />
address, VisiWave would sometimes give this AP the wrong<br />
manufacturer name. Now Locally Administered addresses<br />
start "local:".<br />
</ul><br />
<br />
New features in v5.0.3:<br />
<ul><br />
<li>AP Marker Custom Names in Report View Were Incorrect<br />
<br />
If you set a custom name on an AP Marker, save the survey file<br />
then reload the survey file, the custom names won't be correct<br />
when viewed on any report pages.<br />
<br />
<li>Data Points Where Nothing Was Seen Were Not Contributing to<br />
Heatmaps<br />
<br />
If a data point that was collected but no access points where<br />
seen at that location then that point was just skipped when<br />
calculating a heatmap. Now that point contributes to the<br />
heatmap by saying there is no coverage there.<br />
<br />
<li>Changing the Survey Map Image Could Stretch Report Images<br />
<br />
If you changed the survey map image file on an already<br />
existing survey file, the width or height of a report image<br />
would be wrong if the aspect ratio of the new image didn't<br />
match the aspect ratio of the old image.<br />
</ul><br />
<br />
New features in v5.0.2:<br />
<ul><br />
<li>Failed to Load v4.0 Survey Files With "AP#'s" in Caption<br />
<br />
Trying to load a survey file created with an earlier version<br />
of VisiWave would fail if the string "AP#" occurred in<br />
any caption or text description unless the string was<br />
followed by a number.<br />
<br />
<li>Issue When Generating Report With Legend Tab Outside Range<br />
<br />
There was an issue with generating a report when the legend<br />
for a heatmap had one of the tabs outside of the Min/Max<br />
range of the color legend.<br />
<br />
<li>Generating PDF Report Would Randomly Fail<br />
<br />
An uninitialized variable would cause generating a PDF report<br />
to randomly fail.<br />
<br />
<li>Changing the Survey Map Image Could Stretch Report Images<br />
<br />
If you changed the survey map image file on an already<br />
existing survey file, the width or height of a report image<br />
would be wrong if the aspect ratio of the new image didn't<br />
match the aspect ratio of the old image.<br />
<br />
<li>Loading v3.0 Survey Files Could Cause Data Points to be in the<br />
Wrong Location<br />
<br />
Survey files created using v3.0 or earlier of VisiWave did not<br />
contain the floor plan image file, but rather the filename of<br />
the image file. If that filename is no longer valid, then you<br />
are prompted to pick the right image file. Doing this in v5.0<br />
would cause the data points to not be located in the correct<br />
locations.<br />
</ul><br />
<br />
New features in v5.0.1:<br />
<ul><br />
<li>Can't Add Data Points After Loading an Empty v4.0 Survey File<br />
<br />
If you load a survey file created by v4.0 of VisiWave that<br />
didn't have any data points in it already, then adding a data<br />
point to it would give you the error message "Encountered an<br />
improper argument".<br />
<br />
<li>Issue Selecting Interference Tab After Stopping Continuous Capture<br />
<br />
If you switched to the Interference Details Tab after stopping<br />
a Continuous mode data capture it could cause a crash.<br />
<br />
<li>Issue Setting the Name Property On a New Survey<br />
<br />
On a new survey file, if you selected a floor plan image file<br />
and set the "Name" property on the Name tab, then VisiWave<br />
would show an error or crash.<br />
<br />
<li>AP Names Sent from the AP Controller Were Not Presenting Correctly<br />
<br />
The character conversion of AP Names sent by the AP controller<br />
where not using the correct conversion and could end up<br />
looking like Chinese, Japanese, or Korean characters.<br />
<br />
<li>Issue Loading and Saving Report Templates<br />
<br />
Loading or saving Report Templates by pressing the Templates<br />
button in the Report View wasn't working correctly.<br />
<br />
</ul><br />
<br />
<a href="http://www.visiwave.com/wifi/visiwave-v50-features.php">Original new features found in v5.0</a>
VisiWave Blognospam@example.com (Administrator)2019-01-09T16:12:00Zhttps://www.visiwave.com/blog/wfwcomment.php?cid=340https://www.visiwave.com/blog/rss.php?version=1.0&type=comments&cid=34VisiWave Site Survey v5.0.8 Released
https://www.visiwave.com/blog/index.php?/archives/33-VisiWave-Site-Survey-v5.0.8-Released.html
A maintenance release of VisiWave (v5.0.8 ) is now available for download. If you already own v5.0 of VisiWave, just download the eval version and install it over-top of your current version. Your existing license will continue to work. If you would like to evaluate VisiWave, just download the eval version and try it out.<br />
<br />
New features in v5.0.8:<br />
<ul><br />
<li>Predictive Surveys<br />
<br />
VisiWave Site Survey Pro now supports predictive surveys as<br />
well as traditional surveys. A predictive survey is when you<br />
describe the barriers (walls and other solid objects) in the<br />
survey area and the location and characteristics of one or<br />
more access points and then run a theoretical simulation of<br />
how radio waves would propagate through the survey area.<br />
It is a way of estimating wireless coverage without having to<br />
collect survey measurements in the real world. This is<br />
useful for dealing with buildings that haven't been built yet<br />
or for doing what-if analysis for existing areas that can't be<br />
easily modified.<br />
<br />
<li>Difference Heatmap Legend Issue<br />
<br />
There was an issue where the legend of a difference heatmap<br />
would only allow you to see the positive values. Now the full<br />
range of positive and negative numbers can be seen.<br />
<br />
</ul><br />
<br />
New features in v5.0.5:<br />
<ul><br />
<li>Issue with PDF Floor Plan Image File Names<br />
<br />
If the name of a PDF file with non-ASCII characters was used<br />
as a floor plan image, loading that image might have failed.<br />
Now any characters can be used in the file name.<br />
<br />
<li>Issue with Duplicate AP Names Appearing in AP List<br />
<br />
When capturing survey data, the same APs could appear many<br />
times in the AP List. This might happen if a virtual AP<br />
continuously changes an AP's SSID in between scans. Now the<br />
AP List is updated to show the most recent SSID for the AP.<br />
<br />
<li>Issue Using Left/Right Arrow Keys to Move from Point to Point<br />
<br />
Fixed an issue where VisiWave could randomly crash when<br />
selecting a data point in Survey View and then pressing the<br />
left or right arrow key to move to the previous or next data<br />
point.<br />
</ul><br />
<br />
New features in v5.0.4:<br />
<ul><br />
<li>Support for Large Floor Plan Image Files<br />
<br />
If an image file is too large for the amount of memory your<br />
computer has, VisiWave now automatically reduces the size of<br />
the image so it will work. Typically images that are 4000<br />
pixels on a side or less work fine. Larger images might get<br />
automatically resized to around this width or height. You can<br />
see the final image size by selecting Set Scale.<br />
<br />
<li>Wrong AP#'s Listed in AP List in PDF Reports<br />
<br />
If you generated a PDF report, the numbers listed for each AP#<br />
was off by one on AP List report pages.<br />
<br />
<li>MAC Addresses Given Wrong Name for Locally Administered Names<br />
<br />
If an access point generates a Locally Administered MAC<br />
address, VisiWave would sometimes give this AP the wrong<br />
manufacturer name. Now Locally Administered addresses<br />
start "local:".<br />
</ul><br />
<br />
New features in v5.0.3:<br />
<ul><br />
<li>AP Marker Custom Names in Report View Were Incorrect<br />
<br />
If you set a custom name on an AP Marker, save the survey file<br />
then reload the survey file, the custom names won't be correct<br />
when viewed on any report pages.<br />
<br />
<li>Data Points Where Nothing Was Seen Were Not Contributing to<br />
Heatmaps<br />
<br />
If a data point that was collected but no access points where<br />
seen at that location then that point was just skipped when<br />
calculating a heatmap. Now that point contributes to the<br />
heatmap by saying there is no coverage there.<br />
<br />
<li>Changing the Survey Map Image Could Stretch Report Images<br />
<br />
If you changed the survey map image file on an already<br />
existing survey file, the width or height of a report image<br />
would be wrong if the aspect ratio of the new image didn't<br />
match the aspect ratio of the old image.<br />
</ul><br />
<br />
New features in v5.0.2:<br />
<ul><br />
<li>Failed to Load v4.0 Survey Files With "AP#'s" in Caption<br />
<br />
Trying to load a survey file created with an earlier version<br />
of VisiWave would fail if the string "AP#" occurred in<br />
any caption or text description unless the string was<br />
followed by a number.<br />
<br />
<li>Issue When Generating Report With Legend Tab Outside Range<br />
<br />
There was an issue with generating a report when the legend<br />
for a heatmap had one of the tabs outside of the Min/Max<br />
range of the color legend.<br />
<br />
<li>Generating PDF Report Would Randomly Fail<br />
<br />
An uninitialized variable would cause generating a PDF report<br />
to randomly fail.<br />
<br />
<li>Changing the Survey Map Image Could Stretch Report Images<br />
<br />
If you changed the survey map image file on an already<br />
existing survey file, the width or height of a report image<br />
would be wrong if the aspect ratio of the new image didn't<br />
match the aspect ratio of the old image.<br />
<br />
<li>Loading v3.0 Survey Files Could Cause Data Points to be in the<br />
Wrong Location<br />
<br />
Survey files created using v3.0 or earlier of VisiWave did not<br />
contain the floor plan image file, but rather the filename of<br />
the image file. If that filename is no longer valid, then you<br />
are prompted to pick the right image file. Doing this in v5.0<br />
would cause the data points to not be located in the correct<br />
locations.<br />
</ul><br />
<br />
New features in v5.0.1:<br />
<ul><br />
<li>Can't Add Data Points After Loading an Empty v4.0 Survey File<br />
<br />
If you load a survey file created by v4.0 of VisiWave that<br />
didn't have any data points in it already, then adding a data<br />
point to it would give you the error message "Encountered an<br />
improper argument".<br />
<br />
<li>Issue Selecting Interference Tab After Stopping Continuous Capture<br />
<br />
If you switched to the Interference Details Tab after stopping<br />
a Continuous mode data capture it could cause a crash.<br />
<br />
<li>Issue Setting the Name Property On a New Survey<br />
<br />
On a new survey file, if you selected a floor plan image file<br />
and set the "Name" property on the Name tab, then VisiWave<br />
would show an error or crash.<br />
<br />
<li>AP Names Sent from the AP Controller Were Not Presenting Correctly<br />
<br />
The character conversion of AP Names sent by the AP controller<br />
where not using the correct conversion and could end up<br />
looking like Chinese, Japanese, or Korean characters.<br />
<br />
<li>Issue Loading and Saving Report Templates<br />
<br />
Loading or saving Report Templates by pressing the Templates<br />
button in the Report View wasn't working correctly.<br />
<br />
</ul><br />
<br />
<a href="http://www.visiwave.com/wifi/visiwave-v50-features.php">Original new features found in v5.0</a>
VisiWave Blognospam@example.com (Administrator)2018-12-10T19:50:00Zhttps://www.visiwave.com/blog/wfwcomment.php?cid=330https://www.visiwave.com/blog/rss.php?version=1.0&type=comments&cid=33