Comparing MMDVM/DMRGateway with openSPOT
Jul 27, 2017 3:03:29 GMT -8
Post by K6KD on Jul 27, 2017 3:03:29 GMT -8
MMDVM/DMRGateway access points (hot spots) are in the latest versions of the KB5RAB and Pi Star images.
Prior to DMRGateway, MMDVM access points allowed only 1 DMR server to be active at a time. Changing servers required editing or changing MMDVM.ini files and restarting the service, or rebooting. Because only 1 server was active at a time, there were no conflicts between time slots and talk groups on different servers.
With DMRGateway, up to 4 DMR servers can be simultaneously active (BrandMeister, DMR+, and 2 XLX DMR servers). To resolve conflicts involving time slots and talk groups, DMRGateway allows for time slot and talk group remapping. Specifically, the time slots and talk groups associated with DMR servers can be changed in the radio / access point interface. For example, an XLX talk group 4005 can be changed to talk group 64005. The radio would be programmed with this remapped talk group 64005.
What this means is the DMRGateway configuration needs to be consistent with the radio programming. Because many variations in DMRGateway configurations are possible, many variations in “code plugs” would also be needed. I think the potential complexity and confusion will be mitigated by common mapping schemes that are being illustrated in several example DMRGateway.ini files. These schemes generally do not remap BrandMeister, but remap DMR+ and XLX servers.
Now finally to the openSPOT….
openSPOT allows 5 profiles to be in the system. Each profile consists of a radio configuration and a network configuration. The profiles are independent of each other. Only 1 profile is active at a time, so the potential conflicts discussed above do not apply to openSPOT, and remapping is not provided or needed. But it is very easy to switch from one profile to another, either by web interface or radio command.
The difference in talk groups between MMDVM access points (hot spots) and openSPOTs generally means that for users with both MMDVM/DMRGateway access points and openSPOTs will need to have their radios programmed separately for each, especially for DMR+ and XLX use. Because different hot spots are on different frequencies (or should be!!!) they need separate programming anyway, so this is probably not a big issue.
Prior to DMRGateway, MMDVM access points allowed only 1 DMR server to be active at a time. Changing servers required editing or changing MMDVM.ini files and restarting the service, or rebooting. Because only 1 server was active at a time, there were no conflicts between time slots and talk groups on different servers.
With DMRGateway, up to 4 DMR servers can be simultaneously active (BrandMeister, DMR+, and 2 XLX DMR servers). To resolve conflicts involving time slots and talk groups, DMRGateway allows for time slot and talk group remapping. Specifically, the time slots and talk groups associated with DMR servers can be changed in the radio / access point interface. For example, an XLX talk group 4005 can be changed to talk group 64005. The radio would be programmed with this remapped talk group 64005.
What this means is the DMRGateway configuration needs to be consistent with the radio programming. Because many variations in DMRGateway configurations are possible, many variations in “code plugs” would also be needed. I think the potential complexity and confusion will be mitigated by common mapping schemes that are being illustrated in several example DMRGateway.ini files. These schemes generally do not remap BrandMeister, but remap DMR+ and XLX servers.
Now finally to the openSPOT….
openSPOT allows 5 profiles to be in the system. Each profile consists of a radio configuration and a network configuration. The profiles are independent of each other. Only 1 profile is active at a time, so the potential conflicts discussed above do not apply to openSPOT, and remapping is not provided or needed. But it is very easy to switch from one profile to another, either by web interface or radio command.
The difference in talk groups between MMDVM access points (hot spots) and openSPOTs generally means that for users with both MMDVM/DMRGateway access points and openSPOTs will need to have their radios programmed separately for each, especially for DMR+ and XLX use. Because different hot spots are on different frequencies (or should be!!!) they need separate programming anyway, so this is probably not a big issue.