[werk_ag]

Hi russellb

I2C_scanner found a device at 0x50 so  I set that as display address.

0x50 is the address of the onboard EEPROM, the TFT display is an SPI device not I2C, so it can't be detected by the I2C_scanner utility.
However, this also shows that the BME280 (which is an I2C device) isn't been detected. This can be one of the causes of the device not start properly.
Check the connections of the BME280 sensor, and try until it will be detected by the I2C_scanner utility.

I had already checked voltages, and 3.3 v seems OK.

Good, check the 5V rail, and power supply voltage too. Make sure is between 7.5V and 9V.
Do you see any signs of the regulators running very hot? They should run only barely hot, not very hot.

By the pics I also noted that the RTC module is missing. The system may not work properly without it.

[russellb]

Hi russellb

I2C_scanner found a device at 0x50 so  I set that as display address.

0x50 is the address of the onboard EEPROM, the TFT display is an SPI device not I2C, so it can't be detected by the I2C_scanner utility.
However, this also shows that the BME280 (which is an I2C device) isn't been detected. This can be one of the causes of the device not start properly.
Check the connections of the BME280 sensor, and try until it will be detected by the I2C_scanner utility.

I had already checked voltages, and 3.3 v seems OK.

Good, check the 5V rail, and power supply voltage too. Make sure is between 7.5V and 9V.
Do you see any signs of the regulators running very hot? They should run only barely hot, not very hot.

By the pics I also noted that the RTC module is missing. The system may not work properly without it.

Thanks for your patience with this old man.

I found a dry solder joint on the BME280 which I'm sure wasn't helping anything.
I've installed the RTC and set the LCD address back to 0x27 (After all I was just doing there what the program code told me to do )

Rechecked voltages and they seem OK (9.1, 5.02 and 3.22 v)

I2Scanner now gives:
Scanning...
I2C device found at address 0x50  !
I2C device found at address 0x68  !
I2C device found at address 0x76  !
done

Debugging output from the board shows:

ESP8266 FW Version: AT+GMR

AT version:1.2.0.0(Jul  1 2016 20:04:45)
SDK version:1.5.4.1(39cb9a32)
Ai-Thinker Technology Co. Ltd.
Dec  2 2016 14:21:16
OK
Mode station OK
Multiple mux OK
Join AP failure
WiFi connection is OFF

I had noticed the 3.3 v regulator getting hot, that is now behaving normally.

However the display continues to behave the same.

I have //   Internet Settings
// --------------------------------------------------------------------------------------
#define ENABLE_INTERNET     1                        // 1= Enable Internet connection, 0= Disable


and Wi-Fi credentials are in and valid, but still not connecting to the router

[werk_ag]

Hi,

Seems there are progresses:

Code:

I2Scanner now gives:
Scanning...
I2C device found at address 0x50  !
I2C device found at address 0x68  !
I2C device found at address 0x76  !
done

I2C devices are now detected correctly.

Code:

ESP8266 FW Version: AT+GMR

AT version:1.2.0.0(Jul  1 2016 20:04:45)
SDK version:1.5.4.1(39cb9a32)
Ai-Thinker Technology Co. Ltd.
Dec  2 2016 14:21:16
OK
Mode station OK
Multiple mux OK
Join AP failure
WiFi connection is OFF

I had noticed the 3.3 v regulator getting hot, that is now behaving normally.

However the display continues to behave the same.

I have //   Internet Settings
// --------------------------------------------------------------------------------------
#define ENABLE_INTERNET     1                        // 1= Enable Internet connection, 0= Disable


and Wi-Fi credentials are in and valid, but still not connecting to the router

From this I can see that there is communication between the Meduino and the WiFi module, so despite it is not connecting to your WiFi network, seems that the WiFi module is working.
Check if your are not using any special chars (char above ASCII 127) in both WIFI_SSID and WIFI_PASSWORD (and in your router too, obviously).
(There are also reports that the ESP8266 modules may have problems to connect with some older router - Foneras is one of the cases).


Regarding the TFT display, its not easy for me try to guess what is happening:
Firstly the model of your TFT display is different (PCB is quite different) from the recommended model, however, at least, the display should work, but I can't assure that. Considering that you have two TFT displays, and both are not working, and supposing that those displays are compatible, or there is a problem with the connections with the TFT, or in the worst case, the logic level converter chip is damaged (hope not). My best guess is for double check the connections to the TFT display.
Leave SDO(MISO) unconnected, this signal line is not used.

[russellb]

Hi,

Seems there are progresses:

Code:

I2Scanner now gives:
Scanning...
I2C device found at address 0x50  !
I2C device found at address 0x68  !
I2C device found at address 0x76  !
done

I2C devices are now detected correctly.

Code:

ESP8266 FW Version: AT+GMR

AT version:1.2.0.0(Jul  1 2016 20:04:45)
SDK version:1.5.4.1(39cb9a32)
Ai-Thinker Technology Co. Ltd.
Dec  2 2016 14:21:16
OK
Mode station OK
Multiple mux OK
Join AP failure
WiFi connection is OFF

