Releases: sudorgherd/argus-redline
Releases · sudorgherd/argus-redline
Release list
ARGUS REDLINE v0.1.03
Highlights
- Moved Hub and Node identities out of
protocol.h - Added per-environment device IDs through PlatformIO build flags
- Added
include/device_config.h - Added compile-time checks for missing or conflicting IDs
- Preserved the existing Protocol v0.1 wire format
- Prepared the firmware for additional independently configured nodes
- Updated Hub and Node startup reporting to v0.1.03
Validation
- Hub build: PASS
- Node build: PASS
- Hub flash on COM4: PASS
- Node flash on COM5: PASS
- 13 consecutive command/ACK exchanges verified
- Sequences 9–21 acknowledged without retries or malformed responses
- Addressing verified as Hub
1 → 16and Node ACK16 → 1 - CodeQL checks: PASS
ARGUS REDLINE v0.1.02
Highlights
- Added formal opcode ranges for core, application, and reserved use
- Added a typed
Opcoderegistry - Preserved compatibility with
OPCODE_TEST - Added centralized supported-opcode validation
- Added command payload-length validation
- Added ACK status validation before enum conversion
- Updated Hub ACK matching to use the transmitted command opcode
- Updated Hub and Node startup reporting to v0.1.02
Validation
- Hub build: PASS
- Node build: PASS
- Hub flash on COM4: PASS
- Node flash on COM5: PASS
- 10 consecutive command/ACK exchanges verified
- Sequences 13–22 acknowledged without retries or malformed responses
- CodeQL checks: PASS
ARGUS REDLINE v0.1.01
Highlights
- Replaced the Node's blocking receive cycle with continuous asynchronous
startReceive() - Added DIO1-driven RX and TX completion handling
- Added explicit
LISTENINGandTRANSMITTING_ACKstates - Converted acknowledgment transmission to asynchronous
startTransmit() - Preserved Protocol v0.1 addressing, validation, duplicate suppression, cached ACK replay, and opcode handling
Validation
- Hub build: PASS
- Node build: PASS
- Hardware flash on COM5: PASS
- 18 consecutive command/ACK exchanges verified
- Sequences 216–233 acknowledged without loss
- No periodic receive timeout cycle observed
ARGUS REDLINE Protocol v0.1.0
ARGUS REDLINE Protocol v0.1.0 establishes reliable bidirectional binary LoRa communication between a Hub and Node running on Heltec WiFi LoRa 32 V4 hardware.
Verified capabilities
- Versioned six-byte binary packet header
- Explicit source and destination addressing
- Command opcode support
- Sequence-matched acknowledgments
- Packet-length and packet-type validation
- Bounded acknowledgment retries
- Duplicate-command suppression
- Cached acknowledgment replay
- Automatic recovery after temporary Node loss
- RSSI and SNR serial diagnostics
Hardware tested
- 2× Heltec WiFi LoRa 32 V4
- ESP32-S3
- Semtech SX1262
- 915 MHz LoRa configuration
This remains experimental development firmware and is not intended for safety-critical reliance.