Help Les hjelpen på norsk

How the parts fit together #

• The server holds the events, riders, start lists and results. You reach it with a browser and log in. The venue needs internet during the meeting.
• Chip passings come from the MYLAPS X2 server. The small program Elapse X2 on the timing PC fetches them and sends them on. See The Elapse X2 reader.
• The TimerBox is plugged into the timing PC with USB. A browser window called TimerBox link talks to it: the countdown goes out to the start clock, and the start signal comes back. See The TimerBox link window.
• The big screen, the public page, the speaker page and the pursuit boards are web pages that only read. They need a link, not a login.

The pages and tabs #

The dark bar at the top is the same on every page. When you open an event, its own tabs come under the event name. The back button ‹ sits in front of the heading of the page (from 1.8.0; it was in the dark bar) and goes to the page you came from. On the Events page every event has a thin colour stripe for its venue (the colour is set under Admin › Venues), and when the events you see are at more than one venue, a row of buttons above the list filters on venue: All, each venue with its count, and No venue. The choice is remembered while you are logged in (1.8.2).

At the top right of an event there is a button to the public page: Public page ↗ when it is switched on, Public page: off when it is not.

Roles: who can do what #

Every user has one role. Elapse creates the users under Admin › Users, where they are listed in groups: Elapse, organisers, venue organisers per venue, and users (1.8.0).

Elapse users always have access to every event. For the others, an organiser ticks who can work in the event under Setup › Access. Everybody who is logged in can open Open track.

Five wrong passwords for a user name pause that login for 15 minutes. Elapse can set a new password.

Several people at the same time #

• The names at the top right show who else is in the event right now.
• When somebody has a rider or a race open, the row is marked with their colour and the text … is working on this.
• If you open the same rider or race, a yellow line says … also has this open. Whoever saves last overwrites the other. Agree who saves.
• Every change is written to the Log tab with name and time. What the app sets from chip passings is logged with the name Passings (automatic).

Race status #

Every race has a status. The same colours are used on every page, on the public page and in the PDFs.

Upcoming

The race is in the programme. Its start list is a draft: it has no communiqué number, and the public page says that the start list is not ready yet.

Start list ready

You set this when the start list is final: open the race, open Race settings and status, choose the status and press Save race. The start list now gets its communiqué number when it is printed, and the public page shows it. A next round made by the app starts in this status.

Live

Set by itself the first time something happens on the Run page: a tap, a time, a countdown or a chip passing. The public page shows the standings as they come.

Provisional

The race is finished and the result is being checked. Reading of passings stops. The result list gets its communiqué number when it is printed.

Official

The result is final. Start list and results are locked. An organiser or Elapse can open the race again with Reopen on the Run page, or by setting the status back to Unofficial under Race settings and status.

The track and its timing points #

Each point has a MYLAPS loop and can have a TimerBox channel (a track contact). Elapse fills these in for the venue under Admin › Venues. The event shows them under Setup › Timing points. The loop names Finish, 200m, 100m, Red and Green from the X2 server are understood without any setup.

New event #

1. Open Events in the top menu and press New event. Organisers and Elapse have this button.
2. Type the Name and choose the Venue. The venue gives the track length and the timing points.
3. If the velodrome is not in the list, choose Own setup (venue not in the list) and pick the track length: 250 m, 200 m or Other length.
4. Press Create. You land on the Setup tab of the new event.

A new event has no disciplines switched on, no classes and no riders. Work through the tabs from left to right.

Setup tab: name, dates, venue and language #

Name

Printed on every PDF and shown on the big screen and the public page.

From date, To date

Fill in both for a meeting over several days. The dates give the weekday and date on the programme, and decide which licence register the riders are checked against. The big-screen link of a venue shows the event whose dates include today.

Venue

The track length, the timing points, the equipment and the big-screen link follow the venue. If you save with another venue, the timing points of the event are replaced with that venue’s.

Organiser

Printed on the PDFs together with the date and the venue.

Demo event

1.21.4, organisers and Elapse: a demo for showing the system. It counts as on today, every day – the dates are moved to today each day by themselves, so it is “on now” on the public page, the venue’s screen and in the API without a date span of months. It is marked Demo on the lists. A real event at the venue on the same day goes before it on the venue’s screen, and no backup is mailed for it.

Language on PDFs and the big screen

English or Norwegian. One choice for the big screen, all PDFs and the public page. Rider names, class names and titles you type yourself are shown as you typed them.

Press Save at the bottom of the card. The same button saves the colour, the logos and the printout settings below.

Event colour, logos and PDF design #

• Event colour: pick a colour or press one of the named buttons. It is used on the pages of the event, on the PDF lists and as the accent on the big screen.
• Two colours (1.23.3): the pages in here – header bar, buttons, tabs – always carry the venue’s colour (Admin › Venues › Venue colour): Sola is always yellow, Asker always brown, so you see at a glance where you are. The event colour on this tab is for what the public sees: the accent on the big screen, the public live page and the PDF lists – the organiser’s or the cup’s colour, or one of the presets. An event without a venue colour uses its event colour in here too.
• Event logo: shown on the PDFs, the big screen and the public page.
• Timer logo (timing company): printed at the bottom of the PDFs. The Elapse logo is used when you leave it empty.
• PDF background design (A4 portrait): an image behind the text on every PDF page. Keep the middle light. The top 30 mm holds the logos and the event name, the bottom 25 mm the footer.

For each image you can upload a file or paste a link to an image. It must be a PNG or JPG of at most 3 MB. Tick Remove this image and save to take it away.

Printouts and communiqué numbers #

Under Printouts (PDF) on the Setup tab:

• Number the start lists and result lists as communiqués: every list gets a running number in the heading and first in the file name, for example C012-Men-Elite-Scratch-results.pdf. This is on for new events.
• The first list gets number: type another number than 1 when the organiser’s own communiqués take the first numbers.
• Custom text at the bottom of start lists and result lists: for example the name of the chief commissaire or a sponsor line.

How the numbers are given is explained under PDFs, communiqué numbers and “Revised”.

Add-ons: the paid modules #

Everything needed to run a race – riders, programme, timing, results, PDFs, the public page, the big screen, the speaker page – is in the base and always on. The extras are modules, priced per event: DataRide export, UCI ranking and licence check, Screen Plus (show mode, sponsors, photo finish), Statistics and reports, and API access.

• Price summary (1.25.1): at the top of the tab, what this event costs: the Basic price per event (set by Elapse under Admin › Modules; “as agreed” when not set), one line per add-on that is charged, the modules included for the venue at NOK 0, and the total. Prices are per event, excl. VAT; a demo event is never charged.
• The Add-ons tab of the event lists them with their price and status: included for the venue, activated by whom and when, or not activated. An organiser, a venue organiser or Elapse presses Activate; the module opens at once and can be switched off again.
• An add-on is charged for the event from the moment it is activated (1.23.1) – also when it is switched off again later: the tab then says “Switched off … – activated by …, on the invoice”, and the organiser is told so before both activating and switching off. A module included for the venue costs nothing extra per event. A module that is used on an event without being activated or included (while the modules are not enforced) is charged as used.
• Elapse gets an e-mail on every activation and sees the invoice basis under Admin › Modules (used modules, who activated, the sum to charge). Elapse also sets the prices there and can give one event its own choice of modules under Setup.
• While the modules are not enforced (Admin › Modules, the master switch), every module is open for everybody; activations are still noted. 1.19.0.

Timing points #

When the event has a venue, the Timing points card only shows the points. Elapse changes them for the venue under Admin › Venues, and events that are not over yet follow.

An event with its own setup has the points on the Setup tab itself: switch a point on or off, and type its name, the metres before the finish line, the MYLAPS loop ID and the TimerBox channel. Press Save timing points. See The track and its timing points.

Access #

The Access card on the Setup tab lists the other users. Tick the ones who are going to work in this event and press Save access. Elapse users always have access. A venue organiser has access to every event at their venue. If nobody is listed, Elapse has to create the user accounts first.

Copy an event #

1. On Events, press Copy on the event you want to start from.
2. Type the Name of the new event.
3. Tick Include the riders (number, class and chip) if the same riders come again.
4. Press Copy.

The copy gets the track, timing points, disciplines, classes, the programme with its races and breaks, logos, footer text and access. Start lists and results are never copied. Sponsor logos are not copied either: add them again on the Screen tab. Remember to set the new dates.

Download, upload, test events and delete #

• Download on the Events page saves the whole event to one file (.evz): setup, riders, start lists, results, passings, the change log and the images. Use it as your own archive, or to move an event to another installation. The file holds the riders’ personal data, so treat it that way.
• Upload event file reads such a file in as a new event. Events that exist are never changed. If the name is taken, the new event gets “(uploaded …)” after its name. Access is not in the file: set it again. A file from a newer version of the program is refused.
• Create test event, in the same window as the upload, makes a made-up event for practice. The riders are invented and have the chips SIM-1, SIM-2 and so on, so you can run the races with Test: simulate passings.
• Delete removes an event with all riders, races and results. It cannot be undone. From 1.8.0 only Elapse deletes events, and types their own password first; an organiser’s Delete button says to contact Elapse. Download the event first if you may need it.

Disciplines tab #

Tick the disciplines that will be run and press Save disciplines. Only these can be added to the programme, and only these get a column in the rider import template. Laps and distance are set later, per race.

Each name links to how that discipline is run. How a discipline is timed (which loop starts and stops the time, track contact or chip first) is set once by Elapse under Admin › Disciplines and applies to every event.

Classes tab #

A class is a field of riders who race each other, for example Men Elite, Women Junior, Masters or a cup group. You make the classes yourself.

• Type a name in the row New class, add a short name if you like, and press Save classes. One class is added per save.
• Add from template adds a ready-made set of classes. Elapse makes the sets under Admin › Class templates. Classes you already have are not added twice.
• Order decides the order the classes are listed in.
• Gender (W, M or X = mixed/open), Category (Elite, Junior, M40, 13 – the class without the gender) and No placings (children’s classes whose result is published without places) go to the federation sites through the API (1.23.0). Leave gender and category empty and they are guessed from the name – the guess is shown greyed; set them when the guess is wrong (“Elite Women”, “Jenter 13” and “M40” are guessed right). Class templates (Admin) can carry them as Name; Short; W; Elite; no placings.
• Colour in the timetable is used when “colour by class” is on in the programme. Leave automatic ticked to let the app choose.
• Delete removes a class. Its riders stay, but are left without a class.

Add a rider by hand #

1. On the Riders tab, press New rider.
2. Fill in the fields. Only a name is required. Give every rider a Bib, which is the number you tap and type on the Run page, and a Chip, so the rider can be timed.
3. Under Entered in, tick the disciplines the rider is going to ride.
4. Press Save, or Save and add another to go straight on to the next rider.

Click a name in the list to open the rider again. At the bottom of the rider’s page you see every race the rider is in, with rank and result, and a button Edit that takes you to the results of that race.

