- Recent Updates
- Access Control
- Amplifier
- A/V Receiver
- Climate and Pool Control
- Disc Player / Changer
- Display
- DSP
- DVR
- Irrigation / Sprinklers
- Lighting Control
- Matrix Switch
- Media Server and Player
- Multi-Room A/V
- Power and Rack Management
- Security
- Surveillance
- Teleconferencing
- Training
- Tuner
- Utility
- Video Projector
- Voice Control
- Recent Updates
- Access Control
- Amplifier
- A/V Receiver
- Climate and Pool Control
- Disc Player / Changer
- Display
- DSP
- DVR
- Irrigation / Sprinklers
- Lighting Control
- Matrix Switch
- Media Server and Player
- Multi-Room A/V
- Power and Rack Management
- Security
- Surveillance
- Teleconferencing
- Training
- Tuner
- Utility
- Video Projector
- Voice Control
Description:
This driver is for the SnapAV Binary series HD matrix switchers. It supports both serial and TCP/IP connection to the switch.
Version History:
Version 1.01 adds support for 500 series switches.
Version 1.1 expands driver to 16x16.
Version 1.11 has adjustments in parsing, polling, and initialization routines and now automatically turns the unit on during driver initialization.
Version 1.12 adjusts reconnect routine when using IP control and the driver looses communication to the switch.
Version 1.13 adds dynamic naming and reconfiguration.
Version 1.20 adds XPDiagnostics compatibility and various cumulative code improvements.
Version \1.22 Adjusts heartbeat mechanism for compatibility with newer Binary firmware versions and adjusts initialization variable issues when using serial control.
SnapAV Binary B-100/300/500 Series HD Matrix Switchers
This driver is for the SnapAV Binary series HD matrix switchers. It supports both serial and TCP/IP connection to the switch. Driver version 1.2 was tested with a B-500-MTRX-230-8x8, a B-100-HDMATRIX-8x8 (firmware version 98.01.1), and a B-100-HDMATRIX-4x4 (firmware version 1.07.01). Version 1.22 was tested with the above units along with a B-500-MTRX-230-16x16 with firmware version 1.00.47.
Revision History
1.0 The Initial release of the driver
1.01 Added support for 500 series switches
1.1 Expanded driver to 16x16
1.11 Adjusted parsing, polling and initialization routines.
The switch is now automatically turned on during driver initialization and is no longer selectable.
1.12 Adjusted reconnect routine when using IP control and the driver looses communication to the switch.
1.13 Added dynamic naming and reconfiguration.
Added text variables for input names, output names, and output route.
1.18 Added response timeout routine while set to RS232 connection type for B100 4x4 switches.
1.19 Adjusted Heartbeat command while using serial connectivity.
1.20 Added XPDiagnostics compatibility.
Adjusted driver code for minimizing commands that can be missed while switch is powering up.
Added Firmware Version variable.
1.21 Maintenance update.
1.22 Adjusted heartbeat routine for new SnapAV response format to the VR command.
Adjusted initialization variable authoring when using serial control.
Connection
TCP Connection
The Ethernet connection on the SnapAV Binary switch should be connected to the Network.
The SnapAV Binary switch can be set to a static IP address with the SnapAV configuration utility.
RS-232 Connection
The RS-232 connection on the switch should be connected with a straight-through cable to the processor.
The SnapAV Binary switch defaults to a baud rate of 9600.
Binary Switch Configuration
Output Count
Select the number of outputs on the switch. 4, 8, 16 are the supported selections.
Input Count
Select the number of inputs on the switch. 4, 8, 16 are the supported selections.
Output Configuration
Output Name
Enter the name for the specified output to be used throughout the driver.
Input Configuration
Input Name
Enter the name for the specified input to be used throughout the driver.
Driver Notes
- The driver uses a command stack for sending commands as HDCP negotiation timing can vary from system to system. When the negotiation is occurring the switch may not accept other commands sent to it, so the driver waits for a response from the switch which then allows the driver to send the next command. If using TCP and a response is not received within 15 second, the connection is closed and then reset after 10 seconds.
- The driver now issues a 'q' or quit command before closing the connection to the switch when needed. The 'q' command however cannot be issued if the processor loses power, therefore when the processor loses power the Binary switch may need to be rebooted.
- A system power off sequence needs to fully register with the driver before a Power On command can be executed. If a Power On command is issued while the system is still powering off, the Power On command will be ignored.