Capture only a known authorized packet
Use your own transmitter or an approved lab source. A saved packet can be transmitted later by load, so treat every .lora file as an active RF test asset rather than a passive screenshot.
- Confirm the receiver profile and antenna first.
- Send one distinctive, non-sensitive test payload.
- Download important captures before reflashing or changing partitions.
Verify receive mode and storage
Receive one packet normally before recording it. The record workflow mounts LittleFS and requires at least 2 KB free.
Press Enter to leave continuous receive after the controlled packet appears.
Record exactly one packet
Run record, transmit the known payload from the peer and enter a simple filename. The firmware appends .lora when needed.
Stopping before a packet is safe
Press Enter while waiting to cancel. The command reports No packet saved and includes an RX error count when errors occurred.
Know what the file preserves
| Group | Saved fields | Purpose |
|---|---|---|
| Format | ESP32-Bit-Pirate LoRa, version 1 | Reject incompatible or incomplete files. |
| Modem | Frequency, BW, SF, CR, power, preamble | Reconstruct the radio profile used for capture. |
| Packet options | Sync word, TCXO voltage, CRC, invert IQ | Preserve settings that can prevent decoding even when frequency matches. |
| Capture metrics | RSSI and SNR | Keep signal context; these values are metadata and are not recreated on TX. |
| Payload | Length and hexadecimal bytes | Validate and reproduce the exact packet content. |
Archive or inspect the capture
Use the firmware Web UI Files panel to download the new file. Keep the extension and contents unchanged if you plan to load it again.
- Open the firmware Web UI and its Files panel.
- Find
lab_probe_01.loraand check that its size is non-zero. - Download a copy with the test date, peer identity and authorization context in your project notes.
Load for one controlled transmission
Start receive on the authorized peer first. Then run load, select the capture and confirm the file summary. Selecting the file triggers one transmission.
The saved profile is temporary
load applies the file frequency and modem profile, sends once, then attempts to restore the complete profile that was active before the command. Treat Load: profile restore failed as a stop condition and re-run configuration before further RF work.
Confirm profile restoration
Compare the result with the status snapshot taken before loading. The saved RSSI and SNR belong to the original capture; the peer’s new receive metrics describe the loaded transmission.
Troubleshooting
- LittleFS full: free space until at least 2 KB is available, then run
recordagain. - No packet saved: confirm the peer profile and send only after record reports that it is waiting.
- No .lora files: check the Files panel and exact
.loraextension. - Invalid file size: the selected file must be non-empty and no larger than 8 KB.
- Invalid .lora file: do not hand-edit required fields unless every value and payload length remains valid for version 1.
- Profile restore failed: stop and rebuild the intended profile with
configbefore sending or receiving again.
LoRa file FAQ
What is stored in a .lora file?
The complete supported modem profile, capture RSSI/SNR, payload length and exact hexadecimal payload bytes in a versioned text format.
Does load permanently replace my profile?
No. It applies the file profile for one send and then attempts to restore the frequency and complete modem profile that were active before load.
Can I rename or edit the file?
You can use a simple .lora filename, but the contents must pass strict version, field, range and payload-length validation.