I have a 128x64 display that uses the HD61202 and HD61202 controller IC’s. I’ve had a look around and it seems that the 61202 is s/w compatible with the KS0108 so i’m thinking it wouldn’t take much to implement it with MIOS. The aim is to use this display as a graphical representation of surround control for use in Logic. A joystick would control the surround settings - as described in this post: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=concepts;action=display;num=1039325767;start=0#0. So the questions are:
First off, is this display okay? (datasheets at end of post)…
Would it be possible to use it as a graphical representation of surround control? I see it as summin quite basic, like a cursor (controlled by the joystick) which u’d then just move about on screen and position accordinly…This would have to programmed I assume?
I’m guessing it would require a seperate core (would be used in my LC box) - is this where midibox link comes in?
I also remember TK talking about the ‘layer functionality’ of the MBLC - would that play a role in this config?
this is one of the good ones - as you can see in the datasheet:
it stores the pixels vertically.
The command set is compatible, so it should work with GLCD mode 1 w/o problems. Would be great if you could ensure this
yes, this has to be programmed. No problem with MIOS so far, but requires some skills
if you want to use it as second GLCD: yes, a second core. For MIDIbox Link just connect the grounds together and MO of the “master core” to the MI of the “slave core”. Thereafter the “master core” (your MIDIbox LC) can send special SysEx strings or similar to control the second GLCD via remote (but here again: implementation is easy - routine has to be inserted into the MIDI processor handler - but requires programming skills)
One thing - to test the LCD how should i connect it it to the 18F core module? Should i just follow the pinout of the GLCD as in mbhp_glcd_64240a.pdf? Some of the pins are slighty diff…
Also, as this GLCD would go on a second core - would i also use this for the joystick/surround control addon? Makes sense i guess…
Well, I tried connecting this LCD to an 18F core and it was a no go - lowered all the voltage levels instead :??? I wired it in as shown in GLCD pdf/gif as the pinouts was more-or-less the same…
Perhaps this LCD requires some additional components for the power or summin - as that T6963C did?
the initialization is exactly the same - the display will be turned on with the “0x3f” command, thereafter you should see the pixels.
Also the bus interface is exactly the same. Are you able to control the contrast? Do you see gray pixels? If not, the Vee->V0 connection via the pot has not been setuped correctly. You could also measure Vee against ground, should be ca. -10V. The level at V0 should be between -8V and -10V
Another possible reason could be the reset line (remember the HD64240 problem?). The reset input should be tied to +5V. If this doesn’t work, try ground (the datasheet doesn’t make clear if the reset is inverted or not)
I had it wired exactly as described in ur pdf and the additional 10k pot connected as so. I’ve tried ur other suggestions but I still get the same result - an overall reduction in voltage accross the whole circuit. The points u mentions are coming up at like -0.186V :??? but then once the GLCD is removed it’s all fine again - and working with the standard characted LCD…
Mebbe this GLCD requires some sort of additional power circuit or summin?
One thing, i’m testing without the A&K pins connected - that shouldnt matter tho should it? It’s only for the backlit and works fine with no connection on regular cha LCDs…
yes, the A/K pins are not necessary to control the LCD. Hm… you wrote:
but then once the GLCD is removed it’s all fine again - and working with the standard characted LCD.
does this mean that the core is running with the same LCD type for both displays? This will not work, you have either to change the type setting in the ID field during burning the first-level bootstrap loader, or you have to add a MIOS_LCD_TypeSet function call to the LC_Init hook of the application.
But i cant get that far T, as I’ve said, when the GLCD is connected the voltage levels accross the WHOLE setup (LCD and Core) are all lower then should be - so i cant load MIOS at all atm…
I’ve had a google for this display - not much info came up but i did come across this post from some forum: http://www.skippari.net/phpBB2/viewtopic.php?p=503 - It’s a slighty diff model number to the one I have but it may help to troubleshoot. It mentions the display “… needs some extra negative tensions to work properly (lcd Driving and Contrast)”, so that makes me think thats what the prob here is…
some days ago you wrote that you are seeing the pixels (points), so the contrast voltage level is ok and doesn’t require an additional supply. The backlight is another issue, but not so important yet. However, it would be interesting for me if the display driver is still active. Could you please send the following SysEx string to the core and write down the return message?
some days ago you wrote that you are seeing the pixels (points)
???
I don’t remember sayin that, I havnt been able to see anything on the display…
Again, I cant send that msg to the core as when the GLCD is attached the voltage levels across the WHOLE circuit (lcd/core/etc) get screwed up so the core wont be able to send out a bean…only when the GLCD ISNT attached do the voltage levels on the core return to normal - as ud expect so…
Alright, it seems that I’ve misinterpret one of your comments (“The points u mentions are coming up at like -0.186V”).
The datasheet says the the LCD consumes about 3mA — thats nothing compared to other components. So it must be a wiring error (are you sure that this: http://www.notapplicable.co.uk/mbhp/dg-12864.pdf is the correct datasheet?). One thing that you can do is to remove all wires from the display and to connect them again in the following order
(turn off the power before every step!)
Vss/Vdd
check if the core sends a MIDI message after power-on
Vee->Pot->V0
check if the core sends a MIDI message after power-on
control lines (D/I, R/W, E, CS1, CS2)
check if the core sends a MIDI message after power-on
data lines (D0-D7)
check if the core sends a MIDI message after power-on
reset line with a 10k pull-up against Vdd
check if the core sends a MIDI message after power-on
OR reset line with a 10k pull-down against Vss
check if the core sends a MIDI message after power-on
Thats the thing, it seems this is bit of phantom LCD as after getting in touch with the manufacturer this is what they said:
I think that my design team (in Taiwan) did a little work on the side and made the '15 series pin compatible with the DG-12864, then renamed it the DG-12864-27. Technically this module was not was not
sold by Excel Tech so I can only offer limited (official) support. Take a look at these two datasheets and let me know if you think my theory is correct, the urls are:
yes, the new datasheet makes much more sense - among other pins Vdd and Vss are exchanged, this means that you will get a short when you connect the LCD in the wrong order. Thats exactly what you’ve noticed. It’s also interesting that the pin name for the reset line indicates a low-active input /RST, means: you have to use a pull-up to +5V.
Now I see only two problems: Vee is missing, this means that you have to supply V0 (here: Vlc) with ca. -8V to -10V from external. (Note: in some days I will publish a MAX759 based DC converter which supplies up to -15V from a 5V source).
Another problem are the chip select lines /CS1 and /CS2. They are inverted. However, I can compile a special MIOS version for testing purposes if another polarity is required.
But in the meantime just check if the core voltage is ok with the new pinning.
for the case that you want to try it with an external voltage source w/o the DC converter:
so, once i get this external voltage thing made I can test ye? or do you mean i dont need one now - the lcd works of the core power? I’ve got some of those maxim ics in the post just in case neways…
