JacobC
I have a new OpenSPOT2 with the latest firmware.
I have a new BTech DMR-6x2 with the latest firmware.
I have already run AutoCal.
On any outgoing transmission (from me), including every echo test, audio is fine for approximately 1 second, then drops out for about 1 second, then the rest is fine, no matter how long.
I hear no issue on incoming transmissions from other stations.
I've tested Analog, and it seems to be working fine.
Any ideas?
Thanks,
-JacobC
HA2NON
Does this also happen in a local echo test if you call the openSPOT2's local echo DMR ID? (9999 by default)
Do you see any relevant info in the device log?
JacobC
This does happen in the local echo test consistently. That is how I noticed the problem. I then had several contacts verify they are hearing the issue from me, in a normal talk group.
I tested to the echo service, this morning, and did not notice anything obviously amiss in the call log and the normal log. That said, I'm not certain what I should be noticing, not to mention someone must have cross-linked TAC 310 to some static talk group I have, and was somewhat busy. That muddied up the logs a bit.
I ordered another radio, so when that arrives I'll be able to hopefully rule out a physical radio problem.
If you have any other ideas / suggestions, please let me know.
Thanks.
kd2pm
I may have had a similar issue. When I would use my Alinco MD5 and used the audio test TG, I would hear the 1st 2nd, it would drop then I would hear the rest fine. I have made some changes to the hang timer from 3 seconds to 5 seconds on both the radio and the OS2 and I need to do some more testing but it may be a timing issue between the radios settings and the OS2 settings??
JacobC
Thanks for the info. I haven't made any changes, other than letting AutoCal do it's thing.
I'll take a look at that, when I return home, this afternoon.
It was hard to believe I was the only one that had this specific issue. However, I haven't seen any mention in all of my research.
Thanks again.
-KG5UEK
JacobC
Well, setting the hang time to 5000 ms didn't help, unfortunately.
I set it back to 3000 ms.
Here is a sample log with me testing the echo (9999):
17:43:36 httpsrv[0]: websocket opened with token 12e078ba
17:43:36 httpsrv[0]: websocket opened with token 12e078ba
17:43:39 homebrew: ping sent
17:43:39 homebrew: pong received
17:43:43 dmrcalltracker [0]: prv voice call started, dst: 9999 src: 3129786 id: 421816cc4c62ecda
17:43:43 nvmm-csd: looking up id 9999 type 0
17:43:43 nvmm-csd: dmr ids 9998,9999 nxdn ids 9998,9999 call "OPENSPOT" name "" city "" state "" country ""
17:43:43 nvmm-csd: looking up id 3129786 type 0
17:43:43 nvmm-csd: dmr ids 3129786 nxdn ids 244 call "KG5UEK" name "Jacob A" city "" state "" country "us"
17:43:43 dmrechoprocessor [0]: echo rec start
17:43:45 homebrew: ping sent
17:43:45 homebrew: pong received
17:43:46 dmrcalltracker[0]: call ended, dur 3.4s ber 0.7% loss 0.0% rssi -46
17:43:46 dmrechoprocessor [0]: echo rec stop
17:43:47 dmrechoprocessor [0]: start sending reply (3412 ms)
17:43:50 dmrechoprocessor [0]: reply send finished
17:43:51 homebrew: ping sent
17:43:51 homebrew: pong received
Here is a sample call log from an earlier echo test:
At To From EntryType Duration (s) BER (%) Loss (%) Avg. RSSI (dBm) Remarks
2019-02-05 13:31:49 OPENSPOT (9999) KG5UEK Jacob A (3129786) start 0 0 0 0 Private DMR voice call from modem
2019-02-05 13:31:54 OPENSPOT (9999) KG5UEK Jacob A (3129786) end 4.9 0.5 0 -46 Private DMR voice call from modem
2019-02-05 13:31:55 KG5UEK Jacob A (3129786) OPENSPOT (9999) start 0 0 0 0 DMR local echo reply
2019-02-05 13:31:59 KG5UEK Jacob A (3129786) OPENSPOT (9999) end 4.9 0 0 0 DMR local echo reply
I should have another BTech DMR-6x2, tomorrow, to see if the issue persists with another radio of the same model. I guess I'm hoping it is radio issue. Because, if it isn't then, I'm not sure where else to look.
Any other ideas would be greatly appreciated.
-KG5UEK
DMRShark
So, I believe this is a BrandMeister issue. When I can get their 9990 Parrot mode to work, it would always cut off after the first 1st second, drop and come back just as you described.
However, once I started using OpenSpot's local 9999 Echo test mode... there is no issue. Only when using 9990. So, make sure you're not confusing BrandMeister's 9990 (which goes through the whole network and back to you), with OpenSpot's 9999.
I keep both programmed, because I can test my local radio's audio to the OpenSpot... then compare it through the whole network... and you can hear any further degradation issues the network introduces... (comparing radio-->OpenSpot).
I hope this helps. But your not alone on the issue. I've always chalked it up to BrandMeister.
JacobC
Thanks for the response, DMRShark.
I'm glad I'm not alone.
That said, 9999, at least for me, as far as I can tell, is the OpenSPOT2 configured talk group for the echo service. Maybe I should change it to 9990 in the OS2 config and test like that, in case there is some routing confusion. I may test that, in a bit.
in any case, unfortunately, my issue isn't just with whichever echo / parrot TG. I've had confirmation from QSOs that my normal TXs to any TG seem to drop for a second or so, after a second or so. So, I basically wait at least 2 seconds before talking, after keying up.
It's still workable. But, I know several people have to be using the same model radio on OS2. Or, maybe I'm wrong. In any case, I have confidence we'll all figure it out.
Thanks again for the input. I'll probably re-configure the echo TG ID and test, just to make sure.
-KG5UEK
JacobC
Well, I just received the new radio.
I did not upgrade the firmware, nor configure anything via the software.
I just tested the echo service on the OpenSPOT2.
I am experiencing the same issue.
Any ideas?
Thanks,
-KG5UEK
DMRShark
...I've had confirmation from QSOs that my normal TXs to any TG seem to drop for a second or so, after a second or so. So, I basically wait at least 2 seconds before talking, after keying up.
It's still workable. But, I know several people have to be using the same model radio on OS2. Or, maybe I'm wrong. In any case, I have confidence we'll all figure it out.
Thanks again for the input. I'll probably re-configure the echo TG ID and test, just to make sure.
-KG5UEK
That's what I was wondering... if it was confirmed on all calls. So, my experience might be different. Because I had it confirmed that my transmissions (other than Parrot) were not cut off (or dropping off for a second).
I believe (by default) OpenSpot uses 9999 for the local echo back. As long as that number wasn't changed in the OS interface... adding a TG9999 (as a private call) in your radio, should allow you to confirm the problem isn't happening between your radio and the OpenSpot.
I never experienced that dropout on TG9999, only on BM Parrot TG9990.
JacobC
Thanks for that, DMRShark.
I changed the Echo / Parrot ID to 9990.
I tested, and it worked fine.
That is some weird stuff.
I'll try a few contacts in real TGs, this evening, and see if they can confirm whether I'm still having that issue there.
Thanks!
-KG5UEK
JacobC
Well, after further testing, it indeed is still having the issue on the OpenSPOT2 echo / parrot talk group configured for 9990. Oh well.
I'll still do further testing with a normal talk group, when I have a few minutes.
Without more to go on, maybe I'll get a different radio to test.
-KG5UEK
JacobC
I changed the echo / parrot in the OpenSPOT2 back to 9999.
I made a test to Brandmeister 9990, and it seems to work fine.
So maybe my only issue is to the OpenSPOT2 parrot TG.
I don't know anymore LOL.
I'll test further with regular TGs.
Thanks for all the input, everyone.
-KG5UEK
JacobC
Oh, just to mention, I tested on a second OpenSPOT2 and had the same results.
-KG5UEK
DMRShark
Maybe it's something in your code plug?
I had the same issue on a Pi-Star, OpenSpot and OpenSpot2... all with the same result.
That said, I haven't tried it in awhile. I think it's BrandMeister.
DMRShark
By the way... last night when leaving work I tried BrandMeister's Parrot 9999 (on the radio I was having the 1 second drop outs on)... and it worked perfect. No drop out.
That was on an OpenSpot2 (again originally I had the same issue). I believe it's BrandMeister being flaky on TG9999. Sometimes, I can't get any echo back from it. Other times, it's perfect.
Check further when making contacts with others... get them to confirm if your still having drop out issues or not.
Good luck.
JacobC
Thanks DMRShark.
I ordered a TYT 380 radio, and an Anytone 878 (which is basically the same as my BTech ones, since they make it.)
We'll see how that tests out.
In any case I appeciate you coming back.
I loaned a DMR radio to my buddy, to use with his OpenSPOT2. He's had great success in normal talk groups. Though he's had the same parrot issues.
I had a trip out of state to Dallas, this weekend, so stopped at HRO and grabbed a Zumspot, just to see. And, of course, it won't boot properly LOL. I really figured I'd just try it out with my Fusion radios.
I've owned an IT company for 20+ years, and have a ton of Unix / Linux / Raspberry Pi experience. I'll start troubleshooting that, tomorrow LOL.
Again, thanks for the added information. I'll respond to this thread with any testing I do with the other two radios, just for people that may have this issue in the future.