Pi-Star

  1. Local Dashboard and Log Monitoring
  2. ZumSpot Setup
  3. The G4KLX Software Suite
  4. Firmware Update
  5. Pi-Star Update Dialogue
  6. A strategy to set up a Pi-Star as DMRGateway for Australia
  7. Homebrew repeater protocol
  8. Startup Options for DMRGateway
  9. MMDVM.ini Startup Options
  10. A Special Options String
  11. Direct Mode Operation (DMO)
  12. Phoenix-F sMaster
  13. Pi-Star Dashboard for Mobiles Phones
  14. Unlinking Reflectors
  15. To link/unlink to a given reflector from the command line
  16. Discuss DMRlink, DMRmonitor, HBlink, DVSwitch and DMRDongle
  17. BM API
  18. Received signal strength indication (RSSI)
  19. Build Your Own MMDDVM
  20. CQ-UK
  21. Pi-Star FAQ
  22. Pi-Star Services
  23. Throttling Pi-star to conserve network data
  24. New Australian DMR+IpSC2 settings 28 October 2018

http://www.pistar.uk/index.php

Local Dashboard and Log Monitoring

If ths hotspot running Pi-Star is on the same network then this will dosplay the dashboard
http://pi-star.local/

The monitir the log file:



ZumSpot Setup

http://www.pistar.uk/index.php

https://www.hamdigitaal.nl/download/algemene-informatie/ZumSpot_Pistar_KC6N_20180605.pdf

[Top][Home]


Source Archives

The G4KLX Jonthon Naylor Software Suite: Andy Taylor Software:
https://github.com/AndyTaylorTweet

[Top][Home]


Firmware Update

MMDNV Firmware for STMM32 ZUMspot/MMDVM_HS v1.3.7:
https://github.com/juribeparada/MMDVM_HS/releases/tag/v1.3.7

These are the source files for building the MMDVMHost, the program that interfaces to the MMDVM or DVMega on the one side, and a suitable network on the other. It supports D-Star, DMR, P25 Phase 1, NXDN, and System Fusion on the MMDVM, and D-Star, DMR, and System Fusion on the DVMega.

On the D-Star side the MMDVMHost interfaces with the ircDDB Gateway, on DMR it can connect to BrandMeister, DMR+, HB Link, XLX or DMRGateway (to connect to multiple DMR networks at once) on System Fusion it connects to the YSF Gateway. On P25 it connects to the P25 Gateway.
https://github.com/g4klx/MMDVMHost How to set jumper:

Updating the JumboSpot by John's Musings:
http://www.hagensieker.com/blog/page/?post_id=99&title=jumbospot-dmr-hotspot

[Top][Home]


Pi-Star Update Dialogue



[Top][Home]


A strategy to set up a Pi-Star as DMRGateway for Australia

The three basic Digital Contacts programmed in as Group calls:
  1. [Name] TG9 BM, with Call ID 9
  2. [Name] TG8 DMR+ with Call ID 8
  3. [Name] TG6 XLX with Call ID 6
There are three corresponding channels in the transceiver for talking to your hotspot:
All 3 must be no scan list, no Group list, CC1, Repeater Slot 2, TOT[s] 180
  1. [Chan.name] BM TG9 DmrG, Contact Name same as TS2 TG9 BM
  2. [Chan.name] DMR+ TG8 DmrG, Contact Name TG 8 DMR+
  3. [Chan.name] XLX TG6 DmrG, Contact name TG 6 XLX

Now add a zone called DmrGateway (or your hotspot name) and put all 3 channels in it. When you switch to this zone to use the hotspot, you can decide if you want to use BM, DMR+ or XLX by **channel selection**.

To change reflectors or modules use the keypad, Menu--> Contacts--> 3 Manual Dial and you will find yourself with a clear white screen headed "Radio Number". This is where you type your commands. A press of the ptt for a moment will cause the reflector change to take place.

There is a bit of important info here:-

