> For the complete documentation index, see [llms.txt](https://bittle.petoi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bittle.petoi.com/zhong-wen/8-dong-shou-wan-bittle.md).

# 8 🕹 动手玩Bittle

经历了前面的组装工作，现在的Bittle应该已经可以完美行走了～

那么，来玩吧！

没有任何编程经验的用户可以通过以下4种方式来控制Bittle：

* 使用[**红外遥控器**](https://docs.petoi.com/v/chinese/hong-wai-yao-kong/yao-kong-qi)
* 使用手机应用 [**Petoi**](https://docs.petoi.com/v/chinese/shou-ji-ying-yong/kong-zhi)
* 使用桌面应用程序[**技能创作坊**](https://docs.petoi.com/v/chinese/zhuo-mian-ying-yong/ji-neng-chuang-zuo-fang)
* 使用[**Petoi编程积木**](https://docs.petoi.com/v/chinese/tu-xing-hua-bian-cheng/petoi-bian-cheng-ji-mu)

如果你有一定的编程经验或想探索更高级的功能，可以尝试以下方法：

* 使用 [**Arduino IDE**](https://docs.petoi.com/v/chinese/chuan-kou-xie-yi)
* 使用 [**Python**](https://docs.petoi.com/v/chinese/api/serialmaster-shi-yong-zhi-nan)
* 使用 [**MicroPython**](https://docs.petoi.com/v/chinese/tong-xin-mo-kuai/wifi-mo-kuai-esp8266/micropython-kong-zhi-qi)
* 使用 [**ESP8266 + Python**](https://docs.petoi.com/v/chinese/tong-xin-mo-kuai/wifi-mo-kuai-esp8266/shi-yong-esp8266-+-python-jiao-ben-shi-xian-wu-xian-qun-kong)
* 使用 [**Raspberry Pi**](https://docs.petoi.com/v/chinese/api/tong-guo-shu-mei-pai-kong-zhi-ji-qi-ren)
* 使用[**扩展模块**](https://docs.petoi.com/v/chinese/kuo-zhan-mo-kuai/kuo-zhan-mo-kuai-gai-yao-shuo-ming)


---

# 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://bittle.petoi.com/zhong-wen/8-dong-shou-wan-bittle.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.