Closed nostar closed 3 years ago
I rewrote my changes as configuration variables for radio ID, DT1/DT2 (DCH bytes for VD2 frames 6 and 7), and the required FICH variables. Now, no longer is anything hard coded into the source code, and it is up to the end user to make setting changes and provide a radio ID via the ini file in order to use DMR2YSF over networks using Wires-X. I created a fork of this repo with these changes, since it sounds like you aren't around to look at this much these days. The default ini settings in this fork keep things pretty much as they were without my changes. I hope when you see this you decide to apply the changes to your repo, then I will ditch my fork.
-Doug AD8DP
Thank you very much Doug AD8DP for your work. Sorry to respond to this so late, I haven't had enough time for checking this properly due to my work load. Fortunately @AndyTaylorTweet has tested your work in Pi-Star and summited another PR recently based in your work.
Hi Doug,
Any chance that this awesome work might be exported to DVSwitch? Thanks Mike IK7VXC
It seems that Yaesu has recently released new server software that broke the DMR2YSF feature of MMDVM based hotspots like Pi-Star. DMR users can no longer be heard across Wires-X links that run this new server software, which is causing all kinds of confusion on various repeaters/reflectors because people have been hearing a lot of one sided conversations lately. I made some changes that overcome this problem, and posted a detailed description of the changes on the QRZ forum. A link to that post can be found on my QRZ page for AD8DP. I wanted to create that post on the Pi-Star forum, but I'm going on day 2 now waiting for manual activation.
My patch simply hard codes everything in the source code as sort of a proof of concept, but I think maybe it could be implemented in a way that would require the end user to specifically enable these changes by way of an ini/conf file which could be accessed by the Expert menu, for example.