Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
12/30/04 21:48
Read: times


 
#84148 - It's not so bad
Responding to: ???'s previous message
So it's 16? I wanted to recommed this and a little less (so 8-16), but didn't remember the exact figure and thought it's 8 (and have no access to bibles. right now.)

But in this case, you don't need to interrupt in this high rate all the time, only while searching for the beginning of the start bit, then you interrupt at the bit rate (after the initial half-bit (sw uarts often do an initial one-and-half bittime to interrupt right at the middle of first databit skipping the startbit, but I like to check the startbit too, for added noise immunity)). And the rapid interrupt may consist of
jb rx_in_progress_flag,rx_routine
jnb P1.0,rx_startbit_begins
reti 

only, which is viable even at 4800*16/sec. But, if the design permits, I would rather use an interrupt to detect startit rather then rapid sampling.
And even if you want to do the majority-of-three-sample thing, you don't need to make an interrupt each 1/16 bittime; you make it 14/16-1/16-1/16, this also is not so bad (and usually noise is not an issue with serial and if it is, the three-samplething will not help, either...)

Jan Waclawek





List of 27 messages in thread
TopicAuthorDate
Polling/Interrupt For Serial Input            01/01/70 00:00      
   bible time            01/01/70 00:00      
   Soft UART            01/01/70 00:00      
   Hardware?            01/01/70 00:00      
      SW UART is not a taboo!            01/01/70 00:00      
         yes...            01/01/70 00:00      
         think before you do            01/01/70 00:00      
   Use oversampling            01/01/70 00:00      
      soft UART            01/01/70 00:00      
      Half bits            01/01/70 00:00      
      Oversampling            01/01/70 00:00      
         It's not so bad            01/01/70 00:00      
            Oh yes it is!            01/01/70 00:00      
               Haven't read it completely?             01/01/70 00:00      
                  neither have I            01/01/70 00:00      
                     Sure you did not!            01/01/70 00:00      
                        did I miss it            01/01/70 00:00      
                           Problem displaying posts?            01/01/70 00:00      
                              sure that will work            01/01/70 00:00      
                                 NOT A PIC            01/01/70 00:00      
   Just forget 89c51 then.            01/01/70 00:00      
   @Erik            01/01/70 00:00      
      ...all said already.            01/01/70 00:00      
      OS? Threads?!            01/01/70 00:00      
      Appnote to read            01/01/70 00:00      
      threads            01/01/70 00:00      
         Problem Solved            01/01/70 00:00      

Back to Subject List