> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/s2gw-installation-manual/troubleshooting/s2gw-error-messages.md).

# S2GW error messages

Here is a list of S2GW error messages sent to B3.

<table><thead><tr><th width="284">Message</th><th>Description</th></tr></thead><tbody><tr><td>"No communication with node"</td><td>The node does not answer to radio request.</td></tr><tr><td>"No sensor detected (node sends 0xAA)"</td><td>The node answers on radio but says that it does not have the sensor with a given index.</td></tr><tr><td>"No new value from sensor"</td><td>The sensor exists but there is no new value from it.</td></tr><tr><td>"Sensor type not supported!"</td><td>The sensor type detected is not handled by the current version of S2GW.</td></tr><tr><td>"Wrong sensor type connected to the node!"</td><td>Not used</td></tr><tr><td>"General sensor error"</td><td><p>BadRadioPath (incorrect path string)</p><p>CRCError DataCorrupt (Answer to radio command different from Command+0x10)</p></td></tr><tr><td>"No communication with PC-NODE"</td><td>S2GW receives no answer from its PC node. Check if PC Node is supplied and if the serial cable is connected.</td></tr><tr><td>"Can't open COM PORT"</td><td>S2GW cannot open its serial port used for PC Node communication - check the serial port HAT inside the case.</td></tr><tr><td>"Bad radio group/id in PC-Node. Reinitialized"</td><td>The S2 PC node Radio Group and/or ID are incorrect. The Radio Group programmed in PC Node must be equal to Radio Group defined in B3. The PC Node ID must be equal 1. The S2 Radio Group and ID programming is described in <a data-mention href="/s2-radio-system-manual/tools/s2-init-node.md">S2 Init Node</a>.</td></tr></tbody></table>


---

# 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://help.boomerang3.com/s2gw-installation-manual/troubleshooting/s2gw-error-messages.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.