I had noticed the 3.3 v regulator getting hot, that is now behaving normally.

However the display continues to behave the same.

I have //   Internet Settings
// --------------------------------------------------------------------------------------
#define ENABLE_INTERNET     1                        // 1= Enable Internet connection, 0= Disable


and Wi-Fi credentials are in and valid, but still not connecting to the router

From this I can see that there is communication between the Meduino and the WiFi module, so despite it is not connecting to your WiFi network, seems that the WiFi module is working.
Check if your are not using any special chars (char above ASCII 127) in both WIFI_SSID and WIFI_PASSWORD (and in your router too, obviously).
(There are also reports that the ESP8266 modules may have problems to connect with some older router - Foneras is one of the cases).


Regarding the TFT display, its not easy for me try to guess what is happening:
Firstly the model of your TFT display is different (PCB is quite different) from the recommended model, however, at least, the display should work, but I can't assure that. Considering that you have two TFT displays, and both are not working, and supposing that those displays are compatible, or there is a problem with the connections with the TFT, or in the worst case, the logic level converter chip is damaged (hope not). My best guess is for double check the connections to the TFT display.
Leave SDO(MISO) unconnected, this signal line is not used.

Thanks, I've checked the wiring (again) and can't find any errors.
so I've bitten the bullet and ordered a new display from one of the recommended suppliers.
Meanwhile I'll try climbing the steep learning curve of Arduino interfacing, and see if I can achieve anything with the ones I have.
Hopefully may have an update in a few weeks.

[engolling]

Thanks, I've checked the wiring (again) and can't find any errors.

Hello russellb,

I pretty sure that I have the same type of display running here perfectly (despite of the additional touch rotation) and I had similar problems at the beginning due to a wrong connection.
Could you please provide the Pin connection between the RX pin header and the display pin header. 
Eg. SCK <-> SCK
Then I would crosscheck with my connection.

Regards,
engolling

[russellb]

Thanks, I've checked the wiring (again) and can't find any errors.

Hello russellb,

I pretty sure that I have the same type of display running here perfectly (despite of the additional touch rotation) and I had similar problems at the beginning due to a wrong connection.
Could you please provide the Pin connection between the RX pin header and the display pin header. 
Eg. SCK <-> SCK
Then I would crosscheck with my connection.

Regards,
engolling

Thanks engolling,

I've checked at least 3 times with http://www.meteocercal.info/forum/Thread...77#pid5677, including checking end-to-end resistance, and all correspond to that schema.

I have a "wireless display board" to use the second screen on, so I'm just building that up, and will see if that behaves any differently.
I've also been exploring the arduino forums to see if I can find any more data on the board.
I can see it has an HR2046 chip as U2.

At least in my exploring I found a test sketch for the BME280 which appears to be giving realistic results.

Regards
Russell

[werk_ag]

I have a "wireless display board" to use the second screen on, so I'm just building that up, and will see if that behaves any differently.

That's a good idea to test if the display is working, however even if it will work, the touch panel will be rotated. The software for the Nano based Wireless Display units wasn't adapted to also support those "yellow pins" displays.

[russellb]

I have a "wireless display board" to use the second screen on, so I'm just building that up, and will see if that behaves any differently.

That's a good idea to test if the display is working, however even if it will work, the touch panel will be rotated. The software for the Nano based Wireless Display units wasn't adapted to also support those "yellow pins" displays.

Confession time:

I found in sorting things out that the "push button switch" I was using, and which has been in my junk box for 30+ years, is a "normally closed" one, not an NO as I thought.
That certainly hasn't helped.
I tried the latest software, and can now get it to connect to the wi-fi network, and set the RTC which is an advance.
Display is much the same, I notice it does "blink" when I press the NO button.

I have assembled the WD board, seems to be behaving much the same, with a white display, though it has a constant "flicker" as though it is refreshing.
The display seems to respond to touch, which the one on the Rx board doesn't.
Then when I tried to run it with the Rx board also running, I have (I think) a USB issue, and can't connect to monitor the serial output.
 
Pending the arrival of replacement displays, any ideas on debugging?
Assuming I can sort out the communication problem.

Regards,

Russell

[russellb]

Well, the new displays arrived today, and seem to have just muddied the waters more.
I think I have solved the communication problems, which were due to my ATMega processor on the WD board needing the "Old Bootloader "  so I have at least been able to upload a sketch to the WD.

On Rx board:
Display is generally white, but can be turned off by pressing the push button, and then will turn on again (blank white) if I touch the display.
Wi-Fi is working and I can ping the board on the network, but despite the webserver being nominally activated, nothing is served

On WD board:
Display flashes white on booting, then goes dark, but there is a little background activity visible.
No obvious response to the push button or touch.

Any suggestions?

Regards

Russell

[engolling]

Hi Russell,

I still think there is something going wrong with your SPI communication and in the End with your wiring, although you have checked it ten times, because I had equal problems at the beginning wiring "straight through".
Nevertheless you could get a simple LCD and check is that is working to ensure that the rest of the software is doing fine.

Regards,
engolling