> For the complete documentation index, see [llms.txt](https://avss.gitbook.io/prs-m3dt-for-dji-dock2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://avss.gitbook.io/prs-m3dt-for-dji-dock2/prs-m3dt-for-dji-m3d-and-m3td/maintenance-and-care.md).

# Maintenance & Care

Maintenance and inspection intervals of the AVSS PRS-M3DT are required to maximize the safety of each flight and ensure proper functionality for parachute deployment whenever it may be required. The PRS-M3DT’s Parachute Pod™ must be repacked in either twelve (12) month intervals, or after a deployment.

### Post-Flight (Monthly)

* Visually inspect the PRS-M3DT to ensure there is no damage.

### Storage

* Always ensure the power is off.
* Make sure the unit is clean and dry before putting in the case.

### Extended Storage Considerations

1. Store in a dry room that is at room temperature.
2. Uninstall the AVSS PRS-M3DT assembly from the DJI M3D/T drone.
3. Visually inspect the USB-C located on the underside of the PRS-M3DT. Check against signs of corrosion, dust/dirt buildup, wear, or any other types of abnormalities.
4. Inspect the strap attachment and verify the mounting screw remains secured, and that the strap is free of damage.
5. If any of the above defects are present during the 12 month inspection period, contact AVSS for further information.
6. Verify that the PRS is not expired by checking the PRS pack date.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://avss.gitbook.io/prs-m3dt-for-dji-dock2/prs-m3dt-for-dji-m3d-and-m3td/maintenance-and-care.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.