Setting up your Calibur system

How to start fencing anywhere, anytime? Here’s your quick guide to setting up your Calibur pocket boxes!

To have a more in-detail guide, take a look at our user manual, or contact our customer support at

Firmware update

What is the firmware and why is it important? Here’s your quick guide to update your firmware for getting the most out of your wireless fencing experience!

The firmware is a software that runs on your Calibur pocket boxes. It is important to keep the Calibur application, as well as the firmware updated, because we are constantly working on making Calibur easier to use while adding more features and with each update, you will get more out of your device!

To have a more in-detail guide, take a look at our user manual, or contact our customer support at

Don't miss out on our summer sale

Hints & tricks - guide to avoid errors

The aim of the Calibur system is to make fencing available for anyone, anytime, anywhere. In order to make this feature, we had to design a complex way of registering hits and transferring information.

Because of this, there are some, not so obvious ways in which Calibur differs from other scoring methods. Here, you can find a list of some elements that cause no problem while fencing, but sometimes are unusual to our users.

Most of the issues listed here can be avoided by testing your equipment in testing your equipment in full fencing uniform, in a realistic setting.

Bellguard for foil

With some equipment, bellguard distinction on foil has minor issues. We recommend that if you experience such things, turn on the switch for "register on-target hits for bellguard".

This also resolves the problem if you see that at some point, if you are sweaty enough (which means that your gloves are dripping wet), valid hits on you do not register as they should. This can also be resolved with a dry glove too though.

Bellguard for épée

One small bug that might occur is that if you test your épée's bellguard barehanded, while keeping the other weapon's point on it, it registers as valid. This is really easy to avoid, since in a realistic situation, since either putting on gloves or using a quick thrust never results in this error.

Testing without gloves extremely slowly can light the screen
Always test in realistic situations

Speed of registering hits

If you find that registering hits is somewhat slower than it is with the traditional scoring machines, you can augment the speed by:

Overwhelmed hardware can cause delay in regsitering

Things to pay attention to when testing foil

In some situations, you may experience peculiarities, but only in circumstances that are extremely rare during fencing, and in case they would occur, it’s probable that no points would be given anyway by a referee.

To avoid misleading test results,

Slower than realistic hits can cause error
Test equipment with a quick thrust to avoid error

+1 Hint for athletes: to eventually get better at competitions, you can do more besides training. Get an insight into your daily, weekly, monthly and yearly performance by using sports analytics tools - the most simple one is keeping a log about your bouts (on training and competitions too). Find out how Calibur's bout tracking system works and do everything you can do for that medal!

To have a more in-detail guide, take a look at our user manual, or contact our customer support at

Don't miss out on our summer sale

Remote & referee app

How to use the Remote & referee app

Did you know it was possible to use remote controls for the Calibur scoreboard to start and stop the timer, add or deduct points, penalties, bouts and priorities? Here’s your quick tutorial on using the Calibur Remote Control Mode!

Toggle the remote slider in the mode selectord
Setting the scores, adding cards etc

Useful Hint:

Network speed and your hardware can influence the speed of registering commands; if you wish to improve it, try to close every other application and use a stable network without many users (offline hotspot is also an option).

To have a more in-detail guide, take a look at our user manual, or contact our customer support at

Don't miss out on our summer sale

Lessons from the first broad testing #1

Last week we introduced the Calibur pocket box. It is once again a major leap in product design and features. Testing it is the last step before actual production. 

The plan is something like this: 
1.Build a very reliable, stable and accurate device
2. Use that basis to build on all the smart features in the application. 

We ran a broad épée test back in November which served as a way to pinpoint the weaknesses, analyze the data and incorporate it into a new device.  It’s worth summarizing the major takeaways. Today we’ll cover technical issues and how we addressed them:


Let’s jump start to connectivity. Connectivity is the bread and butter of a wireless system. You can only make wireless as good as the quality of connection is. It is judged by 2 factors: stability and latency. To put it more simply how often the connection drops and how much time it takes for a hit to display. The boxes we shipped in November had inconsistencies in both fields, so we put a lot of effort in fixing it.

Testing connectivity in different setups and distances


In general Apple devices disconnected much sooner than the ones with Android, but we were able to improve on both systems. The development is pretty obvious on this part, we were able to drive down drops to practically 0. Tested on a dozen different, low-end to high-end phones and tablets connection always remained active. The challenge is now to find an otherwise well-functioning phone that fails this test and I’m happy to tell that we haven't find one.


The latency is a bit more complex issue. How long is good enough actually? We found that the threshold for unnoticeable delay to be around 100ms. 

The results are again very promising. The delay dropped significantly and stayed low up until around 15 meters. So now it is up to the phone to process it.

Getting the phone's processing time down proved to be harder to optimise than anticipated. But it’s clear that the delay is mainly caused by the application now which will perform much better after restructuring. More on that later.


The idea that accuracy is based on the utilization of the data pool is a sort of chicken-egg problem. To have people using the devices they need to be enjoyable. To be enjoyable people need to use it. So the deal with the broad épée test was that people would be using them even when it’s not so enjoyable and we will quickly follow-on with updates and by the end of the test they will become quasi-replacement for any system on épée.

After a very strong start, restrictions started to kick in in December basically everywhere and the incoming data started to slow down. But we still managed to get thousands of bouts and tens of thousands of touch data. Huge thanks to our testers for keeping up despite all the hurdles! Two things became clear: 1. That the data will be not sufficiently big with the current model (it's not just a matter of the total volume but the constant flow, to make comparison after every version) and 2. that we certainly underestimated how much work it will be to maintain a system and to develop a new one parallel. So we moved forward and put the focus on incorporating the existing data into the next version.

touching plastron, mask bellguard then interchanging the weapons.

The goal was to make accuracy high enough so that fencers will enjoy using the devices in training sessions and the rest of the data will come much easier. The 2 major questions in accuracy are: does it go off when it shouldn’t and do we need calibration to avoid that? We were able to improve tremendously on both aspects. 

TLDR: The general direction is very clear latency is down, accuracy is up. We are getting through the 3rd wave (so far) of the pandemic and with local clubs shut down, it's more tricky to find the ways for sufficient testing. In our testing the system works well in 90-95% of the cases. So the job for the AI is to close the remaining gap particularly on rare cases. Global testing will start next month with the goal of finding the outlier cases. As soon as the data feed start to improve again so will the system.

In the next posts we will cover the general feedback and future features but for ending watch this video of a short bouting in the office.

short bout in the office
    Your Cart
    Your cart is emptyReturn to Shop