My personal wireless blog

Ekahau Customer Report Template – Loops & APs

Let’s start with the second part of my Ekahau Customer Report Template tutorial.

We know already from the first post, how to create heat maps and show the requirements. As you maybe already notice, the heat map is generated for one floor. If you have more than one floor, you need a loop or just the first floor is shown.

You can generate loops of different kinds. As first loop we’ll use the “floors” loop.

Show AP information

Now we can create heat maps of different types for different floors. But it’s usually needed to create a list of my access points. For this, we’ll work again with a loop. But now the type is “aps”.

Do show you the easy way, I don’t use the created template with the heat maps. We’ll start with a new file.

<#“loop-start”: {”type”: ”aps”}#>

<#${ap-name}#>

<#“loop-end”: {“type”: “aps”}#>

This show you the names of all access points in your file.

We can now filter to show just our own access points.

<#“loop-start”: {”type”: ”aps”,

“filter”: {

“include”:{

“owner”:”my”

}}

}#>

<#${ap-name}#>

<#“loop-end”: {“type”: “aps”}#>

Take a look to the second result, the „Not my AP“ is missing:

The access point information’s are Data Tags. You can see the different values in the User Guide. You can also create a template for site survey and a second on for simulation. In the simulation template you can show the „tx power“ and „antenna height“ from the simulation.

All in one report

In the last step we’ll now merge all this information to one report. I’ll use the sample where I show all information per floor. We’ll now also include the AP loop inside of the floor loop. This will show the APs on a per floor base.

Summary – Ekahau Customer Report Template

I show you some functions of the Ekahau Customer Report Template. But there is a lot more you can do with. The best of all, you can combined almost every loop, filter and information. As I show you, we use the same loop for the AP name. But it show us different information, because we use it in the final version inside a floor loop.

And now some tips from me:

Read the user manual, it shows you all information

Begin with small templates (the only bad part of this report function, debugging is not so easy)