Serial comunication problem


Closed Thread
Results 1 to 23 of 23

Hybrid View

  1. #1
    Join Date
    Oct 2004
    Posts
    440


    Did you find this post helpful? Yes | No

    Default Re: Serial comunication problem

    Quote Originally Posted by Charles Linquis View Post
    Oh, and QUIT using those 16F chips! 18Fs are so much better and don't cost any more.
    I second that.

    Norm

  2. #2
    Join Date
    Aug 2010
    Location
    Maryland, USA
    Posts
    869


    Did you find this post helpful? Yes | No

    Default Re: Serial comunication problem

    Not to continue hi-jacking this thread, but I have to a little. What is so bad about the 16F's? They are easier to configure if you are new to datasheets, work just as well (both 8 bit). OK, less memory, but who needs it for starting out stuff? I have a couple of products running 16f676 that have been going strong now for 8 years I think. Work fine!

    I am starting to play with the 18's, but really just because.
    -Bert

    The glass is not half full or half empty, Its twice as big as needed for the job!

    http://foamcasualty.com/ - Warbird R/C scratch building with foam!

  3. #3
    Join Date
    Sep 2005
    Location
    Campbell, CA
    Posts
    1,107


    Did you find this post helpful? Yes | No

    Default Re: Serial comunication problem

    Yes they work, but the forum would run a little smoother if most everyone was using the same series of chip. I'm sure MELabs thinks that way also.
    The fact that you can easily get parts with large codespace is such a bonus. You can add features over the years without
    changing much.
    90% of Microchip's really neat parts in the 8-bit realm are in the 18F family (18FxxKxx, 18FxxJxx).
    If you write some routines in ASM, it is much nicer to not have to deal with endless bank switching.
    You can use LONGs and 2000 element arrays.
    Even if you don't need all the neat stuff now, why not get a chip that has the peripherals and codespace now so that you can learn to use the extra features in your spare time?

    And they don't cost more. Easy decision for me. I'll be quiet now.
    Charles Linquist

  4. #4
    Join Date
    Sep 2011
    Posts
    20


    Did you find this post helpful? Yes | No

    Default Re: Serial comunication problem

    All Solved!!!

    I know that the issue was on Clock, or better, in wrong clock serial syncronization.
    So I have change the Internal Oscillator with a External quarze and made the code
    changing to use it. Now all work very good and without any problem.
    I have take a look on 16f676 Datasheet where is writted than internal clock have a
    little tollerance about on some kilohert. But in other forum discussion I have found
    than the internal clock is barely enought in use on serial asyncronous comunications.
    This is my case.
    Maybe if I work on OSCCAL calibration I will use the Internal clock.
    But if I put OSSCAL issue on Picbasic source the PBP give a error, like if OSSCAL is
    not avaible on 16f676.
    I have lost a week on this problem but now all is over and in anyway I have get more
    experience about use and expecially the "non-use" of internal oscillator for some specified
    task like comunications, where is very important have a good timing.
    Thank to all friends to have spend their time on this post and for goods solution proposed
    to me.
    This forum is a very good mine of competent and friendly people. I will hope to give some
    contribution in future.
    Thanks again.

Members who have read this thread : 0

You do not have permission to view the list of names.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts