Waveshare LCD (A) V3 issue

[G4HTZ]

dont know if this helps dave ....sorry not good with computors

Update Window
x=2034 y=278
x=1997 y=213
x=1985 y=157
x=1978 y=147
x=2160 y=534
Button Event 14
************** Set FEC = 7
x=2132 y=467
Button Event 14
************** Set FEC = 7
x=2015 y=216
x=2106 y=396
Button Event 14
************** Set FEC = 7
x=2430 y=1129
x=2025 y=232

[G8GKQ]

Thanks Steve

That seems to suggest that you were successfully pressing the FEC 7/8 button. What happens elsewhere on the screen?

Dave

[G4HTZ]

pressing other buttons gives no responce on touch screen or registers on putty

[G8GKQ]

Hi Steve

That suggests that the touch sensor for the rest of the screen area is dead. Sorry.

Dave

[G4HTZ]

Ok thanks Dave
Bad luck getting 2 screens the same I guess ...
Thanks for trying to help
Cheers
Steve

[G4WIM]

Hi guys,

having a bit of 'drama' with my 3.5" LCD A V3 display.

Got the code built and running nicely except for the screen being back lit but totally blank.

Touch screen works fine ( I can see the responses in putty), but zilch displayed on the screen so I'm guessing where to touch the screen.

I've checked the settings in the config and figure it's either a duff screen or driver problem ?

I see in the overlays folder what looks to be the correct file for the screen - but maybe I'm missing something else ?

Any ideas ?

Maybe I should build another project for the rpi and lcd and see what happens ?

edit - just used the image which came on the CD with the display and got the same result, a blank screen so I'm thinking it could be faulty ?

73 Tim

[G8GKQ]

Hi Tim

Does the screen go from white to black during the boot process?

Dave

[G4WIM]

Hi Dave,

no the display stays white all the time although it does change brightness very slightly.

Going to dig a bit deeper to see why I can't get the waveshare image to work, but any help gratefully received.

One small unrelated point point - when I tried to access the rpi at its first boot up, ssh connection was refused. This was easily fixed by adding an empty file called ssh in the boot directory as per the release notes on the os.

edit - so just for kicks I plugged in an HDMI monitor to see what happens during boot.

Everything seems ok, until these last 3 lines

Starting te;; Plymouth to write out runtime data
Reached target remote file system
Starting trigger flushing of journal to persistent storage


Then nothing else happens on the dhmi screen - not sure if this is normal ?

Curiously when I do the same exercise with the Waveshare image, everything appears ok on the HDMI monitor till it gets to

Mounting Fuse Control File System,

Then nothing else.

I'm using a Toshiba 16GB toshiba Exceria http://www.toshiba.co.uk/flash-memory/m ... 02r0160ea/ and I'm wondering if it might be memory related - although I've had no problems in the past.

73 Tim

[G8GKQ]

Hi Tim

The fact that the screen does not go dark during the boot process sounds like it is not reacting properly when its driver is loaded (assuming its driver is being loaded).

Yes - it's easy to miss the need for the ssh file, although it is in set out in detail in bullet 3 of the installation instructions here https://github.com/BritishAmateurTelevi ... /README.md.

I have never booted Portsdown with an HDMI display, so can't help you with analysing that behaviour.

We have had problems in the past with Samsung SD Cards - their timing is more critical and some RPis appear to be incompatible with them. Not sure about Toshiba cards. This is one of the reasons that we have been stocking the SANDisk Cards in the shop because we know that they work well.

Dave

[G4WIM]

Hi Dave,

tried various memory cards / makes / sizes with the same result, so looking like a faulty display at this point unless I stumble on a solution.

73 Tim