Date   

Re: WSJT-X with UDRC anyone?

Nick Ellson
 

Found that setting John, going to have to delete all my other accounts on groups.io so I can add them as aliases..

Thanks for the tip!

Nick Ellson - from iPhone (forgive typos)
CCIE #20018; VCIX-NV, CNSE
Network Hobbyist
"Educating Layer 8, one user at a time."

On Dec 8, 2016, at 11:28 AM, John D Hays - K7VE <john@...> wrote:

As a side note, if you go to your groups.io account, you can list any emails you might reply from.


Select Login -> Advanced Settings for Email Aliases   

You can then send email from any alias in the list.

On Thu, Dec 8, 2016 at 11:18 AM, <nick@...> wrote:


Was unable to reply to any of the threads I had with udrc@..., so I am re-attaching to the groups.io threads with my primary e-mail.



--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   


Re: WSJT-X with UDRC anyone?

 

As a side note, if you go to your groups.io account, you can list any emails you might reply from.


Select Login -> Advanced Settings for Email Aliases   

You can then send email from any alias in the list.

On Thu, Dec 8, 2016 at 11:18 AM, <nick@...> wrote:


Was unable to reply to any of the threads I had with udrc@..., so I am re-attaching to the groups.io threads with my primary e-mail.



--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   


Re: WSJT-X with UDRC anyone?

Nick Ellson
 


Was unable to reply to any of the threads I had with udrc@..., so I am re-attaching to the groups.io threads with my primary e-mail.

I haven't been back at this lately since I found an alternate soundcard solution for my Raspberry PI needs.

But I want to see if I can get tis UDRC-II to work with my Yaesu 857D.

