> For the complete documentation index, see [llms.txt](https://khalil-lab.gitbook.io/evolver/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://khalil-lab.gitbook.io/evolver/troubleshooting/evolver-maintenance.md). # eVOLVER Maintenance We have monitored the lifetime of eVOLVER components since the invention of the device (\~3 years). As in most systems, mechanical parts have the highest possibility of wear and thus need replacement most frequently. Likewise, in eVOLVER, the peristaltic pumps used have a lifetime of 6 months of typical use during continuous culture. Specifically, the silicone tubing within the head of the pump is frequently compressed when actuating peristaltic pumps and will tear over time. The head can easily and inexpensively be replaced ($4/ pump). The computer fan used for stirring has robustly operated continuously for > 3 years, whereas the magnetic stir bars are rated for a limited number of autoclave cycles and need eventual replacement. All other components (e.g. heaters, thermistors, LEDs, diodes, PCB, power sources) have been stably operating for > 3 years. --- # 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://khalil-lab.gitbook.io/evolver/troubleshooting/evolver-maintenance.md?ask=&goal= ``` `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.