> For the complete documentation index, see [llms.txt](https://dev.solid-run.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.solid-run.com/amd/v3000/com-som/amd-v3000-com-express-type-7-ic-power-dissipation-heatmap.md).

# AMD V3000 COM Express Type 7 - IC Power Dissipation Heatmap

Interactive per-IC power dissipation heatmap for the SolidRun AMD Ryzen Embedded V3000 COM Express Type 7 module. Select the CPU (V3C18I or V3C48), the BIOS CPU Power Limit and the number of SODIMM mo

Per-IC power dissipation of the AMD V3000 COM Express Type 7 module, colored by power density (log scale).

Use the **CPU**, **CPU Power Limit** and **SODIMM modules** selectors; the map, the totals and the heat-sensitive parts table follow the selection.\
Board 95 × 125 mm · 28 dissipating parts top / 3 bottom · total estimated dissipation ≈ 74.2 W at the V3C48 54 W limit with two SODIMM modules

{% @bios-viewer/bios-viewer url="<https://www.solid-run.com/power-heatmap/v3000-cex7-heatmap.html>" %}

[Open the heatmap in a full browser window](https://www.solid-run.com/power-heatmap/v3000-cex7-heatmap.html)

{% hint style="info" %}
**NOTE:**

* The CPU Power Limit selector covers V3C18I 8 - 15 W and V3C48 8 - 54 W, in 1 W steps. The APU dissipation is modelled as equal to the selected limit.
* SODIMM modules are assumed at 5 W each. Their heat is carried by the module and is drawn over the on-board part of the socket. With one module fitted, socket 1 (DIMM1, top side) is assumed.
* Parts below 0.05 W at every power limit (most passives, connectors) are shown as faint outlines and excluded from the analysis. Hover a part to see its dissipation and the basis of the estimate.
* The BOTTOM side is an X-ray view from above and is not mirrored: it has the same orientation as the TOP side.
* The heat spread view is relative (1 = maximum of the selected view) and is not a temperature. By default it excludes the APU and the SODIMM modules, which have their own heat paths (heatsink, module).
  {% endhint %}

{% hint style="warning" %}
**Estimate, not a thermal measurement.** Dissipation values are estimated from datasheet data and engineering assumptions at the selected power limit, on the real placement and board stackup. No heatsink, airflow, enclosure or ambient temperature is modelled. Use this page for design guidance only, and validate thermal performance in the target system. For cooling of the module, see [Heatsink and Cooling](/amd/v3000/com-som/amd-v3000-based-com-type-7-hardware-user-manual.md#heatsink-and-cooling) in the [AMD V3000 Based COM Type 7 Hardware User Manual](/amd/v3000/com-som/amd-v3000-based-com-type-7-hardware-user-manual.md).
{% 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 by asking a question.

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

```
GET https://dev.solid-run.com/amd/v3000/com-som/amd-v3000-com-express-type-7-ic-power-dissipation-heatmap.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.