Import from Excel or CSV #

1. Switch on the disciplines first (Disciplines tab). The template gets one column for each of them.
2. On the Riders tab, press Import from Excel, CSV or RaceResult.
3. Press Download Excel template (or Download CSV template). The Excel file has a second sheet with instructions and example rows.
4. Fill in one row per rider on the sheet “Riders”. Keep the first row with the column names.
5. Choose the file and press Upload and preview. Nothing is saved yet.
6. Read the page Check before importing. Each row is marked New, Update or with a problem.
7. Press Import … riders.

• The order of the columns does not matter. Columns the app does not know are ignored and listed in the preview.
• Norwegian column names work too: Nr, Fornavn, Etternavn, Klubb, Lag, Nasjon, Klasse, Aldersklasse, Fødselsdato.
• If the file has a column called “Felt” (or “Field”), that column is taken as the class, and the column called “Klasse” or “Class” becomes the age class.
• Old Excel files (.xls) are not supported. Save the file as .xlsx or CSV.
• After the import, riders without a chip get the chip they have in the chip register.

Example row: bib 12, Kari Nordmann, Sandnes SK, NOR, class Women Elite, age class K Junior, chip PC-12345, and an x under Scratch.

Import from RaceResult #

Use this when the entries are taken in RaceResult.

1. In RaceResult, make a list with the fields below and create a link to it under Main window › Access rights / Simple API, in the format JSON or CSV.
2. On the import page, paste the link in RaceResult link and press Fetch from RaceResult and preview.
3. Check the preview and press Import … riders, as for a file.

The link is kept on the event, so the next import is one click. Riders already in the event (same bib) are updated. Only https links to raceresult.com are fetched.

Fields that are recognised: Bib FirstName LastName Club Nation.IOCName Contest.Name or AgeGroup1.Name (the class) DateOfBirth Transponder1 Transponder2 UCIID. A column named after a discipline, with x or 1, enters the rider in it.

Licence check #

The licence check runs by itself every time the Riders tab is opened, as soon as the register for the year of the event is uploaded. Each rider gets a tag in the column Licence:

OK

The UCI ID is in the register, or the name is there together with the same date of birth or club.

Check

The name is in the register, but the club or the date of birth differs, or several people share the name. Look at it by hand.

Not found

Nobody with that name or UCI ID. Names must be spelled as in the register.

The button Licence check opens the full list, with what the register says about each rider. Use Only those to look at to see just the riders that need attention.

The register

Open Licences in the top menu. An organiser or Elapse types the Year, chooses the file (.xlsx or .csv) and presses Upload. There is one register per year, used by all events. Uploading a year again replaces that year. The export from the NCF licence system works as it is. Look up a licence searches by name, club, licence number or UCI ID.

The register holds names and dates of birth. It is only shown to users who are logged in.

Chips and the chip register #

A rider is timed by the chip that is typed on the rider. No chip, no automatic times or laps for that rider.

• The Riders tab shows … without a chip when active riders lack one.
• The chip register remembers which chip each rider had, across events. It fills itself: every rider who has a chip in an event is put in it, and the newest event wins.
• Press Fill in chips from the register on the Riders tab to give every rider who is in the register their chip. An import does this by itself. Check the list afterwards.
• A rider is recognised by UCI ID. Without one, by the name, when only one rider in the register has that name.

Open Chips in the top menu to see the register. Organisers and Elapse can correct a row and press Save, add a rider with Add to the register, read every old event once with Read chips from all events, or upload a list with names and chips. If the same chip is on two riders, the page warns you: correct or delete the one who no longer has it.

For handing out numbers and transponders, print Numbers and chips from the Staff tab.

Add a race #

1. Go to the card Add race under the programme table.
2. Choose the Discipline. Only the disciplines switched on for the event are in the list.
3. Type the Round if there is more than one, for example Qualifying or Final.
4. Type Laps or Distance. One is enough: 3000 m on a 250 m track gives 12 laps by itself. A number up to 100 without a unit is read as kilometres, so “20” and “20 km” are the same.
5. Tick the classes under Classes. You get one race per ticked class.
6. Press Add race. The race is put last in the programme. Move it to its place.

To change a race later, click its name and open Race settings and status. To remove it, press ✕ on its row. That deletes its start list and results too.

Rounds and heats #

• A round is its own race in the programme: “Keirin – Qualifying” and “Keirin – Final” are two rows. Add the later rounds as empty races so they have a time in the programme, or let the app make them when the first round has a result (see Next round).
• A heat is one start inside a race. Heats are made on the start list. Bunch races (scratch, points race, tempo race, elimination, Madison) are always one heat.
• Until a race has a start list, the column Heats shows a guess from the riders entered, marked ≈. Type your own number there if you know better.
• A sprint in best of three counts two rides per heat, shown as “× 2”.
• Sprint rounds planned ahead: add the later rounds as empty Sprint races with the round names “Quarter-finals”, “Semi-finals”, “Final” and “Final for bronze”, in the same class. When you make the next round from a result, the riders are put in the row that is already in the programme, and the row keeps its place, its minutes and its best of one or three.

Order and start times #

• Move a row: drag it by the handle on the left, use the small arrows, or type a new number in Order. The new order is saved at once. On a tablet, use the arrows or the number.
• Start times: type when the first race starts in Programme starts. Every row then gets a start time from the time used by the rows before it.
• Fixed time: a time typed in this column moves that row and everything after it.
• Saved as you go (1.8.0): a field in the table or in the settings above it (heats, minutes, fixed times, names of breaks, programme starts…) is saved the moment you leave it, as in RaceResult. There is no Save button. A floppy Save appears at the top right while something is not saved yet: changes made in the pencil panel of a row wait for that floppy, or are sent by themselves when you change tab or follow a link, so nothing is lost.

The boxes above the table show the racing time, the breaks, the total time, and from when to when the programme runs.

Minutes per race and standard times #

Time used by a race is the number of heats × minutes per heat. The minutes per heat come from the first of these that applies:

1. The number you typed in Min/heat on the row. It always wins.
2. The Standard times, when that box is ticked: the planning times from the UCI guide for commissaires, the 2026 championship programmes and the local youth distances, per heat for timed races, sprint and keirin, and per race for bunch races. They count the riders coming to the line, the race and the riders leaving the track. Examples: flying 200 m 2:00 per rider (1.26.1; the table says 1:30, Sola showed it is not enough – type a time per heat on the race to override), sprint 3:30 per ride, keirin 5:00, pursuit 4 km 6:40, scratch 2 km 6 minutes and 10 km 18, points race 20 km 32 minutes, elimination 5:50 plus 17 seconds per lap by the number of riders (24 riders: 20 minutes).
3. For a race with laps or a distance: + line-up min plus laps × Seconds per lap. An elimination without typed laps counts two laps per rider.
4. The event’s Minutes per heat.

The grey number in Min/heat is what the app worked out. Hold the mouse over it to see where it comes from. New events have the standard times switched on.

Minutes behind schedule moves the times on the big screen and the public page, not the printed programme. Tick automatic to let the app measure it: it compares when the latest race was set live with its time in the programme.

Breaks and award ceremonies #

• In the card Add break, type a name and the minutes and press Add break. Lunch, warm-up and track preparation are added the same way, so their time is counted.
• Add award ceremony (8 min) adds a ceremony of eight minutes.
• The break is put last. Drag it to its place. Name and minutes can be changed in the table.
• Start on screen on a break row makes the big screen count down from now until the break is over.

Several days #

1. Set From date and To date on the Setup tab.
2. On the Programme tab, under Add day, type when the next day starts and press Add day.
3. The day comes as a coloured row last in the programme. Drag it to where the day begins. Everything below it belongs to that day and is timed from its start.

Day 1 is the From date, day 2 the day after, and so on. The weekday and date are printed on the timetable, the start lists and the result lists. You can print the programme for all days or for one day. The big screen and “now and next” follow the part of the programme that belongs to today.

Classes that ride together #

With few riders, classes are often put together: women with men, juniors with masters. There are three ways:

• For the whole programme: in the card Classes that ride together, tick the classes, choose Results separately per class or One joint result, and press Ride together. Every race the classes have becomes one joint race per discipline and round: one row in the programme, one start list, one race on the Run page. Ride separately again undoes it.
• When you add a race: tick several classes and choose one joint race under When several classes are ticked.
• For one race that exists: open Race settings and status and tick the other classes under Joint race.

With separate results, each class is ranked 1, 2, 3 … from the joint result, with the class as a heading on the result list. Races that have been started are left alone, and the app tells you which.

Omnium in the programme #

When you add an Omnium, the app adds its four races by itself: Scratch (Omnium I), Tempo Race (Omnium II), Elimination (Omnium III) and Points Race (Omnium IV). Untick one of them under Races of the omnium to ride it with three, as is often done for the youngest classes (1.6.0); a race can also be deleted from the programme afterwards as long as it has no result, and the others are numbered again. With several classes they come discipline by discipline: the scratch of every class, then the tempo race of every class, and so on. Move them as you like.

The omnium itself is not a row in the running order. It stands in the line Omnium standings above the table. Click its name there to open the omnium’s start list: riders are added there, and the four races get the same riders. Standings opens the total. See Omnium.

Programme templates and race presets #

• A programme template holds races, classes, breaks, the order and minutes per heat, for example “Club evening, youth”. Organisers save one with Save as template. Anybody can use it in another event: choose it and press Add to this programme. Missing classes are created and the disciplines are switched on. Start lists and results are never part of a template.
• A race preset is one ready-made race (discipline, round, laps, distance, sprints, riders per heat, points by rank). Elapse makes them under Admin › Race presets. You pick one in Start from a preset when you add a race.

The programme PDF and colours #

• Export programme as PDF makes the timetable, with time, discipline, class, round, riders, heats, distance and about how long each race takes. With several days there is also one button per day, and in the PDF for all days every day starts on a new page.
• Tick colour by class and save to get a colour block per class in the PDF, on the big screen and on the public page. The colours are set on the Classes tab.
• Show programme on big screen puts the whole programme on the big screen.
• On each race row, Start list and Results open the PDFs of that race.
• Staff PDF, all times is the same timetable with every start time, for the people who run the meeting. You must be logged in to open it.

Start times on the public programme #

The start times in the programme are estimates. To avoid promising a time that will not hold, the public page, the public PDF and the big screen show the clock time only on some rows. The other rows show the number of heats and about how long the race takes, in a column on the right.

• The standard: the first row of each day, a row with a time typed in Fixed time, and the first row after a break show their time.
• One row: next to the start time of each row there is a small mark, public or hidden. Press it to switch. It is saved at once.
• All rows: Show every time puts the clock time on every row. Back to the standard removes your own choices.
• Staff: the Programme tab, the Staff tab and Staff PDF, all times always show every start time.

Change the name, class or status of a race in the table #

