I recently watched the EEVblog video about hacking the VFD and it "inspired" me to hack my own. I actually have three displays that I pulled out of various devices (one of them is a VFD) and they all have the driver chips on the same board. This is a good start on all of them

. Let's just focus on one of them for now. I think I pulled it out of a VCR or something like that.
The PCB is about 1.5 times the length of the LCD itself and just about the same width. It has "JK1165" and "LMKM-P3X" on the silkscreen. The second one returns a result in Google, but they are unrelated to the board (or at least not directly). However, I did find a datasheet to the driver chip, which is a BU9716K. The datasheet I found actually lists both the BU9716BK and BU9716BKV, the BK is the closest match to the one on my board.
(
datasheet)
My next step was also easy... sorta. The PCB has two connectors on it so I needed to figure out which pins connected where on the chip. Both connectors have six pins. I made a list (table, really) of both connectors like if I were to hold the entire board in proper viewing position and probed with my DMM to see what pin on the chip went where with the datasheet open for reference. This is what I came up with:
| 1 | 2 | 3 | 4 | 5 | 6 | 1 | 2 | 3 | 4 | 5 | 6 |
| CS | CLK | Din | ? | (probably the IR receiver output) | ? | ? | Vdd | Vss | ? | ? | ? |
how do i give tables a border?This is as far as I have made it. Page six of the datasheet suggests that the driver chip will receive 12 bytes of display data followed by one byte of control data. The control byte looks easy enough to be able to figure out via testing; it relies on three bits, one of which is simple to understand. The other two bits are a tad confusing. It's the twelve data bytes that are going to give me problems.
It will be tomorrow (it's about 11:20 PM) before I can do any more research on it. There was something else I was going to say, but it escapes me.