Skip to main content

Introduction

Welcome to the HH Timing V2 help file. This resource is designed to help all ranges of users of HH Timing V2. If you need further support with any topics, and cannot find the answer on this site, please do not hesitate to contact us at support@hh-dev.com.

danger

HH Timing V2 is currently under heavy development any releases should be considered as alpha releases. This means that there may well be bugs and crashes, and significant (potentially undocumented) behaviour changes between releases. Both the plugins and API may change between releases requiring changes on your side to make any applications compatible again.

HH Timing 0.9 is still the recommended version for any users who do not wish to use a potentially unstable experimental software.

Our goals for HH Timing V2 are to address some of the fundamental weaknesses of the orignal software, update the user interface, make the data more accessible by 3rd party applications, and to deliver a smoother cloud experience.

Improvements over HH Timing 0.9​

HH Timing 0.9 has existed since 2011, and over that time we have experienced challenges with the general concept of the software that has at times slowed development as we workaround weaknesses of the software. The goals for HH Timing V2 are to improve the conept of the software to make it easier and quicker to develop new and advanced features.

User interface updates​

The user interface of HH Timing V2 is now built on the same platform as HH Data Management. The first advantage of this is that HH Timing now has a more modern and faster user interface, with light/dark theming built in. By having commonality between the two applications it will be easier for users to switch between the two software, and let HH Development focus on improving a single user interface rather than splitting resources between HH Data Management and HH Timing.

Data accessibility​

In HH Timing 0.9 we have a live Excel export, and static (normally used post-session) CSV and JSON exports, and the plugin framework. In HH Timing V2 the goal is to make it easier for users to access the data they need live during a session. We therefore have worked on the following topics:

  • the Excel and HH DM exports (previously called the DMI) now allow exporting more parameters from the software, and from entities other than the laps / sectors - before they could only export a subset of the lap parameters calculated in the software
  • the desktop software has an API that runs locally meaning you can make API requests against the desktop software and access data for the current active session in the software (future work will expand this to allow all sessions in the local project to be loaded and accessed via the local API)
  • the plugin framework still exists and is similar to the previous software, but a lot of the manual work of responding to messages to build a model of the session in each plugin shouldn't be needed anymore as a full cache of the whole session is provided to the plugins

Cloud features​

Once the desktop version is stabilized we will focus on various cloud-based features for HH Timing. These features are not currently implemented, but some examples are:

  • centralized configuration settings that can be shared within an organization
  • ability for customers to automate the start and stop of their own cloud based timing servers, with the ability to connect to cloud timing feeds, or forward local timing feeds to the cloud
  • the ability for customers to upload timing data to our servers that can then be accessed via a cloud API
  • web version of HH Timing