This was only meant to be a proof of concept for the MMDVM_CM software developer and others, with hard coded values. I was hoping to hear back from the developer by now, but I read some other posts on the MMDVM_CM github site and it looks like he is travelling for study/work pretty much full time these days, and isn't actively maintaining the MMDVM_CM tools. I rewrote my changes so that all variables that need to be changed for DMR2YSF TX to cross Wires-X nodes are user configurable via the DMR2YSF.ini file. The ini file my version is setup to behave the same as the current version of DMR2YSF, so effectively nothing changes until the end user makes settings changes. Here is a link to my fork of the MMDVM_CM software. All software is the same as the original except for the DMR2YSF software:
If access to DMR2YSF.ini (called simply /etc/dmr2ysf on a Pi-Star) is provided via the Expert menu, then end users could make the changes themselves that are required to communicate across Wires-X. I hope this will be added to the next Release Candidate.
Here is an example of settings that I use, and are hard coded in the patch I provided in the earlier post:
Code: Select all
[YSF Network]
...
RadioID=H5000
FICHCallsign=2
FICHCallMode=1
FICHBlockTotal=0
FICHFrameTotal=6
FICHMessageRoute=0
FICHVOIP=0
FICHDataType=2
FICHSQLType=0
FICHSQLCode=0
DT1=1,34,97,95,43,3,17,0,0,0
DT2=0,0,0,0,108,32,28,32,3,8