Adding the ability to synchronize racers of a selected race from a universal API that can be implemented by whoever handles racer registrations on their site.
Bug fix – if chip entries came from a slave device (i.e. a slave suitcase) with antenna number 10 or higher, an error occurred when displaying the suitcase display (if the Antennas page was displayed) and from that point on the display content with the antennas status stopped updating.
Separating the results API (the function to get the results for a given race and perform the upload function of the results for a given race) into a separate group.
Changes to the calculation of race results – addition of so-called Missed sections. In the future, it is planned that the user can add information about missed passes to the racer – he doesn’t have to immediately guess the time and enter the chip entry. So far only the evaluation works – no user input is added.
Support for the external and internal YR9700 active chip reader from Invelion has been added to the system. The external reader can be connected via LAN cable or serial port via USB connector. The chips logs from this external reader are recorded by antenna number 10 (in case it is the main device). In case it is device number 3, the antenna of the external reader is number 40. The use of the external reader is set in the Basic configuration – External RFID tab. More information about the active RFID reader is here.
In the edit/setup of the race there is an option to set the way of uploading the results of the race in JSON format. There is now an option to upload the race results to the FTP server specified in the Basic configuration, or to use a RESTAPI POST request to a server – typically a ” own” server that will process the results from JSON format into its own presentation. Automatic upload of results is not yet available, but for those races that have results upload set to the server, there is a function (button) on the results page for that race that will upload the current results to the server according to the type set.
The ability to derive the chip number from the loaded EPC has been added to the Chip Registration function. The hexadecimal value contained in the EPC of the chip is converted to decimal and the result is the user chip number.
