Good morning,

I'm  tring to test the ds1307 I2c in my sketch. 

My hardware configuration is: Arduino Mega 2560, ds1307 I2C and the 2.4'' lcd tft 320x240 touch with 2M flash. The touch lcd is in SPI mode and the ds1307 in I2C mode.

 I used the Touch_Flash_for_Checkbox_and_Radio_buttons.ino to do my test with the touch and the real time clock.

I added the code to let's start the rtc, and in the loop() function I add my function to print the time on lcd.

When I turn on the Arduino the lcd show all the radio button and the checkbox and also the time, but the problem is that the time is freezed to the start time.

To let's update the showed time on lcd I must touch every second the lcd otherwise the printed time stay there, freezed!!

I need some help to fix this problem...

"that I think is the lcd tuoch take the priority on refresh screen" 

Thanks....

 If you using SPI mode, you must add a pull down resistor (4.7K ~ 20K) between SDO (pin #6) and GND (pin #5) on our display module, more details, please read PAGE #17 in our Manual.

Also, the display module will not accept any new command if you waiting for any touch event, so, if you want access the touch event and display context on the screen at same time, you must check the touch screen pressed using the PENIRQ signal on the moudle, if the PENIRQ is pulled to low, means the touch screen pressed, then you can send command to read the touched X,Y.

I done all that you suggest to me... now the time goes it is always update, but when i touch the lcd the time stops, and this is ok, but when I release the display nothing happens....

sometimes yes, but after a few seconds that I keep pushed the display...

there is something that I must do to resolve??? Now the touch is like that there wasn't!!!

 if you are using I2C or SPI mode, you must read 2 integer data (4 bytes) from display module after "read touch screen" command(s) issued, then send other commands, the module will waiting from you to read these data forever.

If you only send "read touch screen" command, but not reading enough data from moudle, then send other commands, the moudle will not accept any new commands.

Also, you can't read more data then expected, if you want to read 5th byte of data after "read touch screen", the I2C bus will be hold, and you must reset the moudle.

But, if you using UART module, the module will send out these data right away, it don't care whatever your controller is ready to receive these data or not.

hello every body , hello "service"

i was reading this post and find that "service " said  : But, if you using UART module, the module will send out these data right away, it don't care whatever your controller is ready to receive these data or not.

i am using an usart link at 9600bds between my hardware and digole module display  and i can't  obtain a stable reading just only eratics values ,same when no depress touch acted

if i have understood,i must catch "on the flying" characters sent ,may be possible but not secure, so, is it possible to use digole's  interrupt pin to synchronize reception ? or any another advice

all advices are wellcome

thanks by advance

jyb

 Yes, you can use "PENIRQ" pin, this pin will pull to low when touch panel pressed, and this is hardware signal.

If you want to read touch screen, you better use "read touch click" function(RPNXYC) or "read touch pressed" (RPNXYP), if you use "read touch instant return" (RPNXYI), the data you got may be wild, because the input of touch screen is floating.