Important: Use only Compass Linux images and dstarrepeater packages. They contain support specific to the UDRC™. Source is available for review on GitHub.
During initial startup do not modify the basic Raspberry Pi setup. For example, do not overclock the Raspberry Pi, it is not needed as performance is more than adequate, and doing so can change clocking values on busses used by the UDRC™ causing it to either not function or be unstable. If you make any changes not listed in these instructions, and your UDRC™ does not function, return to the original settings.
Please verify your DR-1X has recent firmware installed. For analog and D-STAR with no Fusion Digital, the UDRC™ has been tested against versions 1.00m and 1.00t (no further testing will be performed on the 1.00 series firmware). For D-STAR, Fusion Digital, and analog, the UDRC™ has been tested on 1.10D, 1.10J and 1.10Q. We recommend that you upgrade to 1.10 series firmware.
Mount your UDRC™ on a Raspberry Pi 2 or 3Note: Raspberry Pi 3 Addendum
ARMv6 Raspberry Pis are not supported. This includes the A/A+, Zero, Pi 1 B/B+, and Compute Module.
Make sure the pins are properly aligned and use the supplied standoffs to support the board above the HDMI port.
A video tutorial is available on YouTuberegister a unique callsign for your repeater at ircDDB.net. In the United States this needs to be a club callsign, in other countries a secondary callsign is necessary. If you want to use your personal call sign, you will be able to run the repeater and perform linking to repeaters and reflectors, but will be unable to do callsign routing including STARnet Digital groups. If you already have an ircddbgateway registered, you can just add this repeater to it via configuration.
- From a terminal command line, verify that the UDRC™ is
recognized by typing the command
aplay -l(that's a lowercase l) and observe that udrc is listed as a card. If you do not see it listed, power down and remount the UDRC™.
- To preset the pins and levels on the UDRC™ we provide a
script. Execute the following:
cd ~ curl -L -s https://goo.gl/h04nla > set-udrc-dr1x.sh chmod +x set-udrc-dr1x.sh
- Optionally disable the internal sound chip by editing
/boot/config.txt, with sudo nano or sudo vi, and commenting out this line (recommended unless you
need it for something else):
You may install any mix of GUI and non-GUI versions of the repeater and gateway software. Use the following commands on the command line.
For the GUI tools:
sudo apt-get updatesudo apt-get remove bluez pi-bluetoothsudo apt-mark hold libasound2 libasound2-datasudo apt-get install dstarrepeater ircddbgateway dstarrepeaterd ircddbgatewayd
We install the daemon versions as well because once you have everything configured you would typically run headless.
For the non-GUI tools:
sudo apt-get updatesudo apt-get remove bluez pi-bluetoothsudo apt-mark hold libasound2 libasound2-datasudo apt-get install dstarrepeaterd ircddbgatewayd
If you are running ircddbgateway on another computer, there is no need to install it on the Pi. You will configure dstarrepeater to access the ircddbgateway.
The repeater must be set for remote mode.
Be sure to use CTCSS on RX/TX in analog, avoid 100.0 Hz as that can false on a GMSK signal.
sudo curl -L -s -o /etc/opendv/dstarrepeater_1 https://goo.gl/w3rm3a
If using the GUI install, you can edit the file with:
sudo -E dstarrepeaterconfig 1
If non-GUI, use an editor like nano or vi to edit, e.g.
sudo nano /etc/opendv/dstarrepeater_1
You will need to change the repeater callsign and gateway callsign to your system. If you are doing a 70cm repeater these are the only settings that need changed for initial configuration. Only adjust other settings if you understand their effect.
If you are using a 2 meter configuration, you will need to change the Sound Card Modem RX to 0 or not inverted.
- Auto RX / Fixed FM TX
- Auto RX / Auto TX (Default in the seed file)
- Fusion Digital Fixed RX / Fusion Digital Fixed TX
- Fixed FM RX / Fixed FM TX
(Use this if you are on DR-1X firmware 1.00*)
- Is used for simplex access points (hotspots) and non DR-1X repeaters attached to the Mini DIN-6 connector
Make sure the UDRC™ is connected to the DR-1X using the provided 15 pin cable. This should power up the Raspberry Pi.
NOTE: Many standard VGA Cables do not have all of the pins wired and will not work!
Login to the Raspberry Pi and issue the command:
sudo systemctl start dstarrepeaterd@1
The repeater should now repeat D-STAR signals received on the repeater's input. Test by keying up and watching the D-STAR radio's display.
If you want to see a GUI, run the commands:
sudo systemctl stop dstarrepeaterd@1 sudo dstarrepeater 1
Logs for troubleshooting are at /var/log/opendv
If you want the dstarrepeaterd daemon to start on reboot, issue the command:
sudo systemctl enable dstarrepeaterd@1
A video of hints for management of the daemon.ircDDBGateway If you would like a web based dashboard for ircDDBGateway, check out the real time dashboard at ircNodeDashboard
Visit our quick startup Wiki page for ircDDBGateway.
- Did you follow this Wiki exactly? Please review line by line.
- Make sure you didn't do anything to the Linux install, not listed in the Wiki (e.g. overclocking or other modifications)
- Are you using a Raspberry Pi 3 or 2? If a Raspberry Pi 3 -- review https://nw-digital-radio.groups.io/g/udrc/wiki/UDRC%E2%84%A2-and-Raspberry-Pi-3-Addendum
- Which firmware revision is the repeater controller using? If not the latest 1.00 version, please update.
- Is the repeater set to remote mode?
- Is it on 2m or 70cm? If 2m, note the change you need to make to configuration.
- Is the repeater in FM or Narrow FM? If Narrow FM, you will need to modify the configuration. Start with the LO Driver Gain at 8.0db (25/25 on the scale in alsamixer).
- Does the repeater key up and repeat in FM mode? What PL are you using? Is PL set on both receive and transmit?
- Are you running dstarrepeater in GUI mode or daemon mode? If GUI mode, make sure the daemon is not running in the background.
- Next see if the UDRC is receiving and decoding your transmissions. Open a terminal window and type:
sudo tail -f /var/log/opendv/dstarrepeater_1.log
(if in GUI, otherwise for the daemon run)
sudo tail -f /var/log/opendv/dstarrepeaterd_1.log
- Key up on D-STAR, do you see header information coming from your transmissions? If so, then receive should be good.
- Do you get a response from the repeater, with the end of transmission beep? If yes, then your UDRC is functioning with the dstarrepeater program. If no, then take a second radio and leave it open squelch on the output frequency of the repeater, transmit on D-STAR -- do you hear modem tones? If so, switch the second FM radio to the input frequency of the repeater and transmit D-STAR, are the tones approximately the same "loudness"? If not, then the setup is wrong from the alsa settings you loaded.
The DR-1X operates with a controller attached to the HD-15 accessory port or a Yaesu HRI-200 attached to the Mini DIN-10 connector. You cannot operate with both connected at the same time. If you wish to run D-STAR via the UDRC and WIRES-X on the same repeater, it is necessary to set up a WIRES-X node on the repeater's frequencies.
A WIRES-X node consists of a Microsoft Windows based computer, Yaesu HRI-200, and a radio like the FTM-100DR, with an antenna separate from the repeater.
NW Digital Radio is in the process of setting up various community groups at Groups.io Please create a personal account at Groups.io Join the main NW Digital group by sending an email from your registered email account to email@example.com and then send an email to firstname.lastname@example.org Please use the group for questions and to share your experiences, so that all UDRC™ users can benefit from the replies.