1185 - MMCT Upgrade
DMO Networked Radios Software Update and Configuration
Download the MMCTSound executable and unzip it to: C:\Program Files\C130Sound. The name of the sound application has changed from C130Sound.exe to MMCTSound.exe. The new executable is the same as the original plus the DMO radio update. To start the sound application, launch MMCTSound.exe.
Download DisCommWin and unzip it to: C:\Program Files\C130Sound\data.
Merge the following configuration file with your existing C130Comm.cfg file by copying sections: [DIS], [Global], [HF1], [HF2], [VHF1], [VHF2], [UHF1], and [UHF2] from the new config to your existing. Also copy "CaptureSize" and "UseDSCapture" from the [Audio] section of the new file to your existing. In the [DIS] section, modify the "BroadcastIP" parameter to the subnet of your DIS network.
The following document describes the new entries in the C130Comm config file:
DMO Networked Radios Test/Verification Procedure
In order to test the networked radios in a stand-alone configuration, you will need to setup two radios to allow the application to "talk to itself". This will verify proper network and audio configuration. After that is verified you can attempt to communicate with other entities on the network. The following steps describe how to use HF1 and HF2 to test in a stand-alone configuration. You could also use VHF1 and VHF2 or UHF1 and UHF2 in the same manner.
- Before launching MMCTSound.exe, modify the frequency of HF1 and HF2 so that they are the same; e.g. set both "Freq" parameters in [HF1] and [HF2] to 3100000.
- Start the MMCTSound application and prepare to transmit from the HF1 radio. At the same time have the same station or another station prepared to monitor the HF2 radio.
- Transmit from the HF1 radio - it should be received on the HF2 radio. If you hear an echo, that is OK and actually an indication that everything is working properly - the transmitted voice is being routed through the AudioFire mixer and at the same time is being routed through the DIS network. The voice that is packetized and routed through the network has a slight delay which is what causes the echo.
- After verifying that networked transmit and receive are working, set the HF1 and HF2 frequencies back to different values.
Use our debugging tool, DisCommMonitor, to view all DIS radio packets on the network and to view individual PDU contents:
