> P = ._ _. A total of 14 dit spaces, (3 ending dit spaces)
> A = . _ 8 spaces
> R = . _ . 10 spaces
> I = . . 6 spaces
> S = . . . 8 spaces (Baud)
> For a total of 46 and a word space of 9 gets you to 55 baud/word.
>
> Hope this helps.
>
> Tom
>
>   *
>   |  __O    Thomas C. Sefranek  WA1RHPspam_OUTARRL.NET
>   |_-\<,_   Amateur Radio Operator: WA1RHP
>   (*)/ (*)  Bicycle mobile on 145.41MHz PL74.4
>  
> ARRL Instructor, Technical Specialist, VE Contact.
> hamradio.cmcorp.com/inventory/Inventory.html
> http://www.harvardrepeater.org
>
>  

>> technology.niagarac.on.ca/students/a/bamyote/
>>
>> A bit of googling found this, which uses a start bit, then
>> the same sequence.
>> I don't remember having a start bit though.
>
> My first thought is that it could be done much more efficiently with a
> _stop_ bit instead of a start bit. All that means is that you check for
> byte==0 _before_ transmitting a (unwanted) trailing dash.
>
> A 0110 0000
> B 1000 1000
>
> O 1111 0000
>
> S 0001 0000
>
> 5 0000 0100
>
> $ 0001 0011
>
> Seems to work ok...
>
> ---
> James Newton: PICList webmaster/Admin

> On Friday, March 16, 2007 3:11 PM [GMT-3=CET],
> wouter van ooijen  wrote:
>
>>> The start bit idea is clever! It allows a character to have
>>> up to 7 dits
>>> or dahs. You still have to count the bits as they go out (or
>>> are thrown
>>> out), though since an all dit character would go to zero as
>>> soon as you
>>> throw out the start bit.
>>
>> Wouldn't a stop bit be easier? Shift, if result in register is 0 you are
>> done, else you transmit what is in the carry and shift again.
>>
>> Wouter van Ooijen
>
> Nice Wouter!
> It might be necessary to clean up the carry flag before shifting, isn't
> it?
> Also is better to use "1" for dots than for dashes. Doing so, you can send
> the error sign.
>
>       bsf     STATUS,RP0
>       movlw   B'11111111' ; Error sign
>       movwf   BytesRx
>
> mCODE
>       BCF     STATUS,C ;do not shift "ones" now
>       movlw   0
>       RLF     BytesRx,F
>       XORWF   BytesRx,W
>       BTFSC   STATUS,Z
>       GOTO    end_of_char
>       btfsc   STATUS,C
>       goto    DASH
> DOT                     ; any output routine e.g.
>       bsf     PORTB,7
>       ;(delay intra-elem + 1 element)
>       bcf     PORTB,7;
>       GOTO    mCODE
> DASH  NOP
>       bsf     PORTB,7
>       ;(delay intra-elem + 3 element)
>       bcf     PORTB,7;
>       GOTO    mCODE
> end_of_char
>       ;(end of char delay inter-char-elem + 3 element ???)
>
>
> Dennis.
>

> SendMorseCharA
>        RLF   MorseChar,f  ; shift msb into carry
>        movf  MorseChar,f  ; test to see if we're done
>        bz    SendMorseCharZ ; We're done, get out
>        skpc               ; skip if dit
>        call  DoDah        ; go send dah - PRESERVE CARRY!
>        skpnc
>        call  DoDit        ; go send dit
>        call  InterCharDelay
>        goto  SendMorseCharA ; go send next bit, if any
> SendMorseCharZ
>        return              ; we're outta here!

> On 3/16/07, William Chops Westfield <RemoveMEwestfwTakeThisOuTmac.com> wrote:
>>
>> > SendMorseCharA
>> >        RLF   MorseChar,f  ; shift msb into carry
>> >        movf  MorseChar,f  ; test to see if we're done
>> >        bz    SendMorseCharZ ; We're done, get out
>     movlw DITLEN
>     skpc               ; skip if dit
>     movlw DAHLEN
>> >        call  DoBit        ; go send bit
>> >        call  InterBitDelay
>> >        goto  SendMorseCharA ; go send next bit, if any
>> > SendMorseCharZ
>> >        return              ; we're outta here!
>
>> Speaking of C compilers, this is a good example of the sort of
>> code that I think it would be really difficult for a C compiler
>> to generate; It's what I meant by "explicit use of carry."
>
> I'd do something like the above instead since the difference between a
> dit and a dah is their length...
>
>  > (And on the third hand, it is perhaps also an example of optimization
>> that doesn't need to be done.)
>
> True.
>
> Orin.