On Thu, 5 Nov 1998 18:03:57 +0000 "Peter L. Peres" writes: >On Thu, 5 Nov 1998, Gavin Jackson wrote: > >> The first thing that comes to mind is to decode the >> dot dash dash dot into 0110 with a '1' representing >> dash and a '0' representing the dot. Then store a >> table in the PIC and do a simple compare through >> the table until a match is found. The only problem >> I see with this method is trying to tell the difference >> between a J ( . - - - ) and a 2 ( . . - - - ) which would be >> 0111 and 00111 respectively. > >The usual way to encode decoded morse for id purposes is a 4-way code, >with 2 bits per symbol. That's like: > >00 - dot >01 - dash >10 - long space >11 - error (neither of above) or end symbol. > I did a Morse ENCODER years ago on a motorola 6802. ASCII codes indexed into a table where each Morse character was represented by a byte. The 5 least significant bits were 0 for dit and 1 for dah. The 3 most significant bits indicated how many of the lsb's to use. This allowed the use of 5 dits and/or dahs per character, which handles the alphabet, numbers, and most punctuation (but not stuff like End Of Transmission ...-.-). I wrote that 10 or 15 years ago. A few hundred units still out there running... Harold Harold Hallikainen harold@hallikainen.com Hallikainen & Friends, Inc. See the FCC Rules at http://hallikainen.com/FccRules and comments filed in LPFM proceeding at http://hallikainen.com/lpfm ___________________________________________________________________ You don't need to buy Internet access to use free Internet e-mail. Get completely free e-mail from Juno at http://www.juno.com/getjuno.html or call Juno at (800) 654-JUNO [654-5866]