Date   
Re: New UDRC II No DStarrepeater PTT

 

There are no changes between the dstarrepeater program in the original image and the newer ones.  

This is a case where a change may need to be made to the source of dstarrepeater.

On Sat, May 13, 2017 at 1:41 PM, Rich KR4PI <rich.schnieders@...> wrote:

Thanks Bud, that may be my last resort.

When I ordered the UDRC-II I also ordered your case which is how I discovered the TX leds. Previously my pi was in a black case and i could not see the leds. 

I am currently writing a new sd card with the original compass image from 2016-05-23 to see if that shed any light on the issue. Something is preventing dstarrepeater from utilizing the din-6. 

Thanks again.

Rich, KR4PI





--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   

Re: New UDRC II No DStarrepeater PTT

 

Thanks Bud, that may be my last resort.

When I ordered the UDRC-II I also ordered your case which is how I discovered the TX leds. Previously my pi was in a black case and i could not see the leds. 

I am currently writing a new sd card with the original compass image from 2016-05-23 to see if that shed any light on the issue. Something is preventing dstarrepeater from utilizing the din-6. 

Thanks again.

Rich, KR4PI


Re: New UDRC II No DStarrepeater PTT

Budd Churchward
 

There are through-hole solder points for all pins on the DB-15 right behind the jack on the PCB. Several of us have added a second DIN6 so that we can control two radios with DIN cables. I was able to modify my original case to make room for this additional connector which you can see to the right of the DB-15 in the photo below.
 
2Dins
 
 
Budd Churchward – WB7FHC
360-483-4550
 
 

Re: New UDRC II No DStarrepeater PTT

 

That may be an issue in dstarrepeater software as currently implemented.  I have a HD-15 to DIN6 cable I could try, but I can't really dig into it right now.  Preparing for two major events right now -- Dayton Hamvention and the SEA-PAC Raspberry Pi workshop.

On Sat, May 13, 2017 at 10:23 AM, Rich KR4PI <rich.schnieders@...> wrote:

I have completed more testing today and have discovered that when dstarrepeater keys it is keying out through the db15 and not the din6. With direwolf properly configured and winlink express configured to use kiss2 port the din6 tx led lights and the radio keys. But when dstarrepeater keys it keys the db15 tx led and of course the radio does not key. 

So, how to I tell dstarrepeater to utilize the din 6 port and not the db15 port. On the original UDRC I never had to adjust that. I thought that on the controller tab of dstarrepeaterconfig Config 5 indicated to go out the din6 port. 

I am sure I am missing something simple but I have yet to find it. 

I was not able to get the non gui version working as I do not have an Ethernet cable close to my radio. 

Any help would be appreciated.

Rich, KR4PI





--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   

Re: New UDRC II No DStarrepeater PTT

 

I have completed more testing today and have discovered that when dstarrepeater keys it is keying out through the db15 and not the din6. With direwolf properly configured and winlink express configured to use kiss2 port the din6 tx led lights and the radio keys. But when dstarrepeater keys it keys the db15 tx led and of course the radio does not key. 

So, how to I tell dstarrepeater to utilize the din 6 port and not the db15 port. On the original UDRC I never had to adjust that. I thought that on the controller tab of dstarrepeaterconfig Config 5 indicated to go out the din6 port. 

I am sure I am missing something simple but I have yet to find it. 

I was not able to get the non gui version working as I do not have an Ethernet cable close to my radio. 

Any help would be appreciated.

Rich, KR4PI


Re: New UDRC II No DStarrepeater PTT

 

I have now downloaded the image but have not yet put it on an SD yet. If I am remembering correctly this is not a gui installation only command line or browser interface from another computer. My plan is to have the 7" display mounted on the front of the go kit and to use gui programs. That is how I run my home hotspot and it works very well for me. I have now eliminated the display as the problem. I do have ptt in direwolf but still not in dstarrepeater. I tried with the most recent wilderness image and did not hold back anything but still no ptt in dstarrepeater. It does appear the ptt led is active when it should be but the radio is not keyed. I have tried with two different radios and two cables.

Is there a way to detect if dstarrepeater is actually signalling ptt? Any scripts to run to test the gpio ptt lines?

Thanks


Rich

 

Re: Web based UDRC setup for Repeaters and Hotspots

 

If the button to load the modem hangs, the scripts are in /opt/nwdr/scripts where you can execute them directly.

Re: New UDRC II No DStarrepeater PTT

 

Rich -- have you tried the image at ftp://starbuck.hays.org/20170405-web-udrc.zip  (will move in the future)


You should not have had to do the hold back, etc. on later Wilderness builds.

On Fri, May 12, 2017 at 10:05 AM, Rich KR4PI <rich.schnieders@...> wrote:

I received a new UDRCII this week which I will be installing in my ARES Go Kit. It is attached to Raspberry Pi 3.

I started with a new install utilizing the image from Wilderness 2017-04-12.  Did apt-get update, apt-get upgrade as well as apt-get remove bluez pi-bluetooth and apt-mark hold libasound2 libasound2-data.

