Auto detect screen size and error checking

[shawaj]

The ability to auto detect the screen size (negating the need for papirus-set) would be fantastic.

Additionally error checking within papirus-set, and within other scripts to make sure papirus-set had been run already would be useful

[francesco-vannini]

Me and @tvoverbeek have looked into the screen signatures and unfortunately they all come up with 0x12. So unless we missed something there is no way to auto-configure the screen. We can certainly look into improving the scripts not to run if the screen hasn't been specified. epd-fuse.default https://github.com/repaper/gratis/blob/master/PlatformWithOS/driver-common/epd-fuse.default doesn't populate EPD_SIZE on first installation. We could either check that in each script or forcefully run papirus-set at the end of the installation process. Either of these will solve the problem for EPD_SIZE not having a value but will not solve setting the wrong screen size which in turn causes the bar-code effect.

[shawaj]

I guess setting the wrong size is basically impossible to avoid without it having an identifier on the screen driver chip which it doesn't (unless there is one but we just can't get access to it with current driver?)

Probably checking the size is set at top of scripts is best? What do you think?

Although force running papirus-set after install is quicker to implement and has the same effect

The only failsafe way would be to ask them on every run of the demo scripts

On 27 Mar 2017 9:29 am, "Garage Tech" notifications@github.com wrote:

Me and @tvoverbeek https://github.com/tvoverbeek have looked into the screen signatures and unfortunately they all come up with 0x12. So unless we missed something there is no way to auto-configure the screen. We can certainly look into improving the scripts not to run if the screen hasn't been specified. epd-fuse.default https://github.com/repaper/gratis/blob/master/ PlatformWithOS/driver-common/epd-fuse.default doesn't populate EPD_SIZE on first installation. We could either check that in each script or forcefully run papirus-set at the end of the installation process. Either of these will solve the problem for EPD_SIZE not having a value but will not solve setting the wrong screen size which in turn causes the bar-code effect.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/PiSupply/PaPiRus/issues/101#issuecomment-289387288, or mute the thread https://github.com/notifications/unsubscribe-auth/ADNCukNuNtnoX6olSgAuCTzQnl1xyg7Rks5rp3N0gaJpZM4Mph3A .

[tvoverbeek]

The current installation script (PiSupply/PaPiRus/install on github) leaves EPD_SIZE in /etc/default/epd-fuse commented out. Hence the epd-fuse service starts with the default size 2.0. Probably best to force the user in the papirus-setup script to define their size before starting the epd-fuse service. In all the demo script we could add a check if environment variable EPD_SIZE is set (by sourcing /etc/default/epd-fuse). If not set prompt the user to run papirus-config to set the size and exit.

Working on these changes (and LM75B support in epd.py so the actual temperature is used in all the EPD commands).

Expect a PR in the coming days.

[shawaj]

Thanks @tvoverbeek

On 27 Mar 2017 5:15 pm, "tvoverbeek" notifications@github.com wrote:

The current installation script (PiSupply/PaPiRus/install on github) leaves EPD_SIZE in /etc/default/epd-fuse commented out. Hence the epd-fuse service starts with the default size 2.0. Probably best to force the user in the papirus-setup script to define their size before starting the epd-fuse service. In all the demo script we could add a check if environment variable EPD_SIZE is set (by sourcing /etc/default/epd-fuse). If not set prompt the user to run papirus-config to set the size and exit.

Working on these changes (and LM75B support in epd.py so the actual temperature is used in all the EPD commands).

Expect a PR in the coming days.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/PiSupply/PaPiRus/issues/101#issuecomment-289503747, or mute the thread https://github.com/notifications/unsubscribe-auth/ADNCuj-9hf3YYlI3Kyu1GHC44tN4eXFDks5rp-CYgaJpZM4Mph3A .

[tvoverbeek]

See PR #103

[shawaj]

@francesco-vannini @tvoverbeek - seems like perhaps this is as good as we are going to be able to get it without a concrete way of detecting the screen size automatically.

@francesco-vannini - did you email Pervasive about this and if there is any other way they can be told apart from each other in code?

[francesco-vannini]

Yes I got in touch but as you say this is as far as things gets on this. We can safely close this one I suppose.

On 15 Apr 2017 00:24, "Aaron Shaw" notifications@github.com wrote:

@francesco-vannini https://github.com/francesco-vannini @tvoverbeek https://github.com/tvoverbeek - seems like perhaps this is as good as we are going to be able to get it without a concrete way of detecting the screen size automatically.

@francesco-vannini https://github.com/francesco-vannini - did you email Pervasive about this and if there is any other way they can be told apart from each other in code?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/PiSupply/PaPiRus/issues/101#issuecomment-294254912, or mute the thread https://github.com/notifications/unsubscribe-auth/APUu1w5Vsd_8DZeqeFfdQVFREsG00Ho2ks5rwAA4gaJpZM4Mph3A .

[shawaj]

So they didn't reply with anything useful that could help us?

[francesco-vannini]

We just got an email from Pervasive Displays. "There is no such information embedded in the COG/driver/display.

The returned 0x12 is for G2 COG model only. No size information."

I think we can close this.

[shawaj]

Cool, closing now

[shawaj]

Was fixed in #103