Grass Valley DHP v.1.1 - Manual (Page 43)

35
DHP
Reference Manual
The DHP service also keeps an internal list of which devices are already being re-embedded so
that if anyone would like to route that combination to another destination it will use the already
assembled source.
To clear a re-embedder, route a new source to its ultimate destination.
If a disembedder is not available, or if a re-embedder is not available, the error status is returned
in the router’s response to the ‘Take’ command. The response goes back to the NV9000 and
then, in some form, to the operator’s panel.
Product Limitations
The DHP service currently does not understand what to do with AES asynchronous cards. (It is
best to leave this area of the router as a blank in its configuration.)
The DHP service knows only of cards listed in HybridCards_xxxx.cfg . It will create a sparse
internal matrix based on this information. If a card is removed or replaced with a different type,
this file will need to be updated.
The HybridPorts_xxxx.cfg file is similar. DHP knows only of the port pairs defined in this file.
If either of the configuration files has changed, the DHP service must be restarted. Follow these
steps while logged into the NV9000:
1 Right-click the ‘NVCONFIG CONTROLLER’ icon on the desktop. (This is equivalent to ‘My
Computer’ on a regular PC desktop.)
2 Choose ‘Manage’ from the context menu.
3 When the ‘Computer Management’ window appears, choose ‘Services and Applications’.
4 Right-click Nv HybridSVC_(DHP) in the list of services. Select ‘Restart’ in the context menu:
Be sure to update the configuration (i.e., initialization) files on both NV9000 system controllers if
you have a redundant NV9000 system.
Architectural Defects
Even without DHP, it is possible for NV9000 panels to present false status. That is because the
NV9000 gives status before it performs router operation such as a take. If the operation fails, the
false status remains for a significant time (several seconds to a minute or more) before the
NV9000 recognizes the true status of the router.
DHP was intended to be transparent. It is, perhaps, until a failure occurs. With DHP, take failures
are possible, because DHP relies on a pool of resources that can become depleted.