ZS1I MMDVM / DMR Repeater issues and how to fixed them.
In the last week or two I ran into some issues regarding the DMR Repeater we are using in the Southern Cape Area. Now some might one day run into the same issues and I therefor decided to write this article on how to fix the issues.
Here is the issues I experienced:
- DMR Repeater does not except any "calls" from my trusted TYT MD380 and Hytera MD785G radios.
- The Huawei B525 Router used with the DMR Repeater all of a sudden could not access the Internet.
- I used my Windows computer to program the TYT MD380 HT radio in the past. This time around I could only read the radio but the CPS Firmware refused any other command and would crash as soon as I enter any information.
The above "errors" apart from being frustrating kept me busy for a few days while fault finding. Now let's look at each "error" individually.
DMR Repeater does not except any "calls" from my trusted TYT MD380 and Hytera MD785G radios.
Background: The repeater and the two radios worked flawlessly until one morning when I started / rebooted all three items. Please not all three items was shut down properly the night before. Never ever hotplug any cables to any of the above radios, hotspot or raspberry pi!! Well I did not. I hear some of you say but it must be a problem with the DMR Repeater. I also thought so and worked through all the settings of the repeater firmware, calibration and hardware setup. This took at least two days, working on and off as I find the time. No luck at all. It seems if all three radios just decided to be like a stubborn donkey. Well the next possible fix was to replace the WSPD firmware which I used a the time with Pi-Star firmware. It might have been a firmware "glitch" as my grandson named software issues. I took out the WSPD card and re-write a new SD card with the Pi-Star firmware and slotted it into the Raspberry Pi. No change so I made the assumption that there was nothing wrong with both firmware's. Just as I side-note using DroidStar was working fine on the DMR Repeater, DMR Bridge and ZS Link Hub. I looked at Brandmeister under My Devices and every device in used reflected that it was active and working. ID's matched the devices and Static Talk Groups were set. All that was left was to go through the CPS files of the 2 RF Radios. I thoroughly scrutinized the CPS files but could not find any issues. I started running out of options but somewhere there is a problem and that needs to be fixed.
The error / errors: If I could get one radio to work the other one would be fixed instantly. I needed to look deeply into the error issue. I used the TYT MD380 Radio to label the error. Error = The radio would TX for a short period and then a error beep would sound. The LED on the radio goes red when TX'ing but then alternate between red and green. The DMR Repeater screen stays in the default display while the RX and TX radio LED's will light up as it should. Nothing else happens and this indicate that the MD380 radio does not open the repeater. I hear you shout Talk Group, Color Code, Time Slot, Calibration, TX and RX Frequency, RX Group List and Zone. Well checked all of that with no joy!
To solve the issue: The solution to the problem was quite easy and mainly overlooked. It was a DMR ID issue that was solved by just deleting two numbers. Let's look at the solution. I use a 7 number DMR ID and for the purpose of this article I will use 655xxxx. Let's to to Configuration in Pi-Star. Move down to General Configuration and find CCS7/DMR ID. The ID must be 655xxxx (7 Digits). At the same time make sure that your Hotspot Security Password in DMR Configuration is correct. Also ensure that in DMR ESSID there is no ESSID. It should look like this 655xxxxNone. Now click on Apply Changes and wait for the screen to return. Once the changes were set go to the top of the page and look for Expert. Click on Expert.and then on MMDVMHost. Under the General Tab ensure that the Id is the seven number 655xxxx. Now go down to the DMR Tab and this is where my error originated. Go to Id en make sure that you enter the 655xxxx number. For some rime or reason my Id looked like 655xxxx05. Do not ask me where the two last digits came from. These two numbers created the following number in BrandMeister under My Devices = 655xxxx05 which displayed a green hart as well as 655xxxx which also displayed a green hart. In other words this caused all sorts of mayhem albeit the DMR Repeater not working as it should.
I removed the 05 and rebooted the repeater and wallah the repeater came to life and work as it should. As mentioned before "The solution to the problem was quite easy and mainly overlooked.". The error hiding away until I found it. I am now able to use both DMR Radio to talk to the repeater without any hassles. The repeater can also be linked to the ZS Link Hub providing a further extension of the ZS Link Network. With this problem sorted let's move on to the next "glitch".
(Click on image for larger view.)
The Huawei B525 Router used with the DMR Repeater all of a sudden could not access the Internet.
Okay I must admit that on of the computer I use in the Shack is rather ancient. It runs Window 7. Now I mainly use this computer to monitor nodes, repeaters, bridges etc. I have 3 routers in my shack running different equipment on them. The Huawei B525 Router is used with the DMR Repeater. The router is setup correctly and was working correctly when all of a sudden I would receive the following error message after a reboot of the machine.
"no internet access DNS server isn't responding"
Now I did not have any time to go into a detail setup / search through the firmware of the computer. I found the following solution to the issue.
To fix "DNS server isn't responding," restart your router and modem, clear your browser/system cache, and try flushing DNS via Command Prompt (ipconfig /flushdns). If issues persist, switch to a public DNS server (like Google’s 8.8.8.8 and 8.8.4.4), update network adapter drivers, or temporarily disable firewalls/VPNs.
- Restart Hardware: Power-cycle your router and modem (unplug for 30 seconds).
- Flush DNS Cache: Open Command Prompt as administrator and type
ipconfig /flushdns. - Switch DNS Servers: In network settings, change IPv4 DNS to
8.8.8.8(Preferred) and8.8.4.4(Alternate). - Disable Third-Party Antivirus/VPN: These can often block DNS requests.
- Check Physical Connections: Ensure Ethernet cables are secure, or try a different cable.
- Update/Reinstall Network Adapters: Open Device Manager, find your network adapter, and check for driver updates.
- Disable IPv6: Sometimes switching to IPv4-only fixes connectivity.
(Click on image for larger view.)
Needless to say the only solution that worked for me was the following: (See image above)
I used my Windows computer to program the TYT MD380 HT radio in the past. This time around I could only read the radio but the CPS Firmware refused any other command and would crash as soon as I enter any information.
Onto the final "glitch". I use stock standard firmware and cable to program my TYR MD380 HT Radio. This time around I received an error in Chinese stating that Microsoft will be looking for a solution. Now we all know running a Window 7 machine will result in no feedback, response or support. I expected the problem to be driver related and removed the old drive and install the latest version. Well still no joy. Scratching around the Shack I found my old Windows XP laptop which already had the CPS and driver installed. Success on the first try. The radio was read and write with the necessary changes without any issues.
Moral of the story - Never get rid of your old computers. They can help you out when the newer one's are stubborn and "glitchy".
With the three issues solved the DMR Repeater is now operational in the Mossel Bay Area. Unfortunately the cooling fans are making quite a bit of noise and will have to be replaced. I ordered two fan speed controller and as soon as they arrive I will fit the new fans on the repeater.
Finally: I trust that this article would be of some benefit to those who might experience the same issues. For many this might be general knowledge but for others it might be helpful. I have quite a few "tricks up my sleeve" in the future regarding this repeater. If you interested in how one can use this repeater to it's full potential then do not miss Part 4 and Part 5. Even better come and join in the fun!
