![Cobalt Digital Inc HPF-9000 Product Manual Download Page 45](http://html1.mh-extra.com/html/cobalt-digital-inc/hpf-9000/hpf-9000_product-manual_2629710045.webp)
HPF9000-OM (V1.8)
HPF-9000 PRODUCT MANUAL
2-27
Installation and Setup
Network Controller Card DashBoard Status and Settings Interfaces
Provides controls for Network Controller Card caching
of user card parameters that can enhance
DashBoard-to-frame connection speed using
enumerated parameter list caching
• Parameter Caching Mode Select
Selects caching mode as follows:
• Disabled – no caching; all queries always go thru CAN bus to cards.
• Enabled without enumeration– caching is performed, but an
enumerated list is not written.
• Enabled with enumeration; cards immediately visible– caching is
performed and enumerated list is written. Frame and card presence is
visible even for cards not fully enumerated. (This setting provides fastest
rendering of frame and cards in DashBoard and is the recommended
default setting.) Enumeration list shows write-to-list status.
• Enabled with enumeration; cards hidden until enumerated– similar
to above, but waits until cards are fully enumerated before displaying a
card.
Note: All known instances of Cobalt openGear
®
cards support network
controller card parameter caching. If card will not appear, set Parameter
Caching to Disabled. This mode is the same as previous frame network
controller card function.
Table 2-1
Frame Setup and Auxiliary Control Descriptions — continued
With user cards enumerated by Network Controller
Card, DashBoard instances query for card presence
with communication between only the Network
Controller Card and DashBoard instances. The frame
internal CAN bus is not queried, greatly speeding-up
frame reporting and card presence to DashBoard
instances. Cache is updated if card parameters
change.
Without user cards enumeration, DashBoard
instances must query for card presence using
communication between the Network Controller Card
and DashBoard instances, and additionally then the
Network Controller Card and the frame internal CAN
bus. This can cause longer delays in frame connection
(especially when many DashBoard instances are
trying to query the same frame).