News Categories
ByteBlower Release 2.19
Posted by Craig Godbold on 24 October 2022 08:17 AM

Dear Excentis Customers,

This month sees new releases for all things ByteBlower!

1) ByteBlower GUI,  2) ByteBlower server, 3) ByteBlower Endpoint, 4) API, and 5) CLT are all running version → 2.19

The download links can be found at our setup pages.

So what changes have we made?

Two significant improvements that have been added are: Cancelling Byteblower Endpoints midtest and Average TCP RTT measurements.

Cancelling Endpoint Tests

ByteBlower Endpoints used to go into "Silent Mode" while a test scenario was running. Not anymore! You can now configure the scenario heartbeat interval, and maintain connectivity with each Wireless Endpoint:

This is optional and can be configured for different time intervals. The heartbeat is set as default. 

Sometimes you have a test running and realise that you want to modify some settings and start all over. You will now be able to cancel them from the GUI without having to physcially access the device and cancel the Endpoint app. This is particularly useful if you run longer duration scenarios.

This has also been added to our API.

Customers who wish to use this feature need to update server, GUI, endpoint app and API (if using API).

Average TCP RTT

We have added more TCP Roundtrip statistics in the HTML, CSV and JSON report

  • Time To First Byte (TTF): Is the time it takes for the first TCP payload byte to reach the client. This matches the T2 timestamps mentioned earlier.
  • Minimum RTT: Is the shortest round-trip time throughout the lifetime of the session.
  • Average RTT: The average round-trip time throughout, again over the whole lifetime of the TCP session.
  • Maximum RTT: Finally the longest round-trip time encountered during the session.

The average RTT is now taken over the whole snapshot. The intermediate results can be seen in the HTML report 

CLT Exit Codes

We have now added exit codes for the CLT. After the CLT finishes, it returns a numeric value. This value can be used to verify that the test scenario finished successfully.

For more information about these changes as well as other improvements and bug fixes, please refer to the following changelog and knowledgebase article links:

GUI changelog 2.19

Server changelog 2.19

Endpoint changelog 2.19

API changelog 2.19

Introduction to the CLT

If you have any questions please contact us at

Comments (0)

We to help you!