> For the complete documentation index, see [llms.txt](https://cavedu.gitbook.io/cavedu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cavedu.gitbook.io/cavedu/rk002/module/002_soil_moisture.md).

# 土壤溼度模組

![](/files/-LwXL64vEwGw8XUgpLII)

## 專案說明

使用「科易KEYES Arduino UNO R3 開發板」連接「土壤溼度模組」,讀取土壤溼度模組數值變化。

此**土壤溼度模組**包含於**「**[洞洞兩教學材料包 Education Kit 002](https://www.robotkingdom.com.tw/product/rk-education-kit-002/)**」**內。

## KEYES Arduino UNO R3電路圖

* [KEYES Arduino UNO R3](https://www.robotkingdom.com.tw/product/keyes-uno-r3/)
* 通用型彩色Sensor shield v5.0感測器擴充板
* 土壤溼度模組

**土壤溼度模組**是**類比訊號輸入**，可以接「A0 \~ A5」的KEYES Arduino UNO R3訊號端上。 本範例連接到「**A0」**

![](/files/-LwXL64w8l4_oWSuzWtb)

## Arduino 程式

每0.5秒鐘會讀取土壤溼度模組的數值一次， 並顯示在序列埠監控視窗上。

![](/files/-LwXL64xhfzzf6AH-zm2)

產生出的 Arduino 程式如下

```c
void setup()
{
 Serial.begin(9600);
}
void loop()
{
 Serial.println(analogRead(A0));
 delay(500);
}
```


---

# 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://cavedu.gitbook.io/cavedu/rk002/module/002_soil_moisture.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.