DEFINE OSC too limited


Closed Thread
Results 1 to 19 of 19

Hybrid View

  1. #1
    Join Date
    Jul 2003
    Posts
    2,358


    Did you find this post helpful? Yes | No

    Default

    Of course the PAUSE works properly... you just need to make an adjustment with a little bit of math. So if you want to time 1 second with a DEFINE OSC of 16MHz and your 17.734MHz xtal, all you need is...

    16/17.734*1000

    Pause 902

    Think outside the box. The limits of PBP are your imagination.

  2. #2
    mytekcontrols's Avatar
    mytekcontrols Guest


    Did you find this post helpful? Yes | No

    Smile Too cryptic for me, but perhaps not for others

    Hi Melanie,
    Yes I understand that you can take the approach you just gave, but I tend to like things to mean what they say. If I have a statement that says "Pauseus 100" then I would like it to actually mean that I am taking a 100 microsecond pause. In this case we really aren't talking about "thinking outside of the box", but instead, about writing understandable code. Besides we aren't just talking about Pause routines here. There are 24 PBP functions that are all affected by incorrect oscillator selection.
    Code:
    COUNT, DEBUG, DEBUGIN,DTMFOUT,FREQOUT,HPWM,HSERIN,HSEROUT,
    I2CREAD,I2CWRITE,LCDOUT,OWIN,OWOUT,PAUSE,PAUSEUS,
    SERIN,SERIN2,SEROUT,SEROUT2,SHIFTIN,SHIFTOUT,
    SOUND,XIN, and XOUT
    I would hate to come back later, and try to debug even my own code, not say someone elses, if I used the method you suggested. Especially if a variety of the functions mentioned above were sprinkled throughout.

    Don't get me wrong, I like PBP, and really appreciate the effort that had to be put into making it what it is today. However this is a "Wish List" and my wish is to see a better way to do the Oscillator Define, so that all functions utilizing timing in their makeup continue to do what they say, and to mean what they mean. Is this asking too much? Or am I developing a case of OCD?

  3. #3
    Join Date
    Jul 2005
    Posts
    65


    Did you find this post helpful? Yes | No

    Smile

    Hello mytekcontrols

    In deed, you are absolutely right.

  4. #4
    breogan's Avatar
    breogan Guest


    Did you find this post helpful? Yes | No

    Default Problems with OSC.

    Hi,
    I'm trying to use 20MHz oscillator with PIC16C74A, for example, I have written this program to make blink a led for 1 second, but it doesn't work, the frequency is not 1Hz (it is more slow):

    '********** Definitions **********
    DEFINE OSC 20

    '********** Main prog **********
    Main:
    high PORTA.0
    pause 500
    low PORTA.0
    pause 500
    goto Main

    End

    '***************************************

    I'm using the David Tait programmer (home made) with the PIC74.EXE program (PIC16C74 Programmer Version 1.0b Copyright (C) 1996 Paul Vollebregt.) With the options "-hp8" (HS osc), also I have triyed with "-xp8" (XT osc).

    Thanks !
    Last edited by breogan; - 21st November 2005 at 11:06.

  5. #5
    Join Date
    Jul 2003
    Posts
    2,358


    Did you find this post helpful? Yes | No

    Default

    Of course it'll be slower...

    Lets assume that Pause 500 is a perfect 500mS (which is unlikely but probably close). Your HIGH and your LOW and your GOTO all take up time too which has to be taken into account. Finally, how accurate is your Oscillator? 20.00000MHz or is it a few percent high or low?

    You want exactly 1Hz... go grab an oscillocope and trim it... now you have control in 1uS steps... but you add any other code or you nudge your room thermostat a little, and bang goes your timing!

    Main:
    high PORTA.0
    pause 499
    pauseus 1000
    low PORTA.0
    pause 499
    pauseus 1000
    goto Main

  6. #6
    Join Date
    Sep 2003
    Location
    Vermont
    Posts
    373


    Did you find this post helpful? Yes | No

    Question

    Is there some way to nudge the "DEFINE" value that PBP uses when compiling?

  7. #7
    Join Date
    Jun 2011
    Location
    Indian Harbour Nova Scotia
    Posts
    108


    Did you find this post helpful? Yes | No

    Default Re: DEFINE OSC too limited

    Good answer Melanie, I agree 100% with what you say. Purists tend to focus too much on one parameter, not realizing that in the big picture, there are lots of things that affect your reading, like temperature! In engineering we typically ignore the bottom 10% and the top 90% and concentrate efforts in between, meaning we don't sweat the small stuff unless it is ABSOLUTELY necessary. A LED that doesn't blink at exactly 1.0000Hz? Who cares, unless your using to to time Longines watches.

  8. #8
    Join Date
    May 2004
    Location
    NW France
    Posts
    3,653


    Did you find this post helpful? Yes | No

    Default Re: DEFINE OSC too limited

    Quote Originally Posted by queenidog View Post
    Good answer Melanie, I agree 100% with what you say. Purists tend to focus too much on one parameter, not realizing that in the big picture, there are lots of things that affect your reading, like temperature! In engineering we typically ignore the bottom 10% and the top 90% and concentrate efforts in between, meaning we don't sweat the small stuff unless it is ABSOLUTELY necessary. A LED that doesn't blink at exactly 1.0000Hz? Who cares, unless your using to to time Longines watches.
    ... I do not know if Mel will even see your post ...

    did you notice it is a 10 years after dig out ( tadaaa, music ON ) ... add to that Mel has left this forum many years ago ... ( 2 or more ...)

    Last Activity:- 22nd February 2012 01:20
    Alain
    ************************************************** ***********************
    Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
    ************************************************** ***********************
    IF there is the word "Problem" in your question ...
    certainly the answer is " RTFM " or " RTFDataSheet " !!!
    *****************************************

Similar Threads

  1. RF Modules
    By tonyfelloni in forum mel PIC BASIC Pro
    Replies: 44
    Last Post: - 26th June 2010, 17:42
  2. PIC16F877A analog problem
    By DeViLa_Q8 in forum mel PIC BASIC
    Replies: 0
    Last Post: - 30th July 2009, 20:19
  3. RX TX modules - intermitent communication
    By ruijc in forum mel PIC BASIC Pro
    Replies: 13
    Last Post: - 11th June 2009, 00:13
  4. PIC HSERIN problem
    By shaiqbashir in forum mel PIC BASIC Pro
    Replies: 10
    Last Post: - 20th July 2008, 11:08
  5. Replies: 8
    Last Post: - 17th September 2006, 17:46

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