Cannot connect to Brandmeister network

[G4TVP]

I *assumed* (as a newbie) that it would only be connecting to one server, as my DMR master is set to "BM_United_Kingdom_2341" in the configuration tab.

However, the "Expert" quick edit lists : "XLX Network, DMR Network 1, DMR Network 2, DMR Network 3" (all of which are not enabled), so I am confused as to what/who it's trying to connect to. How do I make it only talk to BM?

It would be really useful to compare my configuration against a working copy.

[G8SEZ]

You definitely need to turn off the DMRGateway, literally just run the DMR service with nothing else enabled.

[G4TVP]

I got it to work for about 5 seconds and then hangs, until I reboot it. Oddly Dstar works absolutely fine.

When I've got a few pennies to spare, I think I might buy a new one, any recommendations?

[G4TVP]

Thank you for your reply.

Firstly, it seems setting the configuration on the basic window alone doesn't work. It leaves in the default userid as 1234567, which is then picked up by the startup script as "incomplete" and it aborts starting the daemon. I've debugged the script as much as I can, and can see where it stops.

Code: Select all

if [[ $(egrep -h -i "1234567|M1ABC" ${CONFIG} | wc -l) -gt 0 ]]; then
  exit 1;
fi

I have already setup a (non default) password on BM self-care and entered this into the configuration. In fact, I believe I've changed it a couple of times now to be sure it was correct and have done it again.

Why would purchasing another hot-spot not resolve these issues ?

E: 2020-07-24 18:42:20.584 MMDVM RX buffer has overflowed
E: 2020-07-24 18:42:20.836 MMDVM RX buffer has overflowed
E: 2020-07-24 18:42:22.843 No reply from the modem for some time, resetting it
M: 2020-07-24 18:42:22.843 Closing the MMDVM
M: 2020-07-24 18:42:24.843 Opening the MMDVM
E: 2020-07-24 18:42:37.673 Unable to read the firmware version after six attempts

This cheapie hotspot has worked fine on Dstar, but alias doesn't want to play ball when it comes to DMR.

[G8SEZ]

You should be able to enter your DMR ID on the expert page in the DMR section.

Not sure why the basic page isn't working, can only think there is some sort of problem where the filesystem stays in read-only mode.

[G4TVP]

I have downloaded the latest version of Pi-Star this week (4.1.2) on the recommendation of Brian. All I did was put into the basic config my DMR id, selected BM UK and entered my self-care password. The SD card Iam using is a Kingston SDHC/16gb (class 10). We have been using these for about a year, without issue.

I really don't want to change anything on the Expert configuration, but the stock firmware just leaves the DMR id of 1234567 in there, so had no choice but to change that, otherwise I can see the script would fail.

My question would be, are the errors I am seeing (see my last post), indicative of a hardware failure or software configuration? I've asked a couple of times for the complete config, so I can try that, but to no avail.

[G8SEZ]

Have a look at your email Mike

[G4TVP]

Thankyou, will try tonight

[G4TVP]

Hi Brian, I've tried using the configuration you sent me, and I still get the same result, which is :

E: 2020-07-25 16:52:44.137 Unable to read the firmware version after six attempts

Monitoring the frequency with my analog handie, I can hear an open carrier on 438.6375.

Just to be sure, I've tried mounting the MMDVM on a Pi-Zero I had here already and I get the same result. I think we can say this board is not working?

Can this boards (MMDVM) be purchased still. I can see Zumspots and OpenSpots, but they are expensive.

[G8SEZ]

Sounds like there is something not right, but fault-finding is not too easy

You could look at this link:

https://www.ebay.co.uk/itm/Hot-Jumbospo ... Swr1Fe-8y-

which offers different costs depending on which parts you want.

There are plenty of others, they usually arrive more rapidly than advertised.