- Hiqnet Audio Architect Download For Mac
- Hiqnet Band Manager For Mac
- Hiqnet For Mac
- Hiqnet Audio Architect For Mac
hiqnet.protocol module¶
- JBL Professional software Software: Latest Version: Platform: Related Products: CBT Calculator: 1.3.0.1: CBT 100LA-1, CBT 100LA-LS, CBT 200LA-1, CBT 50LA-1, CBT 50LA-LS, CBT 70J-1, CBT 70J-1 + 70JE-1 System, CBT 1000, CBT 1000 + CBT 1000E System: CDM 2.02.04 WHQL Certified.zip.
- HiQnet Performance Manager™ Windows VRack 12000HD, VRack 4x3500HD, I-Tech 5000HD, I-Tech 9000HD, MA 12000i, MA 9000i, MA 5000i, I-Tech 4x3500HD, I-Tech 12000HD.
- Software for BSS products. BSS software Software: Latest Version: Platform: Related Products: BSS BLU-USB Class 2 Driver.
- BSS Audio HiQnet London Architect functionality has been added to HiQnet Audio Architect configuration and control software. Along with HiQnet capable products from AKG, Crown, dbx and JBL, BSS Audio Soundweb London products previously managed by London Architect can now be managed by HiQnet.
HiQnet protocol library.
Hiqnet.protocol module¶ HiQnet protocol library. Class hiqnet.protocol.Command (source=None, destination=None, command=None) source ¶ Bases: object. Addressused source ¶ Build an Address Used command. Bytesremaining = 0¶ commandlen¶ decode (command) source ¶ Decodes a binary command.
hiqnet.protocol.
Command
(source=None, destination=None, command=None)[source]¶Bases:
object
HiQnet command.
address_used
()[source]¶Build an Address Used command.
bytes_remaining
= 0¶
commandlen
¶
decode
(command)[source]¶Decodes a binary command.
Parameters: | command – The binary command to decode |
---|
decode_discoinfo
()[source]¶Decode discovery information command payload.
Payload:- HiQnet Device- Cost- Serial Number- Max Message size- Keep alive period- NetwordID- NetworkInfo
destination_address
= None.0.0.0.0¶
disco_info
(device, disco_type='Q')[source]¶Build a Discovery Information command.
Parameters: |
|
---|
error_code
= 0¶
error_string
= '¶
flags
= reqack:0 ack:0 info:0 error:0 res1:0 guaranteed:0 multipart:0 res2:0 session:0 res3:0 res4:0 res5:0 res6:0 res7:0 res8:0 res9:0 ¶
get_attributes
()[source]¶Build a Get Attributes command.
get_vd_list
(workgroup=')[source]¶Build a Get VD List command.
Parameters: | workgroup (str) – The workgroup to get the VD list from. |
---|
header
= 'x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00x00'¶
headerlen
¶
hello
()[source]¶Build an hello command.
Starts a session.
Returns: | The session number |
---|---|
Return type: | int |
hop_counter
= 5¶
locate
(time, serial_number)[source]¶Builds a Locate command.
The receiver makes itself visible. Usually this is done by flashing some LEDs on the front panel.
Parameters: |
|
---|
locate_off
(serial_number)[source]¶Builds a locate command asking for the visual clue to be inactive.
Parameters: | serial_number (str) – The target device’s serial number |
---|
locate_on
(serial_number)[source]¶![Manager Manager](/uploads/1/1/8/5/118560939/799599414.jpg)
Builds a locate command asking for the visual clue to be active.
Parameters: | serial_number (str) – The target device’s serial number |
---|
message
= DISCOINFO¶
new_sequence_number
= count(0)¶
optional_headers
= '¶
payload
= '¶
recall
()[source]¶Build a Recall command.
Recalls a preset.
request_address
(req_addr)[source]¶Build a Request Address command.
Parameters: | req_addr (int) – |
---|
sequence_number
= 0¶
session_number
= 0¶
source_address
= None.0.0.0.0¶
start_seq_no
= 0¶
store
()[source]¶Build a Store command.
Stores current state to a preset.
version
¶
hiqnet.protocol.
FullyQualifiedAddress
(device_address=None, vd_address='x00', object_address='x00x00x00', devicevdobject=None)[source]¶Bases:
object
Fully Qualified HiQnet Address.
broadcast_address
()[source]¶Get the Fully Qualified HiQnet Broadcast Address.
Return type: | FullyQualifiedAddress |
---|
device_address
= None¶
object_address
= None¶
vd_address
= None¶
hiqnet.protocol.
Message
(identifier=None, name=None)[source]¶Bases:
object
HiQnet messages handling.
MESSAGES
= {'x00x02': 'GETNETINFO', 'x00x03': 'RESERVED1', 'x00x00': 'DISCOINFO', 'x00x01': 'RESERVED0', 'x00x06': 'SETADDR', 'x00x07': 'GOODBYE', 'x00x04': 'REQADDR', 'x00x05': 'ADDRUSED', 'x00x08': 'HELLO', 'MULTPARMSUB': 'x01x0f', 'GETATTR': 'x01r', 'PARMUNSUBALL': 'x01x14', 'SUBEVTLOGMSGS': 'x01x15', 'PARMSUBPCT': 'x01x11', 'PARMSUBALL': 'x01x13', 'HELLO': 'x00x08', 'MULTPARMGET': 'x01x03', 'SETATTR': 'x01x0e', 'UNSUBEVTLOGMSGS': 'x01+', 'GETNETINFO': 'x00x02', 'MULTPARMUNSUB': 'x01x12', 'ADDRUSED': 'x00x05', 'MULTOBJPARMSET': 'x01x01', 'RESERVED1': 'x00x03', 'RESERVED0': 'x00x01', 'REQADDR': 'x00x04', 'x01x01': 'MULTOBJPARMSET', 'SETADDR': 'x00x06', 'PARMSETPCT': 'x01x02', 'GOODBYE': 'x00x07', 'REQEVTLOG': 'x01,', 'DISCOINFO': 'x00x00', 'GETVDLIST': 'x01x1a', 'LOCATE': 'x01)', 'x01x00': 'MULTPARMSET', 'x01x03': 'MULTPARMGET', 'x01x02': 'PARMSETPCT', 'x01r': 'GETATTR', 'x01x0f': 'MULTPARMSUB', 'x01x0e': 'SETATTR', 'x01x11': 'PARMSUBPCT', 'x01x13': 'PARMSUBALL', 'x01x12': 'MULTPARMUNSUB', 'x01x15': 'SUBEVTLOGMSGS', 'x01x14': 'PARMUNSUBALL', 'MULTPARMSET': 'x01x00', 'x01x1a': 'GETVDLIST', 'STORE': 'x01$', 'x01%': 'RECALL', 'x01$': 'STORE', 'x01)': 'LOCATE', 'RECALL': 'x01%', 'x01+': 'UNSUBEVTLOGMSGS', 'x01,': 'REQEVTLOG'}¶
identifier
= None¶
name
= None¶
hiqnet.device module¶
HiQnet device architecture.
Node (Device)¶
- At least one virtual device (The first is the device manager)
- Parameters and/or objects
- Objects contains parameters and/or other objects
Attributes everywhere¶
Either STATIC, Instance or Instance+Dynamic
Virtual devices, objects and parameters¶
Have a Class Name and a Class ID
hiqnet.device.
Attribute
(atr_type)[source]¶Bases:
object
Member variables of the HiQnet architecture.
Static are basically constants.Instance are variables that are set at device bootup.Instance+Dynamic are regular variables that can change during the life of the device.
type
= None¶
hiqnet.device.
Device
(name, hiqnet_address=6797, network_info=<hiqnet.networkinfo.IPNetworkInfo object>)[source]¶Bases:
object
Describes a device (aka node).
address
¶Get the device manager address
Returns: | The fully qualified address of the device manager |
---|---|
Return type: | FullyQualifiedAddress |
hiqnet_address
¶Get the device HiQnet address
Returns: | The device HiQnet address |
---|---|
Return type: | int |
manager
= None¶
name
¶Get the device name
Returns: | The device name |
---|---|
Return type: | str |
network_info
= None¶
virtual_devices
= None¶
hiqnet.device.
DeviceManager
(name_string, class_name=None, flags=0, serial_number=None, software_version=None)[source]¶Bases:
hiqnet.device.VirtualDevice
Describes a HiQnet device manager.
Each device has one and this is always the first virtual device.
flags
= reqack:0 ack:0 info:0 error:0 res1:0 guaranteed:0 multipart:0 res2:0 session:0 res3:0 res4:0 res5:0 res6:0 res7:0 res8:0 res9:0 ¶
serial_number
= None¶
software_version
= None¶
hiqnet.device.
Object
[source]¶Bases:
object
HiQnet objects.
May contain other objects or parameters.
hiqnet.device.
Parameter
[source]¶Bases:
hiqnet.device.Object
HiQnet parameters.
Represents the manipulable elements and their attributes.
control_law
= None¶
data_type
= None¶
flags
= res1:0 sensor:0 res2:0 res3:0 ¶
maximum_value
= None¶
minimum_value
= None¶
name_string
= '¶
hiqnet.device.
VirtualDevice
[source]¶Bases:
object
Describes a HiQnet virtual device.
This is the basic container object type.
attributes
= None¶
class_name
= <hiqnet.device.Attribute object>¶
name_string
= <hiqnet.device.Attribute object>¶
objects
= None¶
parameters
= None¶
hiqnet.device.
negotiate_address
()[source]¶Generates a random HiQnet address.
The address is automatically checked on the network.
hiqnet.networkinfo module¶
HiQnet device network informations.
hiqnet.networkinfo.
IPNetworkInfo
(mac_address, dhcp, ip_address, subnet_mask, gateway_address='0.0.0.0')[source]¶Bases:
hiqnet.networkinfo.NetworkInfo
IPv4 network informations.
autodetect
()[source]¶Get infos from the interface.
We assume that interface to the default gateway is the one we wantand fallback to the second interface since the first is usually “lo”.
Return type: | NetworkInfo |
---|
dhcp
= True¶
gateway
= None¶
![Hiqnet Hiqnet](/uploads/1/1/8/5/118560939/466747144.jpg)
ip_address
= None¶
mac_address
= None¶
subnet_mask
= None¶
hiqnet.networkinfo.
NetworkInfo
(network_id=1)[source]¶Bases:
object
Network informations.
NET_ID_RS232
= 4¶
NET_ID_TCP_IP
= 1¶
network_id
= None¶- 1: TCP/IP
- 2: reserved
- 3: reserved
- 4: RS232
hiqnet.networkinfo.
RS232NetworkInfo
[source]¶Bases:
hiqnet.networkinfo.NetworkInfo
RS232 network informations.
- com_id 1 byte
- baud_rate 4 bytes
- parity 1 byte
- 0 - None
- 1 - Odd
- 2 - Even
- 3 - Mark
- 4 - Space
- stop_bits 1 byte
- data_bits 1 byte
- 4-9
- flow_control 1_byte
hiqnet.flags module¶
HiQnet Flags.
Simplified flags management with direct bitfields access.
See also
hiqnet.flags.
DeviceFlags
[source]¶Bases:
_ctypes.Union
Device flags.
ack
¶Structure/Union member
asByte
¶Structure/Union member
b
¶Structure/Union member
error
¶Structure/Union member
guaranteed
¶Structure/Union member
info
¶Structure/Union member
multipart
¶Structure/Union member
reqack
¶Structure/Union member
res1
¶Structure/Union member
res2
¶Structure/Union member
res3
¶Structure/Union member
res4
¶Structure/Union member
res5
¶Structure/Union member
res6
¶Structure/Union member
res7
¶Structure/Union member
res8
¶Structure/Union member
res9
¶Structure/Union member
session
¶Structure/Union member
hiqnet.flags.
DeviceFlagsBits
[source]¶Bases:
_ctypes.Structure
Bitfields for the device flags.
ack
¶Structure/Union member
error
¶Structure/Union member
guaranteed
¶Structure/Union member
info
¶Structure/Union member
multipart
¶Structure/Union member
reqack
¶Structure/Union member
res1
¶Structure/Union member
res2
¶Structure/Union member
res3
¶Structure/Union member
res4
¶Structure/Union member
res5
¶Structure/Union member
res6
¶Structure/Union member
res7
¶Structure/Union member
res8
¶Structure/Union member
res9
¶Structure/Union member
session
¶Structure/Union member
hiqnet.flags.
ParameterFlags
[source]¶Bases:
_ctypes.Union
Parameter flags.
asByte
¶Structure/Union member
b
¶Structure/Union member
res1
¶Structure/Union member
res2
¶Structure/Union member
res3
¶Structure/Union member
sensor
¶Structure/Union member
hiqnet.flags.
ParameterFlagsBits
[source]¶Bases:
_ctypes.Structure
Bitfields for the parameters flags.
- Bits 0, 2, and 3 are reserved. Bit 1 is the Sensor Attribute.
- 0 = Non-Sensor1 = Sensor
res1
¶Structure/Union member
res2
¶Structure/Union member
res3
¶Structure/Union member
sensor
¶Structure/Union member
hiqnet.service.ip module¶
HiQnet IP communication.
hiqnet.service.ip.
Connection
(udp_transport, tcp_transport)[source]¶Bases:
object
Handles HiQnet IP connection.
Warning
Other connection types such as RS232, RS485 or USB are not handled yet.
sendto
(command, destination='<broadcast>')[source]¶Send command to the destination.
Parameters: |
|
---|
tcp_transport
= None¶
udp_transport
= None¶
hiqnet.service.ip.
Factory
(app)[source]¶Bases:
twisted.internet.protocol.Factory
HiQnet Twisted Factory.
protocol
¶alias of
TCPProtocol
hiqnet.service.ip.
TCPProtocol
[source]¶Bases:
twisted.internet.protocol.Protocol
HiQnet Twisted TCP protocol.
dataReceived
(data)[source]¶Called when data is received.
Parameters: | data (bytearray) – Received binary data |
---|
name
= 'HiQnetTCP'¶
startProtocol
()[source]¶Called after protocol started listening.
hiqnet.service.ip.
UDPProtocol
(app)[source]¶Bases:
twisted.internet.protocol.DatagramProtocol
HiQnet Twisted UDP protocol.
datagramReceived
(data, addr)[source]¶Called when data is received.
Parameters: |
|
---|
name
= 'HiQnetUDP'¶
startProtocol
()[source]¶Called after protocol started listening.
All columns enable numeric ascending / descending sorting:
Clicking on the column header will sort initially by ascending value then text string.
Clicking a second time will sort descending value then text string.
Clicking a third time reverts back to the original unsorted order.
An unknown value will be sorted first in the ascending list, last in the descending list
The Grid
The grid is divided into 12 sections:
DHCP / Auto-IP checkbox
Random ID checkbox
On editable fields, entering invalid information in editable fields will revert the field to its previous state.
Displays the MAC Address(es) of the discovered device.
If more than one MAC Address is discovered for a single device (HiQnet device MAC Address / AVB card MAC Address etc), the field is represented as a drop list. You may select between the connected MAC Addresses.
Depending on the selected Ethernet MAC Address the following fields update accordingly:
IP Address
Subnet Mask
Default Gateway
The data in this field cannot be edited.
• For a device connected to the same control network with two control MAC Addresses, the MAC Address field will be displayed in red.
If the discovered device is set to use DHCP / Auto-IP, the check box will be checked.
If it is not using DHCP / Auto-IP, you may check the box so it will do so on applying edits. The device row will then become selected.
The device will attempt to have its IP settings configured by DHCP on applying the edits, if no DHCP server is present the device will attempt to have IP settings configured by Auto-IP.
All devices in the current filter view may be set to DHCP / Auto-IP on by checking the check box in the column header.
The individual check boxes for all devices will be checked. If a single individual check boxes for all devices is subsequently unchecked the column header DHCP / Auto-IP checkbox will be automatically unchecked.
The devices in the current filter view may be set to DHCP / Auto-IP off by unchecking the check box in the column header.
DHCP server status will be among the information displayed at the bottom of the window:
For example: nnn.xxx.yyy.zzz
Where nnn.xxx.yyy.zzz is the IP Address of the detected DHCP server.
If a DHCP server is not detected, the information will read ‘DHCP server not detected’ Checking a device’s DHCP / Auto-IP check box has no immediate effect on the column sort order.
Displays the IP address of the discovered device
A valid IP address may be edited inline if you want to change the device IP Address on applying current edits.
If the edited value scopes the device out of the current Display filter, it will not be visible. No devices will be selected.
Devices discovered with a conflicting IP Address
A discovered device with an IP Address that conflicts with one that has already been discovered will be displayed in red.
A conflicting IP Address may be edited inline if you wish to change the device IP Address on applying current edits.
If DHCP / Auto-IP is enabled the IP address field may not be edited inline.
Displays the Subnet Mask of the discovered device.
The Subnet Mask may be edited inline if you wish to change the device Subnet Mask on applying current edits.
• The device row will be ordered accordingly with the current column sort immediately on successful editing of the field
• The device row will remain selected
If DHCP / Auto-IP is enabled the Subnet Mask field may not be edited inline.
Displays the Default Gateway of discovered device
May be edited inline
• The device row will be ordered accordingly with the current column sort immediately on successful editing of the field
The device row will remain selected
If DHCP / Auto-IP is enabled the Default Gateway field may not be edited inline
If the device is being rediscovered:
• When the device is not selected, the device Default Gateway address field is displayed but is grayed out, represented in light gray.
• When the device is selected and highlighted in orange the field is represented in dark gray.
Displays the Node address of the discovered device. The node address is the first two bytes of the HiQNet address. That is differentiated for third party control.
May be edited inline if you want to change the device HiQnet address on applying current edits.
If the edited value scopes the device out of the current Display filter, it will not be visible. No devices will be selected
If DHCP / Auto-IP is enabled the HiQnet address field may not be edited inline
Devices discovered with a conflicting HiQnet Address
The HiQnet ID field of a discovered device with a HiQnet Address which conflicts with a HiQnet Address which has already been discovered will be displayed in pink.
• A conflicting HiQnet Address may be edited inline if you want to change the device HiQnet Address on applying current edits.
• When the device is selected and highlighted in orange the field is represented in red.
• The HiQnet address is not displayed, instead a dash is displayed as grayed out.
Devices not discoverable at the IP level
A device which is not discoverable at the IP level (invalid IP address etc) will not be able to report a HiQnet address. In this instance, the HiQnet ID field will display a ‘?’ to indicate that the field may exist but that the software does not have enough discoverability of the device to determine the value.
A blank field or ‘-‘ implies the value is null
• The HiQnet ID field may not be edited inline
If you want to set the HiQnet address of a device to a random ID on applying current edits, check the Random ID check box.
• The device will be given a random HiQnet address on applying current edits
• If the check box is unchecked before applying current edits, the prior HiQnet ID value will be restored
• All devices in the current filter view may be set to Random HiQnet ID by checking the check box in the column header
• The individual check boxes for all devices will be checked if a single individual check boxes for all devices is subsequently unchecked the column header Random ID checkbox will be automatically unchecked.
• If all devices in the current filter view are set to Random ID on and the Random HiQnet ID column header check box is checked, all devices may be set to Random ID off by unchecking the column header check box. The individual check boxes for all devices will be unchecked
Devices not discoverable at the IP level
A device which is not discoverable at the IP level (invalid IP address etc) will not be able to report a HiQnet address. In this instance, the Random ID check box will be unavailable.
Displays the current discovery status of the device. Discovery status hierarchy is as follows:
• Discovered. If a device has a unique IP address and a unique HiQnet address, this condition will be shown unless the device is access controlled
• IP conflict. If a device has an IP Address conflict, this error will be shown regardless of other status notifications
• HiQnet conflict. If a device has a unique IP address yet has a HiQnet address conflict, this error will be shown regardless of other status notifications
• Locked. If a device has a unique IP address and a unique HiQnet address, this condition will be shown if the device is access controlled
• Discovering. This condition will be displayed if the device has had changes made to IP configuration or HiQnet address and HiQnet NetSetter is waiting to reestablish connection
The Status field may not be edited
Discovered
• The ‘Discovered’ status is determined by the following conditions:
Hiqnet Audio Architect Download For Mac
The device is discoverable at the MAC Address level
The device has a valid and unique IP Address (manual or DHCP / Auto-IP)
The device has a unique HiQnet address
The device is not Access Controlled
• When the device is not selected, the ‘Discovered’ label is represented in green.
IP conflict
• The 'IP conflict’ status is determined by the following conditions:
The device is discoverable at the MAC Address level
The device has an IP address which conflicts with another device which has already been discovered by NetSetter
• When the device is not selected, the ‘IP conflict’ label is represented in blue.
HiQnet conflict
• The ‘HiQnet conflict’ status is determined by the following conditions:
The device is discoverable at the MAC Address level
The device has a valid and unique IP Address (manual or DHCP / Auto-IP)
The device has a HiQnet address which conflicts with another device which has already been discovered by NetSetter
• When the device is not selected, the ‘HiQnet conflict’ label is represented in red.
Locked
• The ‘Discovered’ status is determined by the following conditions:
The device is discoverable at the MAC Address level
The device has a valid and unique IP Address (manual or DHCP / Auto-IP)
The device has a unique HiQnet address
The device is Access Controlled
• When the device is not selected, the ‘Locked’ label is represented in yellow.
When the device has been discovered in the Locked state, a dialog must be displayed to prompt for the Admin password the first time any field is attempted to be edited
A successful login with the Admin password only will enable all fields to be edited subsequently
This state may need to be reset on rediscovery after applying current edits, requiring the Admin password to be entered again
Discovering
• The ‘Discovering’ status is determined by the following conditions:
The device had been previously discovered at at least the MAC Address level
Edits had been made to one or more fields
The device is being rediscovered after applying current edits
Hiqnet Band Manager For Mac
Since the sort order automatically updates when a field within the sorted column is updated, the rediscovered device will occupy the same row on rediscovery.
Unless DHCP / Auto-IP or Random ID has been set prior to applying current edits, in which case the rediscovered device will occupy the appropriate row in the current column sort order.
• When a device being rediscovered is not selected, all fields within the device row are displayed but is grayed out, represented in light gray.
• The device class name is displayed, as reported by the discovered device. To the left of each device class name is displayed the brand icon.
• The software application name is displayed for discovered PCs running an instance of HiQnet software
System Architect
Performance Manager
London Architect
• The Device Type field may not be edited inline
Devices not discoverable at the IP or HiQnet level
A device which is not discoverable at the IP level (invalid IP address etc.) or HiQnet address level (HiQnet address conflict etc) will not be able to report its class name. In this instance, the Device Type field will display a ‘?’ to indicate that the field may exist but that the software does not have enough discoverability of the device to determine the value.
A blank field or ‘-‘ implies the value is null
The user-definable Device Name is displayed, as reported by the discovered device
Hiqnet For Mac
• May be edited inline if you want to change the Device Name on applying current edits
• May not be edited for discovered PCs running an instance of HiQnet software
Devices not discoverable at the IP or HiQnet level
A device which is not discoverable at the IP level (invalid IP address etc) or HiQnet address level (HiQnet address conflict etc) will not be able to report its Device Name. In this instance, the Device Name field will display a ‘?’ to indicate that the field may exist but that the software does not have enough discoverability of the device to determine the value
A blank field or ‘-‘ implies the value is null
The Container and Position Venue Data is displayed (separated by a colon), as reported by the discovered device.
The field is left blank for discovered PCs running an instance of HiQnet software
System Architect
Performance Manager
London Architect
• The Container / Position Venue Data may not be edited inline
• A selected device may have its Venue Data cleared (including all Building, Floor and Room Venue data) by pressing the Clear Container button. This action takes place on applying current edits only and can be undone with the Undo Current Edits button
Devices not discoverable at the IP or HiQnet level
A device which is not discoverable at the IP level (invalid IP address etc) or HiQnet address level (HiQnet address conflict etc) will not be able to report its Device Name. In this instance, the Device Name field will display a ‘?’ to indicate that the field may exist but that the software does not have enough discoverability of the device to determine the value
A blank field or ‘-‘ implies the value is null
Hiqnet Audio Architect For Mac
Clicking in the Locate column for a device will put the corresponding device on the network into a Locate state, and the Locate icon will be displayed.
• Clicking an active Locate icon will disable the Locate state for the device
• Disabling the Locate state from the device will clear the icon
• Devices may be put into Locate state independently from selection so that more than one device can be located at any one time
NOTE: If you attempt to exit NetSetter without applying the edits, the following pop-up will appear:
Clicking 'OK' will apply the edits you have made since opening NetSetter.
Clicking 'Cancel' will return you to the program.