Out of curiosity, which PIC didn't worked for you?
Out of curiosity, which PIC didn't worked for you?
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
i was trying to use pic16f628a.
I have seen over the internet some others they succeed with pic12f629
it could even work with a 10F, but probably not with PBP as it consume too much RAM, but that's another story
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
hi
can anyone please send info regarding interfacing the nokia 6610 display with 8051..
You're probably out of luck on a Microchip PIC oriented forum like here, but
http://www.google.ca/search?q=nokia+...w=1366&bih=596
then
http://www.lcdinterfacing.info/Nokia...-Interface.php
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Hi Steve,
i'm looking forward to see the new driver.
I have 5 of the Nokia 5110 and i would like to play with them.
I'm sure you did a good work.
You can work with them right now, everything here work as long as you're aware of some Macro limitations. Which PIC do you plan to use ???
BTW, I'll take no credits, all the job have been done here and well done. I just put some of my spices in, some user configurables settings and some ease of use. It will be like my Keypad routine.
Still working on the final touch, code optimisation, documentation, some code example, basic schematics... fun job.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Hi Steve,
you are right about being able to using it except of some Macro limitations.
It works like a charm with the 16F88 microcontroller IF i dont use the "@ PrintStr x,y, "string goes here"" . But...IF i use that i get the truncated errors.
Regards
That's because the macro use DATA, you want to jump on the DA or DT asm instruction
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Hi Steve,
are you going to share the new Nokia 3310 and 5110 driver with us the following days?
thanks
Do you want to be a beta tester or a happy user?
Trust Steve that he will post a good piece of working code when he decides it is ready. Besides being on different time zone.
Ioannis
Last edited by Ioannis; - 29th June 2011 at 20:30.
Ioannis,
i can wait as long as it needs to be ready.
thanks
I have it working, no problem, I just always find some features to add in, and/or way to use it. Yes it will works on almost everything. 12f629 is enough with PBP... but damn, dont'expect being able to show a lot of string and embedded pictures with a so RAM/EEPROM underpowered device Still doable to add some eeprom to it, but WHY?!? Too much new 8 pin device with much more horse power under the hood for the same price.
The magic is at compilation time... hidden but there. The "driver" know which method to use to store/retrieve the strings out of the code space... OR EEPROM if you want.
Some PIC allow to read/write to their code space (PIC16F88, 877 and so forth), some don't (16F628, 12F629...)... and then you have the PIC18. 3 different method, one driver deciding for you. Sick! I learned a lot out of it... again.
Sure there will be odd PIC somewhere though... there's ALWAYS one ... or twelve.
Stay tunned... free stuff need patience
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
i would like to thank you once more Steve.
:-)
Really welcome my friend. BTW it will be handy for me too
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Simple follow up: I haven't gave up, just really busy.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
I compile the code and I got an error message:When I delete this line:@ DEVICE pic16F628A, XT_OSC, WDT_OFF, PWRT_OFF, BOD_OFF, MCLR_ON, LVP_OFF, CPD_OFF, PROTECT_OFF
there is no Error.When the line isn't deleted there is an error,that is saying Illegal opcode(pic16F628A) This error is when I use pic16F648A
which code?
@ DEVICE line is for PM assembler, if you're using MPASM to compile, you need to change it accordingly.
So again, Post #1 & #5
http://www.picbasic.co.uk/forum/showthread.php?t=543
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
I am using MPASM to compile.I try with two of them @DEVICE and _config_... etc. but it doesn't working on my PC.
If you have read post #1 and #5 of the above link and it still don't work.... Post what you tried then...
For MPASM you will use @ __CONFIG thing. notice there's 2 underscore character before CONFIG
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Teaser time... have a good reading BEFORE the launch... or lunch... whatever floats your boat.
Readme.txt
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Hi steve,
i have downloaded the txt, reading time.
thanks.
OK, since I'm changing my ISP and I'll be unavailable for a few days, I've decided to post the BETA version of it today. It's not finished yet, but quite workable.
Extract the archive to your root directory, it should create a NokiaGLCD folder. from there surf in the few code example and you should be able to understand most part of it.
Like I said, it's not 100% finished yet, the documentation is not finished (maybe not 100% accurate either) AND I'm still adding/modify features and try to shrink the whole codesize. No need for ANY complaints and I know some part have to be coded better than they already are
Before next friday (july 5th) I might not be able to access the internet as much as I would like to.
Beta Enjoy.. or beta wait
Last edited by ScaleRobotics; - 30th July 2011 at 05:08. Reason: removed outdated file
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
OUPS, discard the previous.. from wrong computer
here you go, sorry
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Wow !!! GREAT JOB !!! Thanks Mr. E !
...In some applications I put the "RES" pin of display to V+ (max 3v3), and I have no problem...Maybe it's usefull for having one "extra-pin" free, for 12F675, for example.
Thanks Fratello,
Yup, I'm aware of that, But I would prefer the CE option, since it's better to initialise the LCD right after a hardware reset. Basically you can set the CE pin to ground without problem. Now if you really run out of I/O, you could use a R/C network on the RES pin, and do the initialisation. Another thing, if you run your unit and want to go in Sleep mode... you can still re-initialise the display after the Sleep. Not sure if you can do it properly with the RES pin always high.. However, I haven't messed too much with this too much.
If you want to save an I/O, set the RES pin to Ground and use the following define
DEFINE GLCD_OVERRIDE_CE
This will remove the CE High/Low at compile time.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Thank you Steve for your work on this,
Will do some experiments this week.
Best regards
Rui
Thanks Rujic. This should work
The next and final version Include the Variable/constant to HEx/Bin/Dec conversion routine, improvement for custom, character/custom screen and... that's all. After that, it will be to the end user to make his own homework
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
as of today, 37 downloads, no bug report, no questions, not much comment... must be ok
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Mister_e: I had very long time since last read this thread!
I see that ther has been great project with NOKIA LCD stuf!!!
Excellent work you've done my friend!
If ever I need to use nokia lcd ,in the future, your routine will certainly be my first option!!!
Haha thanks Bitmaniac!
I don't know how much future there is in those Nokia LCD right now, seems the deal is no longer the deal some had couple of years ago, however it's been a good and funny project. Learnt a lot from it. Still polishing the latest version for PBP 2.60, and I guess I could have it easier to use for PBP3 but not sure yet.
Side note, for the Proteus/Isis user, one of my friend found a Model for that. I haven't used it myself because... I don't use Proteus.
OK, it seems it doesnt simulate all Nokia features like Contrast, Inverse Video and couple of other, but It looks workable. Here's the link for those interested.
http://www.8051projects.net/download...eus-model.html
What I've been told about the installation: You unpack the .zip file and copy the files located in Models and Library folder of this zip archive to Proteus/Isis Models and Library folder. Period... and it should work. My friend use Version 7.8 on Win 7 , not sure if this is the latest version or not... however...
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
@ Steve,
Perhaps one can convert it to work on a modern TFT type NOKIA lcd display, as 3310 displays may not be available in future.
Regards,
Sarma
Sure enough, it's a huge core for ANY Glcd. Sure they will be available for some times... but not those <= 2$
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Hi,could you please send me hex code an schematic for me, my email [email protected] many thanks.
Bookmarks