msp430 lcd display for sale

LCDs are very easy to get, adafruit has a nice one, as does sparkfun. If you are going to buy one it would be useful consider these two characteristics:

The MSP430 (like most MCUs today) runs on 3.3-3.5V. If you get an LCD module that takes 5V then be prepared to either have separate voltage sources for your MCU and LCM or have the ability to step up/down your voltage source. Here"s a link that has some ideas on how to do this. Texas Iinstruments has a document that describes 1.5V to 5V boost conversion mechanisms. For my own setup I just used approx 4.3V voltage source (from 3 AA batteries) to power the LCM and used a simple diode on the same source to achieve a forward drop to source the MSP430. This is ok for prototyping but hardly a long term solution.

Some LCD modules also support a serial interface. This uses much fewer pins and is therefore great to use with MCUs that have a low pin count. However the interfacing for that is quite different than the and will not be discussed here.

This is all the code for the MSP430 LCD driver. A simple flow is demonstrated in the main() function. This code should be copy-paste runnable on the value line part plugged into the shipping launchpad. If things aren"t working it might be because your LCD module is slower.  Try extending the __delay_cycles, first in the Initialization routine. If that doesn"t fix it extend the delay time in the pulse module as well.

In this video instructable, I show how to hook a cheap 16X2 LCD display up to an Arduino, then a TI Launchpad MSP430 running Energia, then a breadboarded MSP430.

These displays are cheap - I got mine for $2.26 shipped on eBay.  They only require 6 i/o pins from your microcontroller, and are compatible with EVERYTHING since they use the HD44780 controller.

I am using a 16x2 LCD with an MSP430 and am unable to figure out how to print a value from my AtoD. My LCD is using the ST7066U driver, and the setup code for my LCD is this:

In my main code, I read an AtoD value, but I am not too sure how to display it. The AtoD works fine, I can use debug mode in Crossworks and see the AtoD value is what I am expecting. I can display text on the LCD with something like this:

I am a complete novice at this, and the code for setting up the LCD was taken from HERE and edited slightly to fit my MSP and setup. Essentially, I just want to do something like

I get an error saying too many arguments to lcd_print. I assume this means in my setup, I need to change something to the way lcd_print works, but not sure how to do this. Can someone please let me know how to edit this so I can do something along the lines of

Port 2 can be used to provide the six data signals required to control the LCD.   Note how the LCD is connected to the breadboard and that wires can be connected to the pins as shown in figure 1. There is a four bit interface for the data (D4-D7), a RS (select command versus text) and an enable (E).   Figure 2 shows the other required connections as well. The datasheet for the LCD can be found here GDM1602K-Extended.pdf.  The commands are correct but the electrical specifications may vary between LCDs so make sure you have the correct datasheet for your specific LCD (3.3V versus 5.0V for instance)

Specific to this lab and the corresponding lcd_lib files we will setup the LCD to use all six available pins in Port 2 to write directly to the 16 x 2 LCD in 4-bit operation using only the most significant data nibble.

This is a library to interface Nokia 6610 (6100, 6610, 7210, 7250 and 5100) color LCD displays with MSP430s. The code is specific to the displays containing Philips PCF8833 controllers (see below for details).

Nokia 6610 (6100, 6610, 7210, 7250 and 5100) LCDs (and knock-offs) are 132x132 displays supporting 4096 colors, and for whatever reason, are easily available and very inexpensive.

There are many projects available around the net for interfacing these displays with various microcontrollers. But there were none for interfacing them with MSP430s (which happen to be my favourite due to the MSP430 Launchpads). This library addresses that.

These displays do have quirks of their own, but those are fairly minor compared to the advantages. One of the quirks is that these aren"t made for hobbyists (obviously). Therefore, the connector is small, and delicate. While there are breakout boards available that make it easier to connect these, you still have to be careful not to put too much pressure on the connectors.

The other quirk is that these displays are driven by one of the two controllers: Philips PCF8833 or Epson S1D15G00. And it"s not easy to tell which controller is in the display you"ve bought. There are minor differences in the controllers that can cause some confusion.

The MIDIS LCD datasheet is available here. The code written in C++ makes use of the Energia Wire library that has been ported from Arduino Wire for the I2C interface.

The I2C interface is a serial bus that allows for synchronous transmission of data in a serial fashion. It requires two lines one for the clock and one for the data. A ground connection is also required. The SDA and SCL lines require external pull-up resistors, typically 4-10k. These are required as the devices attached to the bus only pull the data line low to indicate a zero and a one is indicated by letting the line float (open drain). The MSP430G2553 uses pins P1.7 for the Serial Data (SDA) and P1.6 for the Serial Clock (SCL).

To install this library within Energia download and extract the LCD library folder into your libraries sub-directory of your Energia sketchbook directory.