************************************************** ***********************
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 " !!!
*****************************************
Hi, Ioannis
could you PM me a mail adress for sending the scheme... ( and explanations of the NE 604 use ... if you can read French ( sorry ...))
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 " !!!
*****************************************
Alain,
Finally got a chance to run your bargraph. (it works)
But I'm still not crazy about the 5-bars. Here's what it looks like
<script type="text/javascript"src="http://www.pbpgroup.com/DT_INTS-14/V-LCD_Disp.js"></script>
<script type="text/javascript"src="http://www.pbpgroup.com/js/AceBargraph.js"></script>
It's not as noticable when it moves fast, but that jump is still there.
And while it compiles to about 100 words less than mine, it doesn't have all those features like placing it anywhere on the screen, making it any width of characters, scaling the input values to any range up to 32768, multiple bars on the screen and 3 different styles.
But it definately does a 1-line 3/5-bar graph.
DT
Well, I tested NE604 and was amazed at Audio freqs. A nearly 65dB range was obtainable on a breadborad! Incredible! So the LCD_Bargraph has now a friend for audio signals making great VU-meter. One catch is that NE604 is expensive one. Here about 10 Euros in small qts. Thanks Alain for the tip.
C/O Darrel:
While trying to develop my project using your interrupts, I stuck on, I think for sure, stupid one. The attached sample code does not respond to PORTB.0 interrupt. Is there any mistake I 've made and can't see?
Ioannis
Last edited by Ioannis; - 24th June 2007 at 19:03.
Hi, Darrel
Yes, ... I know the big problem at "high speed" is unequal calculating times upon the place pointed at ...
but we must remember it's not a GLCD ... "some holes in the somewhere" ...
Your picture's really nice !!! ...
By the way ... I have a beautiful 122x32 GLCD here ... hmmmmmm, I might give a look to that !!!
read you soon
Alain
Last edited by Acetronics2; - 24th June 2007 at 20:07.
************************************************** ***********************
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 " !!!
*****************************************
I've got some 'pre-fab' code for the 122x32 types. Nothing wild, just the basic setup/configure routines, some basic 'x,y' plotting, and some text output routines. But it works great for me...
EDIT: I just started a new thread with the code described above attached. Again, nothing fancy, but I've been using the same block of code for a couple of years now...
Last edited by skimask; - 24th June 2007 at 22:29. Reason: EDIT: added thread notice
Thanks Darrel, but it really doesn't matter since there is a real resistor for Pull-up on the pcb (Picdem2+).
I have not found why is not responding...
Ioannis
Ioannis,
I can't see any other problems with the program. Or, any reason why it wouldn't work with the PICDEM2+.
Which PIC are you using with the PICDEM?
<br>
DT
Currently the 16F877. I have handy also other to try. Maybe a 18F452.
To be sure that Portb.0 is OK, I tested with a simple loop of the kind:
while portb.0=1
wend
high LED1
and worked OK. So electrically there is no problem.
PICDEM2+ is connected to ICD2 working in programmer mode only. So, there is for sure no other source of interference.
Skimask: could you post the link you mentioned? Thanks
Ioannis
Last edited by Ioannis; - 26th June 2007 at 06:57.
Hi, Ioannis
There : http://www.picbasic.co.uk/forum/showthread.php?t=6574
<< While trying to develop my project using your interrupts, I stuck on, I think for sure, stupid one. The attached sample code does not respond to PORTB.0 interrupt. Is there any mistake I 've made and can't see? >>
Thanks to PbP ... TRISB = 255 and led on PORTB.2 will work ...
BUT does your PORTB.0 change state when button ( ?) pushed ... in other words, is the pullup or pulldown resistor the OTHER side of the Pushbutton ... ( yes, I know it's a really stupid mistake ...but ...)
have a nice day
Alain
Last edited by Acetronics2; - 26th June 2007 at 10:13.
************************************************** ***********************
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