Configure Routers Menu
Use this command to setup communication between RouteMaster and the routers you want to control. This opens the
Manage Routers dialog:
- Routers – list of routers configured for this system.
Add Physical Router– button to add a router to the list.
Add Stack Router– button to add a stack router to the list.
Delete-remove selected router from the list.
Set as Master– button that sets selected router as the Master Router.
To start setting up your routers so that RouteMaster can control them you need to add them to the Routers list. Click the
Add Physical Router button to add a new router. By default a new Dummy Router appears in the list. Select it to display the router configuration tabs.
RouteMaster can control routers using the protocols shown in Appendix 1
RouteMaster allows you to edit Source, Destination and Level names to make them easier for users to understand. This is particularly useful when the router itself does not support names.
Routemaster will normally use names provided by the router. Any names specified in these tables will override the router’s own names
Use the three tabs called “Source Names”, “Destination Names” and “Level Names”. Just type in the name you want in the text edit field to the right of the input, output or level, to override the default name.
Changes to names are seen when the server is in Run mode.
RouteMaster allows you to define named groups of sources and destinations that are used by input and output group selector controls on web panels.
These work in a similar way to Router Group Map files in Helm.
RouteMaster lets you alter the relationship between the physical crosspoints on your router and the virtual crosspoints managed by RouteMaster. What do we mean by this?
If a control panel connected to RouteMaster sends a command to route source 8 to destination 11 for example, using mapping we can cause that make a route between physical input 3 and output 8. Here’s how this works.
The physical router has a source offset of 5 and a destination offset of 2. You set this up in the Mapping tab as shown below.
The first step is to check the Enable mapping box (1). Then you can set offsets for source, destination and level (2), and you can also change the mapped size of the router (3). These features are particularly useful with Stack Routers where several physical routers are controlled together.
You can use RouteMaster to combine different physical routers from different manufacturers into a single router system. This is done by setting up a Stack Router.
Let’s see how this works:
We use the Add Stack Router button (1) to create a new stack router, and in the General tab we give it a name (2), and set up the size of our virtual stack router (3).
Now we go to the Stacked Configuration tab to assign physical routers to our virtual Stack Router.
Using the dropdowns, we can assign a physical router (1) and a physical level (2) to each layer of our stack router. Stack routers can have up to eight layers.
For example, here we have assigned the first level of both physical routers to stack level zero in our stack router. So if we then make the Stack Router the Master Router, switching on Level 0 will switch will switch both physical routers.
Combined with crosspoint mapping, stack routers allow you to implement very powerful routing functions, for example switching of multiple crosspoints simultaneously for Ultra High Definition routing.
When the server is not running you can use this command to view and change the TCP/IP ports used by clients. When you select this menu a dialog opens with a tab for each supported protocol.
For example Evertz (Quartz) protocol uses port 2008 by default. Using this command you can change the port, and enable / disable the protocol.
For Web Panels you can also set the path used for the web panel files, as well as independently enabling the internal webserver.
This command shows and hides the application log window which is displayed at the bottom of the screen. The log is used for diagnostic purposes.
If Verbose logging is enabled in the Router configuration, all crosspoint changes are displayed in the log.