Cisco Cisco StadiumVision Mobile Maintenance Manual
© 2012 Cisco Systems, Inc. All rights reserved.
Page 94 of 103
negotiate the PoE class with the switch and simply passes through the available
power it receives over the cable run.
power it receives over the cable run.
The following PoE 12V splitter has been test to operate correctly with the DMP-
4310:
4310:
Microsemi PD-AS-701/12
DMP HDMI Issue
DMP 4310G units with serial numbers below USI
1515
xxxx may exhibit a problem
where no video signal is output on the HDMI port, resulting in a black screen.
Everything else about the DMP appears to be normal.
Everything else about the DMP appears to be normal.
Workaround
Powering of the DMP and allow it to cool for at least 10 minutes. Then turn it back
on. If the problem persists then consider replacing the unit.
on. If the problem persists then consider replacing the unit.
DMP Reboot Behaviour
If you reboot a DMP during an event script, expect the following behavior:
• If the event is not running or the event script does not control the DMP, you will
be brought back to full screen video of defaultVideoUrl from the registry.
• If the DMP is controlled by the event script, then you should see the following
behavior:
o
During the reboot, you will lose all video / templates / etc.
o
After the reboot has recovered, the DMP will take a few seconds to recover.
o
After recovery has completed, you should see the template from the script.
(Full screen / 3 region / etc.), and the non-video playlists will be correct.
However, if the current script state has a video region with no actions
configured, then the video will be that of the defaultVideoURL. If the current
state has a video region with "actions" then the DMP will play out the action
described in that state after it receives the next state update multicast
message.
However, if the current script state has a video region with no actions
configured, then the video will be that of the defaultVideoURL. If the current
state has a video region with "actions" then the DMP will play out the action
described in that state after it receives the next state update multicast
message.