> 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/es/usando-wiclax/adquisicion-de-datos-de-cronometraje/correspondencia-dorsal-chip.md).
# Correspondencia dorsal - chip
Cuando se trabaja con transpondedores, normalmente es necesario rellenar una tabla de correspondencia, es decir, indicar para un determinado identificador de chip el número de dorsal que representará.
Esta asociación se puede realizar de varias maneras:
* importando una tabla de correspondencia completa
* importando una información de "ID de chip" en una lista de participantes
* mediante entrada manual en el formulario de registro de un participante
{% hint style="info" %}
Proporcionar una tabla de correspondencia es opcional en el caso de que los identificadores del chip sean también los números de dorsal. Por ejemplo, Chip 1208 = Dorsal 1208.
{% endhint %}
{% hint style="info" %}
Un mismo dorsal puede estar asociado a varios identificadores de chip.
{% endhint %}
Viewing/entering the chip ID associated with a bib
Importing chip ID with a list of participants
## La tabla de correspondencia
Sea cual sea el método que elijas, puedes consultar esta tabla haciendo clic aquí, o cambiando de pestaña en la ventana de adquisiciones:
En esta ventana podrás añadir/eliminar/consultar asociaciones.
Están disponibles algunas funciones de importación de archivos o portapapeles.
También puedes guardar listas reutilizables, útiles por ejemplo si tienes un conjunto de transpondedores que siempre es idéntico.
## Filtros
Los filtros están destinados principalmente a eliminar lecturas parásitas, es decir la detección de transpondedores que no son los suyos.
Most often your chips are encoded with a discriminating prefix. For example "9588000164" where 164 represents the useful identifier and 9588 is the prefix found on all transponders. In this case we can indicate to Wiclax that only chips with this prefix are to be processed.
In addition, you can choose to process only part of the code, for example only the last 6 characters from the right. If necessary:
* either the retained part is equal to the bib number, and you do not need a correspondence table
* either it is a random identifier and you will fill your correspondence table without using the prefix
## Códigos cortos
Los códigos cortos son como atajos para los ID de chips.
For example, your batch of transponders is numbered from 1 to 100, but their identifiers are arbitrary.
The principle is as follows: in the example above, if bib 98 receives the encoded chip AH-3453, I can directly assign it the chip identifier 2.
Upon receipt of a detection of the AH-3453 chip, Wiclax will know from the short code associated which bib this chip belongs to.
A list of short codes therefore complements the correspondence table, it does not replace it.
---
# 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/es/usando-wiclax/adquisicion-de-datos-de-cronometraje/correspondencia-dorsal-chip.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.
