[Solved] Conflict between RFM69 and TFT display libraries

[MechEngineer]

Hi guys,

So I have a sketch that utilizes both the RFM69 and TFT libraries and there seems to be a conflict between the two. Each half of the sketch works flawlessly without the other, i.e. I comment out the radio.initialize() or TFTdisplay.begin() line for either the TFT or RFM69. However, when together neither works. The moteino fails to receive data through the radio commands and the TFT screen remains black or displays static white noise.

I have already check to make sure there are no pin conflicts. Also the order of initialization does not mater either, I've tried both ways with the same result. One puzzling development I discovered though is if I disconnect the MISO pin (pin 12) to the TFT display then then both the display and RFM69 initialize and function properly, but the screen has a noticeable flicker to it which I am wondering if it is a result from disconnecting MISO.

Any suggestions?

Thanks,

   

[Felix]

Hi,
How does the TFT library do SPI transactions?
What pin do you use for the CS of the TFT?

[MechEngineer]

Here's the pin layout I'm using with the Moteino. There are no other pins being used other than what's needed for the display.

+5V:    +5V
MISO:    pin 12
SCK:    pin 13
MOSI:    pin 11
LCD CS:    pin 10
SD CS:    pin 4
D/C:    pin 9
RESET:    pin 8
BL:    +5V
GND:    GND

The TFT library does SPI through the default arduino SPI library

[Felix]

Boom. Don't use D10, it's used by the radio
Good to check the diagram sometimes: http://lowpowerlab.com/moteino/#pinout

[MechEngineer]

Boom. Don't use D10, it's used by the radio
Good to check the diagram sometimes: http://lowpowerlab.com/moteino/#pinout

Dang it, I thought I looked at that earlier. Well simple problem, simple fix. Thanks a lot!

[Felix]

Glad it worked out