> For the complete documentation index, see [llms.txt](https://bitmerse.gitbook.io/wiser-product-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bitmerse.gitbook.io/wiser-product-manual/appendix.md).

# Appendix

### Glossary of Terms <a href="#toc150171940" id="toc150171940"></a>

For definitions of technical terms and acronyms used in this manual, please refer to the Glossary of Terms table below:

| **Term**                  | **Definition**                                                                                                  |
| ------------------------- | --------------------------------------------------------------------------------------------------------------- |
| COM Port                  | Communication Port, a virtual interface for serial communication on a computer.                                 |
| Baud Rate                 | The rate at which data is transmitted in bits per second (bps).                                                 |
| Flow Control              | A mechanism to manage the flow of data between two devices, often using control signals like RTS and CTS.       |
| DTR (Data Terminal Ready) | A control signal used to indicate that the terminal or device is ready for data communication.                  |
| ESP-NOW                   | A wireless communication protocol developed by Espressif Systems.                                               |
| Header Pins               | Connectors used to interface with a device or circuit board.                                                    |
| Castellated Pins          | Solderable pins with a half-moon or castle-like shape for PCB integration.                                      |
| WiSer-TTL                 | A WiSer device that interfaces with embedded devices using TTL-level serial communication.                      |
| WiSer-USB                 | A WiSer device that connects to a host system via USB for serial communication.                                 |
| WS-UT-BM                  | A WiSer variant with specific configuration (Refer to product documentation).                                   |
| WS-UT-EN                  | A WiSer variant with specific configuration (Refer to product documentation).                                   |
| WS-UU-EN                  | A WiSer variant with specific configuration (Refer to product documentation).                                   |
| WS-UT-BM/EN               | Either of the WiSer variants WS-UT-BM or WS-UT-EN with specific configuration (Refer to product documentation). |

### Regulatory Information <a href="#toc150171941" id="toc150171941"></a>

For regulatory compliance and legal information regarding WiSer devices, please refer to the respective documentation provided with the product. It is important to ensure that you adhere to all relevant regulations and requirements applicable in your region or jurisdiction when using WiSer devices.


---

# 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://bitmerse.gitbook.io/wiser-product-manual/appendix.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.