Menu

RouteMaster: Using Salvos

Overview

Salvos allow multiple routes to be easily made with a single button press or command. Salvos defined and stored by RouteMaster are called RouteMaster Salvos 

Some router protocols support salvos directly, where salvos are configured and managed by the router’s own software, and can be fired remotely by RouteMaster (or Helm). We call these salvos held by the router Device Salvos.  

Salvos can be triggered from Helm panels, Web panels, and Rascular’s ClockWork scheduler. Some 3rd party protocols that support salvo commands can also trigger salvos.

Salvo Definitions

Salvos can be defined in the RouteMaster UI. Each router has a Salvos tab which shows a list of configured salvos. (Salvos defined internally by the router are not shown  in this list). Salvos can be added, deleted or edited from this screen. 

Each salvo must have a unique name. The salvo ID is relevant when controlling RouteMaster with a protocol that uses numeric salvo IDs rather than names. Salvos are shown as a list of source/destination pairs, separated by the “>” character.

Sources and Destinations can be numeric (zero-based!) or use the appropriate source and destination labels. If using labels, the labels are only converted to numeric IDs when the salvo is run. Lines beginning with a ‘#” character are treated as comments.

Using Salvos from Helm Panels

Helm panels can access the list of available salvos using the SalvoNames property of the router. The FireSalvo command is used to actually trigger a particular salvo.

Lua
print (H.ROUTER.SalvoNames) -- print list of salvos to log
H.ROUTER:FireSalvo("Test 1") -- fire salvo "Test 1"

This Helm panel attached shows three common ways for triggering salvos:

  1. Button to fire a predefined salvo
  2. Select Salvo from dropdown, separate button to fire
  3. Radio Group shows available salvos

Download the panel  to experiment and use with your own designs.

Device Salvos

When RouteMaster receives a command to fire a salvo, it first checks if the salvo is defined as a RouteMaster salvo, and if so, runs it.  If the salvo is not defined as a RouteMaster Salvo, it’s assumed to be a Device Salvo and the salvo request is passed directly to the controlled router. Only the following protocols support Device Salvos. Some protocols use named salvos, others use a numeric ID. 

  • Evertz Quartz
  • Pro-bel SW-P-08
  • Sierra Aspen
  • PESA P1N
  • Harris LRC
  • GVG Native
  • Rascular Dummy Router – reports four predefined salvos.
  • Rascular Websocket API

RouteMaster can also receive commands to fire salvos from the upstream clients using the protocols above, 

  • Evertz Quartz
  • Pro-bel SW-P-08
  • Sierra Aspen
  • PESA P1N
  • Harris LRC
  • GVG Native
  • Rascular Websocket API

 

User Guide