Calls to BM are as usual ie 4000, 5000, 4404 etc. (but they could be put in as 94000, 95000, 94404 etc.

Calls to DMR+ must have an 8 in front as in 84000, 85000, 84400

Calls to XLX must have a 6, as in 64001,64002,64003...64026 to switch between modules (reflectors?) A to Z Note that XLX925 is a master. To switch master, from XLX925 to XLX950 the prefix is 68 so the call would be 68950. The xlx masters have a default reflector. For instance, if you switched from XLX950 to XLX925 you'd end up dumped in default reflector D, so then you must call 64001 to switch to XLX925/A to bask in the CQ-UK sunshine.

[Top][Home]


Homebrew repeater protocol

https://wiki.brandmeister.network/index.php/Homebrew_repeater_protocol

[Top][Home]


Startup Options for DMRGateway

When using DMRGateway, the default reflector, is set in the 'Options' box on the configuration page.

Image

Options-parameter can be set in two places:
The default configuration string should be something like this:


An example of a configuration string to enable access to the Tuesday night VK-DMR net is


An example of a configuration string to enable access to CQ-UK is


Hotspots operate in DMO-Mode where there is only one timeslot, therefore the settings are limited.

Startup Options paramaters are: Source: https://github.com/g4klx/MMDVMHost/blob/master/DMRplus_startup_options.md

[Top][Home]


MMDVM.ini Startup Options

You can set some configuration options in the MMDVM.ini file which are send to the DMR-Master on logon. This options provide the same features like sysops of "public repeaters" know from the registration database.

The options that you may set are:

StartRefThe reflector which will be connected at startup (4000 means "disconnected")
RelinkTimeIf the reflector is not used the DMR-Master will reconnect to StartRef after this time (in minutes)
UserLinkSet to 1 to allow users to change the reflector, set to 0 to switch remote control off
TS1_1 to TS1_51 to 5 static linked talk groups on timeslot 1

The command line in the sample MMDVM.ini looks like this:

In older sample files it may be missing, add it after the last entry of the block which starts with [DMR Network].

Change the line to this format:

The line starts with "Options=". This is required for MMDVMHost. The rest of the line is sent transparent to the DMR+Master. In the sample above the DMR-Master will get this part:

It is a semi-colon separated list of the options which were described before.

Example: If the DMR-master provides 5 static talk groups the parameter TS1_5=; (no value) will clear the 5th.

Special limitations apply for DMO mode (hotspots). There is only one timeslots in DMO-Mode, therefore the settings are limited.

DMR-Master maps the single DMO channel to one of the two timeslot of the network based on the destination address.

This influences the options. By default a DMO repeater will be connected to a reflector, either given by the DMR-Master, or by options, or by registration database. If you do not want to connect to a reflector at startup, but want to book a talk group on TS1, set StartRef to 4000 (not linked) in the options and set "TG1_1" to your needs. The DMR+Master will book "TG1_1" if no reflector is set. "TG1_2" to "TG1_5" are not supported in DMO mode.

Priority of settings:

  1. For public repeaters with a 6-digit DMR-ID the DMR+settings in the registration database - if activated - have highest priority.
  2. For all repeaters which have no settings in the database activated the
    "options" in the MMDVM.ini have priority.
  3. Finally, without database entry and without the options being activated,
    or not all parameters set, the settings from the DMR-Master will be used.

The idea with this order is: Many public repeaters are located at special locations with limited access and often sysops are no Linux experts. Therefore the configuration on a web-page may be preferred for public repeaters. Database settings may easily be switched off if sysops prefer settings by MMDVM "options".

When you connecting to a non-DMR+System deactivate the Options line by inserting a "#" at the 1st position.

Source: http://dc7jzb.de/downloads/dmr/misc/mmdvm-options.txt

[Top][Home]


A Special Options String

StartRef=4000;RelinkTime=60;UserLink=1;TS1_1=9;

In normal usage the option string, which is specific to the DMR+ network, allows you to connect and disconnect or not be connected to a reflector by default. A example of normal Option statement is StartRef=4639;RelinkTime=60;UserLink=1;

However, this particular option string is special. It is a Special Hack that allows the connection to a DMR+ server without any default Reflector activated. With DMR+, and no options sent the server determines the Reflector thats automatically assinged (eg; 4400 for UK servers etc) The combination of Ref=4000 (no reflector) and TS1_1=9 for Hotspots means no active Reflector.

There are a couple of things to keep in mind with DMR+

  1. The network decides if you are in DMO (Hotspot) mode or a Repeater based on your DMR ID, settings like simplex/duplex are flat out ignored when that decision is made.
  2. DMO/Hotspots cannot permalink more than on Talkgroup (TS1_1= field) while repeaters can link up to 5 per time slot .
  3. Normally Hotspots are forced to connect to a reflector permanently, and cannot unlink.

The option line above sets the connected reflector to 4000 (Unlink), the relink time can probably be omitted, this is the idle timer (in mins) to relink to your chosen reflectors when idle. UserLink - as you expect, allows RF link commands. TS1_1= - linked TG1 is set to TG9, that sounds weird, since we know that DMO mode uses TS2, and TG9 is a special one, that is the input TG for connected reflectors. This is just some special magic combo that makes DMO mode on DMR+ un-linkable.

[Top][Home]


Direct Mode Operation (DMO)

DMO is the term used by the TETRA industry to describe the ability of TETRA radio terminals to communicate directly with each other independent of the Trunked Mode Operation (TMO) network. DMO is not new and has been a fundamental mode of operation by many traditional PMR user organisations for several decades.

Source:https://tcca.info/tetra/direct-mode-operation-dmo/

[Top][Home]


Phoenix-F sMaster

http://217.182.206.73/

[Top][Home]


Pi-Star Dashboard for Mobiles Phones

http://www.amateurradio.digital/pistar.php
Pi-Star mobile Installation Open SSH Access in your pi-star dashboard in your browser with this link: http://pi-star.local/admin/expert/ssh_access.php Once logged in, copy & paste and execute the following lines (one by one). To do this right-click in the pi-star window and select "Paste from browser". A bos will appear to pagse into. Then select "OK" Note: You may see some errors as commands are executued, this normal

If you need to make a reflector FIXED so that users cannot unlink, for schedulling connections via CRON for example you can use the the following:

Should you wish to Un-Fix a reflector, relink to the same reflector without the fixed flag, such as:



[Top][Home]


Discuss DMRlink, DMRmonitor, HBlink, DVSwitch and DMRDongle

https://dvswitch.groups.io/g/main">https://news.brandmeister.network/introducing-user-api-keys/

PROJECT: Open Source IPSC Client:
https://dvswitch.groups.io/g/main/wiki/DMRlink

[Top][Home]


BM API

http://wiki.pistar.uk/PI-Star_integration_with_BrandMeister_API

https://news.brandmeister.network/introducing-user-api-keys/

[Top][Home]


Received signal strength indication (RSSI)

In an IEEE 802.11 system, RSSI is the relative received signal strength in a wireless environment, in arbitrary units. RSSI is an indication of the power level being received by the receive radio after the antenna and possible cable loss. Therefore, the higher the RSSI number, the stronger the signal. Source: https://en.wikipedia.org/wiki/Received_signal_strength_indication

File: /usr/local/etc/RSSI.dat # should be populated similar t below but depends on
radio. The stock values are there for MMDVM_HS units that support RSSI, if you use
anything else, yes you may well need to tune to the radio.
There is an editor for that in the expert section.

This is what is in that file :


[Top][Home]


Build Your Own MMDDVM

https://www.f5uii.net/en/hotspot-homebrew-zumspot-mmdvm-pistar-tune/3/

[Top][Home]


CQ-UK

http://www.dmr-uk.net/index.php/hotspots/=

http://www.cq-uk.com/linking

These are the setting to access the PI-Star MMDVM Gateway (Repeater) that should work
for UK-CQ:

My understanding is that with these settings, the relevant TG (eg 4409 and 2351) are sent off (re-directed) to the UK Pheonix-F server for re-direction/connection instead of been sent to DMR+_Australia reflector/server which does not know what to do with them. Conversely, I would guess, that the Phoenix-F server does not handle the Australian DMR+ TG's very well. However, with this setup the BM linked TG's are still processed in Aust by the BM_Australia_5051 reflector/server. Probably best to set it back to DMR+_Australia after testing.

Set up 4409 and 2351 in the DMR radio/HH to reach CQ-UK.

This is another way you can connect to CQUK:
Running pi-star use dmr/xlx - look for xlx/dcs/xrf 925 A for cq-uk This way you miss out the middle server Pheonix_F and connect directly to Rickie in Belfast who will transcode OR or setup a talk group on the repeater Rickie can give you an ip address and this way you could keep the talkgroup connected all the time.



[Top][Home]


Pi-Star FAQ

Q. Why does my Configuration page display this
Gateway Hardware Information
Hostname Kernel Platform CPU Load CPU Temp
pi-star 4.9.35-v7+ Pi 3 Model B (1GB) - Embest, CH 0.05/0.01/0.01 46.2°C / 115.2°F


[Top][Home]


Pi-Star Services



[Top][Home]


Throttling Pi-star to conserve network data

Web page updates in Pi-Star are effected using AJAX.
See: Linux/ajax.html

It may be necessary to add a throttle to the web interface to slow AJAX refreah rates. It is not an optimal fix principally because page changes are also affected by the delay, and the display may sometimes miss events taking place.

The throttle period is currently set to 6 seconds. The system still spits out approx 5 to 15 K Bytes of data every throttle period even with nothing going on That equates to about 10 Mega bytes per hour. Goodness knows what it would have been without the throttle!

Other pages like 'configuration' also regularly output data, but they don't output as much as the 'live' status pages.

The web interface appears to be designed for a local area network There may be other more suitable 'control panels' around for MMDVM that play nicer over low bandwidth Internet.

The changes required are:




Adding the throttle to index.php seems to affect all pages (which is what is needed).

The throttle period can be adjusted by setting RATE_LIMIT_IN_MS in the file throttle.js.

Reference:https://github.com/dh3wr/RasPagerDigi/tree/master/software/Simple-WebSocket-Server

[Top][Home]


New Australian DMR+IpSC2 settings 28 October 2018

http://www.rogerclark.net/new-australian-dmr-ipsc2-settings/?fbclid=IwAR3QWrlm1b2CcY6lLP_Euw34Pr_zY58KUpDduIfgbY34Zf6Ob4domi0oe50

http://www.rogerclark.net/mmdvm-hotspot-hardware-network-switch/

#top">[Top][Home]


Pi-Star's MMDVMCal utility

(sudo pistar-mmdvmcal)

#top">[Top][Home]


ZumSpot Setup

https://www.hamdigitaal.nl/download/algemene-informatie/ZumSpot_Pistar_KC6N_20180605.pdf

Firmware Update

MMDNV Firmware for STMM32 ZUMspot/MMDVM_HS v1.3.7:
https://github.com/juribeparada/MMDVM_HS/releases/tag/v1.3.7

These are the source files for building the MMDVMHost, the program that interfaces to the MMDVM or DVMega on the one side, and a suitable network on the other. It supports D-Star, DMR, P25 Phase 1, NXDN, and System Fusion on the MMDVM, and D-Star, DMR, and System Fusion on the DVMega.

On the D-Star side the MMDVMHost interfaces with the ircDDB Gateway, on DMR it can connect to BrandMeister, DMR+, HB Link, XLX or DMRGateway (to connect to multiple DMR networks at once) on System Fusion it connects to the YSF Gateway. On P25 it connects to the P25 Gateway.
https://github.com/g4klx/MMDVMHost How to set jumper:

Updating the JumboSpot by John's Musings:
http://www.hagensieker.com/blog/page/?post_id=99&title=jumbospot-dmr-hotspot

[Top][Home]


Phoenix-F sMaster

http://217.182.206.73/

[Top][Home]


Pi-Star Dashbozard for Mrbiles

http://www.amateurradio.digital/pistar.php">http://www.amateurradio.digital/pistar.php

[Top][Home]


To link/unlink to a given reflector from the command line

You may need to cron this activity so that various regular nets can be heard.

If you need to make a reflector FIXED so that users cannot unlink, for schedulling connections via CRON for example you can use the the following:

Should you wish to Un-Fix a reflector, relink to the same reflector without the fixed flag, such as:



[Top][Home]


IPSC

https://github.com/pd0mz/go-dmr/blob/master/docs/DMRplus%20IPSC%20Protocol%20for%20HB%20repeater%20(20150726).pdf

[Top][Home]


Discuss DMRlink, DMRmonitor, HBlink, DVSwitch and DMRDongle

https://dvswitch.groups.io/g/main">https://dvswitch.groups.io/g/main

PROJECT: Open Source IPSC Client:
https://dvswitch.groups.io/g/main/wiki/DMRlink">https://dvswitch.groups.io/g/main/wiki/DMRlink

[Top][Home]


BrandMeister Dashboard and API

The BM BrandMeister Dashboard: https://brandmeister.network/

These instruction show how to log into https://brandmeister.network/ and generate an API key. This key is a string of random characters. Once generate and display on the screen it will never be displayed again, so make a copy to a file in a safe place. I use my dropbox account. If you lose it you can simply generate anothet key and if you are concenrd that someone else is using your key, simply revoke. http://wiki.pistar.uk/PI-Star_integration_with_BrandMeister_API

This page shows the "Last Heard" on the Mt Cotton Digital Repeater, VK4RDB, repeater node number 505424 https://brandmeister.network/?page=lh&ContextID=^505424$

[Top][Home]


RSSI

File: /usr/local/etc/RSSI.dat # should be populated similar to below but depends on
radio. The stock values are there for MMDVM_HS units that support RSSI, if you use
anything else, yes you may well need to tune to the radio.
There is an editor for that in the expert section.

This is what is in that file :


[Top][Home]


Build Your own MMDDVM

https://www.f5uii.net/en/hotspot-homebrew-zumspot-mmdvm-pistar-tune/3/

[Top][Home]


DMR-UK.net

Image
DMR-UK.net
http://www.dmr-uk.net/index.php/hotspots/=

CQ-UK

Image
CQ-UK.net

What is CQ-UK? My best answer is a communication hub for digital traffic. It attempts to provides as many "spokes to the wheel" as possible allowing many different modes and communication systems to cross connect, with the notable exception of BrandMeister. Brandmeister repeaters NOT AVAILABLE on CQ-UK

This diagram, from the CQ-UK.net web site puts it visually...

Image
CQ-UK.net

http://www.cq-uk.com/linking

These are the setting to access the PI-Star MMDVM Gateway (Repeater) that should work
for UK-CQ:

My understanding is that with these settings, the relevant TG (eg 4409 and 2351) are sent off (re-directed) to the UK Pheonix-F server for re-direction/connection instead of been sent to DMR+_Australia reflector/server which does not know what to do with them. Conversely, I would guess, that the Phoenix-F server does not handle the Australian DMR+ TG's very well. However, with this setup the BM linked TG's are still processed in Aust by the BM_Australia_5051 reflector/server. Probably best to set it back to DMR+_Australia after testing.

Set up 4409 and 2351 in the DMR radio/HH to reach CQ-UK.

This is another way you can connect to CQUK:
Running pi-star use dmr/xlx - look for xlx/dcs/xrf 925 A for cq-uk This way you miss out the middle server Pheonix_F and connect directly to Rickie in Belfast who will transcode OR or setup a talk group on the repeater Rickie can give you an ip address and this way you could keep the talkgroup connected all the time.



[Top][Home]


pi-star Update Dialogue



[Top][Home]


Pi-Star FAQ

Q. Why does my Configuration page display this
Gateway Hardware Information
Hostname Kernel Platform CPU Load CPU Temp
pi-star 4.9.35-v7+ Pi 3 Model B (1GB) - Embest, CH 0.05/0.01/0.01 46.2°C / 115.2°F


[Top][Home]


Pi-Star Services



[Top][Home]


Throttling Pi-star to conserve network data

Web page updates in Pi-Star are effected using AJAX.
See: Linux/ajax.html

It may be necessary to add a throttle to the web interface to slow AJAX refreah rates. It is not an optimal fix principally because page changes are also affected by the delay, and the display may sometimes miss events taking place.

The throttle period is currently set to 6 seconds. The system still spits out approx 5 to 15 K Bytes of data every throttle period even with nothing going on - so that equates to about 10 Mega bytes per hour by my reckoning. Goodness knows what it would have been without the throttle!

Other pages like 'configuration' also regularly output data, but they don't output as much as the 'live' status pages.

The web interface appears to be designed for a local area network There may be other more suitable 'control panels' around for MMDVM that play nicer over low bandwidth Internet.

The changes required are:




Adding the throttle to index.php seems to affect all pages (which is what is needed).

The throttle period can be adjusted by setting RATE_LIMIT_IN_MS in the file throttle.js.

References:






[Top][Home]


Glenn Lyons VK4PK
glenn@LyonsComputer.com.au
Ver:gnl1610821 - pre published v0.9