You are not logged in.
Hi,
Am I right to assume that nanodlp will only work with "arduino compatible" i2c 2x16 lcd displays based on the PCF8574 8 bit i/o expander for 12c bus?
And that other displays will not work?
Thanks
Offline
neurofun,
I have tested it only on 16x2 display as you said. But it probably works on 20x4 too. Also fixed on 5x8 dots.
Offline
Ok, thanks for the fast reply.
I tried to get the adafruit raspberry pi i2c lcd to work with nanodlp but since it uses the mcp23017 16 bit io expander it didn't work.
I'll just order another display.
Offline
Does someone have a tip how to get the I2C Display running. I alway get the message "Could not access LCD write /dev/i2c-1: input/output error". chmod 777 on the file does not make any changes.
I do using this "http://www.sainsmart.com/new-sainsmart- … ga-r3.html" LCD witch is running on Port 27.
With the Python test Prog at commandline i'll get the correct display on the LCD.
Offline
Could you post your /boot/config.txt and /etc/modprobe.d/raspi-blacklist.conf files?
Which python test program is working correctly?
Offline
The Test Python Prog i use is: "wget https://bitbucket.org/MattHawkinsUK/rpispy-misc/raw/master/python/lcd_i2c.py"
The only enabled Setting in config.txt are:
dtparam=audio=on
start_x=1
gpu_mem=128
dtparam=i2c_arm=on
disable_camera_led=1
hdmi_pixel_encoding=2
dtparam=i2c1=on
and the Blacklist is empty
Offline
Initialization bytes are quite different. Usually majority of these matrix LCDs are based on Hitachi HD44780 controller.
On their website it says address is 0x32 and not 0x27
http://www.sainsmart.com/new-sainsmart- … ga-r3.html
Again I have downloaded zip file on the website and init code is same as ours as it written for Hitachi HD44780.
Offline
Adress 32 does also not work and the command "i2cdetect -y 1" gives the following result:
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- 27 -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
Offline
Do the sample on their website worked on your unit? http://www.selloutsoon.com/albums/docum … IC1602.zip
Do you know if it use HD44780 or its a different controller? I am not familiar with these controllers but maybe different initialization codes are acceptable in different conditions.
nanoDLP returned error just after initialization code, so most probably it is due to rejection of initialization code.
Offline
it is a "pcf8574t" i2c controller
Offline
It is i2c controller. See if you could find LCD's controller.
Offline
The only printed Label i cold find is 1602A on the backside.
Teh display looks exaclty like on this one "http://www.aliexpress.com/item/1602A-LC … 52414.html" diferent is just the i2c module.
Offline
Adress 32 does also not work and the command "i2cdetect -y 1" gives the following result:
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- 27 -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
your lcd adress = 27 hexadecimal
in nanodlp you enter the adress in decimal which equates to 39
Offline
Yes, with the Dec. Address of 39 it works.
Offline
Sorry guys is the first time for me with nanodlp.
I've bought a LCD 16x2 but i have not idea how i can connect it at the rasp. What are the pin of the GPIO(there is a wiring diagram for the connection?) ? tanks a lot
Offline
You should use SDA (Physical 3) and SCL (Physical 5) pins.
Offline
Is there a way to specify which I2C bus number is used? In Armbian, on the Orange Pi PC, I2C bus numbers appear to be packed, and the highest numbered I2C bus seems to be unavailable. I've tested that my 16x2 LCD works fine on /dev/i2c-0 using i2cset.
Offline
Please, share bus number and i2c address.
I guess by packed number you mean hexadecimal which must be converted to decimal before entering into nanodlp.
Offline
Sorry to be unclear. The Orange Pi PC under Armbian has /dev/i2c-0 enabled, which goes to some unidentified device with address 0x65. When I enable the overlay for i2c0, the I2C bus on physical pins 5 and 7 shows up as /dev/i2c-0 and the strange bus becomes /dev/i2c-1. This strange bus shows up as highest bus used + 1 rather than its actual hardware unit number. So the algorithm of just using the highest bus number doesn't work for this machine.
Offline
More info:
With i2c0 enabled in the boot config, my I2C LCD board shows up:
root@print0r:/# i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- 27 -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
root@print0r:/# i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- UU -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- -- Without i2c0 enabled in the boot config, no LCD:
root@print0r:/# i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- UU -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
root@print0r:/# i2cdetect -y 1
Error: Could not open file `/dev/i2c-1' or `/dev/i2c/1': No such file or directoryOffline
Have you tried set i2c address 39
Offline
Have you tried set i2c address 39
Yes, that's the default. I've also tried address 38 (0x26), but no change. nanoDLP is using the wrong bus, apparently skipping i2c0 entirely:
crw-rw---- 1 root i2c 89, 0 Sep 13 12:55 /dev/i2c-0 # the bus where the PCF8574 LCD is, works via i2cset
crw-rw---- 1 root i2c 89, 1 Sep 13 12:55 /dev/i2c-1 # a phantom bus, not pinned out on this board, doesn't respond
{"Layer":"0","module":"Gcode","level":"Error","msg":"Could not access LCD write /dev/i2c-1: no such device or address"}Can the I2C bus be made a configuration option? Build 1609.
Offline
Sure it is possible, but we will have yet another field on the setup page.
Offline
Sure it is possible, but we will have yet another field on the setup page.
Would it be better to just try them all in turn, and stick with the first one where a device responds to the address given?
Offline
Checkout the beta version.
Offline