• Name, round and class: press the pencil ✎ after the name of the race. Type the name in Name shown (leave it empty to get class – discipline – round), change Round or choose another Class, and press the floppy Save at the top right (or just change tab: it is saved first). You do not have to delete the race and add it again.
• Sprint, one ride or best of three: a sprint row shows 1 ride or Best of 3 after its name. Press it (or the pencil), choose under Sprint matches and press the floppy Save. It can be changed until the race is official; rides that are already entered are kept.
• The class decides which riders the start list takes. When you move a race to another class, the riders of that class who are entered in the discipline are put on its start list. Riders who were on the list already stay.
• Status: the status of each race is a list in the column Status. Choose for example Start list ready. It is saved at once.
• Many at once: the button Set … to Start list ready under the table sets every race that is Upcoming and has riders on its start list to Start list ready.

Fill the start list from the entries #

The start lists follow the entries by themselves. A rider who is ticked for a discipline under Entered in (or has an x in the import file) is put on the start list of that discipline’s races for the rider’s class. You do not add the rider by hand.

• When: when a rider is saved or imported, when a race is added to the programme, and when the class of a race is changed. A rider who is unticked or moved to another class is taken off the start lists that no longer fit.
• Which races: the first round of each discipline, until the race is started. An omnium is filled on the omnium itself, and its four races follow. Finals, semi-finals and other later rounds get their riders from a result, and so do the sprint rounds after a flying 200 m.
• Riders who were there before: the Programme tab shows how many entered riders are missing on a start list. Press Fill start lists from the entries to add them all.
• Empty start list? The race must be for the rider’s class. The Programme tab says so in the line Entered, but no race for their class. Change the class of the riders or of the race, or put the classes together under Classes that ride together.
• Switch it off: for one race with Start list follows the entries under Race settings and status, for the whole event with Start lists follow the entries under Setup.
• A rider you take off a start list by hand stays off, as long as the rider’s entries are not changed.

By hand, for a rider who is not entered or a race that does not follow the entries:

1. Open the race and stay on the tab Start list.
2. The card Add riders lists the active riders of the class who are not on the list yet. Riders entered in this discipline are ticked already.
3. Tick or untick, or press Tick all, and press Add ticked riders.

To take a rider off, open Start list as a table and press Remove on the row. A race without a class is open to every rider of the event. When a race is official, its start list is locked.

Start order and heats #

Timed races, sprint and keirin have the board Start order: one card per heat, in the order the heats ride.

• Tap two riders to swap them.
• Tap one rider and then a heat, or New heat, to move the rider there. With a mouse you can also drag.
• Reverse the heats makes the last heat ride first.
• Press Save start order. Nothing is saved before that.

Quick ways to make the order, under the board:

• Divide into heats: type the riders per heat and the list is renumbered in the order it has now. Pursuits, sprint and team sprint start with 2 per heat, keirin with 6, the others with 1.
• Random draw draws a new order.
• Set order: order the list by the result of another race in the same class, with best starts last or best starts first.

The same list is under the board as a table, with heat and position as numbers. Change the numbers there and press Save start list if you prefer that.

Sprint: riders with the same heat number meet. A rider alone in a heat goes through on a walkover. With an odd number of riders, choose who gets it and press Set walkover and pair the rest.

The Run page takes the heats in this order. A rider who already has a time keeps the heat they rode in.

Red and green in pursuits and time trials #

• In Individual Pursuit, Team Pursuit, Time Trial and Team Sprint, the first rider or team in a heat starts at the Red line and the second at the Green line. On the board the two have a red and a green edge.
• To change sides, tap the two riders to swap them and save. On the Run page you can also press Swap red and green line before the countdown.
• A rider alone in a heat starts at the red line.

Line-up at the fence and in the sprinters’ lane #

Scratch, Points Race, Tempo Race, Elimination and Madison start as a bunch. Half the riders hold the fence. The other half are held by their coaches in the sprinters’ lane. Both stand in single file from the finish line, the best seeded in front.

These races have the board Line-up at the start on the start list, with the columns At the fence, Sprinters’ lane (held) and Not placed.

• Alternate fence / lane in this order makes the line-up from the order the riders have now.
• Tap two riders to swap them. Tap one and then a column to put the rider last there. Press Save line-up.
• Random draw draws a new order. Set order orders the riders by the result of another race.
• Remove the line-up makes the start list a plain list again.
• Line-up sheet (PDF) prints the sheet for the people who line the riders up.

Until a line-up is made, the start list is a plain list. When it is made, the start list PDF and the big screen show the two groups. A rider added afterwards goes last in the shorter file.

Teams #

In Team Sprint, Team Pursuit and Madison, riders with the same Team code on the start list ride together and get one result row. The code is the team’s number: it is what you tap on the Run page and type in results.

• Open Start list as a table and type the same code on the riders of each team. Press Save start list.
• Or put the riders in order and press Make teams in start order. It numbers the teams with 2 riders per team in Madison, 3 in Team Sprint and 4 in Team Pursuit. You can change the number.
• Team name is typed on the first rider of each team. The team is then shown by that name, with the riders’ names underneath.

Omnium seeding #

• Riders are added and removed on the omnium’s own start list. The four races follow.
• Each of the four races has its own line-up board. The first race has no standings to go by: make its line-up yourself, for example with Random draw.
• When a race of the omnium is set to Unofficial or Official, the next race that has not started gets its line-up from the omnium standings: the leader first at the fence, the second first in the lane, and so on. Equal points are split on the place in the race just before.
• If you save a line-up by hand, the app leaves it alone. Press Seed from the omnium standings to set it from the standings again.

“Start list ready”, PDFs and communiqués #

1. When the start list is final, open Race settings and status at the top of the race page.
2. Set Status to Start list ready and press Save race.
3. Press Start list PDF to print it. With communiqué numbers on, the list gets its number now.

• Quicker: the status can also be chosen straight in the programme table, for one race or for all that have riders. See Change the name, class or status of a race in the table.
• Before the status is set, the PDF is a draft without a number, and the public page says that the start list is not ready yet.
• If you change the start list after it was printed, the next print is marked “Revised”. See PDFs, communiqué numbers and “Revised”.
• Start list to screen shows the start list on the big screen.
• All start lists in one file: All start lists in one PDF on the Results tab.

The TimerBox link window #

The browser talks to the TimerBox itself, through the USB cable. Nothing is installed. It only works in Chrome or Edge on a PC, and the site must be opened with https.

1. Close VelodromeTiming if it is running. Only one program can use the port.
2. On the PC the TimerBox is plugged into, open the event and the tab Equipment.
3. Press Open the TimerBox link. A small window called TimerBox link opens. If nothing opens, allow pop-ups for the site.
4. The first time on this PC: press Connect to TimerBox and choose the port called “USB Serial Port”. After that the window connects by itself every time it is opened.
5. Wait for the tag Connected. The number under TimerBox clock now runs.
6. Leave the window open during the whole meeting. It may lie behind other windows. Work on in the other window.

• The window is the connection. If you close it, the connection ends. The browser asks before it closes a connected window.
• The Equipment tab shows what the link window is doing. You can leave that tab at any time.
• There can be one link window per venue in a browser. A second one says that the link is already running and does nothing.
• The Run page shows TimerBox connected while the link runs. When it does not, the Run page has a link to open it.

What the status tags mean #

Start clock: countdown, start and stop #

Races with a start gate (pursuits, time trial, team sprint) have a green button on the Run page.

1. Check who is on track and the number in Seconds. The standard is 50. Tick Use this time as standard for the event to keep another number.
2. Press START COUNTDOWN.
3. The countdown shows on the Run page and on the big screen. With the TimerBox connected it is sent to the start clock at the track, and the clock starts.
4. At zero the race clock starts to run. When the start signal comes back from the TimerBox, the clock is set to that exact moment.
5. False start or wrong rider: press Abort / reset clock. The start clock stops and is set back to the full time, ready for a new start.

• Starting the countdown also makes this race read passings.
• Without a start signal, the time is counted from the countdown on the web page. Such a time is marked Start taken from the countdown (approximate). Check it against the timing at the track.
• A command waits only a few seconds. If the link window was closed when you pressed the button, open it and press again.

Inputs and the test buttons #

Inputs on the Equipment tab shows the eight inputs of the TimerBox, numbered as the TimeTronics channels: 1 Start, 2 200 m, 3 Finish, 4 Red, 5 Free, 6 Green, 7 200 m BU, 8 100 m (each lamp shows the number and the name; the small B0 to B3 and A0 to A3 is the input as the TimerBox reports it). An input lights up when its contact closes, and each lamp counts the impulses since the link window was opened, with the time of the last one.

• Press a track contact and see which channel lights up and counts. Choose that channel for the timing point in the list below.
• Use the TimeTronics channels sets the whole list at once to the standard wiring: start signal on channel 1, 200 m line on 2, finish on 3, pursuit red on 4, pursuit green on 6, 100 m line on 8. At Sola this is confirmed for the start, the finish and the 200 m line (port logs 08.10 and 16.10.2026).
• Start signal comes on tells which channel the start signal uses.
• Press Save inputs. The link window picks up the change by itself.
• Counters to zero sets the impulse counters of all lamps to zero, for instance before you test a contact.
• A lamp that flashes red for a moment without counting is a flicker: one 100 ms message said closed, but no event message came. It is logged as Flicker in one message only and gives no time. It is noise on an open line or a message lost on the way. A real impulse always comes as an event message, lights the lamp for as long as the contact is closed and counts.
• The TimerBox cannot tell whether a contact is connected: an input with nothing on it reads the same as a contact at rest. The counters are the way to check a contact: press it and see the count go up.

Test sends to the TimerBox at once, without a race. Make sure nobody is in the start gate.

• Start countdown on the clock starts a countdown of the seconds in the box.
• Stop the clock stops it and sets the clock back to those seconds.
• Own command is for Elapse, for trying commands.

The numbers at the top show the port speed, the TimerBox clock, messages read, messages not understood, and what is sent to the server or waiting to be sent. The dark box What happens is the log. In the link window, Download log saves it to a file you can send to Elapse.

The Elapse X2 reader for MYLAPS #

The X2 server cannot be reached from the internet. A small program on a Windows PC in the same network fetches the passings and sends them on. That program is Elapse X2.

First time on a PC

1. Open the event, the tab Equipment, and find the card MYLAPS X2 reader.
2. Check X2 server address and X2 user, and press Save X2 settings if you change them.
3. Press Download the X2 reader. You get a zip file made for this venue.
4. Unpack the whole folder Elapse X2 to a place where it can stay, for example C:\Elapse X2.
5. Double-click Create desktop shortcut.bat. The shortcut Elapse X2 is now on the desktop.

Every time

1. Connect the PC to the network of the X2 server. It needs the internet at the same time.
2. Double-click Elapse X2 on the desktop, or Start X2.bat in the folder.
3. Type the X2 password when the program asks. It is asked for every time and is not stored.
4. Leave the window open during the meeting. It may be minimised. The Run page shows X2 connected.
5. Stop with Ctrl+C or by closing the window.

• Windows may ask whether the file may run the first time: choose “More info” and “Run anyway”.
• If the internet drops, the passings wait on the PC and are sent when it is back, as long as they are not older than 30 seconds.
• Run the reader on one PC per venue. Two do no harm, since a passing is stored once, but one is enough.
• The folder holds the key for sending passings to this venue. Keep it within the timing crew.
• The loop names on the X2 server are matched to the timing points by themselves when they are called Finish, 200m, 100m, Red and Green. Loops that are not in use are listed in Loops that are not used.

Reading periods: which race gets the passings #

The chips are read all the time, also during warm-up. A passing is only kept when a race is reading. One race at a time reads at a venue.

• A passing belongs to the race that was reading at the moment the rider passed, not when the passing arrived. A passing that arrives late, after a short internet drop, still lands in the right race.
• A passing from before reading started, or from after it stopped, is not stored on any race.
• With no race reading, nothing is stored. The only exception is lap counting on the open track.
• An official race takes no more passings.
• A chip that is not on the start list is stored too, and shown as Chip not on this start list.
• A rider who stands still on a loop is read again and again. Reads of the same chip on the same loop that come closer together than the fastest possible lap (10 seconds on a 250 m track) count as one visit to the line, not as laps.

Test without equipment #

• Simulated passings: on the Run page, organisers and Elapse have the button Test: simulate passings. It makes up the chip passings of the race (or of the heat on track) and reads them in the normal way, so the result is worked out exactly as with real passings. The riders need a chip number, and a bunch race needs at least two riders. Use it for testing only, never during a real race.
• Test events: Events › Upload event file › Create test event gives you a made-up meeting with invented riders and chips, ready for simulated passings.
• The start clock: the Test buttons on the Equipment tab send a countdown to the clock without a race.
• The chips: Start X2 (bare se).bat shows what the X2 server reads, without sending anything on.

Delete test results before the meeting, or practise in a test event. After testing with communiqué numbers on, press Start the numbering again on the Staff tab.

The Run page, step by step #

Open it with Run on the race’s row in the programme, or Run race on the race page.

1. Before the start: check the start list, and the tags X2 connected and, for races with a start gate, TimerBox connected.
2. Press Send live view to screen once. The big screen now follows what happens on this page.
3. Start: press the start button of the discipline (see below). The race reads passings from now on, and its status becomes Live by itself.
4. During the race: watch what the passings give. Tap or type where the commissaires see it differently.
5. After the finish: press Finish: provisional. Check the result against the photo finish and the commissaires under Edit results.
6. Press Official, or Official + podium to also show the top three on the big screen.

• The page reloads itself when the passings have changed the result, unless you are typing in a field.
• Every time, lap count and place shows where it came from: Chip, Track contact, Manual or Photo finish.
• To enter everything by hand in one race, untick set the result from the passings (or save the time from the passings by itself in timed races).
• An official race is locked. An organiser or Elapse opens it with Reopen.

Passings, laps and corrections on the Run page #

Bunch races, sprint and keirin have a box called Laps and result from passings (or Heat … from passings). Timed races have Times from passings.

Lap now, To go after this lap

Where the leader is. The next sprint or elimination is shown next to it, in red with THIS LAP when it is on the lap being ridden.

Lap by lap

One column per lap of the leader, newest first, with the order the riders crossed the line. −1 means one lap behind the leader. Sprint laps are yellow, elimination laps red. Tick show every lap to see all of them.

The rider table

Position, laps done, laps to go, the gap, and the last lap time of every rider.

+ now

The chip was not read: adds a passing for this rider at this moment.

+ missed

A lap is missing for this rider: adds it at the time the field crossed the line. The result is worked out again from all passings.

Neutralise, Back in race

After a mishap in a bunch race. The rider keeps the place in the race for the allowed laps (about 1300 m: 6 laps on a 250 m track), and the laps the field rides meanwhile are credited. Press Back in race when the rider is riding again. A rider who stays out longer loses the extra laps. A neutralised rider is not eliminated.

Passings read for this race

Every passing, newest first. Set aside takes one out of the calculation, Use again brings it back. Nothing is ever deleted.

the first crossing is the start, not a lap

Ticked as standard. The riders roll over the line at the start, or stand on it, and that crossing is not counted.

“laps to go” follows the leader

Ticked as standard. The laps to go on the big screen then count down by themselves.

Laps to go: bunch races and keirin have a dark box Laps to go at the top. With chips it follows the leader. By hand: press Show laps to go on screen, then − 1 lap each time the leaders cross the line. The big screen shows the number, “Last lap” at 1 and “Finish” at 0.

Wrong count while the chips are counting (1.6.0): press − 1 lap or + 1 anyway. The whole count moves with it: the sprint laps and the finish follow the corrected number, and a tag shows Lap count corrected by hand with a button back to the plain passings. Half a lap earlier: on the Screen tab, “Laps to go” changes at can be set to a loop on the far side of the track; the next number is then shown when the leader passes that loop instead of the finish line.

After the finish (1.6.0): the race is over when the first rider completes the race distance. Every other rider is placed at his next crossing of the line, and the laps ridden after that (cool-down) are not counted, so a leader who rides on does not put the field a lap down. Laps gained and lost are entered by hand only (+ lap / − lap); the app no longer works them out from the passings, but it takes what you enter into account when it judges sprints and the finish.

Flying 200 m Time Flying start #

Afterwards, the sprint rounds are made from the result. See Sprint.

Sprint Finishing order Bunch start #

Best of three, one ride at a time

At many meetings the three rides of a round are not ridden straight after each other: ride 1, then other races, then ride 2, and a third ride only where it stands 1–1.

Set it up in the programme

1. On the Programme tab, press Best of 3 (or 1 ride) after the name of the sprint round. In the box, press Rides as rows of their own.
2. The race’s own row is now Ride 1, and two new rows come right after it: Ride 2 and Ride 3 (if needed). Drag them to where they are ridden. Each row takes the time of one ride of every heat.

Run ride 2 and ride 3: the same way as ride 1

The three rows are one race with one Run page. Nothing special is switched on for a later ride: the page remembers what has been ridden and counts on from there.

1. Press Run on the ride row. It opens the same Run page as ride 1. Each heat shows where it stands, for example Ride 2 next.
2. Other races have been run in between, so press Read passings again. Only one race reads the chips at a time.
3. Choose the heat that rides under Heat on track. Do this before every start: the page does not move to the next heat by itself while a heat is undecided.
4. Press Ride started: count from now when the riders start. The winner is set from the chips, or you tap the winner under Tap the winner of each ride.
5. Do the same for the next heat. A heat that stands 2–0 after ride 2 shows Decided 2–0 and is not ridden again. Only the heats that stand 1–1 ride the third time.
6. Between the rides, leave the race as Live and go on with the next race in the programme. Do not set it to Provisional before the last heat is decided: that ends the race and stops the reading.
7. When every heat is decided, set the race to Provisional and make the next round.

• A wrong winner: Undo last ride on the heat takes the last ride away, also a ride from earlier in the day as long as it is the last one of that heat.
• The public page, the PDF and the big screen show the rides as rows of their own, for example “Sprint – Semi-finals – Ride 2”. A ride row is marked as done when every heat has had that ride or is decided, so “Ride 3 (if needed)” is done at once when all heats ended 2–0.
• The result list shows, for each rider, the rides in order (1 = won, 0 = lost, for example 1-0-1) and the number of rides won. The big screen draws a trophy for each ride won. The rider is ranked in the heat when the heat is decided.
• The ✕ on a ride row puts all rides back in the race’s own row. Setting the round to one ride removes the ride rows too.

Making the rounds

• Heat names and heat order on the board (1.11.2): on the start list of a sprint or keirin race, every heat on the Start order board has a name field and ▲ ▼ arrows. Name the finals fills in Final for gold, Final for bronze, Final 5–6, 7–8… in riding order (in the screen language); the arrows move a whole heat earlier or later, and the name follows it. Press Save start order. The Run console then says “Final for gold” with the two riders, instead of “Heat 1”, and so do the big screen, the lists and the PDFs.
• Finals straight from the qualifying (1.11.0, the Banecup way): under the same card, Make the finals: the fastest (2, 3 or 4) go straight to the final for gold – a walkover past every earlier round – and the rest ride finals for the places after them, 3–4, 5–6… (or bigger finals, 3–6, 7–10…). One race “Finals” with one named heat per final, ranked across the heats, so the sprint tournament standings run 1, 2, 3… for the whole class. A leftover rider joins the last final. The Programme tab shows a Sprint tournaments card per class – the qualifying and its rounds with their status, like the omnium cards – with the button to make the finals once the qualifying is official, and the standings and PDF after.
• First round: open the Flying 200 m, the tab Results, and find Sprint tournament. Choose how many riders go through, and one ride or best of three, and press Create sprint round. The fastest meets the slowest qualifier, the second fastest the second slowest, and so on.
• Next round: when every heat has a winner, open the sprint round’s Results tab and press Create next round. From the semi-finals you get both the Final and the Final for bronze.
• Sprint heats where everybody rides: press Create sprint heats by ranking instead. The riders are put in heats of 2 to 6 with those nearest in time. Nobody is knocked out. After each round, Create next sprint heats moves the winner of a heat up one heat and the last rider down one.

Team Sprint Time Start gate + countdown #

Rounds: under Next round on the Results tab, the app offers the first round with the 8 fastest teams (4 v 5, 3 v 6, 2 v 7, 1 v 8), and then the finals: of the four heat winners the two fastest ride for gold, the other two for bronze. With fewer teams it offers finals straight from the qualifying.

Time Trial Time Start gate + countdown #

The race needs Laps or Distance, so the app knows which crossing is the finish. Crossings in the first 5 seconds after the start are the start itself.

Individual Pursuit Time Start gate + countdown #

• In the qualifying a caught rider rides on and gets a time. A catch is shown as a warning, but changes nothing.
• For finals, tick these two under Race settings and status: Final: each heat is a duel. The last heat rides for gold, the heat before for bronze and A rider or team that is caught has lost. Finals made by the app have them ticked already.
• Rounds: under Next round on the Results tab of the qualifying, the app offers the finals from the four fastest riders: 3 v 4 for bronze, then 1 v 2 for gold.
• For the coaches at the track there are pursuit boards for tablets.

Team Pursuit Time Start gate + countdown #

Rounds: under Next round the app offers the first round with the 8 fastest teams (6 v 7, 5 v 8, 2 v 3, 1 v 4), and then the finals: the winners of heats 3 and 4 ride for gold, the two fastest of the other teams for bronze. With fewer teams it offers finals from the four fastest.

Keirin Finishing order Bunch start #

Next round: on the Results tab, open Next round. Type how many of each heat go on and to which round, for example the first 2 to “Final 1–6” and the next 2 to “Final 7–12”, and press Make next round. Riders can also be added to a race that exists, such as a repechage.

