PBP 2.50 UPGRADE problems!!!!

[skimask]

Read the manual...You'll find DEFINE LCD_COMMANDUS and DATA_US. Increase those and you should be ok without the extra pause.

[earltyso]

I will be sure to do that.

[Acetronics2]

Hi,

I had the same issue with PbP 2.50a some times ago ...

Thought it was my LCD a bit lazy!!!

DEFINE LCD_COMMANDUS 2000 solved that ...

May be a better PBP timing ... the datasheet told 1.62 ms !!! LOL ...

Alain

[Darrel Taylor]

Interesting.

The default timing has been changed in 2.50

2.46 - pbppic14.lib

    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

    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)

[earltyso]

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!!

[skimask]

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

[Rob]

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