Difference between revisions of "Engage 10"
(Created page with "Engage 10 Wireless LCD Model number : W10T200-HWH1WH The following file is used to make the screen work on a rasberry pi. 60-pluggable.conf Formatting is completely broken...") |
(Trying to get off to a good start... -mouse) |
||
| Line 1: | Line 1: | ||
| − | Engage 10 Wireless LCD | + | Engage 10 Wireless LCD Model number : W10T200-HWH1WH |
| − | Model number : W10T200-HWH1WH | + | |
| − | The | + | These devices were intended to be WUSB touchscreens. |
| + | They include an internal WUSB device dongle, an NEC USB hub, a USB displayport video chip feeding VGA to an RTD LCD driver, and a USB HID touchscreen. | ||
| + | There are some macro buttons, but I have not seen them driving any linux input streams. | ||
| + | The LCD seems to be 1024 x 600 native resolution. | ||
| + | The box should include the display, an external WUSB host dongle, a 12 volt (usually 3 amp) power supply and a USB A to USB A cable. | ||
| + | The cable was included just to allow pairing between the WUSB dongles, but it can be used to connect the display directly to the computer. | ||
| + | The pairing process seems to be tricky... | ||
| − | + | The displayport chip is a DL-125, old and well supported. | |
| + | The current raspbian image has a kernel module driver for it. | ||
| + | Current Ubuntu distrubtions seem to hot plug the display and bring up GUI to configure it, but guess the resolution badly. | ||
| + | Current Debian distrubtions seem to have the driver which generates a green screen, but they do not bring up any GUI to configure it. | ||
| + | Windows XP needs a displayport driver, I have not tried newer versions on the metal, and had trouble with 7 on a VM. | ||
| + | In general, plugging the display into a linux computer should cause a new fb device to show up in /dev/ and you can then do what you like with it, including x11. | ||
| + | A solid green screen is generally a good sign. | ||
| − | + | To configure raspbian to use the display create /usr/share/X11/xorg.conf.d/60-pluggable.conf with the following text: | |
| − | + | ||
| − | + | ||
| + | <pre> | ||
Section "Device" | Section "Device" | ||
Identifier "displaylink device" | Identifier "displaylink device" | ||
| Line 36: | Line 46: | ||
Screen 0 "displaylink screen" 0 0 | Screen 0 "displaylink screen" 0 0 | ||
EndSection | EndSection | ||
| + | </pre> | ||
| + | |||
| + | That should take care of the display.. I just made up most of the config, it is probably not optimised. | ||
| − | + | The touch screen seems to stream HID absoulte X and Y events.. | |
| + | Raspbian seems to convert these to mouse events by default, and gets the axis wrong. | ||
| + | This can probably be fixed in software, but it is an area that needs work. | ||
Revision as of 11:36, 13 December 2016
Engage 10 Wireless LCD Model number : W10T200-HWH1WH
These devices were intended to be WUSB touchscreens. They include an internal WUSB device dongle, an NEC USB hub, a USB displayport video chip feeding VGA to an RTD LCD driver, and a USB HID touchscreen. There are some macro buttons, but I have not seen them driving any linux input streams. The LCD seems to be 1024 x 600 native resolution. The box should include the display, an external WUSB host dongle, a 12 volt (usually 3 amp) power supply and a USB A to USB A cable. The cable was included just to allow pairing between the WUSB dongles, but it can be used to connect the display directly to the computer. The pairing process seems to be tricky...
The displayport chip is a DL-125, old and well supported. The current raspbian image has a kernel module driver for it. Current Ubuntu distrubtions seem to hot plug the display and bring up GUI to configure it, but guess the resolution badly. Current Debian distrubtions seem to have the driver which generates a green screen, but they do not bring up any GUI to configure it. Windows XP needs a displayport driver, I have not tried newer versions on the metal, and had trouble with 7 on a VM. In general, plugging the display into a linux computer should cause a new fb device to show up in /dev/ and you can then do what you like with it, including x11. A solid green screen is generally a good sign.
To configure raspbian to use the display create /usr/share/X11/xorg.conf.d/60-pluggable.conf with the following text:
Section "Device"
Identifier "displaylink device"
driver "fbdev"
Option "fbdev" "/dev/fb1"
Option "ShadowFB" "off"
EndSection
Section "Monitor"
Identifier "displaylink monitor"
EndSection
Section "Screen"
Identifier "displaylink screen"
Device "displaylink device"
Monitor "displaylink monitor"
DefaultDepth 16
SubSection "Display"
Depth 16
Modes "1024x600"
EndSubSection
EndSection
Section "ServerLayout"
Identifier "default"
Screen 0 "displaylink screen" 0 0
EndSection
That should take care of the display.. I just made up most of the config, it is probably not optimised.
The touch screen seems to stream HID absoulte X and Y events.. Raspbian seems to convert these to mouse events by default, and gets the axis wrong. This can probably be fixed in software, but it is an area that needs work.
