BUILT-IN CONTROLLER (KS OR EQUIVALENT). ITEM. DIMENSIONS. UNIT. +5 V POWER SUPPLY. Module Size (W x H x T). 93 x 70 x ( LED). KS from Samsung Semiconductor Division. Find the PDF Datasheet, Specifications and Distributor Information. KS LCD Graphic Display Modules & Accessories are available at Mouser Electronics. Mouser offers inventory, pricing, & datasheets for ELECTRONIC.
|Published (Last):||26 May 2017|
|PDF File Size:||20.47 Mb|
|ePub File Size:||14.54 Mb|
|Price:||Free* [*Free Regsitration Required]|
Forums New posts Search forums. Media New media New comments Search media.
Articles Top Articles Search resources. Welcome to our site! Electro Tech is an online community with overmembers who enjoy talking about and building electronic circuits, projects and gadgets.
KS0107 LCD Display IC Datasheet
Once I get this running I’ll also share Thanks, -Michael. It’s for C18 but should be easy to get working.
The above code was written to work with Bill’s Unicorn kit. If you look at the assembly manual it has the schematic.
Thank you, that ks01107 exactly what I was looking to see! I was curious to see if someone would like to take a look at what I’ve got so far and tell me if they think this will work. The circuit will be breadboarded as the schematic indicates. My main concern at this point is that I believe I only have 6 5V tolerant pins, so in consideration of a status read, I may have to re route those connections so that if it is possible that they’re high 5V VDDthe DSC will tolerate the logical high values.
Of course it may be possible to not worry about doing any reads if my timing is perfect. Any input is greatly appreciated!
H file found on the previously linked post for the C18 Compiler. Mike, I believe on that post you said it needed updated, but I couldn’t find the updated copy. Could you, or anyone tell me what is wrong that version or how to obtain a build able version? The problem with that code was that I wrote it rather hastily and referred to some ports directly. I later changed it and that is the version linked to earlier in this thread.
As far as I’m aware it should now work correctly. I found the problem c18 works finec30 gives build errors.
It looks like in the GLCD. H file datasheer 37 and 38 are defining and pointing the message and logo parameters to program memory within the PutMessage and PutLogo functions. Datasheet problem is that the c18 compiler and the c30 compiler use different storage qualifications for creating variables in program vatasheet.
KS Controllers – – Great Cow BASIC documentation
The comparison below can be found on the c30 compiler user guide: OK, I got it to compile, and it is running now with output to the screen although it doesn’t look like much of anything. What is the purpose of having the dummy reads?
Is it necessary to use reads or can i just use delays? If it is absolutely necessary to use a read, I think i’ll have to use different pins, which will mean the fonts and libraries will need to be offset. If you need to plot individual pixels then you need to be able to read so you can OR in the new data.
If your happy just writing characters on byte boundaries then you can just use a delay.
4″x64 Graphic LCD Display Module w/KS+KS,White on Blue
Gotcha, but since the C30 compiler limits unsigned CHAR arrays to a maximum size ofand since i’m using a bit wide bus, i think i’m pretty much forced into doing reads anyways. The reason is the 2 byte writes to the port will overwrite the entire port each time unless I do a bitwise OR with the 2 bytes.
If I do a bitwise OR i’m not sure how i’d temporarily store it as it sequenced through the array. It may be possible to shift the data in. OK so now i’ve wired up the circuit to allow reads, but that means the data all has to be shifted over 4-bits. I’m not sure of an efficient way to do this with the code. The data pins will be RB4-RB OK, but i need 0x4xx0 where ‘xx’ represents the data.
Most significant 4 bits are the GLCD’s control lines. Any bitwise operations to make this work??
The least amount of operations the better of course. The way I do bitwise in C is this way: LATB instructions overwrite the entire port wiping out the control pins each time, which is the need for the shifting.
A bitmask is what i’m using now, but i’d datashdet rather automate it. LATBx only effects datsheet bit x. You could also use unions and structs to work with custom bit fields in C.
dsPIC33FJ12GP202 DSC with KS0107/KS0108 GLCD
Try this code in SIM to see how it works: Yes i understand that LATBbits. Since the control lines are on the same port as the data lines, a port wide LATB or PORTB instruction will overwrite the entire port when the data is sent unless each bit is addressed independently as mentioned. I started for example breaking down the bits independently for cleaner code, but regardless of how its done, every xatasheet controlling the LCD is on the same port.