PBP 2.50 UPGRADE problems!!!!


Closed Thread
Results 1 to 15 of 15

Hybrid View

  1. #1
    Join Date
    Jul 2003
    Location
    Colorado Springs
    Posts
    4,959


    Did you find this post helpful? Yes | No

    Default

    Interesting.

    The default timing has been changed in 2.50

    2.46 - pbppic14.lib
    Code:
        ifndef LCD_COMMANDUS	; LCD command delay in us
    LCD_COMMANDUS EQU 2000
        endif
        ifndef LCD_DATAUS		; LCD data delay in us (0 - 255)
    LCD_DATAUS EQU 50
        endif
    2.50 - pbppic14.lib
    Code:
        ifndef LCD_COMMANDUS	; LCD command delay in us
    LCD_COMMANDUS EQU 1500
        endif
        ifndef LCD_DATAUS		; LCD data delay in us (0 - 255)
    LCD_DATAUS EQU 44
        endif
    Added: And yes, it's in the manual. (sort of)
    Last edited by Darrel Taylor; - 14th January 2008 at 21:10. Reason: it's in there
    DT

  2. #2
    Join Date
    Jan 2007
    Location
    Houston, TX
    Posts
    96


    Did you find this post helpful? Yes | No

    Talking thanks

    DEFINE LCD_COMMANDUS 2050
    DEFINE LCD_DATAUS 75

    I added the above Defines and this worked out great! Saw in the manual ...what I thougth was the default value (for PBP 2.50A) of 2000 and 50 respectively....I will now drop the delays down to 2000 and 50 respectively.

    Thanks again for bringing some clarity to my confusion!!
    Padawan-78

  3. #3
    skimask's Avatar
    skimask Guest


    Did you find this post helpful? Yes | No

    Default

    The LCD_CommandUS/DataUS change fixed my intermittent/couldn't-find problem on my 3 LCD OBD2 reader/scanner also.

  4. #4
    Join Date
    Feb 2005
    Location
    Essex, UK
    Posts
    94


    Did you find this post helpful? Yes | No

    Exclamation LCD going blank after a few hours

    Hi,

    just to add to this in case this helps someone else if they experience the same problem.

    I had a fair few of the same LCDs all running the same code. After a couple of hours, some of the LCDs would be blank (showing no text at all). Defining the LCD_COMMANDUS back to 2000 and also the LCD_DATAUS back to 50 solved the problem.

    I didn't used to have this problem when using PBP 2.47 only since I upgraded to 2.50 - that'll teach me to always use Defines instead of relying on the library defaults!

    Maybe no-one else will have this problem, maybe some will. Just thought I'd share!

    Cheers

    Rob

  5. #5
    Join Date
    Mar 2003
    Location
    Commerce Michigan USA
    Posts
    1,166


    Did you find this post helpful? Yes | No

    Default

    Rob, Also make sure you download the latest patch for 2.50 from the web site. I had a problem with the LOOKUP2 statement and that fixed it....

    Dave Purola,
    N8NTA

  6. #6
    Join Date
    Feb 2005
    Location
    Essex, UK
    Posts
    94


    Did you find this post helpful? Yes | No

    Default

    Quote Originally Posted by Dave View Post
    Rob, Also make sure you download the latest patch for 2.50 from the web site. I had a problem with the LOOKUP2 statement and that fixed it....

    Dave Purola,
    N8NTA

    Will do - thanks very much!

Similar Threads

  1. PBP 2.50 and Longs
    By mikendee in forum GPS
    Replies: 1
    Last Post: - 21st May 2008, 21:16
  2. Strange problem with PBP 2.50
    By Charles Linquis in forum mel PIC BASIC Pro
    Replies: 2
    Last Post: - 16th October 2007, 20:45
  3. MCS+ with PBP 2.50
    By BrianT in forum mel PIC BASIC Pro
    Replies: 4
    Last Post: - 21st September 2007, 05:52
  4. New PBP 2.50?
    By Dave in forum mel PIC BASIC Pro
    Replies: 19
    Last Post: - 9th September 2007, 19:14
  5. PBP upgrade queries
    By muddy0409 in forum mel PIC BASIC Pro
    Replies: 4
    Last Post: - 7th November 2006, 12:45

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