Tables

Imposed Tables are a regularity system in which the organization provides you with a sheet containing only the passing times every X meters (e.g.: 100 m).

Generally, the organization tends to deliver them shortly before starting the stage or section, which makes it difficult to manage because there is not enough time to enter the data on the Stage Editor screen.

Before starting, let's take a look at a Table to understand its data and how we should use it.

In the left image we have an example of a Table, which consists of two columns. In the left column they indicate the distance and in the right column they indicate the time at which we need to pass at that distance.

As you can see in the image, to go correctly at the average speed imposed by the organizer without being penalized, when we reach 0.100 meters, the chronometer must be at 00:00:13, at 0.200 at 00:00:26, at 0.300 at 00:00:39, and so on.

Another important factor is to observe the average speed changes. In this example, we have:- 0.100, 0.200 and 0.300 at 13 seconds each- 0.400, 0.500 and 0.600 at 10 seconds each- 0.700, 0.800, 0.900 and 1.000 at 14 seconds each

That is, we have two average speed changes, one to increase speed at 0.300 and another to decrease speed at 0.600.

Now that we understand how a Table works, let's see the two examples below of how to use the Tables screen to navigate that stage in a simple way.

The first thing to do is create a stage on the Stage Editor screen. To do this, follow the steps below:

  1. Open the Stage Editor screen.
  2. Click on Manage Stages and select New.
  3. Enter the final mileage of the stage (e.g.: 1km). If you don't have it, enter any mileage that is longer than the stage.
  4. Enter the total time of the stage (e.g.: 00:02:05) in End Time and press ENTER.
  5. Click on Send to Navigator.
  6. Select the Tables screen by clicking on the 3 dots at the top right of the navigation screen.

Below is the Stage Editor screen with our example data.

Now we have to wait for our start time to begin navigation. Once we have started the stage, what we need to do is match the time on the paper sheet with the Tables screen. In the video below we can see the navigation matching our chronometer with the Table times.


DRIVER’S SCREEN! The stages with tables are designed so that the co-driver sees the table and the driver only sees the time for the next checkpoint. Although we do not recommend it, if the driver also wants to see the table, they must create a stage on the device acting as the driver’s screen before connecting to the main device.

Below we have an example of the two files for the mixed stage. In the left image, we have the timed stage that the rally organizer usually makes available at least one day before the rally. And in the right image, we have the Tables sheet that the organizer will deliver minutes before starting the stage.

As in the previous example, the first thing to do is create a stage on the Stage Editor screen. The stage should look like the one in the image below.

After entering all the stage data as in the image above, all that remains is to send the data to the Navigator and wait for our start time.

Once we have started the stage, what we need to do is:

  1. Navigate from the start of the stage to kilometer 4.680 with the Reg. Numbers screen, trying to keep the ideal time as close to zero as possible.
  2. When we reach kilometer 4.680, we need to switch to the Tables screen and try to match the time on the paper sheet with the Tables screen.
  3. When we reach kilometer 5.680, which is the end of the Table, we need to switch back to the Reg. Numbers screen trying to keep the ideal time as close to zero as possible.

In the video below we can see the navigation of this stage in practice, so you can see how simple it is.

  • en/rabbit-rally-2-0-competidores/funciones-avanzadas/tablas.txt
  • Last modified: 2026/03/16 14:40
  • by joan