I first had the UDRCII on a Pi 3 with 7" display and could not get any PTT on the radio for either DStarrepeater or direwolf.

I thought the display might be conflicting somehow so I moved the UDRCII to another Pi 3 without display. I removed the old UDRC from this PI 3. This was running on a new install of

wilderness 2017-04-12 and was working with dstarrepeater and direwolf without issue. After install of the UDRCII on the previously functioning pi 3 I still had no ptt on the radio from either dstarrepeater or direwolf.

I edited direwolf.conf for the UDRCII and changed my Winlink Express setting to attach to kiss port 2. PTT through direwolf now works, so I know the UDRCII is good, but I still do not get PTT from DStarrepeater.

It is my understanding that recent installs of DStarrepeater detect the difference between the UDRC and UDRCII.

I have tried changing RX and TX inversion but to no avail. The UDRCII hears my inbound traffic from the radio and properly responds but the radio is not keyed.

I know that the UDRC uses a different gpio pin for PTT but I am unaware of any setting in DStarrepeater to configure that.

Thanks in advance for the help.

Rich, KR4PI








--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   

New UDRC II No DStarrepeater PTT

 

I received a new UDRCII this week which I will be installing in my ARES Go Kit. It is attached to Raspberry Pi 3.

I started with a new install utilizing the image from Wilderness 2017-04-12.  Did apt-get update, apt-get upgrade as well as apt-get remove bluez pi-bluetooth and apt-mark hold libasound2 libasound2-data.

I first had the UDRCII on a Pi 3 with 7" display and could not get any PTT on the radio for either DStarrepeater or direwolf.

I thought the display might be conflicting somehow so I moved the UDRCII to another Pi 3 without display. I removed the old UDRC from this PI 3. This was running on a new install of

wilderness 2017-04-12 and was working with dstarrepeater and direwolf without issue. After install of the UDRCII on the previously functioning pi 3 I still had no ptt on the radio from either dstarrepeater or direwolf.

I edited direwolf.conf for the UDRCII and changed my Winlink Express setting to attach to kiss port 2. PTT through direwolf now works, so I know the UDRCII is good, but I still do not get PTT from DStarrepeater.

It is my understanding that recent installs of DStarrepeater detect the difference between the UDRC and UDRCII.

I have tried changing RX and TX inversion but to no avail. The UDRCII hears my inbound traffic from the radio and properly responds but the radio is not keyed.

I know that the UDRC uses a different gpio pin for PTT but I am unaware of any setting in DStarrepeater to configure that.

Thanks in advance for the help.

Rich, KR4PI





Hotspot working on Kenwood TM-V71

kc9zjf@...
 

