Skip to content

Riedel Mediornet

RouteMaster VR can control Riedel MediorNet systems using Pro-bel SW-P-08 protocol.

There are a few issues to be aware of:

  • Port 5555 is used for comms.
  • Riedel does not support mnemonic names for source and destinations
  • Riedel does not support lock or protect status

ID-based routing

MediorNet and similar systems use ID numbers to refer to sources and destinations which do not directly correspond to physical ports. These ID numbers are typically large, with source IDs starting at (for example) 10,000 and destination IDs at 20,000.

This is not an ideal fit for RouteMaster VR's matrix-based control model, which typically expects sources and destinations to be sequentially numbered from zero or one, without large gaps.

Let's say you have a MediorNet system with 100 sources and 100 destinations, with source IDs from 10,000 to 10,099 and destination IDs from 20,000 to 20,099. To configure this in RouteMaster VR you'd define the base router as having 10100 sources and 20100 destinations, so all IDs fit within the defined ranges.

alt text

This isn't ideal, as when RouteMaster VR is communicating with client systems it will be sending large amounts of blank data for the unused IDs. To avoid this you should use the Mapping feature to set offsets of 10000 and 20000 for source and destination IDs, and to limit the effective size .

alt text

From a control client's perspective, the router will now appear to have 100 sources and 100 destinations, with IDs from 0 to 99. RouteMaster VR will automatically apply the configured offsets when translating between client commands and the underlying protocol.

This technique should be used with other routers that use high-numbered IDs, to improve performance and reduce memory requirements.