Page 1 of 1

Avolites Titan V3.0 dual screen

Posted: 26 May 2010, 13:22
by Funmaker
We have a avolite expert with the titan V3.0 software running on it.
While trying our touch screen on it we changed some screen settings because we saw that their where 2 screens active. We disabled one, saw that we did something wrong, reversed the settings which caused the "error".
This didn't solve the problem so we rebooted the expert but now we don't have a screen at all... so how can we get our screen back? How do we get our vga 2 screen back?
thanks in advance

Posted: 27 May 2010, 01:50
by Gregory
To reset the screens to their default setting please try the following:
    1. Start up the console and wait for it to finish booting up.
    2. Press and hold the Ctrl, Shift and Alt keys.
    3. Press and release the Esc key twice.
    4. At this point the screens should come to life.
    5. Power off and on the console so that the new settings are used.


Failing that you can try resetting the graphics drivers by uninstalling them, then reinstalling them again or by running the recovery disc. Further instructions are in section 11.1.5 of the manual.

Let us know if you have any other problems or queries.

Please see my next post that has some advice on how to avoid the same problems in future.

Posted: 27 May 2010, 01:53
by Gregory
Due to the possibility of problems occurring, it is advisable to avoid using the Windows display settings to change the configuration of screens on the console.

As an alternative there are options in System Mode > Display Setup to allow you to enable or disable which screens (Expert Touch or VGA) are used by the console software. These settings can easily be changed one way or the other as the system configuration changes with no possibility of a screen getting stuck off or in the wrong place.

If you need to change the resolution of the external VGA monitor there is an option in the Tools menu in the top left hand corner of each display. Tools > Control Panel > External Monitor then choose the desired resolution.

Posted: 27 May 2010, 08:19
by Funmaker
We did a recovery yesterday which fixed the problem