Keyboard Shortcuts
Likes
Search
Cisco Touch 10 Layout
|
Having been through a nightmare of a situation where a client demanded this (or perhaps our sales team sold the concept and painted us into a corner - that seems just as likely) and was then locked into quickly-outdated Cisco software unless they wanted to pay to redevelop the UI with every successive Cisco update, I thought I'd pose the question: with the ease of use and integration of Cisco Touch 10 / Navigator UI extensions with third-party control systems for elements outside Cisco's normal scope of control, is there a reason to develop and deploy a Crestron user interface that emulates Cisco? You may wish to consider letting Cisco drive the bus and having Crestron do what it does best and present the Cisco Touch 10 or Navigator panel as the primary user interface if this is a UC environment that centers around Cisco. These sorts of deployments have been much more successful for us and for our clients long-term than trying to emulate Cisco. Crestron emulations of Cisco do not tend to shine for very long, unless you have a client who is intent on spending their money on Crestron UI updates to keep up with Cisco's pace of development. That's my $.02, anyway.
|
|
Before you go spending a lot of time trying to develop a UI that would resemble the layout of a Cisco Touch 10, why not think about using the Cisco Touch 10 as the UI??
My personal experience has been split across two paths: (1) develop a UI (on Crestron) that looks like a Cisco UI... until the Cisco UI changes; or (2) develop In-Room Controls (or whatever Cisco wants to name / brand the 'customized controls' feature available) on a Navigator / Touch 10. With Option (1) you can create very Crestron-customized user interfaces?however you need to be aware that any mimic of a Cisco UI needs managed that it may become out of sync with any Cisco firmware update (and can become a weird conversation between 'user experience' centric audience and 'network security' centric audience). With Option (2) you get no issues with updating Cisco firmware (when the next feature or bugfix is implemented for that system) with the small tradeoff that all user controls now need to fit within the In-Room Control design boundaries.? FWIW I am a huge fan of option 2 and always lead with that if given the chance.? |
¿ªÔÆÌåÓýFor basic room control I highly endorse the use-the-Touch 10-as-the-UI approach (I have several clients with large deployments in this vein including one where we¡¯ve done a couple hundred rooms in a handful of countries and a few local languages) ¨C not only does it work well and you don¡¯t have to worry about the most complicated part of the UI or keeping up with UI refreshes and improvements but it takes a lot of the UX workload away because Cisco locks you into a relatively rigid framework, so even if you want to reinvent the wheel you can¡¯t really. ? ? For wackier rooms the line is less clear because of that same lack of flexibility (e.g. divisible rooms with multiple codecs, lots of analog controls) and depending on room use cases (is this a room that¡¯s 95% VTC or 5% VTC, for example?) other approaches ?start to make sense, e.g. for a primarily VTC room it may be best to use the Touch 10/Navigator as the primary end user UI but have a real Crestron panel somewhere for more tech/room setup tasks. I¡¯m finding it more and more rarely makes sense to reinvent the VTC UX (Though having said that I do have a project we¡¯re replacing Zoom with WebEx in a dozen or so rooms being build where VTC is less than 1% of the functionality and we¡¯re working with the client on what makes the most sense for the UX. In that case, though, auto join or OBTP and end call are probably the limits of the normal VTC control. ? -- Lincoln King-Cliby, CTS, DMC-E-4K/T/D ? From: [email protected] [mailto:[email protected]]
On Behalf Of Andrew Linck
Sent: Tuesday, April 19, 2022 8:32 AM To: [email protected] Subject: Re: [crestron] Cisco Touch 10 Layout ? Before you go spending a lot of time trying to develop a UI that would resemble the layout of a Cisco Touch 10, why not think about using the Cisco Touch 10 as the UI?? |
|
Ressurecting an old thread, sorry.
Yes, I understand the advantages of controlling a Crestron system via the Cisco touch 10 but how? Where is the documentation for that, adding buttons, setting up connections to third party devices, sending custom commands etc, etc. Everybody says it can be done, but nobody can tell me how. Is there an online training, or documentation, something to point me in the right direction? A customer asked about a Qsys Core being controlled by the touch 10, apparently yes, it can be done also.... but how? Do I have to be a Cisco engineer to have access to that? Thank you for any pointers !? |
|
In these cases, there is still Crestron doing the control of the devices, just the Touch10 is the UI for the Crestron.? There is no direct control of other devices from the Cisco.
Look up "Cisco Room Control"? They have a UI editor (really just a web script that runs in the browser), that lets you add panels/buttons to a layout and assign Text and control ID's too.? Then on the Crestron side, it's all custom at that point, as the main CIsco module does not support any of the extra Room control stuff.? The API document is part of the normal API manual I believe, but I've also seen separate api manuals that cover just the room control commands/responses.? You'll have to do some custom Crestron coding to catch the messages from Cisco and to report back feedback status of buttons and guages etc. to update the UI. -- Jason Mussetter Control Systems Designer Mussetter Programming Services |