Perhaps I have an incompatible radio (sound on the wrong pin, or not how the UDRC wants to see it. I don't have the tools I need to tell what's going on.


I did get the card to do some VHF Direwolf KISS connectivity, but that's about it.


Nick





Re: Where did the modulation go . . .

ab9ca@...
 

Interesting that something has changed. I set up those memories several years ago off some reference that I found online. I did not make up those settings. And so long as we had internet at the rptr site they worked FB. Used them often. Set up several other radios in the area the same way, and those also worked FB. But now it is required that the call be removed and we have 7 spaces with and E or an I . . . . 


Thanks to both you and Dan for the info.


73 de dave

ab9ca/4



Re: Where did the modulation go . . .

 

Your UR should be 7 spaces and an E, not call sign and E and the same for status but using I. 

These are radio configuration issues not dstarrepeater or ircddbgatewayd problems. 

Please visit a D-STAR primer site to understand how the the various fields should be set. 

On Dec 7, 2016 19:15, <ab9ca@...> wrote:

They are both turned ON in ircddbgatewayconfig.


When I try an ECHO test I get this in the ircddb log:


M: 2016-12-08 02:58:55: AB9CA    is trying to G2 route to callsign KI4SAZ E

M: 2016-12-08 02:58:56: USER: AB9CA    KI4SAZ C KI4SAZ G 70.196.133.102

M: 2016-12-08 02:58:59: AB9CA    is trying to G2 route to callsign KI4SAZ E

M: 2016-12-08 02:59:02: USER: AB9CA    KI4SAZ C KI4SAZ G 70.196.133.102


KI4SAZ is the call of the local rptr and the hotspot. 

I have a port forward set up in the router for port 40000 for G2 routing. Is that the port that is needed?

When I first set it up I used my personal call and got the same results. 

I get nothing back when I try STATUS and no audio playback from the ECHO command. 

But the basic hotspot seems to be working thru the rptr. I can link and unlink, talk and hear via the rptr with the hotspot providing the internet connectivity. We have lost the internet at the tower. One too many lightning strikes on the tower. Apparently that nice copper phone line provides a good ground. 

73 de dave
ab9ca/4


Re: Where did the modulation go . . .

Dan Porter (AI2M)
 

You need to put the following in the radio's Your Call field:
_______E (7 spaces before the E)
_______I (7 spaces before the I)
for echo and info respectively. 

Dan, AI2M

On Dec 7, 2016, at 10:15 PM, ab9ca@... wrote:

They are both turned ON in ircddbgatewayconfig.


When I try an ECHO test I get this in the ircddb log:


M: 2016-12-08 02:58:55: AB9CA    is trying to G2 route to callsign KI4SAZ E

M: 2016-12-08 02:58:56: USER: AB9CA    KI4SAZ C KI4SAZ G 70.196.133.102

M: 2016-12-08 02:58:59: AB9CA    is trying to G2 route to callsign KI4SAZ E

M: 2016-12-08 02:59:02: USER: AB9CA    KI4SAZ C KI4SAZ G 70.196.133.102


KI4SAZ is the call of the local rptr and the hotspot. 

I have a port forward set up in the router for port 40000 for G2 routing. Is that the port that is needed?

When I first set it up I used my personal call and got the same results. 

I get nothing back when I try STATUS and no audio playback from the ECHO command. 

But the basic hotspot seems to be working thru the rptr. I can link and unlink, talk and hear via the rptr with the hotspot providing the internet connectivity. We have lost the internet at the tower. One too many lightning strikes on the tower. Apparently that nice copper phone line provides a good ground. 

73 de dave
ab9ca/4


Re: Where did the modulation go . . .

ab9ca@...
 

They are both turned ON in ircddbgatewayconfig.


When I try an ECHO test I get this in the ircddb log:


M: 2016-12-08 02:58:55: AB9CA    is trying to G2 route to callsign KI4SAZ E

M: 2016-12-08 02:58:56: USER: AB9CA    KI4SAZ C KI4SAZ G 70.196.133.102

M: 2016-12-08 02:58:59: AB9CA    is trying to G2 route to callsign KI4SAZ E

M: 2016-12-08 02:59:02: USER: AB9CA    KI4SAZ C KI4SAZ G 70.196.133.102


KI4SAZ is the call of the local rptr and the hotspot. 

I have a port forward set up in the router for port 40000 for G2 routing. Is that the port that is needed?

When I first set it up I used my personal call and got the same results. 

I get nothing back when I try STATUS and no audio playback from the ECHO command. 

But the basic hotspot seems to be working thru the rptr. I can link and unlink, talk and hear via the rptr with the hotspot providing the internet connectivity. We have lost the internet at the tower. One too many lightning strikes on the tower. Apparently that nice copper phone line provides a good ground. 

73 de dave
ab9ca/4


Re: Where did the modulation go . . .

 

If they are turned on, they should work.  Watch the log for an error

tail -f /var/log/opendv/ircddbgatewayd.log



On Wed, Dec 7, 2016 at 11:12 AM, <ab9ca@...> wrote:

OK, seem to have nearly all of it working now. 

Can link and unlink, can talk and hear on the reflectors once linked. 


But I can't get the ECHO test nor the STATUS inquiry to work. I would really like to have these available. What is needed to get these working? Both are turned on the ircddbgatewayconfig.


73 de dave

ab9ca/4





--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   


Re: Where did the modulation go . . .

ab9ca@...
 

OK, seem to have nearly all of it working now. 

Can link and unlink, can talk and hear on the reflectors once linked. 


But I can't get the ECHO test nor the STATUS inquiry to work. I would really like to have these available. What is needed to get these working? Both are turned on the ircddbgatewayconfig.


73 de dave

ab9ca/4



Re: Where did the modulation go . . .

 



On Tue, Dec 6, 2016 at 3:06 PM, <ab9ca@...> wrote:

Some further progress made.


Got it decoding the TX from the HT to the dstarrepeater log:



Congratulations
 

M: 2016-12-06 22:52:45: Radio header decoded - My: AB9CA   /DAVE  Your: CQCQCQ    Rpt1: DIRECT    Rpt2: DIRECT    Flags: 00 00 00

M: 2016-12-06 22:52:45: Received a non-repeater packet, ignoring

M: 2016-12-06 22:52:45: Current DC offset: -0.005470

M: 2016-12-06 22:52:45: AMBE for AB9CA     Frames: 0.5s, Silence: 4.3%, BER: 0.0%

M: 2016-12-06 22:52:46: Transmitting to - My: AB9CA  C/      Your: AB9CA     Rpt1: AB9CA  C  Rpt2: AB9CA  C  Flags: 01 00 00

M: 2016-12-06 22:55:05: Network header received - My: 2M0JLS  /5100  Your: CQCQCQ    Rpt1: AB9CA  G  Rpt2: AB9CA  C  Flags: 00 00 00

M: 2016-12-06 22:55:05: Transmitting to - My: 2M0JLS  /5100  Your: CQCQCQ    Rpt1: AB9CA  G  Rpt2: AB9CA  C  Flags: 00 00 00

M: 2016-12-06 22:55:05: Stats for 2M0JLS    Frames: 0.7s, Loss: 0.0%, Packets: 0/34


And got it to connect to a reflector via the setup in ircddbgatewayconfig. It connects at startup OK.

Good

 
Can't get any commands through it from the HT. Can't get it to link, unlink, echo, or report status via command from the HT. I am assuming the echo and status work with the UDRC?

See below  -- these commands are a function of the ircddbgateway software, not the UDRC.  The UDRC is just like any other modem one would use.
 
Did RX some audio from the reflector. 

Had to set up the port forwarding manually, the script did not work with this Belkin router. 

See if the router has a UPNP option for the script to work, but manual is probably better as long as you have a fixed LAN address.
 

So . . . what is the likely cause of not being able to get commands through from the HT? That part was working before I ran into the roadblock that killed the TX audio. 

And is it normal to see this line:
M: 2016-12-06 22:52:45: Received a non-repeater packet, ignoring

in the dstarrepeater log? 

And is it normal to see the RPTR1 and RPTR2 shown as 'DIRECT' even when this is not what is programmed into the HT RPTR1 and RPTR2 slots.

This probably your problem.  Are you using DR Mode (modern D-STAR radios), with mode set for DUPLEX with an offset of 0.00 Mhz.? 

If the radio is not set to DUPLEX, it will not set the right bit for repeating and that is what forces DIRECT for RPT1 and RPT2.
 

73 de dave
ab9ca/4



--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   


Re: Where did the modulation go . . .

ab9ca@...
 

Some further progress made.


Got it decoding the TX from the HT to the dstarrepeater log:


M: 2016-12-06 22:52:45: Radio header decoded - My: AB9CA   /DAVE  Your: CQCQCQ    Rpt1: DIRECT    Rpt2: DIRECT    Flags: 00 00 00

M: 2016-12-06 22:52:45: Received a non-repeater packet, ignoring

M: 2016-12-06 22:52:45: Current DC offset: -0.005470

M: 2016-12-06 22:52:45: AMBE for AB9CA     Frames: 0.5s, Silence: 4.3%, BER: 0.0%

M: 2016-12-06 22:52:46: Transmitting to - My: AB9CA  C/      Your: AB9CA     Rpt1: AB9CA  C  Rpt2: AB9CA  C  Flags: 01 00 00

M: 2016-12-06 22:55:05: Network header received - My: 2M0JLS  /5100  Your: CQCQCQ    Rpt1: AB9CA  G  Rpt2: AB9CA  C  Flags: 00 00 00

M: 2016-12-06 22:55:05: Transmitting to - My: 2M0JLS  /5100  Your: CQCQCQ    Rpt1: AB9CA  G  Rpt2: AB9CA  C  Flags: 00 00 00

M: 2016-12-06 22:55:05: Stats for 2M0JLS    Frames: 0.7s, Loss: 0.0%, Packets: 0/34


And got it to connect to a reflector via the setup in ircddbgatewayconfig. It connects at startup OK.

Can't get any commands through it from the HT. Can't get it to link, unlink, echo, or report status via command from the HT. I am assuming the echo and status work with the UDRC?

Did RX some audio from the reflector. 

Had to set up the port forwarding manually, the script did not work with this Belkin router. 

So . . . what is the likely cause of not being able to get commands through from the HT? That part was working before I ran into the roadblock that killed the TX audio. 

And is it normal to see this line:
M: 2016-12-06 22:52:45: Received a non-repeater packet, ignoring

in the dstarrepeater log? 

And is it normal to see the RPTR1 and RPTR2 shown as 'DIRECT' even when this is not what is programmed into the HT RPTR1 and RPTR2 slots.

73 de dave
ab9ca/4


Re: DTMF and/or COR

K4DLS
 

My club's repeater is going into a remote location.  I need to be able, at a minimum, to turn the transmitter on and off using DTMF codes transmitted over the input frequency.  It would be nice if the codes could be muted so that they are not re-transmitted by the repeater.  In our current setup, using CAT controllers, I am able to do this and several other functions such as turning the receive tone on and off, and turning the link to another repeater on and off. 


Right now I'm looking for the minimum requirement of transmitter control.  I'm not a programmer and don't aspire to be - no talent.  :D  If anyone can help, I'd appreciate it.  That's all the incentive I can offer.


BTW, the site for this repeater is being rebuilt as we speak. The existing Hi-Pro repeater was at the local utility company's tower site, and that tower was taken out last Wednesday when an EF2 tornado hit it.  Pictures at https://www.facebook.com/mcminnamateurradio.  We temporarily moved the 2m and 440 repeaters to another site.


Re: Where did the modulation go . . .

 

actually TX is always on the same pin for 1200 or 9600, it's the receive that must hit the right pin.

The control that you need to play with in alsamixer is:

ADC Level (It is usually pretty forgiving)




On Mon, Dec 5, 2016 at 4:05 PM, <ab9ca@...> wrote:

Yes, it must be in order for any audio to TX. I tested at both 1200 and 9600 baud. Works only at 9600. 


73 de dave

ab9ca/4





--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   


Re: Where did the modulation go . . .

ab9ca@...
 

Yes, it must be in order for any audio to TX. I tested at both 1200 and 9600 baud. Works only at 9600. 


73 de dave

ab9ca/4



Re: Where did the modulation go . . .

 

Is the radio set for 9600 baud packet 

FT-7900R Operating Manual - Yaesu pages 10-11



On Mon, Dec 5, 2016 at 2:46 PM, <ab9ca@...> wrote:

Some progress to report. 


I don't have a microSD card reader so cannot go all the way back to square 1 right now. 


But in the process of running through the steps, I went in to edit /boot/config.txt and found that these two lines had been added to the end of the file:


#enable_uart=1

#dtoverlay=w1-gpio


I added the # on the line.


The only item not commented out in that file is this line:


# Enable audio (loads snd_bcm2835)

# dtparam=audio=on

force_turbo=1



Once those two lines were commented out and the RPi rebooted TX audio came alive again. I can hear the messages playing.


Unfortunately I have no audio detect. I can key the HT, see the RX indicator light up on the FT-7900, hear it RX audio, but nothing prints in the dstarrepeater@1.log. 


I have switched the RX invert option in dstarrepeaterconfig. Checked that alsamixer was not muted. Adjusted the level of PCM on alsamixer to mid range. What else? 


Here is the result of the 'sudo gpio readall' command:


pi@compass:~ $ sudo gpio readall

 +-----+-----+---------+------+---+---Pi 3---+---+------+---------+-----+-----+

 | BCM | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | BCM |

 +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+

 |     |     |    3.3v |      |   |  1 || 2  |   |      | 5v      |     |     |

 |   2 |   8 |   SDA.1 | ALT0 | 1 |  3 || 4  |   |      | 5V      |     |     |

 |   3 |   9 |   SCL.1 | ALT0 | 1 |  5 || 6  |   |      | 0v      |     |     |

 |   4 |   7 | GPIO. 7 | ALT0 | 0 |  7 || 8  | 0 | IN   | TxD     | 15  | 14  |

 |     |     |      0v |      |   |  9 || 10 | 1 | IN   | RxD     | 16  | 15  |

 |  17 |   0 | GPIO. 0 |   IN | 0 | 11 || 12 | 1 | ALT0 | GPIO. 1 | 1   | 18  |

 |  27 |   2 | GPIO. 2 |  OUT | 0 | 13 || 14 |   |      | 0v      |     |     |

 |  22 |   3 | GPIO. 3 |  OUT | 0 | 15 || 16 | 0 | OUT  | GPIO. 4 | 4   | 23  |

 |     |     |    3.3v |      |   | 17 || 18 | 0 | OUT  | GPIO. 5 | 5   | 24  |

 |  10 |  12 |    MOSI |   IN | 0 | 19 || 20 |   |      | 0v      |     |     |

 |   9 |  13 |    MISO |   IN | 0 | 21 || 22 | 1 | IN   | GPIO. 6 | 6   | 25  |

 |  11 |  14 |    SCLK |   IN | 0 | 23 || 24 | 1 | IN   | CE0     | 10  | 8   |

 |     |     |      0v |      |   | 25 || 26 | 1 | IN   | CE1     | 11  | 7   |

 |   0 |  30 |   SDA.0 |   IN | 1 | 27 || 28 | 1 | IN   | SCL.0   | 31  | 1   |

 |   5 |  21 | GPIO.21 |   IN | 1 | 29 || 30 |   |      | 0v      |     |     |

 |   6 |  22 | GPIO.22 |  OUT | 0 | 31 || 32 | 0 | IN   | GPIO.26 | 26  | 12  |

 |  13 |  23 | GPIO.23 |  OUT | 1 | 33 || 34 |   |      | 0v      |     |     |

 |  19 |  24 | GPIO.24 | ALT0 | 1 | 35 || 36 | 0 | IN   | GPIO.27 | 27  | 16  |

 |  26 |  25 | GPIO.25 |   IN | 0 | 37 || 38 | 0 | ALT0 | GPIO.28 | 28  | 20  |

 |     |     |      0v |      |   | 39 || 40 | 0 | ALT0 | GPIO.29 | 29  | 21  |

 +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+

 | BCM | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | BCM |

 +-----+-----+---------+------+---+---Pi 3---+---+------+---------+-----+-----+

pi@compass:~ $ 

pi@compass:~ $ 

pi@compass:~ $ 



Does this look right or do I still have some pins of the 40 pin header still messed up?

73 de dave
ab9ca/4






--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   


Re: Where did the modulation go . . .

ab9ca@...
 

Some progress to report. 


I don't have a microSD card reader so cannot go all the way back to square 1 right now. 


But in the process of running through the steps, I went in to edit /boot/config.txt and found that these two lines had been added to the end of the file:


#enable_uart=1

#dtoverlay=w1-gpio


I added the # on the line.


The only item not commented out in that file is this line:


# Enable audio (loads snd_bcm2835)

# dtparam=audio=on

force_turbo=1



Once those two lines were commented out and the RPi rebooted TX audio came alive again. I can hear the messages playing.


Unfortunately I have no audio detect. I can key the HT, see the RX indicator light up on the FT-7900, hear it RX audio, but nothing prints in the dstarrepeater@1.log. 


I have switched the RX invert option in dstarrepeaterconfig. Checked that alsamixer was not muted. Adjusted the level of PCM on alsamixer to mid range. What else? 


Here is the result of the 'sudo gpio readall' command:


pi@compass:~ $ sudo gpio readall

 +-----+-----+---------+------+---+---Pi 3---+---+------+---------+-----+-----+

 | BCM | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | BCM |

 +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+

 |     |     |    3.3v |      |   |  1 || 2  |   |      | 5v      |     |     |

 |   2 |   8 |   SDA.1 | ALT0 | 1 |  3 || 4  |   |      | 5V      |     |     |

 |   3 |   9 |   SCL.1 | ALT0 | 1 |  5 || 6  |   |      | 0v      |     |     |

 |   4 |   7 | GPIO. 7 | ALT0 | 0 |  7 || 8  | 0 | IN   | TxD     | 15  | 14  |

 |     |     |      0v |      |   |  9 || 10 | 1 | IN   | RxD     | 16  | 15  |

 |  17 |   0 | GPIO. 0 |   IN | 0 | 11 || 12 | 1 | ALT0 | GPIO. 1 | 1   | 18  |

 |  27 |   2 | GPIO. 2 |  OUT | 0 | 13 || 14 |   |      | 0v      |     |     |

 |  22 |   3 | GPIO. 3 |  OUT | 0 | 15 || 16 | 0 | OUT  | GPIO. 4 | 4   | 23  |

 |     |     |    3.3v |      |   | 17 || 18 | 0 | OUT  | GPIO. 5 | 5   | 24  |

 |  10 |  12 |    MOSI |   IN | 0 | 19 || 20 |   |      | 0v      |     |     |

 |   9 |  13 |    MISO |   IN | 0 | 21 || 22 | 1 | IN   | GPIO. 6 | 6   | 25  |

 |  11 |  14 |    SCLK |   IN | 0 | 23 || 24 | 1 | IN   | CE0     | 10  | 8   |

 |     |     |      0v |      |   | 25 || 26 | 1 | IN   | CE1     | 11  | 7   |

 |   0 |  30 |   SDA.0 |   IN | 1 | 27 || 28 | 1 | IN   | SCL.0   | 31  | 1   |

 |   5 |  21 | GPIO.21 |   IN | 1 | 29 || 30 |   |      | 0v      |     |     |

 |   6 |  22 | GPIO.22 |  OUT | 0 | 31 || 32 | 0 | IN   | GPIO.26 | 26  | 12  |

 |  13 |  23 | GPIO.23 |  OUT | 1 | 33 || 34 |   |      | 0v      |     |     |

 |  19 |  24 | GPIO.24 | ALT0 | 1 | 35 || 36 | 0 | IN   | GPIO.27 | 27  | 16  |

 |  26 |  25 | GPIO.25 |   IN | 0 | 37 || 38 | 0 | ALT0 | GPIO.28 | 28  | 20  |

 |     |     |      0v |      |   | 39 || 40 | 0 | ALT0 | GPIO.29 | 29  | 21  |

 +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+

 | BCM | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | BCM |

 +-----+-----+---------+------+---+---Pi 3---+---+------+---------+-----+-----+

pi@compass:~ $ 

pi@compass:~ $ 

pi@compass:~ $ 



Does this look right or do I still have some pins of the 40 pin header still messed up?

73 de dave
ab9ca/4




Re: Where did the modulation go . . .

 

If you are setting up a hotspot -- follow the directions here https://nw-digital-radio.groups.io/g/udrc/wiki/UDRC%E2%84%A2-For-Simplex-Hotspots-and-Converted-Analog-Repeaters#Install-Compass-Linux


Follow the instructions, including the installation of Compass Linux, step by step and exactly -- (except only install the applications listed for dstarrepeater and ircddbgateway, not direwolf or xastir, etc.)

On Mon, Dec 5, 2016 at 11:36 AM, <ab9ca@...> wrote:


John,

 > The wired/wireless is not at all related to whether dstarrepeaterd is
 > working.

I do not doubt that whatever connection exists between logging onto 
the wireless and killing the UDRC is tenuous, but, rest assured, there 
is a connection. That is what happened. There is definitely a 
connection in there somewhere. It may be inadvertent, perhaps some 
script seizes pin 7 although it does not need to. But there is a 
connection.

Fine on the restart, but . . . .

What do I need to do to delete or supersede the image now on the RPi? 
As I mentioned in a previous post, I picked this up after another 
fellow had done all of the early work. So I don't know what he did. 
And I don't know how to undo it. I don't know which files are stored 
where nor how they were created. How do I wipe the slate clean?

I tried downloading a new copy of dstarrepeaterd. But all it did was 
come back and tell me I already had the latest version.

The rig is a Yaesu FT-7900 for the hotspot.

73 de dave
ab9ca/4





--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   


Re: Where did the modulation go . . .

Ian
 

Dave,

I can sympathize with you as I had similar problem in that my URDC11 was working fine a few days ago when I last fired it up. On starting it on Friday I found that it wasn't transmitting audio; after spending some time ( days ) trying to troubleshoot the problem I bit the bullet and downloaded the latest version of CompassLinux, followed the instructions on the Wiki and, after one or two changes I am back up and running.

Whilst this will not get to the bottom of your problem, it would relieve the frustration, you would have a working system again and time to troubleshoot if you wished.

Grab the latest image from < http://archive.compasslinux.org/images/wilderness/ >, the ones I used are 3rd and 4th from the bottom, unzip then DD the image to a fresh SD card.

Troubleshooting something other than a " vanilla " install is always difficult.

Regards,

Ian..


Re: Where did the modulation go . . .

ab9ca@...
 


John,

 > The wired/wireless is not at all related to whether dstarrepeaterd is
 > working.

I do not doubt that whatever connection exists between logging onto 
the wireless and killing the UDRC is tenuous, but, rest assured, there 
is a connection. That is what happened. There is definitely a 
connection in there somewhere. It may be inadvertent, perhaps some 
script seizes pin 7 although it does not need to. But there is a 
connection.

Fine on the restart, but . . . .

What do I need to do to delete or supersede the image now on the RPi? 
As I mentioned in a previous post, I picked this up after another 
fellow had done all of the early work. So I don't know what he did. 
And I don't know how to undo it. I don't know which files are stored 
where nor how they were created. How do I wipe the slate clean?

I tried downloading a new copy of dstarrepeaterd. But all it did was 
come back and tell me I already had the latest version.

The rig is a Yaesu FT-7900 for the hotspot.

73 de dave
ab9ca/4



Re: DTMF and/or COR

 

These types of projects typically get solved by someone who needs the functionality for themselves and have the skill to code it, then they may share it with the rest of the community.

Without a definition of what exactly you are looking for the program to do, it is hard to determine if it can be done.  Decoding DTMF is well enough understood, but then what?  

If you are looking for a 'volunteer', there needs to be an incentive for said 'volunteer' ...

On Mon, Dec 5, 2016 at 2:51 AM, <k4dls@...> wrote:
Any volunteers?
_._,_._,_


--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223