The actual times seems better for sport timing and we all hope that things will keep going this way.

The first six month of 2022 have been a great period for Wiclax improvements and addition of new features. Most of them have been released along the way in the current public version but they have not been publicized so far.

We will now go back to a public version and a beta version for new developments.

Performances improvement

A great job has been done to improve the performance for massive events with many check points, races and competitors. Some bottlenecks have been identified and solved.

This work will continue in the coming month.

Hardware implementation

Feibot active and passive system are now integrated in Wiclax, both with local connection and through our cloud.

Decoders and trackboxes can now send their data directly to our cloud, giving a peaceful and instant way of retrieving remote split points data.

Dag system was already present in Wiclax for long but now the direct connection to the chronobox finds its place back with the historic connection to Dag center. There is no longer need to use the generic acquisition.

Partnership with Betrail 

Betrail team is encoding trail results from France, Belgium, Nederland and Luxembourg. Following a collaborative work between our teams, you can now access information for most of your runners, and display it on your website, like below.

Computed custom data

You've always wanted to calculate your own data in Wiclax, the way you would do in Excel? That's now possible! 

Customized live screen online

Customized live screen allows you to build the perfect screen to display the result of a particular race. We have simplified the way they can be displayed on your website. You can simply push them from the Web publication windows. You can upload many of them and even overwrite the usual live windows.

Reworked saving, backup and FTP transfer

Again, we have done a hard job to improve saving and FTP syncing.
They are no longer dependent.
Syncing well be done in an automatic way every 3 minutes. If you need to update earlier, for the first finishers for example, you can still force the FTP export with the button.

Backup is improved a lot. It keeps easy to make regular backup but the best thing is that you can now reload a backup while the timing is on. You will keep everything running (decoders connection and g-live).

UCI stages race - stage summary improvement

We've worked hard to make the outprint of the stage summary even more practical and customizable.
Among other things it is now possible to break page after a classification.

For UCI stages race, we also have improved the way you can deal with falls in the last kilometers and added a new way to enter the secondary ranking has been introduced.
Many of you might have already seen this throught the dev version.

Interesting developments are on their way to edit communiqué for UCI races. It will be available in the next release.

For more information about this new release, you can also refer to this page on our website : Wiclax - Versions

The Wiclax team.

We are often asked if Wiclax can interface with RFID readers present on the industrial market.

Indeed, it can be tempting, to start sports timing, to order directly online an industrial RFID reader, manufactured by Impinj, Zebra, ThingMagic, Alien or another less known brand.

But at Génialp, we consider that working directly with an RFID reader by controlling it from a PC is not a professional way to time a race.

There are several reasons for this:

First of all, we believe that a timing device should be self-contained and should not rely on a PC to be set up and to start reading the electronic chips.

Secondly, we believe that timing equipment should be able to store all the chip readings it takes during timing and should be easily interrogated after timing. This is essential if there is a computer or network problem during the event, which can always happen. It is better to have rankings with a little delay than no rankings at all.

To be well designed, a timing box must therefore integrate a micro-controller which will allow the reader(s) to be set up (reading power, antennas activated/deactivated, box time, etc). It is this micro-controller that will dialogue directly with the RFID reader. Depending on the reader, it may use a standard communication language (LLRP), or a proprietary communication protocol.

The second role of the micro-controller will be to communicate with your computer and more particularly with the timing software. This is where Wiclax comes in.
Each manufacturer of RFID timing equipment has its own communication protocol for the software. But there are always at least frames that send the chip number and the time of the box at the time of reading. In general, it is also possible to read the time from the box and set it from the PC. And of course, it is possible to request all the chips read by the box afterwards, in case for example any problem has occurred during the race.

These are the main reasons for not using a reader directly. But there are several others. A modern timing box integrates a number of other elements that make timing reliable and easy.

First of all, there is energy management, with the integration of batteries and a display of the remaining charge.
There will also often be an integrated modem router to send data directly to a cloud (either Genialp's or the manufacturer's). This is an essential element for remote pointing.
Or a GPS module to automatically set the time on the box.
And of course, on most equipment, you will find a man/machine interface consisting of a screen and a few buttons for displaying and modifying the box's information.

 Example of a fully integrated UHF RFID timing system (URTime - but there are many others).

