Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report DMR only repeater information to APRS. #620

Open
hb9eue opened this issue Aug 2, 2020 · 20 comments
Open

Report DMR only repeater information to APRS. #620

hb9eue opened this issue Aug 2, 2020 · 20 comments

Comments

@hb9eue
Copy link

hb9eue commented Aug 2, 2020

Hi Gang

I'm not sure if I am missing someting.

I can set the location in MMDVM.ini and this is reported to the Brandmeister Server I am connecting to and shown on the Brandmeister dashboard.

When I also use YSFGateway and ircddbgateway those submit the repeater position to APRS IS with some information about the frequencies.
So while I was on vacation, that was cool, I could look at aprsdirect.com and could have found some close repeater offering C4FM or D*Star. But what about DMR only repeater?

DMR only repeater do not show up there. At least I found no way to make my DMR only dual hat hotspot show up on APRS also MMDVM.ini does not incluse an [aprs] section.

Also if I enable GPS position reporting on my DMR Handheld, my position is shown on the aprs map, and the via indicates it was received via my hotspot, but as this is missing, the nice coverage map feature of aprsdirect.com also cannot show the reach of my hotspot.

Would it be the task of the brandmeister servers to push objects to APRS or is this something which could be included in MMDVMHost?

73
-Benoit- HB9EUE

@g4klx
Copy link
Owner

g4klx commented Aug 4, 2020

All DMR APRS reporting is done via BM, not from the MMDVM. The host reports the host position to BM using the data from the ini file (or a GPS receiver) but does not send it directly.

@picchiosat
Copy link

But is this a choice or a necessity? Why can't APRS DMR data be transmitted directly to the server like YSFGateway or ircDDGateway do? A repeater is not necessarily connected to BM

Roby IV3JDV

@g4klx
Copy link
Owner

g4klx commented Aug 7, 2020 via email

@hb9eue
Copy link
Author

hb9eue commented Aug 7, 2020

I think we talk about two different things:

1: Reporting Positions of Radios broadcasting their GPS Data to APRS. Sure, this is something which has to be done by Brandmeister, as they get and decode those packets.

2: (this is what I was talking about): Reporting the position of the repeater itself to APRS, with Information about it's frequencies and CC so it can be found on the map.
This position is configured in MMDMVHost.ini (and can also be updated by gpds now I believe). This is something which MMDVMhost could be sending to APRS as there is no need to decode a packet from a radio.

Yes, I have found some PHP script, which I suppose is intended to be run on the BM Master Server to export this data to APRS. But it looks like the Server Admins do not run this script. My hotspots do now show up on the map. Nice features like aprsdirect.com coverage map is not available this way.

73 Benoit HB9EUE

@picchiosat
Copy link

yes Benoit, you are right. I also meant point 2

@g4klx
Copy link
Owner

g4klx commented Aug 7, 2020

I know that the MMDVM sends details of the repeaters location, CC and other information to all of the DMR networks. You need initially to ask BM why it isn't being displayed. I could do it myself but I thought that they were handling it. Please do so, and let me know what they say. For it to work properly the transmitted position must include the repeater in the path otherwise the map won't show the RF connection.

@picchiosat
Copy link

But wouldn't it be possible to insert the APRS code that is present in YSFGateway and NXDNGateway into the MMDVMHost to directly transmit the position of the repeater to the APRS server without going through BM?

@g4klx
Copy link
Owner

g4klx commented Aug 7, 2020 via email

@picchiosat
Copy link

Jonathan, many thanks for the time you dedicate to us. But if I have a network of repeaters connected, for example, to a HBLink server, it would be nice to be able to transmit the position of the repeaters on APRS.fi. Then be able to decide whether to send the data via MMDVM or directly to the APRS Server

@hb9eue
Copy link
Author

hb9eue commented Aug 22, 2020

I had a look on how positions from handhelds are sent to APRS IS via BM. I updated my callsign to HB9EUE-3 in the MMDVMHost .ini file to be able to clearly identify it.

HB9EUE-8>APBM1D via HB9EUE-3,DMR*,qAR,HB9EUE-3

Well, so from my understanding, this clearly states the packet from HB9EUE-8 (Hytera Handheld) was received by the iGate HB9EUE-3 which is MMDVMhost.

So if MMDVMHost would push the position of HB9EUE-3 to APRS IS it would show up correctly, it would show which clients send packets to it, and aprsdirect.com could create coverage maps.