Scratch Laps, then finishing order Bunch start #

Points Race Points Bunch start #

Tempo Race Points Bunch start #

Elimination Elimination order Bunch start #

Longest Lap Finishing order Bunch start #

Madison Points Bunch start #

Omnium Sum of four races #

From provisional to official #

1. When the race is over, press Finish: provisional on the Run page. The race stops reading passings.
2. Check the result against the photo finish and with the commissaires. Correct under Edit results.
3. Print or show the unofficial result if you like. The big screen says “Provisional results”.
4. When the commissaires approve, press Official, or Official + podium.

An official race is locked: the start list and the results cannot be changed, and no more passings are stored on it. If something must be corrected, an organiser or Elapse presses Reopen on the Run page. The race goes back to Unofficial.

You can also set any status by hand under Race settings and status on the race page. See Race status.

Correct a result by hand #

Open the race and its tab Results (the button Edit results on the Run page, or Edit on the Results tab of the event). The card is called Enter and correct results.

Press Save results. Every change is logged with your name. The card Calculated result below shows the result as it now stands.

DNS, DNF and DSQ #

DNS

Did not start.

DNF

Did not finish.

DSQ

Disqualified.

• Set it in the Status column under Edit results, or next to the time field on the Run page of a timed race.
• A rider with one of these has no rank and is listed last: DNF first, then DSQ, then DNS.
• In an omnium the rider gets 0 points from that race. Adjust with Points adj. on the omnium if the commissaires decide otherwise.
• In a sprint, a rider whose opponent is DNS, DNF or DSQ goes through on a walkover.
• A rider who is not coming to the event at all: set the rider’s own status to DNS (did not start) or Withdrawn on the Riders tab. The rider is then not offered for new start lists.

Decisions: warnings and relegations #

The tab Decisions on the race page holds the decisions of the commissaires’ panel.

1. Choose the Rider, or leave it on General.
2. Choose the Code: Note, Warning, Fine, Relegation or Disqualification.
3. For a relegation, type the place in To place.
4. Pick a Reason from the list or write your own, and press Add decision.

• Disqualification sets the rider to DSQ in this race.
• Relegation with a place sets the rider’s rank. The riders behind move up. Without a place, correct the order yourself under Results.
• Warning: the app counts the warnings of each rider in the event and tells you when it is not the first.
• The decisions are printed under the results on the result list. W and REL are shown next to the rider.
• The list of all decisions of the event is on the Staff tab.

1.27.0 – the commissaires’ standard texts. The decision form has a Standard text list: the track commissaires’ penalty list (38 texts in seven groups – movements on the track, behaviour, advertising, equipment, intervention of staff, absences, race number), in the event’s language, each with the row of the UCI track penalty table it refers to. Choosing one fills the reason as “For riding on the blue band (ref. 5.2)”; the reason stays editable, and a “...” in a text (“For deliberate and flagrant fault against ...”) is selected so you type the name over it. With the rider and the code the communiqué line reads “Rider 99 – Warning – For not holding their line during the final sprint (ref. 5.1)”. Typing still works: the same texts are offered as you type. What a code does to the result is unchanged (above).

Next round #

When a race has a result, its Results tab has the card Next round.

• Any race: “The first … go to …” and “The next … go to …”. Type the numbers and the name of each round, and press Make next round. In races with heats the numbers are per heat. The best riders are spread over the heats of the new race.
• Riders can go to a new race, or be added to a race that already stands in the programme.
• Pursuits and team events have ready-made buttons for the first round and the finals. See Individual Pursuit, Team Pursuit and Team Sprint.
• Sprint has its own card, Sprint tournament. See Sprint.

The new race is an ordinary race with the status “Start list ready”. Check its heats on the start list and move it to its place in the programme.

Track records and personal bests #

• TR marks a time in a timed race that beats the track record of the venue the event is held at, for the same discipline, distance and class.
• NR marks a time that beats the Norwegian record (1.8.0). The big screen shows “New Norwegian record” when the time comes in.
• PB marks a rider’s best time in that discipline and distance across all events. It needs a UCI ID on the rider and no setup.
• All three are shown on the result lists, in the PDFs and on the big screen. The marks say that the time is faster than the list; records are ratified by the federation.

The records are under Records in the top menu. Organisers and Elapse add and change them: discipline, distance, class names, time, holder, club, date, and Applies to: the Norwegian record, or the track record of one venue. When the winner of a race beats the track record, or no track record is registered, the Results tab of the race shows a yellow box with the button Save as track record; it is saved for the venue of the event.

Points by rank and points standings #

For a cup or a series, a race can give points for the final rank. Type the list in Points by rank when you add the race, or later under Race settings.

• A list, the winner first: 10 8 6 5 4 3 2 1. Ranks beyond the list give 0.
• The word auto: the last place gives 1 point, and one more per place up to the winner. With 14 starters the winner gets 14. Riders with DNS are not counted.
• The result list gets the column Pts, and the rider’s page shows the total.
• The Results tab and the public page show Points standings per class: the sum over all races of the event. Equal totals are split on most wins, then most second places.

These points are separate from the points inside a points race or an omnium.

PDFs, communiqué numbers and “Revised” #

Every PDF is made fresh from the stored data each time you open it, so it always shows the latest result.

Communiqué numbers

• With numbering on (Setup › Printouts), start lists and result lists are numbered in the order they are first printed by somebody who is logged in.
• A start list gets its number once the race is “Start list ready”. A result list gets its number once the race is Unofficial or Official. Before that the list is a draft without a number.
• The number stands in the heading (“Communiqué No. 12”) and first in the file name.
• If the list has changed since it was last printed, the next print is marked Revised 1, then Revised 2, and so on. Going from Unofficial to Official alone does not make a revision.
• To use your own number for a race, type it in Communiqué no. (own) under Race settings. It is used on both lists of that race.
• A number is never used again, also when the race is deleted. PDFs opened from the public page never take a number.
• The Staff tab lists the numbers given so far.

Export #

• Export on a race page gives the result of that race as an Excel file.
• Export all results (Excel, DataRide layout) on the Results tab gives one file with one sheet per race that has a result.

The columns are Rank, BIB, UCI ID, Last Name, First Name, Country, Team, Gender, Phase, Heat, Result, IRM and Sort Order. Gender is taken from the class name and is empty when the name does not tell. Look through the file before you upload it to UCI DataRide.

Open the big screen #

• On a second display on your own PC: on the Screen tab, under Screen link, press Open on external screen. Chrome or Edge asks once for permission to place windows. Click in the new window, or press F, for full screen.
• On another PC: copy the link from the same card, open it in the browser there and press F11.
• Open in a new tab shows the screen in a tab, and the Preview at the bottom of the card shows it on the page.

Screen of the venue: when the event has a venue, the card also has a link that belongs to the venue. It always shows the event that is on there: the event whose dates include today. The screen PC at the venue then needs its link only once. For a test day, press Show this event at the venue now, and Let the venue follow the date again afterwards.

If the screen cuts the picture along the edges, set Free edge % under Fit to the screen.

Main and timekeeper: who decides #

Two controls can put something on the screen:

Main

The Screen tab. Whatever is chosen here is shown.

Timekeeper

The buttons on a race: Start list to screen, Results to screen and Podium to screen on the race page, and Send live view to screen on the Run page.

Main always wins, except when Main is set to Follow timekeeper. That is the normal setting during racing: the timekeeper’s choice then goes straight to the screen.

The box at the top of the Screen tab shows three lines: Main, Timekeeper and On screen now. If the timekeeper sends something while Main shows something else, a yellow message tells them that it will appear when Main is set to follow the timekeeper.

What the screen shows by itself #

The screen does not jump to a new race by itself: somebody sends the race to it. But what it shows of that race follows the race and its status.

The choices on the Screen tab #

Follow timekeeper

Lets the timekeeper’s choice through. Use this during racing.

Logo

The event logo.

Clock

A big clock with the date.

Black screen

Nothing.

Race

Choose a race, then Show start list, Show results, Show live race or Show podium. Finished races are listed last and greyed, so the next race is at the top (1.6.0). A race with heats gets a second choice: All heats page by page, or one heat only, for the start list, the live view and the result.

“Laps to go” changes at

Under Appearance. Normally the laps to go change when the leader crosses the finish line. Choose a loop on the far side of the track and the next number is shown when the leader passes that loop, half a lap earlier.

Message

Type a heading and a text, for example “Welcome” and “Racing resumes at 14:30”, and press Show message.

The button of the choice that is on is coloured. To go back to normal, press Follow timekeeper.

Podium #

The podium shows the top three of a race in gold, silver and bronze, with flag, club and time or points. Three ways to show it:

• Official + podium on the Run page: sets the race official and shows the podium in one press.
• Podium to screen on the race page.
• Show podium on the Screen tab, after choosing the race.

A race that is decided heat by heat (sprint, keirin), or that has no ranked riders yet, shows the result list instead. In a joint race with separate results the podium shows the first class.

Programme and break screens #

• Follow programme shows what is on now and what comes next, from the times in the programme. A race that is Live is “now”. A race that is Unofficial or Official is done. Otherwise the clock decides.
• Show whole programme shows the timetable of the day.
• Start break countdown now: type the name and the minutes. The screen counts down and says when racing resumes. The same is done with Start on screen on a break in the programme.
• Behind schedule: move the times on the screen with − 5 and + 5, press On time to go back to zero, or Automatic to let the app measure the delay. The printed programme is not changed.

Language, colours, logos and sponsors #

Under Appearance and extras on the Screen tab. Press Save appearance after a change.

Language on the screen and on PDFs

English or Norwegian. The same setting as on the Setup tab. Names, class names, your own titles, messages and the text line are shown as typed.

Background colour, Accent colour

The colours of the screen. The accent follows the event colour until you choose another.

Show the clock in the corner

A small clock on top of whatever the screen shows.

Text line along the bottom

A line of text on top of everything, for example the next race. Empty means off.

Show flags next to the riders

The flag comes from the rider’s nation code.

Club logos next to the riders

As they are puts transparent logos straight on the background, On a white chip is for dark logos that would disappear, Off shows none. The logos come from one folder on the web, set once by Elapse under Admin › Branding: the file name is made from the club name (lower case, æøå as ae/o/a, “Sykleklubb” and “Sykkelklubb” as sk, “Cykleklubb” as ck, “Cycle Club” as cc, “Idrettslag” as il, then letters and digits only), so Stavanger SK looks for stavangersk.png and Sola Cykleklubb for solack.png. A club whose file has another name is listed there as Club name = file. A club without a file simply shows no logo. That page also lists every club in the database with the file it looks for.

Seconds “points awarded” is shown

How long the points panel stays up in points races.

• Event logo and timer logo are set on the Setup tab.
• Sponsor logos: add PNG or JPG files of at most 3 MB under Sponsor logos and press Add logos. They are shown along the bottom of “Follow programme” and the break countdowns, and one at a time with Show sponsors.

