address range. In a local network environment such as an office where there is a DHCP server, both
the computer and the Device will be in the DHCP IP address range, and so will connect immediately.
AUTO-IP
The device will initially search for a DHCP server when first switched on (during which time its Online
Indicator will be flashing). As it can take up to one minute to establish that there is no DHCP server
available, this is the time it may take before Auto IP is entered.
Please be aware that it can also take some time from a computer being switched on in an isolated
network (without a DHCP server), or unplugged from a network with DHCP to time out of DHCP
searching, so it will not connect immediately to amplifiers that are already using Auto IP. The time it
takes before it decides to revert to Auto IP depends on the operating system but it can take several
minutes to acquire an Auto IP address.
Static-IP
If the device or the computer has a static IP address set, System Engineer may not be able to 'see'
the device if it is in a different IP Address range (i.e. in a different
subnet
).
Unless there are good
reasons it is best to avoid the use of static IP addressing if at all possible.
IP Troubleshooting
If System Engineer cannot connect to the device:
A Router acting as a DHCP server is highly recommended as this provides the most trouble-
free way of administering IP addresses. Always switch on any DHCP server before connecting
either the computer or HDC to the network.
If not using a DHCP server, check that the Current IP address in the device is compatible with
the IP address of the computer. Generally, the leftmost two sets of 3 digits should be the
same.
If there is no Router in the system acting as a DHCP server, wait 10 minutes (for the
computer to acquire the correct IP address) and try again.
Check that the Firewall in the computer will allow System Engineer access to the network
for
both private and public networks
. Please refer to the Help feature in the System Engineer
application for further guidance on this
Snapshots
A Snapshot may be recalled either via the device User Interface, from the System Engineer
application or via the AUX port on the rear of the HDC48.
The snapshot menu is accessed via the utility pages. Recalling a Snapshot triggers the recalling of a
Component to each input and output, and may change other device-wide settings, effectively
recalling a processor-wide preset. In addition to being able to recall snapshots from System Engineer
and from the HDC's front panel, some of the snapshots are also recallable from the auxiliary port.
Also see
Aux Port
The parameters inside the Drive Modules are not individually stored in Snapshots. Recalling a
Snapshot will merely trigger the recall of the appropriate Input and Output Components, rather than
restoring the parameters that were active when the Snapshot was stored. This has the distinct
advantage that the library of OEM presets may be updated without having to be concerned about
Summary of Contents for HDC 84
Page 1: ......
Page 35: ...Processing Block Diagram...
Page 38: ...EQ and Filter Response Graphs...
Page 39: ......
Page 43: ......