Rane HAL1x Installation Guide - Page 113

Troubleshooting the HAL Connection

Get Rane HAL1x PDF manuals and user guides View all Rane HAL1x manuals
Add to My Manuals
Save this manual to your list of manuals

Page 113 highlights

CHAPTER 5: Troubleshooting Your HAL System Installation NOTE: When an EXP is missing, all downstream EXPs also indicate Missing status. 5. If all EXPs are present but not connected in the configuration's expected order on the expansion bus, Hal- ogen displays Device Mismatch status for the affected devices. The following image shows that the EXP5x and EXP3x are connected to the expansion bus but not in the correct order: In the above example, you should fix the problem by either changing the physical cabling or by swapping the devices in the Halogen Hardware Workspace EXP Navigation Panel. See "Swapping Hardware Devices" on page 98 for details. We do not recommend selecting the proper EXP devices from the EXP picker (white arrow); although this solves the mismatch problem, it also removes all RAD and/or DR devices from the Processing Workspace. And if the RADs or DRs have settings stored in presets, or a linked to parameters, all these would be lost. Swapping is a better alternative in this case. Troubleshooting the HAL Connection Before troubleshooting a connection issue, it may help if you understand the basics of how Halogen discovers and then establishes communications with a HAL. HAL devices send occasional UDP broadcast messages. RaneLink II (a Windows Service installed with Halogen that helps establish communication with HAL devices) listens constantly for these messages and, when it receives one, does the following three things, if necessary: It sets up a temporary link-local IP address (in other words, the address is cleared when the computer reboots) on the appropriate network interface card (NIC). It also adds an entry to the computer's network route table. This entry tells Windows and Halogen which NIC to use for communicating with the HAL. The same UDP messages also indicate to Halogen that a HAL device is on the network, so it can be displayed in the Connect to Device dialog box. Lastly, so that it can receive system status updates, RaneLink II opens and maintains a TCP connection with the HAL. NOTE: To review the list of processes required for a HAL connection, see "Required Processes " on page 9. 107

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
NOTE
:
When an EXP is missing, all downstream EXPs also indicate
Missing
status.
5.
If all EXPs are present but not connected in the configuration's expected order on the expansion bus, Hal-
ogen displays
Device Mismatch
status for the affected devices. The following image shows that the
EXP5x and EXP3x are connected to the expansion bus but not in the correct order:
In the above example, you should fix the problem by either changing the physical cabling or by swap-
ping the devices in the Halogen Hardware Workspace EXP Navigation Panel. See "Swapping Hardware
Devices" on page 98 for details. We do not recommend selecting the proper EXP devices from the EXP
picker (white arrow); although this solves the mismatch problem, it also removes all RAD and/or DR
devices from the Processing Workspace. And if the RADs or DRs have settings stored in presets, or a
linked to parameters, all these would be lost. Swapping is a better alternative in this case.
Troubleshooting the HAL Connection
Before troubleshooting a connection issue, it may help if you understand the basics of how Halogen discovers and
then establishes communications with a HAL. HAL devices send occasional UDP broadcast messages. RaneLink II
(a Windows Service installed with Halogen that helps establish communication with HAL devices) listens con-
stantly for these messages and, when it receives one, does the following three things, if necessary: It sets up a tem-
porary link-local IP address (in other words, the address is cleared when the computer reboots) on the appropriate
network interface card (NIC). It also adds an entry to the computer's network route table. This entry tells Windows
and Halogen which NIC to use for communicating with the HAL. The same UDP messages also indicate to Hal-
ogen that a HAL device is on the network, so it can be displayed in the Connect to Device dialog box. Lastly, so
that it can receive system status updates, RaneLink II opens and maintains a TCP connection with the HAL.
NOTE
:
To review the list of processes required for a HAL connection, see "Required Processes " on page 9.
CHAPTER 5: Troubleshooting Your HAL System Installation
107