My version is 2.47
But i will try a 2nd pic now and see...
.
How better/worst it is if you dump the appended .HEX file in your PIC... don't change anything in the config fuses.. use it AS-IS
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
I just changed the MCLR off to on ( i was affraid i could get my pic locked ).
But it worked and both ports are 0.15V ... meaning...are reading both LM35
EDIT:
The first line of the LCD is not steady...i mean...i get VOLTAGE..0.15V and dLTAGE..0.15V ( blinking some times )
.
Last edited by ruijc; - 7th December 2007 at 22:20.
After the Line2 command, I found that I often had to add a space ahead the text, or the first character would get dropped. Some LCD's are too slow to change lines and display immediately. Apparently you need a delay, since it's effecting more than one character.
I still get behaviour no matter what i change...
except with Mister-e's code that works OK
Is it just a pbp version issue or is it something else ?
If it's a version problem...is there a way to get arround it ?
.
Hi, Ruijc
I just re-wrote your code ... works fine ( I'm only talking of the PIC point of view - do not talk about precision ...)
Try to write carefully ( and readably) ALL your config sequence ( I know ... ~ 50 lines ! )... and it will work !!!
Just a tip:
instead of :
" temp = (va1*/500)>> 2 "
try :
" temp = val*125
temp = temp.highbyte "
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 " !!!
*****************************************
Bookmarks