PLSChat • T1000-E Firmware

1 · Download the firmware

One .uf2 file — this is everything the tracker needs

Download plschat_t1000e_v0_1.uf2

v0.1 · 868 MHz · public channel · compatible with the Heltec / XIAO mesh

2 · Drag it onto the tracker

Uses the tracker's built-in drag-and-drop (UF2) bootloader

1

Plug the magnetic USB cable into your computer — but don't attach it to the tracker yet.

2

Press and hold the tracker's button, and while holding it, snap the cable onto the tracker, pull it off, and snap it straight back on — quickly. When it works, the green LED goes solid and a USB drive called T1000-E appears on your computer — that's DFU mode. The timing is fiddly, so expect a few attempts. Keep holding the button until the drive shows up.

3

Drag plschat_t1000e_v0_1.uf2 onto the T1000-E drive. Ignore the files already on the drive (CURRENT.UF2 etc.) — they belong to the bootloader, leave them be. The copy takes a few seconds, then the drive disappears and the tracker reboots into PLSChat. That's it.

4

Open the PLSChat Android app and tap “Using a SenseCAP tracker? Connect over Bluetooth”. The app finds the tracker (it advertises as PLSChat-T1000) and opens the public-channel chat.

Need the app? The Android app with Bluetooth support is built from this repo — see app-android/BLUETOOTH.md for how the two transports fit together.

Good to know

v0.1 is an early build — here's exactly where it stands

Public channel only for now. Messages are byte-compatible with the Heltec fleet's public channel. Contacts and Rooms need a firmware update and are greyed out in the app until then.
Not yet field-proven. This build compiles and runs, but radio range against the Heltec fleet hasn't been confirmed on real hardware yet. If you flash one, a range check against a Heltec is the single most useful test you can do.
Fully reversible. The bootloader is untouched — double-press the button any time to get the T1000-E drive back and drag on any other firmware (including Meshtastic or Seeed's original).
Battery note. v0.1 beacons every 60 seconds so other nodes can see it — fine for testing, tuned down in a later release.