Pursuit boards for tablets #

At the bottom of the Screen tab there are two links: Red line (start position 1) and Green line (start position 2). Open one on a tablet at each pursuit line and hold it up to the rider.

• The board fills the screen with the gap to the opponent at every half lap, in seconds and metres. − means ahead, + means behind.
• It also shows the lap and the last half-lap time. With one rider on the track, the gap is to the best time so far.
• It follows the pursuit, team pursuit or time trial that is live. It needs no login and updates about once a second.

The public live page #

1. On the Results tab, press Switch on public live page.
2. Copy the link that appears and share it, for example as a QR code at the track.
3. The button Public page ↗ at the top right of the event opens the page.

The page shows:

• On now and Coming up, from the programme.
• Before the event: the page goes by the date, not only by the clock. Until the first day it says how many days are left (“Starts in 3 days”, “Starts tomorrow”) with the day and the time of the first row, and nothing is marked as on now. On a day of the event, before the first row, it says “Starts in 2 h 10 min”. After the last day the whole programme is shown as finished. This needs From date under Setup: without a date the page can only go by the clock.
• The race that is Live, with the standings as they come, laps to go and the last sprint.
• The whole programme with status. The clock time is shown on the rows marked “public” (see Start times on the public programme), the others show the number of heats and about how long they take. The times follow the minutes behind schedule.
• The points standings, when races give points by rank.
• Every race: its start list once the race is “Start list ready”, and its result once the race is Live, Unofficial or Official.
• Links to the PDFs: start list, results, programme and all results.

The page reloads itself every 10 seconds while a race is live, else every 30 seconds. It uses the language of the event. After the event it stays as the result archive, until you press Switch off.

All public events #

All public events, next to the link on the Results tab, opens the list of every event whose public page is switched on, newest first, year by year. An event with a race that is live is marked Live.

The speaker page #

Press Speaker page on the Results tab and give the link to the speaker. Since 1.14.0 it is a page in three columns:

• Programme (left): every row of the day with the programme time, the estimated time when the day is behind or ahead of schedule (the delay from the Screen tab, automatic or set by hand), ON NOW, NEXT with “in 12 min”, and ✓ for the races that are run. Click a race to show it in the middle.
• The race (middle): the one clicked, else the one on now, else the next. Its times, discipline, laps, distance, sprints, heats and the record to beat; laps to go and the standings while it is live, the result when it is finished; and the riders with bib, full name, club and team, nation, age class, UCI ID, UCI rank (on UCI events) and what they have done earlier today (“1. Scratch · 3. Tempo race”). Line-ups show fence and lane, timed races the heats.
• Coming up and latest results (right): the next races with their estimated times, and the top three of the last finished races. Click any of them to open it in the middle.

The page reloads itself every 5 seconds and keeps the race you chose and your place on the page. The clock and “Behind schedule” are at the top. The link holds a key, so do not post it publicly.

Links for the organiser’s website #

The organiser often has a page of its own (for example on trackcycling.no) with the start lists and results as PDF. Instead of uploading files, give them links: a PDF is made the moment somebody opens the link, so a link pasted on the website before the event shows the final list afterwards, corrections included.

1. Switch on the public live page on the Results tab.
2. Open Links for the organiser’s website under the buttons, on the Results tab or the Programme tab (1.6.2). There is one link for the live page, the programme PDF (and one per day when the event has several days), all start lists and all results, and for every race a start list link and a results link.
3. Click a field to select the link and copy it. Send the links to the organiser once.

• The links work without login as long as the public live page is on.
• A start list opens when the race is Start list ready, a result list when the race is live, unofficial or official. Before that the link says “Not found”.
• The simplest set for a website: the live page, “All start lists” and “All results”.

The roles of the event #

• Add: pick the role, write the name (the field suggests the people who hold that role, the venue’s first) and a note if you like (“day 1”, “afternoon”), press Add. Several at once: “Anne Berg, Ola Dahl”. A role can have any number of names – the jury has several.
• remember (ticked by default): a new name goes on the people list with the role, so it is suggested next time. A name that is already on the list is linked to it, and the role is added to that person if they did not have it.
• Copy the officials of another event – the last one at this venue, say – puts its names here; names already here are not doubled.
• Where they show: the speaker page (card Officials), the end of the programme PDF, one small line with the commissaires’ panel and the timing on every result PDF (as on a UCI result sheet), and – when Show on the public page and in the API is ticked (it is by default) – a card on the public live page and officials in the API’s event answer. Untick it to keep the names in-house.
• ✕ removes a name from this event only.
• Accreditation cards (PDF) (1.25.0): one credit-card-sized card per official – name, roles, a colour band per group (organisation in the event colour, the panel red, timing dark), the event’s logo, name and dates – ten per A4 page with cut marks, for the laminator. badges.php?event=…&role=pcp gives one role only.
• Team of the day (1.25.0): on the Screen tab the officials can be put on the big screen as a calm slide by group – between races, or at the end of the day.

The people list #

One list for the whole server: a person, the roles they usually hold, their venue (optional), club, a note – and, for managers only, e-mail and phone. Everyone logged in may add a person; managers edit and remove. The list is filtered by venue, and the suggestions on the Officials tab put the event’s venue first, then people without a venue, then the rest. Removing a person never touches events: the name stays on every event it was written on. Use on a row jumps to the add field with the person’s name and first role.

Contact details are for the organiser’s own use (calling the speaker); they are never shown to the public, never in PDFs or the API. They live in the database like the rider list – so they are in the backup, and nowhere else.

Notifications (1.25.0): a person with an e-mail address gets the event notifications – the first official result of the day, “event finished” and the final report – for every event at their venue, and for events they are an official on. Managers switch it off per person (notifications in the form; ✉ off on the row). The Elapse address, the venue organisers and the event’s users get them as before.

Line-up sheets #

A line-up sheet is for the starter and the people who line the riders up. It has the start order of the race with a box to tick, where each rider stands (at the fence or in the sprinters’ lane, or at the red or green line in pursuits and time trials), and the chip the rider should have.

• The table lists every race with its start time, the number of riders and the state of the line-up: fence / lane set, not set, or the number of heats.
• Line-up sheet on a row opens the sheet of that race.
• All line-up sheets (PDF) gives every sheet in one file. With several days there is also one button per day.

The order itself is set on the start list of each race. See Start lists.

Communiqué overview #

The card Communiqués lists every numbered list: the number, whether it is a start list or a result list, the race, when it was issued and by whom, and Revised 1 when it has been printed again with changes. It also tells you which number comes next.

Start the numbering again (organisers and Elapse) removes the numbers given so far. Lists get new numbers the next time they are printed. Do this after testing, before the event starts, and not during the event.

Decisions, chips list and other sheets #

Decisions and penalties

Warnings, relegations, fines and disqualifications, race by race: the list the secretary hands out at the end of the day.

Numbers and chips

Every active rider with number, club, class and chip, for handing out numbers and transponders. The card tells you how many riders have no chip yet.

Timetable

The programme with start times.

All start lists, all results

Every list in programme order in one file.

Counting laps #

1. Start the Elapse X2 reader, as for a race. The laps come from the chips.
2. Press Switch on. The tag says Counting laps, and a green dot shows next to Open track in the top menu.
3. Press Switch off before a race, and on again afterwards.

• A lap is counted from finish line to finish line: two passings of the same chip in a row.
• Riding while counting is off is not counted, and the break between two periods never becomes a lap.
• A rider who leaves the track and comes back later than Longest lap that counts (s) does not get a lap for the break. The standard is 120 seconds.
• The board shows, per rider: laps in this period, total laps, total distance, the last and the best lap time, and when the rider was last seen. It refreshes by itself.
• Lap screen on external screen opens the board for a big screen.

Under Settings, organisers and Elapse choose the Venue whose equipment counts the laps and the longest lap. Reset all totals sets every rider back to zero and cannot be undone.

Riders and their own page #

• Under Add a rider, type the name and the chip number and press Add. Laps for that chip are counted from now on, and what the chip has already ridden shows up at once.
• A chip that is read but belongs to nobody is listed as Unknown chip …. Add a rider with that chip number to give the laps a name.
• QR / link gives the rider a page of their own with laps, kilometres, laps per day and the latest lap times. It needs no login.
• Remove takes a rider off the list. The laps stay on the chip and come back if the rider is added again.

Users #

Every user with name, role (Elapse, organiser, venue organiser of one venue), colour, e-mail, whether the account is active, and a new password. 2-step switches the two-step login on for the user (see What protects the results). Users are grouped by role and venue.

Venues #

A venue is a velodrome with its track length, its timing points (MyLaps loops and TimerBox channels, each with its distance before the finish), its own key for the equipment PC and its own link for the big screen and the live page. Each event picks its venue under Setup and gets the track length and timing points from here. When a venue is changed, the events at the venue that are not over yet follow; finished events are left as they were.

Two venues can be used at the same time: passings from a venue’s equipment only reach the race that is reading at that venue, and the venue’s screen link shows the event that is on there that day (a real event before a demo).

Race presets #

Ready-made race setups that are picked when adding a race to any event’s programme: discipline, round, laps or distance, laps between sprints, number of sprints, riders per heat and points by rank. Under Programme › Add race, choosing a class shows the presets made for that class, and a preset fills in every field: the organiser can still change anything before adding the race, and on the race afterwards. The table at the bottom shows, per class and discipline, which presets exist; “n for all” = only presets that fit every class; empty = nothing yet (the organiser then fills in the race by hand). Hover a name to see the setup.

Disciplines #

How each discipline is run and timed here. The settings apply to every event; a single race can still have its own start and stop point under its race settings. Everything worked out from the equipment can be corrected by hand in the Run console.

• Time from → split → time to is the order the rider passes the loops and track contacts. Suggested time decides whether the track contact or the chip is used when both have given a time; with “only”, the other one is still listed in the Run console and can be picked by hand.
• Laps, sprints, eliminations and the finishing order are counted from the chip readings on the laps counted on loop. Team event decides whether riders are grouped in teams on the start list (Madison) or ride alone.

Branding and the logo archive #

The Elapse logo is shown in the top bar and on the small “Timing system by” badge on the big screen: upload one version for dark backgrounds and one for light backgrounds; the built-in logo is used until then. The logo archive holds logos that every organiser can take from on the event’s Setup tab – the federation, UCI, Trackcycling, cups, arenas and clubs. Upload them here once, PNG or JPG (transparent PNG looks best on the big screen), up to 3 MB each. On the event the organiser presses Use to make one the event logo, the timer logo or the PDF background, or to add it as a part of a combined logo. Removing a logo here leaves the events that already use it alone: they got their own copy.

Hardware: countdown clocks and the lap counter #

Countdown clocks. From the TimeTronics manuals: the clocks are driven over a serial line from the timing PC (through the connection box, clock set to LED mode), and it is the countdown clock that releases the start gate at zero. The manuals do not give the bytes; capture them with the Elapse listener (see its README) and paste them here.