Wanted to update people on the hookup to a Kenwood TM-V71:  (note I am computer savvy but not a Linux guru, (enough to get myself into trouble) 

Using the 2016-05-23 image, after a corrupt image the other day I did run set up with 2017-04-18 Compass but just have some odd issues (remote desktop not connecting) having to restart ircDDB to get it to link up to REF just little odd items

After set up of repeater and ircDDB made adjustments under Sound Card Settings for the V-71 seems to want both RX Inversion and TX inversion set to on (I'm running this on 2 meter) any other combination it will either not receive or transmit.  also after experiencing intermittent drops on transmit I increased the TX Delay initially to 150 ms, current setting at 160 ms, we will see if this helps, it did at 150 ms but not 100% I think the transmitter needs to settle down on the TM-V71 and needs just a little time.

Alsa mixer settings 

PCM 38 (0 dB) 

ADC 24 (0 dB)

Lo Drive 47 (16 dB) I've gone back and forth on these settings but this seems to be where everyone in my area has the best luck, anything else they have decode issues 

The hotspot (located in Northern Wisconsin) is connected to my comet GP9 top of antenna is at 67 feet, what I have found though driving around is receive range is outstanding, around 30 miles not quite able to hit this on transmit with my 5100 

other things running- Dashboard working great, glogg up and running for headless access to a visual of both dstar repeater and irc, systemadm for controlling both 

have not run the script for updating host files to DNS names, had issues in the previous run of the software not sure if it was related or not so as it stands it boots and works right now, although I'm sure I will have to mess around as some xref don't want to connect

Next work is TS2000, I have the cable and have done some experimenting with it, one not, it works but getting Alsamixer set right seems be be the challenge very touchy

hats off to the NW folks and John for being very responsive to my sometimes very simple questions - love this board and even when the D-Star repeater goes up in the area (built just waiting for a tower climb) this hospot will be my go to in the area.  


73 Mike, KC9ZJF 




Remote Desktop

kc9zjf@...
 

Hope this is the last post, just about everything up and running at this point after my corrupted SD card.  Note my previous install (yesterday) remote desktop working fine

installed xrdp from windows go to log in get following error 


Re: Web based UDRC setup for Repeaters and Hotspots

 

Bridgecom users -- adjust "Transmit Hang Time (seconds) [Misnamed] to 180 --


Re: Dstar Repeater

 

There is missing context.

Which log file are you looking at?  /var/log/opendv/dstarrepeater_1.log  or /var/log/opendv/dstarrepeaterd_1.log

The /root/en_US.indx is not important.

Which image are you using?

If I were to guess, you have two copies running,  one in the background and one in the foreground. (The daemon 'yeah', and the GUI 'not needed'), the first one started 'locks' the UDRC to itself, which would explain the 'Cannot Open...' lines.

You need to stop both, and delete the /tmp/D-Star_Repeater_1  -- if you run the gui as root that is what caused it to be owned by root.

What is the radio/repeater it is attached to?

You might want to view https://nw-digital-radio.groups.io/g/udrc/topic/web_based_udrc_setup_for/4816993  -- especially if you are attached to a Yaesu or Bridgecom repeater. 


On Fri, Apr 21, 2017 at 7:58 AM, <kc9zjf@...> wrote:

so last night my image seemed to get corrupted, re-installed new and now getting below errors I"m seeing 

any thoughts






--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   

Dstar Repeater

kc9zjf@...
 

so last night my image seemed to get corrupted, re-installed new and now getting below errors I"m seeing 

any thoughts



UDRC PTT Keying Application Note #udrc-ii #ptt

 

New wiki post:

https://nw-digital-radio.groups.io/g/udrc/wiki/PTT-Keying-Application-Note---UDRC-II

Re: Compass Linux and RPi 3b BlueTooth?

Nick Ellson
 

OK, so looks like this was uncommented out in the /boot/config.txt <sigh> I put the comment back and Bluetooth is WORKING!

# Enable serial console
#dtoverlay=pi3-disable-bt

Re: Compass Nightly Build FLDIGI, no port audo?

Nick Ellson
 

Nevermind, did not realize that I ran Basil's Direwolf AX.25 Packet stuff first, so Direwolf had the soundcard locked. I stopped the direwolf service and FLDIGI/WSJTX found the audio card and I got waterfalls.


Nick

Re: Web based UDRC setup for Repeaters and Hotspots

 

For a basic install

To setup the repeater, select the "Radio Type" then you press the "Modem Level" button, to setup the UDRC levels.
Input the repeater callsign plus the Module ID and submit.

Inline image 1

Similarly, for the gateway, put in the gateway callsign (matches repeater callsign), without a module ID (the 'G' is not input).
Press the "Guess Location" button, and edit the returned Lat/Lon and Location

Putting in this information will pre-fill URLs, and logins.  (If you want to use ircDDB.net, you will need to add the password)

Enable services,  DPlus requires a US Trust registered USER CALLSIGN to operate.

Submit.  If you want the latest http://ar-dns.net gateway and reflector lists, press the Update Hosts button. 

Use the Commands tab, to start and stop services -- you can reboot the system, and you can enable UPNP port forwarding if your router supports it.

Inline image 2

Web based UDRC setup for Repeaters and Hotspots

 

A public beta for a new image is available for anonymous ftp from ftp://starbuck.hays.org -- it makes setting up a Yaesu or Bridgecom repeater using a web browser, very quick and easy. 

The dstarconfig-extras.tar file has already been applied, there is no need to download it, unless you were in the private beta and want to add features.  (To apply it to an old beta, cd / and untar the file)

This image is based on a nightly Compass Linux build of current Jesse Raspbian and has up to date packages.

Unzip the image file and use the directions at 
https://www.raspberrypi.org/documentation/installation/installing-images/README.md
to create a SD Card (4GB or larger)

Insert the card into a Raspberry Pi 2 or 3, with a UDRC installed and boot up.

Login using ssh (or keyboard and monitor). If using ssh you will need to find
the IP address, usually this can be found under DHCP leases on your router. On
MacOS or Linux, you may find it at compass.local

Username: pi
Password: compass1

(Be sure to change the password for security)

Inspect the filesystem and see if it expanded to fill your SD card, (use the
df command), if not then use 

sudo raspi-config
select Advanced Options
select Expand Filesystem

After a reboot, the filesystem should now be expanded.

Once its booted up, point a modern browser at http://<IP ADDR>:8073

If the interface doesn't come up (give it a minute) then from the command line

sudo systemctl start dstarconfig

The login for the configuration tool is:

admin
compass1

(Be sure to change the password in the 'User Account' page for security)

Enjoy.

20170405-web-udrc.img does not have a GUI, and thus VNC is not installed. It
is intended for Web configuration and there is a dashboard for monitoring its
operation.

Here is the home page of the tool:
Inline image 1

--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   

Compass Nihtly Build FLDIGI, no port audo?

Nick Ellson
 

After installing Compass Linux from the 4-8-2017 nightly build (in hopes of having RPi BlueTooth working) I saw my UDRC-II in "aplay -l" as before, but when I run FLDIGI, the Port Audio is grayed out as if it is not seeing the sound system?


I did run the set-up:

pi@hammy:~$ curl -L -s https://goo.gl/7rXUFJ > set-udrc-din6.sh

pi@hammy:~$ chmod +x set-udrc-din6.sh

pi@hammy:~$ sudo ~/set-udrc-din6.sh

Prior to running FLDIGI.

Nick