16F677 lcd troubles

[12aBridge]

thanks joe ,Ive been through that data sheet over and over ,looking to turn off all the hardware stuff,completely missed that though. any ideas why the control commands worked,surely they would need the same data pins ,or have I missed something in the screens data sheet too....

thanks again

[Archangel]

any ideas why the control commands worked,surely they would need the same data pins ,or have I missed something in the screens data sheet too....

I am not sure which "control commands" you refer to . . . But some PBP statements do a whole lot of stuff behind the scenes. For instance the High / Low commands set tris registers on the fly and may well kill off some analog functions as well, I won't swear by that though.

[Dave]

12aBridge, What are you trying to accomplish with the statements:
lcdout $FE,1
pause 700
lcdout $FE,1,"one" 'this doesnt work
pause 700
lcdout $FE,1
pause 700
lcdout $FE,2,"two" 'this doesnt work
pause 700
lcdout $FE,1
pause 700
LCDOUt $FE,#temp 'this doesnt work
pause 700

The statement:lcdout $FE,1 will try to clear the display. Some display's require a small amount of time ~5 to 15 milliseconds before being able to receive data. You are sending the data string "one","two",and the ascii representation of the value in temp to the display before it has had a chance to execute the previous command of clear screen. After sending the clear screen command "$FE,$01" wait for about 10 milliseconds (pause 10) and see if that doesn't cure the problem... I normally wait for 100uS after I send any commands that require the use of the $FE command. especially the ones that change curcor position. If you read the data sheet for the display you are using these delays will be called out...

Dave Purola,
N8NTA