On the one hand, we have the RFID timing hardware, whose role is to dialogue with the reader(s), to record all the readings in an internal memory and to send them in real time or deferred to the software.
On the other hand, we have the software (Wiclax), whose role is to retrieve in real time (or deferred in degraded mode) the raw information from the box and to process it to establish a ranking and broadcast it in real time on different media.

These are two different missions.

And that's why we don't develop direct connections with readers coming directly from the industrial market. It is not Wiclax's job to manage the setup and start-up of the RFID reader.
Nevertheless, for those who would like to try the adventure, we have integrated a dll allowing to establish an LLRP connection with RFID readers. You will find a dedicated acquisition type in the software.
In conclusion, we invite you to discover the offers of the major integrators in the market.
They bring years of experience and will probably not cost more than your own R&D.
We are talking about experience. We developed our own low frequency system with Texas Instruments drives many years ago. We were happy to use fully integrated systems afterwards!

On nous demande souvent si Wiclax peut s'interfacer avec des lecteurs RFID présents sur le marché industriel.

En effet, il peut être tentant, pour commencer le chronométrage sportif, de commander directement en ligne un lecteur RFID industriel, fabriqué par Impinj, Zebra, ThingMagic, Alien ou une autre marque moins connue.

Mais à Génialp, nous considérons que travailler directement avec un lecteur RFID en le pilotant depuis un PC n'est pas une manière professionnelle de chronométrer une course.

Il y a plusieurs raisons à cela :

Tout d'abord, nous estimons qu'un matériel de chronométrage doit être autonome et ne doit pas reposer sur un PC pour être paramétré et pour commencer à lire les puces électroniques.

Ensuite, nous estimons qu'un matériel de chronométrage doit être en capacité de mémoriser toutes les lectures de puces qu'il réalise pendant le chronométrage et doit pouvoir être interrogé facilement après le chronométrage. C'est essentiel si on connait un problème d'ordinateur ou de réseau pendant l'épreuve, ce qui peut toujours arriver. Mieux vaut des classements avec un peu de retard que pas de classement du tout.

Pour être bien conçue, une box de chronométrage doit donc intégrer un micro contrôleur qui va permettre de paramétrer le ou les lecteurs (puissance de lecture, antennes activées/désactivées, heures de la box, etc). C'est ce micro contrôleur qui va dialoguer directement avec le lecteur RFID. Suivant les lecteurs, il peut utiliser un langage de communication standard (le LLRP), ou un protocole de communication propriétaire.
Le deuxième rôle du micro-contrôleur va être de communiquer avec votre ordinateur et plus particulièrement avec le logiciel de chronométrage. C'est là qu'intervient Wiclax.
Chaque fabriquant de matériel de chronométrage RFID a son propre protocole de communication à destination des logiciels. Mais on retrouve toujours au minimum des trames qui envoient le numéro de puce et l'heure de la box au moment de la lecture. En général il est aussi possible de lire l'heure de la box et de la régler depuis le PC. Et bien sûr, il est possible de demander l'ensemble des puces lues par la box a posteriori, dans le cas par exemple où un problème quelconque est survenu pendant la course.

Ce sont là des raisons essentielles pour ne pas utiliser directement un lecteur. Mais il y en a plusieurs autres. Une box de chronométrage moderne intègre un certain nombre d'autres éléments qui rendent le chronométrage fiable et aisée.

On retrouvera d'abord une gestion de l'énergie, avec l'intégration de batteries et un affichage de la charge restante.
On aura également très souvent un modem routeur intégré pour envoyer directement les données sur un cloud (celui de Génialp ou celui du fabricant). C'est un élément essentiel pour les pointages distants.
Ou encore, un module GPS permettant de régler automatiquement l'heure de la box.
Et bien sûr, sur la plupart des matériels, vous retrouverez une interface homme/machine constituée d'un écran et de quelques boutons permettant d'afficher les informations de la box et de les modifier.

Exemple de système de chronométrage UHF RFID complétement intégré (URTime - mais il en existe de nombreux autres).

