From 84ccbf972d05a1a3621d34edc4121e95ef3ec0ac Mon Sep 17 00:00:00 2001 From: Philip Heron Date: Sat, 10 Oct 2015 17:22:42 +0100 Subject: [PATCH] Use a callsign example that fits... --- README | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README b/README index 0e6a5af..b4f6288 100644 --- a/README +++ b/README @@ -9,9 +9,9 @@ Uses the Reed-Solomon codec written by Phil Karn, KA9Q. ENCODING -$ ssdv -e -c CALLSIGN -i ID input.jpeg output.bin +$ ssdv -e -c TEST01 -i ID input.jpeg output.bin -This encodes the 'input.jpeg' image file into SSDV packets stored in the 'output.bin' file. CALLSIGN (an alphanumeric string up to 6 characters) and ID (a number from 0-255) are encoded into the header of each packet. The ID should be changed for each new image transmitted to allow the decoder to identify when a new image begins. +This encodes the 'input.jpeg' image file into SSDV packets stored in the 'output.bin' file. TEST01 (the callsign, an alphanumeric string up to 6 characters) and ID (a number from 0-255) are encoded into the header of each packet. The ID should be changed for each new image transmitted to allow the decoder to identify when a new image begins. The output file contains a series of SSDV packets, each packet always being 256 bytes in length. Additional data may be transmitted between each packet, the decoder will ignore this.