Knowledge base : Knowledge Base > ByteBlower > Creating and running a test

Sometimes you have a test running and realise that you want to modify some settings and start all over.
Then you want to cancel your active test:

ByteBlower Endpoints can be canceled remotely since version 2.19.0.

You can now choose if you want the ByteBlower Endpoint to

  • keep contact with its MeetingPoint at regular intervals ("Heartbeating Mode")
  • remain completely silent ("Silent Mode")

Every heartbeat signal is an opportunity to exchange information. This way, a command can be sent to each ByteBlower Endpoint to cancel the running scenario.

Heartbeating Mode

  • In the GUI, you can configure this here, under File>Project Properties>Scenario:

    When enabled, you you can cancel tests from within your GUI. 
  • In the API, you can configure this by using the ScenarioHeartbeatIntervalSet command on a ByteBlower Endpoint.  It has one argument, representing the interval in nanoseconds.

Silent Mode

For some tests, it is crucial that the configured test traffic is the only network traffic. 

  • In the GUI, you can configure this here, under File>Project Properties>Scenario:
  • In the API this is the default behavior.

Old versions

In old ByteBlower Endpoints, with a version before 2.19.0, the app stopped heartbeating to the Meeting Point while a test scenario was running. While running a test, all ByteBlower Endpoints went into "Silent Mode".
This behavior was chosen because it often is undesired to have additional management traffic on top of the actual test traffic.

The downside of this is that you have to wait until the end of the test until the Wireless Endpoint becomes reachable again. So, you can not cancel such a test remotely.
If you want to cancel the test, you have to walk to each Wireless Endpoint, and push the "Abort" button.

The ByteBlower Wireless Endpoint is software that turns your mobile devices into ByteBlower Ports.
With minimal effort, you can integrate iPhones, iPads, Windows phones, Android devices, but also Linux machines, MacBooks, Windows PCs, ... into your network test scenarios.


The Wireless Endpoint runs on your SmartPhone, tablet or Laptop; it's the software that generates the testing traffic. You need to install the Wireless Endpoint on all devices you want to test. This Wireless Endpoint software is available for free on all major app stores. You can find the download links collected in the website below.

Tests are organized from the ByteBlower chassis. For the Wireless Endpoint to become active it needs to reach the management connection of the ByteBlower. When possible, we suggest connecting the second management interface into the Access Point. This is the Lan only option explained in the the link below:

On the ByteBlower chassis, it's the Meeting Point software that does the interaction with the Wireless Endpoint. It can be installed on any ByteBlower server when you have a valid license for it.

Basic Workflow

Setting up a Wireless Endpoint is identical on all supported devices.

Start the Wireless Endpoint

Enter the IP address of your Meeting Point. This is required the first time only. Next time, the app will fill in the previously used address by default.

Push the button to go to the next page to connect with the Meeting Point.
The Wireless Endpoint connects with the Meeting Point, and reaches the "Registered" state.


On top of the screen, the Wireless Endpoint displays its current state. There are five possible states

  • Ready - waiting until you enter the IP address of the Meeting Point.
  • Contacting - establishing a connection with the Meeting Point.
  • Registered - initial handshake with the Meeting Point succeeded. From now on, the Wireless Endpoint can be controlled using your GUI. The Wireless Endpoint starts sending heartbeat messages to the Meeting Point, to signal that it is still alive.
  • Armed - when you run a test scenario using the GUI, the entire set of instructions for this device is transmitted at the beginning. When all instructions are received, the device goes into the Armed state. Now, the Wireless Endpoint becomes quiet, and will no longer send heartbeat messages, so that the test traffic is not disturbed.
  • Running - when the start time has come, the Wireless Endpoint will begin sending/receiving network traffic.

At the bottom of the screen, there is an Abort button. When you push this button, the Wireless Endpoint will go back from the Registered to the Ready state. When in the Armed or Running, the Abort button is disabled.

For more information, have a look at this article: Wireless Endpoint States


From now on, you can sit back and control the entire test process using your GUI.
All you need to do is adding the Meeting Point in the Server View.

All connected Wireless Endpoints become visible.

Now you can dock ByteBlower Ports on your Wireless Endpoints to integrate them into your test scenarios.

Running Test Scenarios

When you start a test scenario using Wireless Endpoints, the Meeting Point will automatically initialize all Wireless Endpoints.
All Wireless Endpoints go into the "Armed" State.

While the actual test is running, there is complete radio silence between the Meeting Point and the Wireless Endpoints.
This way, the network test traffic itself is not influenced by any unwanted signals.
When you look at the Wireless Endpoint while a test is running, you can see the Current Speed.

After the test finishes, the Meeting Point gathers all results from the Wireless Endpoints.
And then the report is generated.

Have a great time using our Wireless Endpoints !

On this page you find the latency noise floor of the ByteBlower systems. This provides the lower bound of what can be reliably measured.

Better performing systems are found on the left side.

How to Install and Run a Simple Test on the Wireless Endpoint App

The purpose of this article is to help you get started with the 'Wireless Endpoint' app easily and efficiently and run your first test!

The  app is a very convenient and useful tool which helps the user test a wireless device or a range of devices and compare their performances. In this article we will create a simple test example that sends traffic from a 'server' to a device connected to WIFI. 

We will cover  ⇒ 

                                  1) Downloading the app and connecting your device(s) to the ByteBlower server

                                  2) Creating and connecting ports

                                  3) Setting up test parameters

                                  4) Running the test

                                  5) Troubleshooting


 ⇒    Let's go!


Step 1 - Setting Up the Wireless Endpoint App


1.1 Downloading the App


Go to and scroll down to the relevant operating system for your device(s).

You will see a list of options to download the wireless endpoint app. These are either from an app store or direct downloads. 


App Store Downloads

  • If you are using a mobile Android device → Click on 'Google Play'   → Click 'Install'          
  • If you are using a mobile IOS device → Click on the 'App Store'     → Click 'Install'


Direct Downloads


  • If you are using a Windows PC or a Mac → Click on     

  • If you are using Linux → Follow the appropriate instructions in the Linux section (either Debian/Ubuntu or Fedora)



          ⇒  Download the app to your device


1.2 Connect the App to the ByteBlower GUI


Once you have successfully downloaded the wireless endpoint app, you will see the meeting point software (see below). 


Here you have two choices ⇒


                                                1) Enter the IPv4 address of your ByteBlower server.

                                                2) Enter the name of your server if it has a fully qualified domain name (FQDN).




A laptop with Windows 10 is the device under test (DUT) in this demonstration.