Essentially, if you handed the right text to it, I have a SAME encoder. There are other technical specifications regarding its use in the real world, but it’s irrelevant here. Bytes are transmitted in reverse order (LSB -> MSB), that is, 00010111 would be transmitted as 11101000. Mark tone (binary 1) is 2083.3 Hz and space tone (binary 0) is 1562.5 Hz, with each tone lasting about 1920 microseconds. These bursts are AFSK-modulated data with a throughput of 520.83 bits per second. Information about an emergency message (such as locations affected, type of message, where it’s coming from, and how long it will be considered effective) is transmitted in the form of digital bursts at the beginning and end of said message. NOAA’s Specific Area Message Encoding (or SAME) protocol is used to further streamline the Emergency Alert System. Greg Hewgill, has updated the source to his NWR tools, now at: It does appear that software to decode SAME data exists, just not open source.Ī SAME software decoder would benefit projects like thelinkbox, and asterisk app_rpt as well as other projects. I am thinking for interfacing to repeaters to provide custom weather alert signaling. One could dedicate a cheap USB sound FOB to a receiver parked on their NOAA weather radio frequency that would sit and decode any SAME data bursts. ![]() ![]() I have often thought it would be nice if there was an open source (soundcard/ FOB based) SAME decoder solution.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |