rhubarbdog / microbit-lcd-driver

An i2c driver for 16x2 .. 40x4 LCD displays on the microbit

microbit-LCD-driver

An i2c driver for 16x2 .. 40x4 LCD displays on the microbit

The module microbit_i2c_lcd.py uses the module time. That requires a modern firmware, version 1.9.2 works. If you only have vanilla firmware (version 1.7.9) available you can swap all time.sleep_ms for microbit's sleep and swap time.sleep_us for microbits sleep of 1 milli second. This will degrade the writing to speed.

These LCD displays run on 5v not the 3v you can get from the microbit edge connector. You need a separate power suply, remember you need to connect all grounds together. I2C protocol requires that the data line (SDA) and the clock (SCL) line have pull up resistors in a range of 3K-10K. I have pulled them to the microbit's 3v and everything works.

My breakout board doesn't have pins 19 and 20 which are the microbit's i2c pins. So both lcd_example.py and lcd_rom_type.py use function i2c.init. This requires a modern firmware, version 1.9.2 works.

lcd_rom_type.py is used to determine if you have a japanese or european character set.

microbit-lcd-driver's Issues

problem with address in line 64, self.__bus.write(self.__addr,buf) of microbit_i2c_lcd.py

Hello! Our class for interaction prototyping uses this code for lcd i2c communication with it.

I try to use this code with multiple lcds.

But there`s some error occurs when I just adjust the ADDRESS constant

when I try to alter the ADDRESS constant with any number,

the OSerror, I2Cwrite error - 1010 occurs at

line 64 of microbit_i2c_lcd.py, which is

def write_cmd(self, cmd):
buf=bytearray(1)
buf[0]=cmd
self.__bus.write(self.__addr,buf) ##<<here
time.sleep_us(100)

How can i deal with this?