Update 'WSPR Message Coding'
parent
09483cf29e
commit
155e78f497
|
@ -1,5 +1,5 @@
|
|||
Message types
|
||||
--------------------
|
||||
-------------
|
||||
|
||||
Reverse engineered from the original `wqdecode` fortran routine.
|
||||
|
||||
|
@ -29,15 +29,15 @@ Three common use cases:
|
|||
The prefix will also be part of the hash so your messages can be matched.
|
||||
|
||||
Standard Message
|
||||
-------------------------
|
||||
----------------
|
||||
Explained quite well in [The WSPR Coding Process](http://g4jnt.com/WSPR_Coding_Process.pdf) by G4JNT.
|
||||
|
||||
|
||||
Prefixed Callsign Message
|
||||
------------------------------------
|
||||
-------------------------
|
||||
**TODO**
|
||||
|
||||
Exetended Locator Message
|
||||
---------------------------------------
|
||||
--------------------------
|
||||
Hash function use for the call sign is `hashlittle` from [lookup3.c](http://burtleburtle.net/bob/c/lookup3.c) one of the [Jenkins hash functions](https://en.wikipedia.org/wiki/Jenkins_hash_function).
|
||||
The hash function is applied to the complete call sign including any prefix or suffix.
|
||||
|
|
Loading…
Reference in New Issue