> For the complete documentation index, see [llms.txt](https://support.onegiantleap.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.onegiantleap.co.nz/legacy-features/high-speed-data/how-to-resolve-the-high-speed-data-recording-fault.md).

# How to resolve the High Speed Data recording fault

You may discover that your High Speed Data model Power Meter is not successfully recording HSD files. This issue can temporarily develop if the Power Meter was charged with the incorrect procedure following the battery being completely flat. 

The correct charging procedure is to place the charger onto the shaft **prior to supplying power to the charger**.

To remedy this issue, you must fully discharge the Power Meter. You can do this by leaving it connected to the Web App for a few hours which ensures the Power Meter won't fall asleep due to inactivity.\
\
Once the battery is fully depleted, take care to place the charger on the shaft *prior* to supplying power to the charger.

{% hint style="info" %}
Only when the battery is fully discharged do the electronics turn off completely.\
\
When the electronics are turned on for the first time, a stable power source must be provided for the initialisation to occur correctly.\
\
When you bring a **powered** charger into position, there's a brief period, as the charger moves closer to the shaft, where the power from the charger causes the electronics to be neither on or off (much like Schrödinger's cat). This rapid switching between on and off, causes the High Speed Data initialisation to fail.\
\
Placing the charger *prior* to supplying power to it, provides a stable power source to the Power Meter.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.onegiantleap.co.nz/legacy-features/high-speed-data/how-to-resolve-the-high-speed-data-recording-fault.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.