en_alt:receivers
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| en_alt:receivers [2026/08/11 09:36] – XIAO write-up, catalogue order, Ulm coverage entry hajo | en_alt:receivers [2026/08/15 00:06] (current) – Renamed to The OpenTrafficMap server; Berlin coverage; imprint moved hajo | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Receivers ====== | ====== Receivers ====== | ||
| - | What you need to actually hear C-ITS. There is one purpose-built receiver that most people use, and a growing number of independent projects that solve the same problem with different hardware. All of them end up in the same place: raw 802.11p frames on the [[en_alt:reporting|central MQTT broker]]. | + | What you need to actually hear C-ITS. There is one purpose-built receiver that most people use, and a growing number of independent projects that solve the same problem with different hardware. All of them end up in the same place: raw 802.11p frames on the [[en_alt:server|central MQTT broker]]. |
| Whatever you build, [[en_alt: | Whatever you build, [[en_alt: | ||
| Line 167: | Line 167: | ||
| - [[en_alt: | - [[en_alt: | ||
| - [[en_alt: | - [[en_alt: | ||
| - | - [[en_alt:reporting|Reporting to OTM]] — how the data actually leaves the node, and how to read along | + | - [[en_alt:server|The OpenTrafficMap server]] — how the data actually leaves the node, and how to read along |
| ===== Other receiver projects ===== | ===== Other receiver projects ===== | ||
| Line 221: | Line 221: | ||
| Practical warning: several people have hit SPI checksum errors that turned out to be wiring problems, and some GPIOs did not work as the datasheets suggested. If the link does not come up, try different pins before you suspect the software. | Practical warning: several people have hit SPI checksum errors that turned out to be wiring problems, and some GPIOs did not work as the datasheets suggested. If the link does not come up, try different pins before you suspect the software. | ||
| - | The temporaerhaus hackerspace in Ulm documents this build end to end with two Seeed Studio XIAO boards — a **XIAO ESP32-C5** as the sniffer and a **XIAO ESP32-C3** as the Wi-Fi bridge, both stamp-sized and solderable in an evening. The page gives the exact pin mapping and links prebuilt images you can flash from the browser, so no build environment is needed. The sniffer image comes from a fork of the receiver firmware. | + | The temporaerhaus hackerspace in Ulm [[https:// |
| - | + | ||
| - | [[https:// | + | |
| **TODO:** [[https:// | **TODO:** [[https:// | ||
| Line 232: | Line 230: | ||
| ^ Reports to OTM | yes, the same as the official board | | ^ Reports to OTM | yes, the same as the official board | | ||
| ^ Advantages | no cable to the mounting point; the '' | ^ Advantages | no cable to the mounting point; the '' | ||
| - | ^ Drawbacks | two boards and five SPI wires to get right; wiring problems are common; neither project documents a licence | + | ^ Drawbacks | two boards and five SPI wires to get right | |
| ^ Repositories | [[https:// | ^ Repositories | [[https:// | ||
| Line 267: | Line 265: | ||
| ^ Reports to OTM | yes, with the supplied example configuration | | ^ Reports to OTM | yes, with the supplied example configuration | | ||
| ^ Advantages | frames become Home Assistant data; free choice of uplink and destination; | ^ Advantages | frames become Home Assistant data; free choice of uplink and destination; | ||
| - | ^ Drawbacks | no Wi-Fi; the KSZ8851SNL path is experimental; no licence stated in the repository | + | ^ Drawbacks | no Wi-Fi; the KSZ8851SNL path is experimental | |
| ^ Repository | [[https:// | ^ Repository | [[https:// | ||
| - | Note that this is a different thing from **monitoring** a node in Home Assistant, where the node runs on its own and Home Assistant simply reads its telemetry. That is described under [[en_alt:reporting# | + | Note that this is a different thing from **monitoring** a node in Home Assistant, where the node runs on its own and Home Assistant simply reads its telemetry. That is described under [[en_alt:server# |
| ==== USB to an Android phone ==== | ==== USB to an Android phone ==== | ||
| Line 341: | Line 339: | ||
| ^ Reports to OTM | **no** | | ^ Reports to OTM | **no** | | ||
| ^ Advantages | small, single-file code base; straight to PCAP and Wireshark; no ESP-IDF toolchain needed | | ^ Advantages | small, single-file code base; straight to PCAP and Wireshark; no ESP-IDF toolchain needed | | ||
| - | ^ Drawbacks | no OTM upload, no Ethernet, no runtime configuration; | + | ^ Drawbacks | no OTM upload, no Ethernet, no runtime configuration; |
| ^ Repository | [[https:// | ^ Repository | [[https:// | ||
en_alt/receivers.txt · Last modified: by hajo