> 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-network-interface-hardware/vehicle-network-interface-hardware-valuelog.md).

# Vehicle Network Interface Hardware: ValueLOG

The ValueLOG is the next-generation, low-cost, high-performance data logging device for CAN FD and LIN networks. The ValueLOG includes Ethernet (DoIP), four channels of CAN FD (Including SW CAN) and LIN in one tool. All channels run simultaneously and are time-stamped in hardware.

<figure><img src="/files/QL9p97QfD3h9ozKNRMNb" alt="" width="375"><figcaption></figcaption></figure>

#### Applications

* Standalone data logger
* Standalone ECU or vehicle simulator
* In-vehicle data acquisition system
* Captive test fleet data collection
* Fleet management
* Vehicle interface with J2534 and RP1210

#### Features

* Up to 4x CAN FD
* Up to 1x SW CAN
* Up to 1x LIN / K-Line
* Up to 1x Ethernet (100BASE-TX for DoIP, switchable for 2x CAN FD network)
* 32GB eMMC storage
* External GPS antenna support for collecting locations during data logging sessions
* General purpose engineering tool for OBDII, enabling a wide array of applications such as data logging, simulation and gatewaying
* Optional Unique configurable OBD II pinout through neoVI Universal Connector (NUC) architecture (optional)
* 9-axis Inertial Measurement Unit
* RTC with battery

User Guide for ValueLOG - [https://cdn.intrepidcs.net/guides/ValueLOG](https://cdn.intrepidcs.net/guides/ValueLOG/index.html)


---

# 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://docs.intrepidcs.com/vspy-3-documentation/vehicle-network-interface-hardware/vehicle-network-interface-hardware-valuelog.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.
