> For the complete documentation index, see [llms.txt](https://docs.intrepidcs.com/vspy-3-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intrepidcs.com/vspy-3-documentation/vehicle-spy-tutorials/tutorial-standalone-video-logging.md). # Tutorial: Standalone Video Logging ### Overview Logging video can be an incredibly powerful tool when used simultaneously with other types of logged traffic. From the ability to monitor tell-tales on the dashboard of a vehicle to verifying a certain module is physically actuating as it should, utilizing video can be crucial to any automotive project. In this example, video data will be collected from an AXIS network camera using VehicleScape DAQ. Before getting to that, there is a list of requirements that should be met: * AXIS IP Camera * neoVI Device capable of logging over ethernet * Ethernet Cable * Ethernet to USB adapter (Needed if you cannot connect to your camera over your PC's network interface) * [AXIS IP Utility](https://www.axis.com/support/tools/axis-ip-utility) Once everything on the list has been verified, continue to the tutorial. --- # 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://docs.intrepidcs.com/vspy-3-documentation/vehicle-spy-tutorials/tutorial-standalone-video-logging.md?ask=&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.