> 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/transmision-de-resultados-en-vivo/pantallas-quiosco.md).
# Pantallas Quiosco
A Kiosk Live screen is a custom [Live Screen](broken://pages/P4BJMnQePeF4Q4fNxbu4) used to display data for an athlete, independently from result acquisition.
It can be useful before the race as a data checking screen, or post race as a photo background for finishers.
### Plugging the acquisition
The configuration works this way:
* there is an RFID reader for the purpose, connected to the main Wiclax
* the live screen is displayed from the local network, with the ability to reach the main PC address
Once this is in place, you simply need to route the acquisition, i.e. to tell it will process incoming chip reads as data requests for the screen. This is available here on top of the acquisitions settings:
{% hint style="info" %}
If you're not working with an electronic detection, you can still feed the screen in 2 ways:
* clicking anywhere on it and enter a bib number
* adding a `bib` argument to the browser URL, for instance\
[http://192.168.8.61:8070/Screen/Screen-Name?bib=1003](http://192.168.8.61:8070/Screen/Kiosk?bib=1003)\
value can be either a bib number or a chip ID
Those methods are also convenient for testing the screen.
{% endhint %}
### Screen design
A Kiosk screen is designed the same way than a regular Live screen.
Simple adaptation to do is to work with *Result list* kind of widgets, setting their `List kind` property as `Kiosk display`. The table can be made of a single row and a single column in the simplest configuration.
{% hint style="info" %}
If you look at delivered screen samples, you can find one named Kiosk to help you discover how it's made:
{% endhint %}
{% hint style="info" %}
As for any regular Live screen a Live session has to be running so that it's reachable
{% endhint %}
---
# 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/transmision-de-resultados-en-vivo/pantallas-quiosco.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.
