juribeparada / MMDVM_HS

MMDVM HotSpot: firmware for ZUMspot or MMDVM_HS based boards (D-Star, DMR, YSF, P25, NXDN and POCSAG)
GNU General Public License v2.0
345 stars 141 forks source link

Revisit COS Timing Issue with Duplex MMDVMs #126

Open JeffHochberg opened 3 years ago

JeffHochberg commented 3 years ago

The issue documented in https://github.com/juribeparada/MMDVM_HS/issues/70 - Duplex problem when replying to over after leaving a pause for other stations - needs to be revisited.

I own a duplex MMDVM and have been experiencing an issue where it does not respond to keying after another station ends its transmission. I contacted the manufacturer and they clued me into this issue.

I initially thought it was an issue with the RXOffset/TXOffset values. I adjusted them to the point where my BER is incredibly low (at most 0.02% to 0.05%). I am using Motorola DMR radios (XPR 7550, XPR 5550e, and XPR 4550). I have verified that the alignment in all of my radios is accurate.

I've also tried adjusting the offset and hang values and I don't see any improvement. The only thing that helps is waiting a second or two for the COS LED to illuminate. Having to monitor the status of the COS LED is not realistic as it's not reasonable to assume the user will be close to their hotspot.

@juribeparada I understand that you are busy and have not been able to return to development for quite some time. The last official build was in May of 2019 and the most recent beta build was in December 2019. Is there anyone else involved in the development of the MMDVM firmware or is the MMDVM_HS project dead at this point?

rd0fun commented 3 years ago

I have experienced the same issue.

JeffHochberg commented 3 years ago

It's made my duplex MMDVM unusable. It would be nice to understand if it's something that will be addressed or if it's not even being considered. I'd prefer to know what the intent is that rather than have the issue left open/unresolved.

On Mon, Jan 18, 2021 at 7:48 PM rd0fun notifications@github.com wrote:

I have experienced the same issue.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/juribeparada/MMDVM_HS/issues/126#issuecomment-762533535, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJL7HZ3332EILTIXDVFZMTS2TJFJANCNFSM4RWHQXJA .

stevelenti commented 3 years ago

With the n5boc duplex board I am seeing the same issue. I have been able to mitigate this with using these settings https://www.k2ie.net/blog/2020/05/08/duplex-hotspot-reliability-revisited/

It still happens but not nearly as much and makes the board very usable in duplex mode. Now the n5boc boards are much better quality than their Chinese counterparts so your results might not be as good using the settings above.

I'm not a programmer but since I can adjust settings to mitigate the issue it seems to me that there must be a way to program a fix into the firmware.

-Steve

macroexp commented 1 year ago

@stevelenti the settings you linked to made a huge difference for me. My MD-380 only fails handshake maybe 5% of the time now, compared to nearly 100% of the time before changing settings. I am going to keep fiddling to figure out what the critical setting is, but thanks for the link.

stevelenti commented 1 year ago

@stevelenti the settings you linked to made a huge difference for me. My MD-380 only fails handshake maybe 5% of the time now, compared to nearly 100% of the time before changing settings. I am going to keep fiddling to figure out what the critical setting is, but thanks for the link.

@macroexp Try these settings. You might need to adjust the RXOffset and TXOffset for what gives you the best BER for your board. These settings have been the best hands down with absolutely no issues. Let me know if it works for you. Pistar duplex 2 Pistar duplex 1

-Steve