forum.pistar.uk

Has anyone had any luck getting this Going..

Been Trying to follow the Directions but at this time the Options do not come up..

Rob..

MW1COE

https://github.com/nostar/MMDVM_CM

This thread may help provide insight:

viewtopic.php?f=24&t=2724

It all works well if you follow the instructions, make sure you edit the .ini files with your own details and make sure all the file paths are pointing to valid locations.

I am trying to install DMR2P25 and connect on TG 32000 on a specific P25 DVMega server. Where do I set this information.
I need to set and ipaddress (A.B.C.D and a port 41000)
I edited the dmr2p25.ini file and placed it in /etc/ ( changed callsign and id, and set paths for .dat and log files)
I started p25gateway manually as suggested, it starts ok
I started dmr2p25 manually as suggested and get a lockup as indicated here. just sits here forever.
In another ssh connection I see that dmr2p25 is not running

I: 2020-08-10 22:54:52.350 MMDVM Network Parameters
I: 2020-08-10 22:54:52.350 Rpt Address: 127.0.0.1
I: 2020-08-10 22:54:52.350 Rpt Port: 62032
I: 2020-08-10 22:54:52.350 Local Address: 127.0.0.4
I: 2020-08-10 22:54:52.350 Local Port: 62037
M: 2020-08-10 22:54:52.350 MMDVM Network, Opening
M: 2020-08-10 22:54:52.350 Waiting for MMDVM to connect.....

There must be something I am missing in the setup instructions.

I tryed changing the host file string from
DMR2P25 0000 127.0.0.4 none 62037
to
DMR2P25 0000 A.B.C.D none 41000

but this did not help

Well... the first thing that catches my eye is that 127.0.0.4

127.0.0.1 is the IP address of the loopback device -- ie; for traffic going from one application on the device to another application on the same device.

127.0.0.1 is the ONLY IP address known in the 127.x.x.x world.

Not entirely true /usr/local/etc/DMR_Hosts.txt
##############################################################################################
#
# DMRGateway / Internal Hosts Below
#
##############################################################################################
# Name DMR-ID IP/Hostname Password Port #
##############################################################################################
DMRGateway 0000 127.0.0.1 none 62031
DMR2YSF 0000 127.0.0.2 none 62033
DMR2NXDN 0000 127.0.0.3 none 62035
##############################################################################################
---------------------------------------------------------------------
added
DMR2P25 0000 127.0.0.4 none 62037

The lockup occurs here in an endless loop reading DMR network

LogMessage("Waiting for MMDVM to connect.....");
------------------------------------------------------------------------------------
while (!m_killed) {
m_configLen = m_dmrNetwork->getConfig(m_config);
if (m_configLen > 0U && m_dmrNetwork->getId() > 1000U)
break;
m_dmrNetwork->clock(10U);

CThread::sleep(10U);
}
-------------------------------------------------------------------------------------------
if (m_killed) {
m_dmrNetwork->close();
delete m_dmrNetwork;
return 0;
}

LogMessage("MMDVM has connected");

VE3RD wrote: ↑Tue Aug 11, 2020 8:32 pm Not entirely true /usr/local/etc/DMR_Hosts.txt
##############################################################################################
#
# DMRGateway / Internal Hosts Below
#
##############################################################################################
# Name DMR-ID IP/Hostname Password Port #
##############################################################################################
DMRGateway 0000 127.0.0.1 none 62031
DMR2YSF 0000 127.0.0.2 none 62033
DMR2NXDN 0000 127.0.0.3 none 62035
##############################################################################################
---------------------------------------------------------------------
added
DMR2P25 0000 127.0.0.4 none 62037

Well... Okay... I'd consider that a perversion of "localhost" since the combination of IP/port is what should be listened for -- and "localhost/p#" should be valid (note that even that listing says "IP/Hostname"), and "localhost" => 127.0.0.1

Okay, Wikipedia states that all 127.x.y.z are considered loopback, but also mentions that not all OS support those others. It also mentions that they can be used to allow multiple servers all listening to the SAME port # -- which doesn't apply above.

Getting Closer
Cleared the lockup . It was a mismatched port issue

Now I get a data error, and a report that it is not registering a connection to the server

D: 2020-08-11 23:10:46.313 Network Received
D: 2020-08-11 23:10:46.313 0000: 44 4D 52 44 11 2E 24 52 00 7D 00 12 06 30 10 84 *DMRD..$R.}...0..*
D: 2020-08-11 23:10:46.313 0010: 60 26 09 5C 22 00 02 04 02 20 40 44 00 22 00 02 *`&.\".... @D."..*
D: 2020-08-11 23:10:46.314 0020: 04 01 51 B8 22 2D 80 72 20 40 44 00 22 00 02 04 *..Q."-.r @D."...*
D: 2020-08-11 23:10:46.314 0030: 02 20 40 44 00 00 2F *. @D../*
D: 2020-08-11 23:10:46.326 P25 Network Data Sent
D: 2020-08-11 23:10:46.326 0000: 6E 00 00 00 00 01 5F 02 02 00 00 00 00 00 00 09 *n....._.........*
D: 2020-08-11 23:10:46.326 0010: 02 *.*
E: 2020-08-11 23:10:46.327 Error returned from sendto, err: 22
D: 2020-08-11 23:10:46.342 P25 Network Data Sent
D: 2020-08-11 23:10:46.342 0000: 6F 00 00 00 00 01 5F 02 02 00 00 00 00 00 00 09 *o....._.........*
D: 2020-08-11 23:10:46.342 0010: 02 *.*
E: 2020-08-11 23:10:46.343 Error returned from sendto, err: 22

Likely not helpful but...

Linux error code 22 is "invalid argument"