Assuming the library example images display OK, then I suspect the encoding format is the problem.

It looks like the MCU size is 8x8 whereas the examples I have tested are 16x16.

It looks like you have used Photoshop to encode the jpeg, perhaps try a different image edit program and try that.

I do not have access to my Arduino stuff at the moment so cannot test. If there is a bug in the 8x8 decoding then I will see if I can track it down. The other possibility is that the SPI clock frequency is too high for the display. Try 27MHz if you think that may be the case.

I checked the JPEGDecoder library with you files and get the same results on a NodeMCU and a Mega with a different graphics library so the problem must be in the JPEGDecoder library somewhere. The images are encoded as 8x8 MCU blocks and it looks like the decoder does not like this. I used IrfanView to re-saved one of the files and this turned it into a 16x16 MCU size and this renders fine. It also renders faster. See attached.

I have not managed to track down this bug so the only work-around is to use jpeg files encoded in 16x16 MCU blocks. I will post this as an issue on Github.

Hello Bodmer,I got one of the raspberry pi displays working with the demo code but am having a problem getting the Plane spotter to work, have you gotten it to work on one of these displays? I is using the ILI9486 #5 driver.Regards,Stan

I happen to have one of those Kedei screens (two actually) so if I can be to any help that would be awesome. One works on my Pi, I want to use the other for Planespotter and Weatherstation.

I read that it uses 3 pin SPI ( Someone mentioned that here) and afaik they all have the same markings but only the signals and display controllers change with almost every iteration. I know that there are a few guys that already connected some version (V5,4,3,2,1 if I am not mistaken) of these tft's to an Arduino and found out by scope what the timings are. That's a start I guess.

Anyway, what do we not know to make it work?

3 pins SPI

Markings

On the back there are 2 connectors. One has 4 pins, 2 for 5 Vdc and 2 NC.

The other one has 8 pins:L_CS T_CS IRQ GNDGND CLK MISO MOSI

This guy already interfaced (v5) with the ESp8266 and worked out the init for that version.

Mine is V6.3 so I think we need the Init for it (Maybe use working version on Raspberry for testing?) or I have to find out what controller is on the display and hope someone wrote the init part already. Right?

I want to merge Planespotter and the Weather Station so I can switch between them.

I guess for a start is that I merge settings and libraries. Then write some code so that both "programs" are simultaneous running (in the background I would say).Then write some code to switch the display to show PS or WS. Could be by using on-screen button, could be swiping.

Do you think that the esp8266 is capable of executing that or would it be too slow?

Full pinout of the Waveshare/knockof. If someone wants to make a Waveshare<>ESP pinout that would be awesome. I had to make a lot of guesses today and it's not working (Sometimes with some ocassional flickering and gibberish on the serial). So if you want a free beer (or two) please tell me how to wire this puppy up.

Hello Bodmer,I got one of the raspberry pi displays working with the demo code but am having a problem getting the Plane spotter to work, have you gotten it to work on one of these displays? I is using the ILI9486 #5 driver.Regards,Stan

Try the attached version. It is not perfect (some text position issues) but it should work OK. It is for a 480x320 screen.

Full pinout of the Waveshare/knockof. If someone wants to make a Waveshare<>ESP pinout that would be awesome. I had to make a lot of guesses today and it's not working (Sometimes with some ocassional flickering and gibberish on the serial). So if you want a free beer (or two) please tell me how to wire this puppy up.

The image attached appears to be corrupted so is not much use.

With reference to the image in post #103 and assuming a ESP8266 NodeMCU is used: