-
Notifications
You must be signed in to change notification settings - Fork 1
User's Guide
This document will use <siteurl.com> as a placeholder for the URL of the target DMRHub instance. Replace it as appropriate.
By default, DMRHub ships with Material Dark Compact Indigo as the theme. Click the palette icon on the right side of the page to open up a theming panel that will allow you to chose your look and feel. This is saved to the browser's local storage, not account-wide.
The home page shows the last heard public talkgroup calls on the DMRHub instance if not logged in, and if logged in, shows the last heard calls that involve your DMR user ID, your DMR repeater ID, or talkgroups you're subscribed to. The lastheard list will update in realtime. The table shows RSSI and Bit Error Rate (BER) if the source repeater sends the information. Jitter is a measurement of how far, on average, the timing of the DMR packets strays from the 60ms timing. Positive Jitter means the packets are being sent too slowly and negative means the packets are being sent too fast.
After a DMRHub instance is configured and running, users can visit <siteurl.com>/register to sign up for an account. This requires the RadioID.net ID of the user, a username, the user's callsign, and a password. DMRHub will check the RadioID users database for the radio id and will ensure the callsign matches. The users database is automatically updated in memory on server startup and every day at midnight UTC if internet is available. If the DMRHub instance was deployed with HaveIBeenPwned password checking enabled, passwords that have been found in previous data breaches may not be allowed. Passwords are immediately salted and hashed with Argon2i upon registration and never stored in plain text.
Note, applications like AREDN require plaintext communications, so keep in mind that any hops the password makes to be routed are potential points where the password can be obtained, so make sure to use a unique password.
After registration, a DMRHub instance administrator will need to approve your access.
DMRHub does not differentiate between a hotspot and repeater in any meaningful way.
Repeaters can be registered with only the ID. These IDs are supported:
- A repeater ID issued by RadioID.net (6 digits). This will be checked against the DMR repeater ID database to ensure the registered owner of the repeater matches the user registering it
- Your DMR radio ID issue by RadioID.net (7 digits)
- Your DMR radio ID issue by RadioID.net, suffixed with a two digit number between 00 and 99. (9 digits)
With this repeater ID, navigate to <siteurl.com>/repeaters/new and type it in. You will be given an example configuration for connecting DMRGateway to DMRHub. The password in this configuration is unique and will not be shown again. Make sure to note it down.
Instructions on configuring DMRGateway is out of scope for this document.
Once your repeater has been registered and is connecting to DMRHub, the repeaters page should show the last connected and last ping times. These are updated automatically after every 5 seconds. Clicking the icon on the left side of a repeater in the list will allow users to edit their dynamic and static talkgroups. The dropdown boxes that appear when doing this are searchable by talkgroup name and by talkgroup ID.
The talkgroup list can be seen at <siteurl.com>/talkgroups. These are managed by the DMRHub administrators. Parrot is a talkgroup, however it will always respond with a private call and will not route talkgroup 9990 traffic like standard DMR traffic.
Static and dynamic talkgroups for a repeater can be edited under the Repeaters section of DMRHub. Alternatively, just keying up on a talkgroup will dynamically link it on the same timeslot as the transmission, and keying up talkgroup 4000 will unlink on the same timeslot as well. Eventually, an API will be offered to allow this as well.
Talkgroup admins can edit the talkgroup name and description as well as appoint net control operators (NCOs).
Eventually, admins and NCOs will be able to create scheduled nets where check-ins can be done just by keying up the talkgroup, and a participants list will be generated on the site in realtime.