Cisco StadiumVision
Jeff Lockyear
Posts: 147
Has anyone had any experience with Cisco's StadiumVision? I have the API and the implementation guide, and while it seems relatively straightforward, I thought I'd put out a query in case someone knows and tips or tricks. We're just going to be using one TP to control 8 DMPs/displays, so it's not an extensive system.
0
Comments
This program is really about controlling the display devices attached to the DMPs. I've setup some commands for basic DMP control, but I haven't had a live system to work with yet to test channel selection on IPTV etc.
Maybe this is the type of system you are referring to.
In which case, it's all HTTPS, from what I can see.
So be prepared
Am I on the right page with you for this product? I wont bore you with anymore details in case I'm on the wrong track.
How are you handling the HTTPS connection?
There are at least three solutions.
Two solutions will require a PC. The third solution, as I understand it, is the new NX series processors and a Duet module - but I haven't had the chance to investigate that path.
So, back to two PC options. The first was something I read about on this forum, and involves doing some scripting on a linux box.
The final option I've taken is to write an application in Windows that will act as a gateway and take HTTP commands from the AMX processor and convert them to HTTPS for the DMPs.
As I mentioned earlier, this has worked on the bench with a test system. I am still waiting to get my chance to scale the project up into the site wide system.
Anyway, if you are planning a new project, maybe the NX will solve the HTTPS issue. If they had been ready six months ago then maybe I would have looked closer for this latest installation.
Lastly, the DMP SDK is reasonably simple to implement.
This is some sample http preparation ..
ciscoDMP[index].cmdline = "'GET /set_param?',comand,' HTTPS/1.1', 13,10,
'Host: ', ciscoDMP[index].network, 13, 10,
'User: ', ciscoDMP[index].user, 13, 10,
'Pass: ', ciscoDMP[index].password, 13, 10,
'Connection: Close', 13, 10,
13, 10,
13, 10";
where 'command' would be something like ..
'mng.command=write ciscocraft showIP{}'
or
'rs232.tx_hex=8c000002008e'
See how you go with those suggestions. I'm very curious what approach you choose in the end. I'd certainly like to avoid the gateway PC if possible.
I'll definitely update when and if this rolls out. Thanks again!
Jeff
I have still only operated my one to one test system and haven't had access to the large system yet.
My test system is working, with https. The issue I'm waiting to check is many devices thru one https gateway pc (potential bottleneck).
It's good to see you have a http only version. Maybe I missed something, or there is new firmware, but I didn't see where https could be disabled in the devices.
By going with http only, the control should be fairly straightforward. I'd suggest using the ''mng.command=write ciscocraft showIP{}'' command to start with, it's creates an OSD message for the device when successful.
I'm curious about the http only, so keep us posted.