The lap counter. The big lap display that is stepped down by hand. Everything on the TimerBox line that is not a TimerBox message reaches the server through the link window, and the Run console shows it beside the chip count – never on the big screen. Read a number out of it in one of two ways: a regular expression with one group on the text of a message (e.g. ^L(\d+) when the counter sends L012), or the TimerBox input the counter’s button is wired to: the count then starts at the race’s laps and goes down one per impulse. Until one of them is set, the Run console shows the raw messages so the format can be seen.

Backup #

Downloads one file with everything: events, riders, start lists, results, users and the audit log (logos are not included); download a copy before and after each race day. A copy by e-mail now and by itself the day before and after each event, and restore from a file – see Automatic backups.

Local copy for the timing PC (1.25.2). When the web host is slow or unreachable on race day, the whole program runs on the timing PC. Download the local copy (Elapse users) gives one zip with the program files of this version, a fresh copy of the database and the uploaded logos. Set up the PC the day before: unzip the package to C:\velodrome, unzip PHP for Windows (Thread Safe, x64) into C:\velodrome\php, copy local\php.ini into it and start local\START-LOCAL.cmd once to see the program open on http://localhost:8080/ (see local\README-LOCAL.md in the package). On the day: download the local copy, unzip it over the folder, start it, point the X2 listener (url in x2.ini), the TimerBox link and the screens at that PC, and run the day there. Afterwards Restore from a file on the server with data\velodrome.sqlite from the PC. Never run both for the same event at once.

1.27.6 – disk space. On a shared host the account’s quota is what fills up, and every site and mailbox under the account shares it; when it is full the host answers 507 Insufficient Storage and the database cannot write. The daily copies are now kept for 5 days (14 before), the before-update and before-restore copies to the newest 3 (they were never removed before – 20 MB each), and Tidy old copies under Backup does the same at once. Photo-finish pictures are scaled to at most 1920 px wide and saved as JPEG when they come in (a 12 MB screenshot becomes a few hundred kB). Server health shows what the data folder uses, by kind.

Feeds #

1.25.4. What every equipment PC sends in, per venue: whether the X2 reader and the TimerBox link are heard from, the last post (passings, stored, time it took), the last hour and the last day (posts, passings, stored, dropped, errors, average time per post), the race that reads passings at the venue with how many passings it has collected, and a bar per five minutes for the last two hours (grey = heartbeats only, red = errors). A reader at a venue nobody is racing at – a test race left on “Read passings”, a club training in the evening – fills the database and costs the server for everyone; here you see it and can do two things from afar: Stop reading (the race’s “Stop” in the Run console) and Pause feed. A paused feed answers the reader 200 with paused: true and keeps nothing, so the reader does not pile up and resend; the Run console at that venue shows “X2 paused by Elapse”. Pause all feeds does it for every venue. Resume before a race: what came while paused is gone. Elapse users only.

1.26.1 – the counting costs less, and a flood is pointed out. The counts are collected in a small file and written to the database every ten seconds, in one go (until 1.26.0 every post from a reader made two writes of its own, and a paused venue whose readers kept posting took the write lock ten times a second for bookkeeping – that was behind “database is locked” on pages at the other venue). The numbers on this tab can therefore be a few seconds behind. One reader program posts about twelve times a minute when the track is quiet; when a venue shows far more than that, the tab says many posts – several reader programs, or a test tool, are sending at once, and the extra ones should be stopped on the equipment PCs. A reader of 1.26.1 or later waits ten seconds between posts while its venue is paused.

1.26.2 – Block feed. The harder switch beside Pause: the equipment at that venue is answered 403 before anything is read or written – nothing stored, nothing counted, no cost to the server. The reader keeps its passings and tries again every 10 s. For equipment that must stay out, such as tests from another venue against the live server; the keys stay as they are, so unblocking needs nothing on the equipment PC. The Audit log notes who blocked and unblocked.

1.26.3 – the emergency brake by FTP. When the server is so busy that Admin cannot be reached: upload a text file BLOCK-FEEDS.txt to the program folder (next to api.php) with one scope per line – v3 for venue 3, e12 for an event with its own setup – or the word all. api.php answers those 403 before the program or the database is loaded, so a flood from that equipment costs nothing from then on. Admin › Feeds shows “blocked by BLOCK-FEEDS.txt”; remove the file or the line to let the equipment in again. The file is not part of the update package and is never overwritten by one.

1.27.2 – the equipment is answered fast. A request from a reader or the TimerBox waits 1.5 s for the database at most (a page waits 5 s and tries again four times). When the database is busy, the reader gets 503 busy, send again as a short JSON answer – it keeps its passings and sends them again two seconds later (a reader of 1.27.2 says so in its window; older readers log “no contact” and send again after a second – nothing is lost either way). Why: on a shared host every waiting request is a PHP process the host cannot give to any other site under the same account. On 11–12 November the readers’ waiting requests filled every process, and all of elapse.no stood still, not only Velodrome.

1.27.3 – a cap on passings per race. Every post from the equipment makes the program recompute the reading race from all its passings – fast for a race (a 40 km points race is a few thousand), slow when a race has read for a whole day of training (17 000 at one venue). At 12 000 passings the program stops reading on that race, says so in the Run console and the log, and the equipment is answered normally. Press “Race started: count from now” (the old passings are set aside) or use a new race, then Read passings again. Reading also stops by itself after six hours (1.11.0).

Log #

1.26.4. The whole audit log in one place: every event and everything logged outside an event – logins, API keys, backups and the local copy, venues and their keys, users, feeds paused or blocked, records, the chip and licence registers, updates. Filter on part of a user’s name, part of an action (“Deleted”, “Logged in”, “key”) and a period; the list of users shows who has entries in the last 90 days. With a user filtered, a line above the table counts their entries per action – click one to narrow further. Each row links to the event’s own Log tab.

What the log does not hold: page views, result lookups, PDF and start-list downloads, API reads, and what the public page or the screen showed. It notes changes and logins. Failed logins of the last 24 hours are under Security; logins themselves are entries (“Logged in”) here and there. The log is kept for good – it is not trimmed.

Security #

The security check (the data folder blocked, HTTPS, program files against the manifest), the error log, the photo-finish code and the version list – see The security check, program files and the error log.

Server health (1.25.2). The card at the top of the tab shows what to look at when the server is slow or says “database is locked”: the database size and journal mode (WAL, where readers and writers do not block each other), how long one read and one write took, how many lock waits there were in the last 24 hours, whether PHP can finish a page before the after-work (webhooks) runs, webhook deliveries waiting and keys failing, and free disk. A lock wait is not an error any more: the statement waits up to 5 seconds and then tries four more times with pauses before giving up; each wait is noted in the error log with the page it happened on.

1.27.7 – if you switch the PHP version in the host’s control panel (a way to restart stuck PHP processes), make sure these extensions are on for the version you land on: pdo_sqlite, sqlite3, gd, mbstring, fileinfo, zip, curl. Without pdo_sqlite every page says “could not find driver”.

1.27.8 – session files. Every request used to start a PHP session, and a reader keeps no cookies, so every post from the equipment left a session file on the host – tens of thousands a day, which count against the account’s quota as surely as megabytes do. Key-based requests start none now, and Server health shows the session files with Delete old session files. If the folder cannot be read from here, the host’s file manager can delete old sess_* files (often in tmp under the account).

Usage and the season report #

Season report (1.23.1). Pick a venue and a period – a season is October to February, and the quick buttons give the seasons that have events – and the card lists every event of the venue whose first day is in the period: dates, organiser, riders, races, races with results, the add-ons activated (by whom; “off” when switched off again, still charged) and the modules used, and the sum to charge per event and in all. PDF gives the same as a document for the invoice (events, add-ons and modules per event, a summary per module with the venue’s included modules and the prices); CSV one line per event and module for a spreadsheet. Demo events are listed but never charged. Prices are the ones set under Admin › Modules when the report is made.

Every event on this server, by venue: riders, races, races with results and chip passings. The last column points out what can mean that one event has been reused for several: dates moved more than once, the event renamed, riders imported after results were official, or many riders deleted. The change log of the event (Log tab) shows who did what. A new event costs nothing, so a venue with few events and many flags is worth a conversation.

Show #

For the events that are a show – lights, sound and an audience to entertain. Ticked events get the extras on the big screen (rider presentation, winner celebration, LAST LAP); every other event stays exactly as it is. The organiser sees a “Show mode” tag on the Screen tab, and the button Present riders next to the start list.

Modules #

The base – events, riders, programme, timing, results, PDFs, the public page, the big screen and the speaker page – is always there. The extras are modules a venue pays for per event. With the switch off (standard) nothing changes: every feature is open for every event, and only the use is counted. With the switch on, an event gets the modules its venue has (ticked here, with an optional last day), the add-ons activated on the event, or its own choice of modules under its Setup tab (Elapse users); an event without a venue has everything. A feature that is not included is shown greyed with a note – nothing disappears. If anything goes wrong, switch it off and everything is as it was.

Invoice basis: how many times each module was used on each event – a DataRide file made, the licence check run, a photo or sponsors on the screen, the statistics opened, the report sent, the API called – counted whether the switch is on or off. To charge = the price of every module used that is not included for the venue; “venue” = covered by the venue’s modules.

Updates never touch your data #

• An update replaces the program files only. The events, riders, results, users, logos and backups are in the data folder, which is not part of an update and is never replaced.
• When a new version needs a change in the database, a copy of the database is saved first. The change only ever adds things, and it is done in one step: if it fails, the database is left exactly as it was.
• The version number is at the bottom of every page.

Automatic backups #

• Every day: one copy of the whole database is made on the first visit of the day. The copies of the latest 14 days are kept on the server, in data/backups.
• Before an update of the database: one extra copy, kept in the same folder.
• By hand: Elapse opens Admin › Backup and presses Download backup now, or downloads one of the daily copies in the list.

The security check, program files and the error log #

Admin › Security (Elapse) shows a list of checks:

Encrypted connection (https)

Should say OK. Without https, passwords can be read on the network, and the TimerBox link does not work.

Program files

Complete means that every file of the version is on the server and unchanged. Not complete or Mixed versions means that an update was only partly uploaded: upload the whole update again. Below it the latest errors are listed.

Database closed to the web

Should say OK. The page tries to fetch the database file the way an outsider would.

Wrong passwords

Five wrong passwords for a user name pause that login for 15 minutes.

Copies

How many daily copies there are, and the date of the latest.

If a page fails, it says This page could not be shown, with the time. Nothing was changed by the failure. Somebody who is logged in also sees the error text: copy it and send it to Elapse. The error is written to the error log of the installation (data/errors.log), and the latest ones are shown under Program files.

What protects the results #

• Nothing can be changed without logging in. The big screen, the public page, the speaker page and the riders’ own lap pages can only read.
• An official race is locked until an organiser or Elapse reopens it.
• Every change is in the Log tab of the event, with name and time.
• What you enter by hand is never overwritten by the chip passings.
• The licence register, the chip register and the staff sheets hold personal data and are only shown to users who are logged in.

Addresses without .php #

The pages can be opened as …/elapse-velodrome/programme?event=1 instead of programme.php?event=1. That needs the file .htaccess in the program folder and a web server that reads it. The app notices by itself when the server does it and then writes every link without .php; when the server stops doing it, the links go back to .php within 15 minutes. Admin › Security shows the state. The .php addresses always work, so a bookmark with .php is never wrong.

Versions #

Show: All New Improved Fixed – new features, things that work better or look nicer, and faults repaired. “In use here from” is when the version was installed on this server.

From the loop to the screen #

So a chip passing is on the Run page and the big screen about 1 to 3 seconds after the rider crossed the line. The time of the passing itself is exact: the reader stamps every passing with the X2 clock and tells the server how long it held it, so the delay never ends up in the result. Results typed or tapped by hand reach the screen within 1.5 s.

Limits that decide what counts #

Users, presence and login #

• Every page tells the server every 5 s that its user is there and what the user has open; a “working on this” mark expires 30 s after the last sign of life.
• The same user can be logged in in any number of windows, browsers and computers at the same time. The TimerBox link window is the one thing that exists once per venue per browser.
• 5 wrong passwords in a row pause that user name for 15 minutes.
• The server keeps everything in one SQLite database file, data/velodrome.sqlite, with a daily copy and a copy before every update in data/backups/. An event file (.evz) is a zip with the event’s tables as JSON plus its images.

The public read API #

Other systems – a federation website, a club page, a TV graphics box – can read the programme, start lists, results and live standings of public events (the public page switched on) as JSON. Read only, GET only, nothing beyond what the public page shows. Keys are made under Admin › API (Elapse users). 1.18.1.

Getting started. Everything is one address with a key and a what parameter: https://<site>/elapse-velodrome/apiv1.php?key=ev_…&what=events. The key is ev_ + 32 characters; it can be limited to one velodrome’s events and switched off at any time. Keep it on the server side of your system – CORS is open, so a browser page can call the API directly, but then the key is in the page source. Ids of events and races never change.

A race of an omnium is a race of its own (omnium_id points at the omnium); the omnium itself (is_omnium) gives the overall standings under results. A sprint tournament is its rounds as separate races.

Extras (1.19.0). startlist and results with event=ID instead of race= give every list of the event in one answer ({event_id, races: [...]}). class= (a class name, short name or id) keeps only that class’s races on event, programme and the whole-event lists. fields=rank,bib,name keeps only those fields on every row. format=csv gives the same answer as a CSV file (UTF-8 with BOM; the first rider’s names, nation and UCI ID as columns; the list’s extra cells under their column names). The key can also be sent as the header X-Api-Key, and the same calls exist in path form: apiv1/events, apiv1/7/programme, apiv1/7/results, apiv1/7/results/202. A key can be made for one event only (Admin › API), to hand to that event’s organiser.

Answers. Always JSON in one envelope: {"ok": true, "generated": "2026-11-01T09:35:25+01:00", "data": …}; generated is when the answer was computed (Europe/Oslo) and can be a few seconds old because of the server cache. On an error: {"ok": false, "error": "…"} with 400 (unknown what), 401 (no or wrong key), 403 (the key is for another venue, or the API module is not included for the event), 404 (no such public event or race, start list not ready, no results yet), 405 (not GET) or 429 (too many calls – wait the Retry-After seconds). Two headers save calls: ETag – send it back as If-None-Match and get 304 Not Modified with no body when nothing changed; Cache-Control: max-age=N – how many seconds the answer is good for.

Fields.

• Event: id, name, date_from, date_to (YYYY-MM-DD), venue, venue_id, track_length (m), language (no/en), timezone (1.23.0, Europe/Oslo), championship (nm or null), uci, state, demo, public_page; in event also classes [{id, name, short, gender (W/M/X), category (Elite, Junior, M40, 13…), hide_ranks}] and races. Gender and category are set on the Classes tab; left empty they are guessed from the class name.
• Race: id, title, title_local (the event’s language), discipline (sprint200, sprint, keirin, scratch, points, tempo, elimination, pursuit, teampursuit, timetrial, teamsprint, madison, longestlap, omnium), discipline_name, round, round_type (1.23.0: qualifying, first_round, repechage, quarterfinal, semifinal, final, heats or null, read from the round’s text), class, class_id, class_gender, class_category, class_hide_ranks, status (planned, startlist, live, unofficial = provisional, official), status_at and confirmed_at (1.23.0: ISO 8601 with offset; confirmed_at only when official), laps, distance_m, omnium_id, is_omnium, rank_across_heats (1.23.0: false in a sprint or keirin round whose ranks start again in every heat), entries, pdf (1.23.0: relative links to the start list, result and omnium PDFs; a public event’s PDFs open without login).
• Start list row: rider_id (1.23.0: Elapse’s id of the rider in this event – the same in every round, also for riders without a UCI ID), bib, name (as printed, Henrik SPURTNES), club_team, heat, pos (in the heat; with a line-up the order from the finish line within the line), line (fence, lane or null), status (DNS, DNF, DSQ, REL or null), seed, advances and advances_to (1.23.0, see below), is_team, members [{rider_id, bib, first_name, last_name, club, team, nation, uci_id, licence_no only for keys with the licence option}]. heat_names maps a heat number to its name (“Final for gold”); heat_types (1.23.0) the same number to a machine-readable type: final_gold, final_bronze, final_a, final_b, final_c, final, repechage, heat – read from the names (“Final for gold”, “Final 1–6”, “A Final”, “Repechage”…) and the round.
• Result row: as the start list plus rank (string, null without a rank), rank_n, time_ms, time (as printed), points, laps (1.23.0: laps gained + / lost − in a scratch or points race), cells (the extra columns as printed, matching columns), flags (NR, TR, PB, OVL, EARLY, W, REL). results also carries status, has_results, ranked_by_heat (1.23.0: true = the ranks start again in every heat), heat_names, heat_types, laps_left, elapsed and avg_kmh. The column titles in columns are always the English ones (“Time”, “Laps”, “Total”, “Ride 1-2-3”), whatever the event’s language.
• Who went on (1.23.0): when the next round is made from a result (Advance, By hand, the sprint finals, the ladder, the pursuit finals), every rider who goes on gets advances = Q (on placing) or R (to a repechage) and advances_to = the id of the race they ride next, on the start list and the result of the round they came from. q (fastest loser on time) is reserved: Elapse picks on placing, so it is not produced yet. Rounds made before 1.23.0 have null.
• Programme item: type (race, ride, break, day), race_id, ride, title, day, date, planned, estimated (HH:MM), planned_at, estimated_at (1.23.0: ISO 8601 with offset, e.g. 2026-10-16T18:30:00+02:00), minutes, state (done, now, next, wait), status, show_time; the answer also has now, delay_minutes, day and days.

Example. curl -i "https://www.elapse.no/elapse-velodrome/apiv1.php?key=ev_YOURKEY&what=results&race=12" – then the same with -H 'If-None-Match: "<the ETag>"' answers 304 while nothing has changed. A page that follows a live race asks what=live every 2–3 seconds with the ETag; a club page fetches programme once a minute.

Limits. 120 calls per key per minute, of which at most 60 live; over that 429 with Retry-After: 30. Asking faster than the cache time gives the same answer. Show unofficial results as unofficial – they can change until the race is set official.

Not in the API: nothing personal beyond the public result list (no chips, birth dates, e-mail addresses, decisions of the commissaires’ panel), nothing from events whose public page is off, no open-track boards, no writing. Licence numbers are the one exception, and only for a key where Elapse has ticked Include licence numbers (a federation system that needs them): then licence_no comes from the licence register, for the riders the register check matched, else null. Questions and keys: post@elapse.no. The API is the “API access” module; a velodrome without it gets 403.

Result webhooks #

1.23.0. Instead of asking the API every few seconds, a site can be told when a result changes. An API key gets a webhook URL and a signing secret under Admin › API (the receiving site generates both). From then on Elapse POSTs a small signed note to that URL whenever a race’s result is saved as provisional or official, corrected afterwards, withdrawn or deleted, whenever a start list is saved or changed, and whenever the event’s races change or its public page is switched off. The note names the race; the site then reads it through the API as before – so the API stays the only result format, a webhook can never disagree with it, and a missed webhook is caught up by reading. Only events the key can read, and only while the event’s public page is on; live standings send nothing.

The note. POST with Content-Type: application/json and a body like {"id": "whk_01M6…", "type": "race.result", "created": "2026-10-31T13:27:41+01:00", "api_version": "1.23.0", "event": 7, "race": 227, "status": "official", "updated_at": "2026-10-31T13:27:39+01:00"}. type is race.result, race.startlist, race.deleted (a published result withdrawn or its race deleted), event.updated (races added, removed, renamed, moved; the public page switched off) or ping (the test button). status is provisional or official (null for race.deleted and the event types). race is null for event.updated and ping; event is 0 for a ping. updated_at is when the change was first seen, so a receiver can skip a note older than what it has. Fields may be added later.

Signature. The header Elapse-Signature: t=1793912861,v1=5257a8… carries a Unix time and HMAC_SHA256(secret, t + "." + raw body) as lowercase hex – the scheme Stripe uses, so standard verification code works. The receiver recomputes it over the raw bytes before parsing and accepts when a v1 matches and t is within five minutes of its clock. While a key has two secrets (rotation), the header carries one v1 per secret; switch the receiver to the new one, then remove the old. https only; redirects are not followed.

Delivery. Delivered = any 2xx within 10 seconds. Anything else is retried after 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours (six attempts in all), with the same id and body and a fresh t. Order is not guaranteed; the receiver reads the current state anyway. Answer fast and work afterwards. A 410 Gone switches the URL off at once; a URL that has failed every attempt for 3 days is switched off too, and Admin › API says so. Several saves within a few seconds give one note. Deliveries are made right after the page that found the change has been sent, so they cost the person working in Elapse nothing; the last 200 per key (time, type, state, attempt, answer) are listed under Settings on the key.

Testing. Send test webhook sends a ping and shows the answer and the time it took. After that, test end to end on a demo event: a provisional then an official result (two race.result), a corrected place (one more), the final drawn after the heats (race.startlist, and advances on the heats), a deleted race (race.deleted), the public page switched off (event.updated, then silence).

How Elapse finds the changes. Results are saved in many places (the Run console, the race page, the automatic results from the passings, the photo-finish, the pursuit board, imports), so a change detector runs on every request, at most every 3 seconds: it fingerprints every race of the public events of the last 45 days (status, finishing order, times, sprints, laps, decisions, start list) and sends a note when one differs. A correction to an event older than 45 days sends nothing; the receiver reads it when it wants.

TimerBox and start clock #

Chips and the X2 reader #

Pages, results and the big screen #