D'un côté, nous avons donc le matériel RFID de chronométrage, dont le rôle est de dialoguer avec le ou les lecteur(s), d'enregistrer toutes les lectures dans une mémoire interne et de les envoyer en temps réel ou en différé au logiciel.

De l'autre coté, nous avons le logiciel (Wiclax), dont le rôle est de récupérer en temps réel (ou en différé en mode dégradé) les infos brutes en provenance de la box et de les traiter pour établir un classement et le diffuser en temps réel sur différents media.

Ce sont deux missions différentes.

Et c'est pour cela que nous ne développons pas de connexions directes avec les lecteurs provenant directement du marché industriel. Ce n'est pas le métier de Wiclax de gérer le paramétrage et le démarrage du lecteur RFID.
Néanmoins, pour ceux qui voudraient quand même tenter l'aventure, nous avons intégré une dll permettant d'établir une connexion LLRP avec des lecteurs RFID. Vous trouverez un type d'acquisition dédié dans le logiciel.

En conclusion, nous vous invitons à découvrir les offres des grands intégrateurs du marché.
Ils apportent des années d'expérience et ne seront probablement pas plus cher que votre propre R&D.
Nous parlons d'expérience. Nous avions développé notre propre système basse fréquence avec des lecteurs Texas Instruments il y a de nombreuses années. Nous avons été heureux ensuite d'utiliser des systèmes complétement intégrés !

Bringing the power of a desktop application and the flexibily of the cloud in the same tool : that is what we strive to do with Wiclax.

Today, after great feedback from our beta testers, we are pleased to offer you a new feature : the ability to enter new competitors from a web browser, wherever you are, as long as you have internet access.
This feature is also extended to the entry of DNF.

Note that the purpose of this feature is to allow entries to be made from several sites before the start of the race. The ambition is not to make it an online registration system.

How to set up the entry of competitors through the cloud ?

• The feature is associated to the "Live" option of the Wiclax licence.
• In the "Registrations" tab, click the Network icon and activate the entry data edition via Internet.

In the network menu, you can find the URL to access the entry/modification of the participants of your event along with a unique access code by event.

The windows looks exactly like the existing one for the local access.
It enables the entering of all the competitors data. The age group is worked out and displayed automatically.
According to the setting, the next available bib number is affected or it is possible to edit it.

A lookup function allows to select a participant that is already registered and to modify him.

The entered competitors will appears directly within Wiclax with a mark indicating that the data comes from an external source.

And to finish on the subject, a menu on the side of the window allows to visualize a history of the entries and to open a new window to enter runners in abandon.

Apporter la puissance d'une application bureau et la souplesse du cloud dans le même outil : c'est ce que nous nous efforçons de faire avec Wiclax.

Aujourd'hui, après des retours très positifs de nos beta testeur, nous sommes heureux de vous offrir une nouvelle fonctionnalité : la possibilité de saisir de nouveaux engagés depuis un navigateur, où que vous soyez, pour peu que vous ayez accès à Internet.
La fonctionnalité est également étendue à la saisie des abandons.

Notez que l'objectif de cette fonctionnalité est de permettre de saisir des engagés depuis plusieurs sites avant le départ de la course. L'ambition n'est pas d'en faire un système d'inscription en ligne.

Comment mettre en œuvre la saisie des engagés via le cloud ?

• la fonctionnalité est associée à l'option "Live" de la licence Wiclax.
• dans l'onglet "Engagement", cliquez sur l'icône Réseau et activé l'édition des données d'inscription en réseau via Internet.
  
  

Dans le menu réseau, vous pouvez retrouver l'URL d'accès à la saisie/modification des engagées de votre épreuve ainsi qu'un code d'accès unique par épreuve.

La fenêtre qui s'ouvre se présente exactement comme celle qui existe déjà en accès local réseau.
Il est possible d'entrer toutes les informations d'un coureur. Sa catégorie est calculée et affichée automatiquement.
Suivant le paramétrage, le dossard suivant immédiatement disponible est affecté ou il est possible de l'ouvrir à la saisie.

Une fonction de recherche permet de sélectionner un coureur déjà engagé et de le modifier.

Les coureurs saisis apparaîtront directement dans Wiclax avec une marque signalant que la donnée provient d'une source extérieure.