Only issue I found, is that if you don't put your callsign without suffix in MMDVMHost's ini file, it does now show up under 'hotspots' on your BM Dashboard. But as you can still access it via entering the correct URI, I suppose that is just something the BM web devs didn't consider.

So, IMHO, providing a way to publish your repeater / hotspot to APRS IS as YSFGateway does, would be beneficial to all.

73 HB9EUE

@g4klx
Copy link
Owner

g4klx commented Aug 22, 2020 via email

@hb9eue
Copy link
Author

hb9eue commented Aug 22, 2020

Hi Jonathan

I fear you are still misunderstanding my input. It's NOT about transmitting position of DMR Handhelds to APRS IS, this is already done by Brandmeister. That works, they decode the packets from the various handheld variants. As you see im my example where my Hytera Handheld (HB9EUE-8) sent it's position to APRS.

It did so via HB9EUE-3 which is my MMDMVMHost Repeater.

HB9EUE-3 cannot be found on APRS. And this is the Callsign configured in MMDVMHost for my repeater.

What I was suggesting, is adding a way to optionally publish the coordinates of the repeater, those which are configured in the ini file of MMDVMHost, to APRS. Those are in a defined format. This already works in YSFGateway etc.

That would make it possible for aprsdirect.com to plot coverage maps
This would look nice, when aprs.fi or aprsdirect.com can display the path the packet took.
This would make it possible for repeaters to show up on the map.

73 Benoit / HB9EUE

@g4klx
Copy link
Owner

g4klx commented Aug 28, 2020 via email

@picchiosat
Copy link

Hi Jonathan, I also tried this version and unfortunately the transmission to APRS.FI does not work.
From the APRSGateway log I don't see any TX from DMRGateway.
I spoke to BM about the incorrect display issue. I'm waiting for a reply

@picchiosat
Copy link

Good news, just wait ..
DMRGateway also transmits the position to APRS.FI.
Great job Jonathan

@g4klx
Copy link
Owner

g4klx commented Aug 28, 2020

Which GPS device do you use?

@g4klx
Copy link
Owner

g4klx commented Aug 28, 2020 via email

@picchiosat
Copy link

Nothing.
Just I configure /etc/default/gpsd with the used ttyACM USB port
and I used the "-G" option

@hb9eue
Copy link
Author

hb9eue commented Aug 30, 2020

Hi Jonathan

Thank you for your excellent work. But I don't manage to get them to talk to each other.

I cloned the repositories DMRGateway and MMDVMHost and switched both to the SimpleDMR branch, compiled.

MMDVMHost
I: 2020-08-30 07:18:39.494 DMR Network Parameters
I: 2020-08-30 07:18:39.494 Address: 127.0.0.1
I: 2020-08-30 07:18:39.495 Port: 62031
I: 2020-08-30 07:18:39.495 Local: random
I: 2020-08-30 07:18:39.495 Jitter: 360ms
I: 2020-08-30 07:18:39.495 Slot 1: disabled
I: 2020-08-30 07:18:39.495 Slot 2: enabled
I: 2020-08-30 07:18:39.495 Mode Hang: 300s

DMRGateway
I: 2020-08-30 07:18:05.272 MMDVM Network Parameters
I: 2020-08-30 07:18:05.272 Rpt Address: 127.0.0.1
I: 2020-08-30 07:18:05.272 Rpt Port: 62032
I: 2020-08-30 07:18:05.272 Local Address: 127.0.0.1
I: 2020-08-30 07:18:05.272 Local Port: 62031
M: 2020-08-30 07:18:05.273 MMDVM Network, Opening
M: 2020-08-30 07:18:05.273 Waiting for MMDVM to connect.....
M: 2020-08-30 07:18:09.345 Packet received from an invalid source, 0100007F != 0100007F and/or 62032 != 49786
M: 2020-08-30 07:18:19.358 Packet received from an invalid source, 0100007F != 0100007F and/or 62032 != 49786
M: 2020-08-30 07:18:53.434 Packet received from an invalid source, 0100007F != 0100007F and/or 62032 != 60466
M: 2020-08-30 07:19:03.448 Packet received from an invalid source, 0100007F != 0100007F and/or 62032 != 60466
M: 2020-08-30 07:19:13.449 Packet received from an invalid source, 0100007F != 0100007F and/or 62032 != 60466

What did I miss?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants