I have read through all of the posts under "two monitors on an Element" and we still cannot get our Element to talk to our touchscreen monitors on the DVI-D ports.
Both monitors are working and work well when plugged into the AVG port individually.
The Monitors are the recommended ELO touchscreen monitors. The resolutions are correct and the frequencies are correct (60Hz).
We tried rebooting a few times with the monitors plugged into the DVI ports, We have tried opening the settings shell at startup to identify or locate the monitors. We are having no luck at all.
What can we do to make the Element recognise that these monitors are connected?
Thanks
Hi Mike,
Sorry for the difficulties you're having. Check to make sure that you're running the most recent version of software (you can do so at this wiki article), and try the monitor configuration technique outlined in this article: http://www.etcconnect.com/Community/wikis/products/ion-element-and-rvi-monitor-arrangement-after-v-1-9-5.aspx.
If you're still having difficulty, please Contact ETC Technical Services at the office nearest you.
Hans Hinrichsen
ETC Technical Support Specialist
Hi Hans, I am having the same problem with my Element. It refuses to recognize the second monitor. When it is booting up both monitors mirror each other then one of them shuts off and it will not recognize the 2nd monitor, I have tried everything. I am downloading the new software today.
scott
Hi Scott,
If that doesn't work, please go ahead and give us a call and we can help you sort it out. Contact information for all of our offices is located here: http://www.etcconnect.com/Community/wikis/products/contact-etc-technical-services.aspx
Thanks!
Hans
Hi
We now have managed to get a replacement 2nd monitor for our Element.
It is an ELO 1900L touch screen and it has a DVI-D connection. The display works, the mouse works.
The touch screen function does not - it also does not work when connected to port 1. We think it might ba monitor driver issue. Which drivers should we try to use from the ELO site - the window compatable versions or some other platform?
Here are our options fron the ELO site. http://www.elotouch.com/Support/Downloads/dnld.asp
If you have another idea about what the problem might be please let me know.
What is the part number of the Elo monitor? Is the touchscreen connected to the console via USB as well as DVI-D?
Yes both USB and DVI-D connections are made.
Elo monitor part number the monitor is a Elo 1900L
.... Can't find anything that says PN or SN but we have these numbers. (Hope this helps)
J10L038318
ET-1900L-AUWA-1-GY-G
E623689
SD601236 Rev E
Thanks, Mike
And we just found this on the paperwork with it - not actually on the monitor
Rev B E964007 - this may just be the manual part #
It appears that part number E623689 features Acoustic Pulse Recognition touch technology, which is not currently supported by the Eos family of consoles.
We currently support Elo monitors with Accu-touch (5-wire resistive) technology, which is currently available on the 1928L model (as well as others). I apologize for any confusion -- the same Elo model number can have several different part numbers, each with a different touch technology. More information can be found on our wiki article here about compatible touchscreens: http://www.etcconnect.com/Community/wikis/products/touchscreen-monitors.aspx
Hi Hans,
I've called ETC tech support (talked specifically to you actually) for this very issue on multiple occasions and the only thing that ever works for me is using the keyboard shortcut on the shell screen that brings up the Windows based monitor dialog. I actually have this very problem right now and I can't remember what that shortcut is.
I'm currently running the most recent version of the software, and when I first booted the board both monitors were working, but then in the External Monitor Arrangement I swapped the order of the monitors and upon applying the settings the second monitor cut out and now I can't get it working again.
Can you share what the keyboard shortcut is?
Thanks,
Chris
Hi Chris,
Please check your email.
This happened to us too -
We plugged ONE in, booted up the console, and when it was on, plugged in the other. This seems to work.