Self-Illuminating, No Backlight Required.
Parallel and Synchronous Serial Interfaces.
Please click here to see a complete product listing.
Which line that is would speak to what strategy you must employ to do the latching and blanking.Ĭode: Select all // Arduino VFD Driver Library If there is not such continuity, or there is only between 2 of those 3 places, there may be an inverter (or transistor version thereof) in there, which is good. I suppose the easiest way to find that out would be if you have continuity between pins 24 and 26 on one of the MSC1162A chips and TP8 at the interface header. If the display is not wired that way, this is completely wrong. For each column, you'd lower it to blank the display, shift 92 bits, and raise it again to unblank the display until it is time to refresh the next column. If the ~CL and LS lines on the driver chip are simply tied together to make that line in the module interface (I have no way to know this I do not have this module, and it is just a guess), that means you'd want to drive the combined line low (because that blanks the display) until you start scanning the display. This display appears to use the same line for latching and blanking. Interrupt it how? Do the lit pixels bear any relationship to what is supposed to be displayed? Maybe you're blanking the display most of the time, and maybe interrupting the microcontroller (whatever that means in this particular case) unblanks the display long enough for you to see something. Peter Loron wrote:I'm pretty sure the display itself is functional because occasionally when I interrupt the microcontroller, I get some pixels lit on the display.just got lucky with spurious signals. I'm not sure what else to throw out there, not having any idea what you're doing, or even what you're doing right. You have to send out 20 columns of 92 bits per column, and you need to refresh the entire frame over 60 times per second to avoid flicker. You can't just clock in the data once and have it keep going. I'm assuming you know that you have to continuously refresh the display. The thing is, though, I also cannot figure out what you're doing wrong, since I cannot see what you're doing at all.
Not the same display, but something similar. I'd really appreciate some help from the hive mind.
It appears that you need to clock in the raw bits for each column.there is no high level interface.ĭoes anybody have experience with writing code to interface with a similar display? I've pulled out what little hair remains, but I cannot figure out what I'm doing wrong! According to the OVC site linked above the lines are Vcc, Gnd, Clock, Data, and Enable. The module has a 10-pin socket, with the lines duplicated. I'm pretty sure the display itself is functional because occasionally when I interrupt the microcontroller, I get some pixels lit on the display.just got lucky with spurious signals. These displays were apparently custom made for NCR, and I can find no programming information for the module as a whole, except for what is at this site.īetween that very high-level information and the datasheet on the C1162A, I've written some code for my Arduino (ATmega168), but I cannot get the the display to work. They are available very cheaply at Prime Electronics. It is a nice 20x2 display module with 2x Oki MSC1162A chips and one MSC1164 chip. I have a Futaba NA202MD13AA vacuum fluorescent display.