Date   

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
   


Re: Where did the modulation go . . .

 

Dave,

I would suggest building a new image and following the steps on the Wiki to get to a known state.

What are you hooking to (DR-1X, Radio for Hotspot)?

On Mon, Dec 5, 2016 at 9:58 AM, <ab9ca@...> wrote:

Still needing some help on this one. 


Sent a note the other day to that effect and have heard nothing.


How about some helpl?


Sorry about that.
 

I have unmasked dstarrepeaterd and reenabled it. It starts but I still have the issue of pin 7. It is still showing as IN and not ALTO. What do I need to do to get this thing working?


See above
 

I guess you do not believe me when I tell you what happened. Let me repeat it once again. This is what happened and you need to start from here in troubleshooting this issue. 


We believe you, but we are not there and cannot see what else may have affected your installation.
 

I had the UDRC running. It was playing the canned messages and I could see on the ircddbgatewayd tail that I was connecting to the reflectors. But in the process of trying to get the port forwarding set up on the router I ended up losing wired internet. So I logged onto the wireless. Somehow this caused me to lose pin 7 of the GPIO. Maybe it was the logging on process? Or maybe something else. Once I logged onto the wireless it has not worked since.  Dunno if it matters but the wired was still connected to the RPi. The wired cat5 connection was still active but no internet access. It could go as far as the router but no further. I had typo'ed the addresses of the LAN and WAN sides of the router and they were set to the same network subset. But the wireless side still worked. 


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

So what script in the wireless logging-on process would steal GPIO pin 7? And, if dstarrepeaterd needs pin 7, why does does it not steal it back? Or, why, at the very least do I not get a resource conflict error message from the OS? 


I don't know.
 

Is there not some way to interrogate the OS and have it tell whom has claimed pin 7? 


Perhaps Jeremy knows. 

If all of the above fails then what do I need to do to start over? Wipe the slate clean. I'm not opposed to doing that if that is what is needed to get this thing working. But I need to know how to go about that process. 


See above.  Do not make any other changes until it is working from the instructions in the Wiki, then only make 1 change at a time, test, and roll back if something breaks.
 

Still looking for some help . . . .


dave

ab9ca/4


_

--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   


Re: DTMF and/or COR

K4DLS
 

Any volunteers?


Re: Where did the modulation go . . .

ab9ca@...
 

Still needing some help on this one. 


Sent a note the other day to that effect and have heard nothing.


How about some helpl?


I have unmasked dstarrepeaterd and reenabled it. It starts but I still have the issue of pin 7. It is still showing as IN and not ALTO. What do I need to do to get this thing working?


I guess you do not believe me when I tell you what happened. Let me repeat it once again. This is what happened and you need to start from here in troubleshooting this issue. 


I had the UDRC running. It was playing the canned messages and I could see on the ircddbgatewayd tail that I was connecting to the reflectors. But in the process of trying to get the port forwarding set up on the router I ended up losing wired internet. So I logged onto the wireless. Somehow this caused me to lose pin 7 of the GPIO. Maybe it was the logging on process? Or maybe something else. Once I logged onto the wireless it has not worked since.  Dunno if it matters but the wired was still connected to the RPi. The wired cat5 connection was still active but no internet access. It could go as far as the router but no further. I had typo'ed the addresses of the LAN and WAN sides of the router and they were set to the same network subset. But the wireless side still worked. 


So what script in the wireless logging-on process would steal GPIO pin 7? And, if dstarrepeaterd needs pin 7, why does does it not steal it back? Or, why, at the very least do I not get a resource conflict error message from the OS? 


Is there not some way to interrogate the OS and have it tell whom has claimed pin 7? 


If all of the above fails then what do I need to do to start over? Wipe the slate clean. I'm not opposed to doing that if that is what is needed to get this thing working. But I need to know how to go about that process. 


Still looking for some help . . . .


dave

ab9ca/4



Re: ircnodedashboard updated

 

I might add that this has only been tested on a Raspberry Pi running Compass Linux with the Compass Linux package for ircddbgateway.  The method for getting the data is accomplished reading certain files in the system on a set interval (default is 10 seconds).  It may be necessary to modify webserver.js (and possibly public/index.html) on other distributions.  A search for loadavg in the source will get you into the right area.

On Sun, Dec 4, 2016 at 5:24 PM, John D. Hays <john@...> wrote:
I received a request to add some CPU monitoring capability to the Dashboard.  If you installed using the procedure at https://github.com/johnhays/ircNodeDashboard -- go to /var/www-node/ircNodeDashboard and issue a

git pull

and restart the dashboard

sudo systemctl restart ircnodedashboard.service 

At the bottom of the dashboard the following will update every 10 seconds (edit webserver.js to change interval).

Inline image 1

--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   




--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   


Re: ircnodedashboard updated

 

If you have modified any files after the pull, you cannot make a pull on top of them. (Well you can, but you need to have an advanced understanding of git fetch and merge).

On Mon, Dec 5, 2016 at 6:31 AM, Rich KR4PI <rich.schnieders@...> wrote:

Thanks John, that is a great addition to the dashboard. The only issue I had was I had to delete the index.html file in public before it would accept the pull and change the file. Once I deleted index.html git pull worked and it showed up on the web page.

Thanks again.

Rich, KR4PI



--


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
   


Re: DTMF and/or COR

 

I am not volunteering, but what exactly would you want the program to do?

On Dec 5, 2016 7:06 AM, <k4dls@...> wrote:
Great!  All we need now is a programmer to do it.


Re: DTMF and/or COR

K4DLS
 

Great!  All we need now is a programmer to do it.


Re: ircnodedashboard updated

 

Thanks John, that is a great addition to the dashboard. The only issue I had was I had to delete the index.html file in public before it would accept the pull and change the file. Once I deleted index.html git pull worked and it showed up on the web page.

Thanks again.

Rich, KR4PI