RoPieee LCD Beta stuff - tell it like it is

[wizardofoz]

Lets keep the LCD stuff in a thread of its own

[spockfish]

He guys, thanks to @RBM we’ve got our own space

Ok. Back to the screen part. I’ve got stuff scrolling. Looks great I must say.
But now the bad part. Doing scrolling stuff on the screen requires hardware acceleration (for the non-geeks: basically a way that drawing to the screen is being taken care of in hardware in stead of the software) and that part is extremely buggy and in progress on the Raspberry Pi.

I can’t get it to work reliably, so for now I’m afraid this is a no-go. Which is extremely frustrating, because the scrolling looks so good and it took me a while to get it actually working

Anyways, let’s stop with the whining. I’ll follow progress on this area closely, and it’s already in the software, but it’s just disabled. It also means that we really need the ‘multiple screens’ option, because right now some of you (including me actually) are not that happy with the little space for texts etc.

That’s it for now, keep you guys posted.

[Sean2016]

Great plan Harry.

[wizardofoz]

Ok my PI just timed rebooted and the display is all unknown and blank art. Granted thee is no playlist on roon controller at this time. So I sent feedback.

[Sean2016]

I did notice that your last screenshot had radio turned off.

If you actually pause a song before you go to bed, have a look tomorrow what’s on the screen after the scheduled daily reboot. I won’t be surprised if the last song you paused still shows on the touchscreen in the morning.

When you have this “unknown” showing in the morning, if you start playing something in the morning in Roon, does Touchscreen come alive again? Or only a manual ‘reboot’ or cold boot brings it alive?

[wizardofoz]

All is still not well…I went into roon and hit back in the top area to last nights playing album…hit play…though that’s louder than I remember…it was still set at 24…I thought this might be a bad sign so went to the volume adjustment and soon as I touched it it jumped to max vol on the digiamp+ and I swiftly mini used it to 0 where it when quiet, but moving it up again even to 5 resulted in max vol on the speakers.

@spockfish
I sent a feedback both in the unknown state and again in the 0 volume state and will now shutdown and power up again

[wizardofoz]

Some more fun and games…My 2 extra LCD’s arrived…and cases… very nice case from RS Online…post a pic later

BUT now with 2 cores and 2 LCD’s its impossible to tell which is which…so not sure if the Ropieee Hostname can be identified in the extension details…that would be a huge help

[wizardofoz]

This is the RS Online case http://sg.rs-online.com/web/p/development-board-enclosures/9064665/ also comes in White and Clear …I got a black and a clear…but hard to get a HAT in there - can mount on a wall tho - handy here is a UK link bundle http://uk.rs-online.com/web/p/graphics-display-development-kits/1228914/?origin=PSF_431023|alt

[joel]

That’s a nice bundle for £60. The Pi is increasingly a RAAT-enabled Squeezebox Touch on steroids.

[wizardofoz]

Boot time with a display for those that are worried its taking some time is round 10 mins to get the web page to respond. and then you can do things like set the time zone, boot time, HAT, USB, zone monitoring name and screen orientation if its upside down

[wizardofoz]

@spockfish Harry now I have 3 LCD screens running … the defining of the HostName in the extension is really desirable.

Another thing is that using 2 Zone Monitoring of the same name is working fine

BUT I think there bis a problem changing all the settings in one go…I think the time I got it to work was when I didn’t change the orientation…and on that note I think that 99% off all screen installs will be upside-down so a default for rotated might be a better default.

I also noted there an AutoBoot option that is set to 1 - so this a setting for the future to be able to force ones own updates?

And on that note…is it possible at all to have the web page reload back to the non commit or shutdown link as I often just hit refresh and wonder why the system is restarting again… just for the unwary user

[volpone]

Using the same setup: RPI 3, 7" official 7" TouchScreen, Case.
I’ve got some huge audio interferences on USB output using DietPi / RoonBridge with touchscreen linked.

See: https://community.roonlabs.com/t/powering-raspberry-pi-3-touchscreen

I’m powering RPI+screen from the same PSU at the screen level (microsusb connector from Ifipower 5V 2.5A). Seems possibly to be an under voltage issue ?

I’m interested in feedback from other users about SQ with and without screen.
Currently my choice is to use RPI + Touchscreen out of the audio path as a display/control device only.

[Sean2016]

Is the same Extension name for multiple zones an issue?

I setup multizone Ropieee’s for my old man and once you hit enable for both extensions, you should never have to look at that screen ever again.

So in my old man’s system, giving it different names won’t change anything because it’s a ‘once off’ step.

It’s not like giving each Ropieee a host name where you do need that to identify things daily.

It’s very stable now (apart from your ‘unknown’ title issue which I hope gets sorted of course).

I may be missing something though where it may be useful giving each extension a different name but can’t think of any case? It’s a ‘set it and forget it’ thing with the extensions (I think)

Having said that, for ‘completeness’ it might be good to have each extension’s name link to the ropieee host name, as you requested already. Just to make it look cleaner

[Sean2016]

One thing I forgot to ask you last time - why not plug your microUSB cable into the Pi, not the Screen?

So the screen will be powered by the Pi, whereas currently the Pi is powered by the screen?

Does it make a difference?

[volpone]

One thing I forgot to ask you last time - why not plug your microUSB cable into the Pi, not the Screen?

So the screen will be powered by the Pi, whereas currently the Pi is powered by the screen?

Thank you Sean.
Currently i’ve unlinked the screen from my PI to be able to enjoy music but will try:

1. Powering PI and screen from two distinct 5V PSU (via microUSB)
2. Powering at the PI level (microUSB too) from only 1 PSU according to your idea. For this test do you think the 2 GPIO links (red and black) are OK to feed the screen.

[Sean2016]

2. Powering at the PI level (microUSB too) from only 1 PSU according to your idea. For this test do you think the 2 GPIO links (red and black) are OK to feed the screen.

Yes it won’t work without those links - that’s actually what those links are for - sending power both ways.

If using 2 separate 5V PSU’s, disconnect the red and black links.

[wizardofoz]

@volpone also if you are using a 3B you don’t need the other connections that come with the screen… this is all you need

https://www.raspberrypi.org/learning/addons-guide/display/

[volpone]

@volpone also if you are using a 3B you don’t need the other connections that come with the screen… this is all you need

https://www.raspberrypi.org/learning/addons-guide/display/

Thank you @wizardofoz.
I’m using 3B and this is exactly how are my connections.
Unfortunately quite a lot of interferences on USB output when powered from screen microUSB via 5V, 2.5A PSU.

Under DietPi i’ve got yellow thunder bolt symbol on desktop display. I think this is “under voltage” indicator.

[spockfish]

don’t shutdown, just reboot.

[wizardofoz]

Well yes if I want to reboot thats what I do…but sometimes i need to shutdown…like if I need to swap power supplies or move the unit so then when I plug it back in…brain has forgotten and just does a refresh page and poof shutdown again