Web Timing setup

Posts: 785
Initial webserver setup
To setup the ATVO Web Timing, please follow these steps:

  1. Prepare a location on your webserver where the timing webpages will go.
  2. Start ATVO, find and click the Web Timing menu item.
  3. In the Web Timing window, go to the Help tab.
  4. Follow the instructions on that tab to upload the website files to your webserver.


Running the Web Timing
To run the Web Timing:
  • Connect to an iRacing session.
  • Make sure your connection settings are correct in the Web Timing window.
  • Press Start.
  • Go to the Log tab to check for any errors.
  • If there are no errors and the status text remains "Running", then your Web Timing should now be updating live.
  • If there are errors, please check below.


View / test the Web Timing page
  • After everything is setup and running, your Web Timing should be visible under the URL where you uploaded the webserver files. For example, if your post.php file is under "mywebsite.com/livetiming/post.php", then the Web Timing should be visible under "mywebsite.com/livetiming" or "mywebsite.com/livetiming/index.html"
  • The Events page is accessible via the extension "/#/events". For example: mywebsite.com/livetiming/#/events.
  • The Timing Screen is the default page but is also accessible via the extension "/#/timingscreen". For example: mywebsite.com/livetiming/#/timingscreen.


Resolving common errors
The most common errors include:

  • Invalid URI: The format of the URI could not be determined.
    • Solution: check if your Connection URL is a valid URL.
  • Invalid password.
    • The password you entered in the Web Timing connection does not match the password in the 'post.php' file on your server.

Other errors could occur due to several other reasons, including:
  • Your server does not have write access to the 'sessions' folder, or you renamed the sessions folder, or you renamed the 'cachedir' variable in the post.php file.
  • Your server is somehow not accepting the webrequest from HTTP. This could be related to SSL/TLS/HTTPS issues.
Edited (2 times)