-
Notifications
You must be signed in to change notification settings - Fork 1
Home
#DVImatrix848
Remote Control for an 8x8 DVI routing matrix
##Introduction
DVImatrix848 allows you to remote-control a DVI routing matrix via an RS232 (aka serial line).
Currently supported devices
- Gefen EXT-DVI-848
If you do not have one of the supported devices, DVImatrix848 is of very limited use (if any)
Connect you DVI matrix device to your computer via a serial cable.
##Usage
On start, the application will scan for available serial ports. It will try to connect to the port it used last time, and - if that fails - will chose one of the available ones.
Once you are connected to the serial port, you can then choose an input (listed in the left-most column) for an output (as listed in the top-most row) (and repeat ad lib).
The used serial port can be changed via the "Configuration" menu. If the desired serial port does not show up, select Rescan to scan for newly attached serial devices.
You can change the labels for the inputs and outputs by pressing Ctrl+E, which will make the labels modifiable. Once you have edited all labels to your satisfaction, press Ctrl+E again. The new labels will be saved when you quit the application via Ctrl+Q.
The number of inputs and outputs can be changed by editing the configuration file, and appending (or deleting) new labels in the input (resp. output) section.
On W32 you can find the configuration file in %AppData%\DVImatrix848\setup.json (the actual value of %APPDATA% depends on your setup, but is typically something like C:\Users\fudel\AppData\roamin).
On unix-like systems (like Linux), the configuration is stored in ~/.config/DVImatrix848/setup.json (with ~ being your home directory)
The application will query the current routing state from the device either when the user clicks on the Get State button in the upper-left corner or when the application connects to a new serial port (either on application startup or when the user selects a new serial port via the menu).
This can be configured via the fetchstate value in the configuration file (in the generic section).
Possible configurations are:
-
never(do not fetch the routing state from the device) -
automatic(fetch the routing state on startup and when a new serial port is selected) -
interactive(fetch the routing state when the user requests it via the Get State button) -
always(both automatic and interactive fetching of the routing state)