> For the complete documentation index, see [llms.txt](https://docs.wiclax.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wiclax.com/en/use-wiclax/acquisition-of-timing-data/principle-of-acquisitions.md). # Principle of acquisitions The expression time acquisition refers to the retrieval of “times” by Wiclax, coming from an external device. An acquisition is distinguished from a simple import carried out manually from a file. The different types of acquisitions are: * From an external stopwatch, a photocell or a gate * From an electronic detection system (RFID) (Pro version) * From a photo finish system (Pro version) * From a local or remote file (network/web) (Pro version) * From an online passage storage service (Pro version) ## Creation and setting The acquisitions window can be opened from here on the ribbon, or via the F9 shortcut.
Creating an acquisition is done by clicking on one of the buttons on the ribbon that groups together all the possible types. We will generally choose the manufacturer of the equipment, or a file/cloud type of acquisition if we rather target only data:
Good to know: * the number of acquisitions simultaneously active is not limited * acquisitions are recorded on the workstation, not on the test. The logic is to quickly move on to a new event with your usual equipment. * for complex scenarios, for example a race configuration prepared on a different station than the one that will be used on D-Day, you can export/import a complete acquisition configuration via the buttons located at the top right of the ribbon. * the button at the top right of the ribbon allows you to clear up the interface by keeping only the equipment that you are likely to use. * you can also search for a manufacturer or model of stopwatch via the search field in the ribbon title bar ## Activation Activation is usually synonymous with connecting to the equipment. In the case of a file type acquisition, this means starting automatic imports. Activation is done by the switch button to the right of each acquisition line:
## Settings of an acquisition Configuring an RFID reader type of equipment generally requires specifying: * **the equipment model** - if this is not the case it means that the acquisition will work in the same way with the different models of the manufacturer * **the connection address** - COM port for a serial/USB connection, IP address for an Ethernet connection. Note that entering the TCP port number is usually optional, as long as the hardware's default port has not been changed. ### **Repassing delay** Initialized by default at 10s, it prevents the too frequent rise of a transponder reading. A reading of the same chip before the expiration of this interval will be ignored by Wiclax. In the case where a destination is set to take into account the last pass, this delay is ignored. This delay is generally useful and sufficient to avoid a too rapid transition from one split point to the next, or to limit the effects of an athlete who is stationed on the line. For more control over the splits themselves and the minimum time between 2 splits, see the [passage conditions](/en/use-wiclax/acquisition-of-timing-data/passage-conditions.md). ### Offset The offset allows to solve non-standard cases such as for example a clock synchronization fault of a decoder. We can choose to add or subtract a time value to the received passages. ## Target The most important parameter of an acquisition is its destination, which can be a single split or a series of splits. Let's look at some of the most common cases to understand the logic: {% tabs %} {% tab title="A single split" %}
This is the simplest configuration. All the splits of the acquisition will go to the intermediate split 10km, and only a first pass will be taken into account for each competitor (the icon to take into account the re-passes is not activated). {% endtab %} {% tab title="A simple finish" %}
Only the finish line is checked. Only one crossing of the line will be integrated, the following ones will be considered as recrossings. This is the classic configuration for a lap race, where each crossing of the finish line increments the number of laps of a competitor. {% endtab %} {% tab title="Start and finish" %}
By default for a start line the option taking into account the last passing - in orange on the capture - is activated. If a chip is read several times on the line, it is therefore the last time value which will ultimately be kept. The delay after the gun is indicated here at 10 minutes. This means that a new passage on the line more than 10 minutes after the start time of the race of a runner will be considered as another split, in this case as a finish. Or simply discarded if there's no further targeted split. {% endtab %} {% tab title="Intermediate splits and finish" %}
The basic principle of multiple destinations is that the passages will be filled sequentially. In this example the same line is used for the intermediate points at 20km and 48km, and then for the finish. This means that if a passing arrives for a competitor who already has a passing time at 48km, this passing will be considered as a finish. Important: the algorithm takes into account the assignment of split points to the different races. For example, a competitor on the 30km race will not be affected by the passing to 48km. His 2nd passing over the line will therefore be a finish. {% endtab %} {% endtabs %} {% hint style="info" %} In the event that no target is eligible for a passage, you will get the message "No valid destination for passage". This is the case, for example, if the passage arrives with a source address that does not match any of the source addresses entered on the destinations. {% endhint %} ### Source address The @source field present on each destination line allows the target to focus on a subset only of the incoming data.
Depending on the type of acquisition, this can be: * the location identifier when connected to an intermediate software between Wiclax and the readers * a channel number in case of a stopwatch * an antenna number or a reader id, depending on each type of equipment Good to know: the drop-down menu of the input field gives visibility on the predefined values ​​if any, or on the received values. This can help to discover them or to make checks. ### Backup line The backup line property, valid only for the finish line, has the following effects: * it limits the audio and visual notifications for readings on this line * it displays a "backup line" marker on a result row in case the competitor was not detected on the main line In the event that for a technical reason the reading of the main line arrives after that of the backup line, the integrated passage time is immediately overwritten by the first time. ### Start check The selection of `Start check` as the target allows you to set up a simple detection, for example at the entry of a zone. By simple check we mean that we will only store a yes/no information, rather than a split time. In the grid of participants we find this information in the form of a column entitled `Start check`, which display check boxes. ## Monitoring For devices that send this information, the row of an acquisition in the list can display the battery charge level, the charging status (plugged or not), the status of the connection to the GPRS network, the active antennas and their power level, etc. The log of an acquisition is displayed below the list. It contains events such as errors or indications regarding rejected passages. The passages received are displayed on the main window in the form of thumbnails, which highlight information like the bib, the score, the race. {% hint style="info" %} If the thumbnails become too numerous and do not provide you with any usefulness in terms of monitoring, you can decide to make the acquisition "mute" by clicking on this icon: {% endhint %} {% hint style="info" %} By clicking on a thumbnail you can move their stacking to the other side of the main window. {% endhint %} ## Rewind The rewind operation consists of asking the hardware or a cloud service to return its passage data, for a range of dates of your choice.
Specify the date range, click on the rewind button: a window opens to present the obtained data. At this stage you can simply view them, for example to see the number of "new" passages, that is to say which have not been integrated into the event.
From that on you can of course decide to launch the import of the data, the entirety or a selection. ## Data monitoring The history of acquired passings can be found on the results entry form. There you can consult: * all acquired passages, whether integrated or not, sorted by destination split * the history of all passages of a particular competitor
Passage grids can be filtered on a chip number or a particular status. If necessary, it is possible to enter a new bib to assign the passage, either because the registration has arrived without a bib (like in case of a cell signal) or because the bib is not the right one. Also note the feature to mark passages as "to ignore". This status means that if these same passages come back via an acquisition (typically by a periodic file import), they will no longer be processed. ## Filters Filters on an acquisition allow you to respond to more advanced issues: for example, several races are active but the competitors of one of the races must not be detected at a split point. The filters are activated either at the level of the global acquisition or at the level of one of its destinations. It can be an inclusive or exclusive condition:
## Simulate an acquisition The acquisition simulation is a very practical tool, especially to validate your settings, your transponder matches or your live screens before the race.
2 types of simulation are available: * a mass simulation that will send random passages at the desired frequency * a manual simulation where you choose a bib number or chip ID yourself. This simulation can also be opened with the Control + F9 shortcut without needing to open the acquisitions window. ## My devices
The My devices menu refers to the management of equipment linked to your user account. The online management page allows you to create these devices. The benefits are as follows: * If the model is compatible with the Wiclax cloud service, you can set the RFID reader to synchronize its data and you will easily reach this data using a cloud acquisition. * For other cases, it will be convenient to create an acquisition on one of the company's equipment with one click, directly configured with the correct type and IP address of the box. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.wiclax.com/en/use-wiclax/acquisition-of-timing-data/principle-of-acquisitions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.