Et pour finir sur le sujet, un menu sur le côté de la fenêtre permet de visualiser un historique des saisies et d'ouvrir une nouvelle fenêtre pour saisir des coureurs en abandon.

All about keeping the pace, despite all. So here we continue with an additional release upon our successful v9. Wishing it to add up on the software strong basis - with a number of fixes included - and to continue bringing valuable new features for all of you.

As usual, a list of things to extend the range of race configuration possibilities and to maximize the ergonomics of the solution - not to say the pleasure to use it.

Some new implementation for acquisitions

The BeChronized acquisition is updated to comply with the new system Ceres G3.

Still through the same Online passings acquisition, you can connect to DotVision API and take advantage of their geo-fencing timing capacities. The passings get down to your event file just like any regular acquisition.

Tag Heuer devices equipped with a modem can be set up to synchronize their data with your Génialp cloud service. Backup and import service, but best of all instant forward to your Wiclax event. More to see in your service administration page if you're still to discover it.

New design extensions for G-Live

No new release without bonus gifts to the most visible part of the solution! We've worked this time on these topics, as you've probably noticed already through our Facebook posts:

Athletes pictures

Making some progress on this feature, aiming to enrich your results online with some pictures of participants.

Currently possible in one way, which reuses the fact that the athlete summary is looking for a <bib-number>.jpg file in the event folder. In case the picture found is less than 150px, it's assumed it's something like a user profile picture and is positioned and styled this way:

Of course limited as you won't often have such a set of pictures, named after bib numbers. So we're working on more flexible options like looking up in a centralized folder, having something else than the bib as an identifier, or calling a custom URL that will return an image (from a DB or whatever). More on that soon, waiting for that don't hesitate to share your own use cases.

Custom color palette

Want to present your race results in a more colorful way, or to get them closer to your brand colors? This is now possible! More information about it in this post.

New settings menu

The new menu - intended to remain discrete on the main page - gives a definitely simpler access to those features mainly useful on the local area: switching the dark/light color themes, running the TV mode - auto scrolling or not.

Points on rankings

2 different concepts are getting developed in parallel:

• Some points based events, where point values are the primary ranking criteria and they actually replace time performances. Available from the Points ranking entry of the event creation assistant. So far intended for some collateral use cases when you need to publish such a ranking. Latest changes allow the points entry through the result input form or through data file import.
• A points allocation as a secondary data, when the primary ranking is still based on timing.

This second concept is now coming live, opening some new possibilities to manage sports where points are participating to the rankings.

Some details about the implementation:

• A new Points tab in the event options form allow for specifying which point values are allocated. Based on final ranks, and point series can be specified either globally or based on rank by category/by level group.
• As of now the allocation is applied after a manual action and not automatically (exception made of an allocation on the general ranking).
• A new Points column can be displayed in the result grid. If necessary, some point values can be entered manually in grid cells.
• Different point series can be specified by stage/heat in a stage race, and the general ranking can be set to be calculated on points (i.e. the sum of points for each stage is used to order the ranking).
• A team ranking can be set to be calculated from individual point values (note that the previous point allocation grid that was there is now moved)
• An option of the Championship module allows it to work on point values extracted from the events, instead of being (re)calculated locally.

Passings to ignore on acquisitions

Useful feature when an acquisition is running as an automated file import, or is plugged on a cloud data service: when a passing has to be eliminated for some reason, the risk exists that it keeps coming down again and again if it's still in the original data and in the time period scope.

To avoid that, you can now put an 'ignore' flag on some passings from the history.

New menu is available at the bottom of the result entry form, below the time lists. Click All first to display the whole history and then you can locate some records by filtering a bib number for example.

Miscellaneous

On printout: ability to print only selected rows from the current grid. Simply by launching a print preview after selection is made. A confirmation will be prompted.

Team ranking: for the case of a points based ranking, you can now specify a number of best results to keep.

Emails: new context menu item Send an email for a competitor or a selection of competitors in the grid. Opens the system's default mail client and initializes the message.

Races without ranking: the option to publish an event without ranking (i.e. only performances are displayed for athletes, which are simply sorted by their registration order) is now available at the race level. Allowing to manage such a race among regular ones in the same event file.