Model Boat Mayhem

Please login or register.

Login with username, password and session length.
Pages: [1]   Go Down

Author Topic: Printer screen  (Read 1168 times)

funtimefrankie

  • Full Mayhemer
  • *****
  • Offline Offline
  • Posts: 1,259
  • Location: Birkdale, Lancashire. twixt the Mersey & the Ribble
Printer screen
« on: October 15, 2010, 07:18:53 pm »

I've  a broken printer with a 2.5inch screen to view the photos, anyone know what the input would be to this, could it be wired up and used for something else, perhaps a GPS chart  screen on a model boat bridge.
I hate throwing things out that might come in handy, one day.
Logged

Wasyl

  • Guest
Re: Printer screen
« Reply #1 on: October 15, 2010, 09:48:43 pm »

I,ve got a loft full of "might come in handies" {-)

Wullie
Logged

RaaArtyGunner

  • Guest
Re: Printer screen
« Reply #2 on: October 15, 2010, 10:41:11 pm »

Wullie's got it.  :-)) :-))

Over here Murphy's law applies.  O0 O0
As soon as you throw it away you will find a use for it.  <*< <*< <:( <:(

Maybe it is possible to "backlight it" for use in a console setting??
Logged

Wasyl

  • Guest
Re: Printer screen
« Reply #3 on: October 16, 2010, 12:13:37 am »

S,funny how different names apply for the same thing,...here, its Sods Law,

Wullie
Logged

fatcat123

  • Guest
Re: Printer screen
« Reply #4 on: October 19, 2010, 06:09:13 pm »

I've had similar ideas for charts and things.

However any image to be displayed on the screen istself would need some sort of display driver etc. Bottom line is, its horendously complicated stuff ( i know first hand after studying chipset programming in college).

best bet would be to try and power it up, hoping it emits a white light and overlay an image on top. I think theres now transparent inkjet printable vinyl around so it would make for an excellent little addition to any wheelhouse.

I tried an old digital camera preview screen and it refused to power up and emit white light so it may depend on the unit itself.

Dan
Logged
Pages: [1]   Go Up
 

Page created in 0.092 seconds with 22 queries.