CHESTER DevKit One box on the table. The module decides what it is.

Every project starts as a list of things to measure. Four dry contacts, a Modbus meter, two temperature probes, and a sensor nobody has chosen yet. The usual answer is to go shopping: one supplier per line on the list, four enclosures, four radios, four certifications, four things to support for a decade. This hour is the other answer, shown on one device on the table. CHESTER is a mainboard, a radio, an enclosure and a battery that never change, and two slots that decide what the device actually is. Eighteen modules fit those slots today: dry contacts and current loops, RTDs and thermocouples, load cells, current probes, RS-485, RS-232, CAN, Ethernet, 1-Wire. You will watch two things happen live. First the kit boots, joins the network and reports, and we follow the payload through to the dashboard and out again over REST into your own application. Then we pull one module out, fit another, and a different measurement appears in the same dashboard: same enclosure, same firmware image, same certification, no code written. On radio, both are already on the board. The catalog applications ship with cellular and LoRaWAN populated, and moving between them is one configuration command. We will describe the LoRaWAN path in full, from OTAA join through your own gateway to a ChirpStack server you host yourself, though the kit on the table runs cellular on the day. One kit, led from the desk, with the modules passed around the room. Bring questions rather than a laptop.