I have a Qwiic Keypad (COM-15290 ) and and LCD-14073 hooked up to a Arduino Due via I2C. The LCD works fine, but I can not connect to the Keypad. Customer support sent me a new keypad, but I can not connect to it either. Additionally, the I2CScanner example program detects the LCD address, but does not detect the Keypad address. I tried with and without the keypad pullup resistors. I see someone posted here a week ago with the same issue… is this just a bad batch of keypads?
Can you try using an example sketch from the hookup guide using the default I2C address 0x4B?
Hi,
Yes, the I2C Scanner is example #4 from the hookup guide. I did try example #1 as well, but it did not work either.
Can you provide pictures of your setup and connections to the Keypad board?
See below.
So I can verify if the Qwiic Keypad is defective can you try the following (if possible):
Try running an example sketch with a Qwiic microcontroller board such as the RedBoard Qwiic.
Move the I2C pins the the pins closest to the USB plug-ins above the digital pins.
Does the power LED illuminate when powered on the Qwiic Keypad?
Can you probe with an oscilloscope the SDA/SCL lines on the Qwiic Keypad to see if signals are being transmitted?
No problem
-
I do not have a Qwiic microcontroller.
-
I moved the I2C to the pins SCL1 and SDA1, which resulted in the example finding no devices (not even the LCD). So I modified the example to have the line: extern TwoWire Wire1; And changed all references of Wire to be Wire1. Running the example again, the LCD address is found, but the Keypad is not. I tried with and without the pullups on the keypad.
-
Yes, the power led is lit red
-
I do see activity on the SDA and SCL lines coming from the Due with a scope. If I disconnect the SDA/SCL lines from the Due and probe the SDA/SCL from the Keypad (with the Keypad still powered) I only see 3.3V on either line. Pressing buttons on the Keypad has no effect.
Do you have access to an Arduino Uno?
I2C on the Arduino Due is [notoriously buggy and that might be a source for your problem.](arduino due i2c problem - Google Search)
I only have the Arduino Due. The LCD seems to work fine on the I2C bus… is there any reason the Keypad specifically would not work with the Due? Unfortunately, I do not have any other I2C devices to try out.
Like I said, I2C is buggy on the Due, it’s always been.
Some code works, some doesn’t. Some I2C devices work while others don’t. Not really sure why this is but I’ve had the same thing happen. Never tried the qwiic keypad with a Due, but it might be one of those devices that don’t work.
See if you can borrow or buy an Uno, those are the gold standard for testing things like this. If it’s not working on an Uno, it’s probably a bad keypad but the only way to know for sure is to try it out with an Uno.
I ordered two COM-15290 keypads through Digi-Key. Both are nonfunctional. The red LED illuminates. I am using the DEV-15123 dev board. No response when using i2c_scanner using either keypad. I also hooked up a protocol analyzer and nothing but NACK’s on all I2C addresses. Other I2C devices work fine. It’s almost like the ATtiny85 was not flashed at the factory. I have submitted an RMA for both keypads to SparkFun but I would like them to look into it because I think there is a good chance they have a bad batch.
TS-Brandon:
So I can verify if the Qwiic Keypad is defective can you try the following (if possible):Try running an example sketch with a Qwiic microcontroller board such as the RedBoard Qwiic.
Move the I2C pins the the pins closest to the USB plug-ins above the digital pins.
Does the power LED illuminate when powered on the Qwiic Keypad?
Can you probe with an oscilloscope the SDA/SCL lines on the Qwiic Keypad to see if signals are being transmitted?
If you purchased through DigiKey, then you’ll have to ask them for an RMA instead of us. I’ve notified internal teams of your issue. We will investigate further when possible. However, I would suggest that you ask DigiKey for replacements in the meantime.