[arm-allstar] Echolink server reporting issues
B. Cater
TxLawMan at aol.com
Sun Nov 1 17:59:48 EST 2015
A while back I added echolink to my RPi2 Allstar node. It seemed to work
fine at the time. I converted it from a wired Ethernet connection, to the
recommended IOGear wireless dongle and now it doesn't report to the Echolink
server.
Of course I set up the Echolink.conf file and changed its name from
echolink.xxx to echolink.conf
I forwarded the Echolink ports to the same IP address that I had my Allstar
node ports forwarded to. Are there ports to open in the dongle itself? I saw
no access to anything like that.
My Allstar node reports to its server just fine.
I did notice that when I boot up my node and it announces its IP Address, it
announces 127.0.0.1, instead of a 192.168.x.x address like it used to. Could
that be causing problems? You would think if it were, the Allstar side would
not work either.
Any ideas on what I could check next?
Brian
KC5YSM
#42045
-----Original Message-----
From: arm-allstar-bounces at hamvoip.org
[mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of
arm-allstar-request at hamvoip.org
Sent: Saturday, October 31, 2015 12:00 PM
To: arm-allstar at hamvoip.org
Subject: arm-allstar Digest, Vol 17, Issue 27
Send arm-allstar mailing list submissions to
arm-allstar at hamvoip.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
or, via email, send a message with subject or body 'help' to
arm-allstar-request at hamvoip.org
You can reach the person managing the list at
arm-allstar-owner at hamvoip.org
When replying, please edit your Subject line so it is more specific than
"Re: Contents of arm-allstar digest..."
Today's Topics:
1. Re: arm-allstar Digest, Vol 17, Issue 26 (Bryan D. Boyle)
2. Re: arm-allstar Digest, Vol 17, Issue 26 (Jay Freeman)
3. GPIO control for ctcss (Doug Crompton)
----------------------------------------------------------------------
Message: 1
Date: Fri, 30 Oct 2015 19:58:06 -0400
From: "Bryan D. Boyle" <bdboyle at bdboyle.com>
To: arm-allstar at hamvoip.org
Subject: Re: [arm-allstar] arm-allstar Digest, Vol 17, Issue 26
Message-ID: <5634040E.4040008 at bdboyle.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
On 10/30/2015 1:00 PM, arm-allstar-request at hamvoip.org wrote:
> Message: 1
> Date: Thu, 29 Oct 2015 10:18:55 -0700
> From: Jay Freeman <wt9s at me.com>
> To: "arm-allstar at hamvoip.org" <arm-allstar at hamvoip.org>
> Subject: [arm-allstar] GPIO control of fan
> Message-ID: <0NWZ00MIXS3JN500 at st11p00im-asmtp001.me.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi folks,
>
> I?ve been running my repeater here with an Arcom RC210 controller for
years. I have the repeater, an IRLP computer, and the Allstar node (now on a
Pi) each connected to a port on the controller. The controller currently
switches on a fan for 60 seconds whenever PTT goes active. I am thinking of
ditching the IRLP and the Arcom and running my repeater with the Allstar
node as the controller. I?m looking for some pointers on how to control the
fan with either the URI GPIO, or the USB GPIO described in the How-Tos. I
guess using the URI would be simpler.
>
> Thanks,
You won't be sorry to dump the 210. Asterisk is a lot more configurable and
flexible.
Kyle (K0KN) has an explanation of his txfan script that I have running;
there's a diagram of an interface (1 transistor, 1 diode, 1 resistor, and a
relay) on the DMK site that isolates the uri from the controlled fan. Lots
of ways of doing it...I've been using his script for over 3 years with the
DMK suggested interface with 0 problems...the link doug posted was a mod to
that, but can work just as well. Basically, you run the script in the
initial stand-up of the OS, and it checks for a flag that gets set in the
/tmp directory...using the event function of allstar, when the tx keys up,
it sets the flag, and the script counts off 20 seconds, starts the fan...and
keeps it running until some determined time of no key-ups (I use 2 minutes).
Some may think relay control is old skool. But, nothing like hearing the
snap of it closing to let you know that it's actually engaged.
Since I have 3 repeaters in the same location, all tied together through my
hub, it runs fans on all three tx radios, as well as the power supply heat
sink. Been running that way, as I said, for 3 years.
HTH
Bryan WB0YLE
Morrisville PA
------------------------------
Message: 2
Date: Fri, 30 Oct 2015 21:57:41 -0700
From: Jay Freeman <wt9s at me.com>
To: "Bryan D. Boyle" <bdboyle at bdboyle.com>, "arm-allstar at hamvoip.org"
<arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] arm-allstar Digest, Vol 17, Issue 26
Message-ID: <0NX2009GMJ43R300 at mr11p00im-asmtp004.me.com>
Content-Type: text/plain; charset="utf-8"
Thanks for the info guys. It looks like it should be easy enough to run a
fan. BTW, I?m using an AC fan, AC switched by a solid state relay, which is
turned on by transistor switched DC.
The other thing I just noticed is the URI apparently does not have CTCSS
encode on/off logic, is there some way of doing that with a GPIO pin? My
repeater is a converted MastrExec II from Micro Computer Concepts, it has a
TS-64 board installed for CTCSS encode/decode.
Thanks,
Jay ? WT9S
Sent from Mail for Windows 10
From: Bryan D. Boyle
Sent: Friday, October 30, 2015 4:58 PM
To: arm-allstar at hamvoip.org
Subject: Re: [arm-allstar] arm-allstar Digest, Vol 17, Issue 26
On 10/30/2015 1:00 PM, arm-allstar-request at hamvoip.org wrote:
> Message: 1
> Date: Thu, 29 Oct 2015 10:18:55 -0700
> From: Jay Freeman <wt9s at me.com>
> To: "arm-allstar at hamvoip.org" <arm-allstar at hamvoip.org>
> Subject: [arm-allstar] GPIO control of fan
> Message-ID: <0NWZ00MIXS3JN500 at st11p00im-asmtp001.me.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi folks,
>
> I?ve been running my repeater here with an Arcom RC210 controller for
years. I have the repeater, an IRLP computer, and the Allstar node (now on a
Pi) each connected to a port on the controller. The controller currently
switches on a fan for 60 seconds whenever PTT goes active. I am thinking of
ditching the IRLP and the Arcom and running my repeater with the Allstar
node as the controller. I?m looking for some pointers on how to control the
fan with either the URI GPIO, or the USB GPIO described in the How-Tos. I
guess using the URI would be simpler.
>
> Thanks,
You won't be sorry to dump the 210. Asterisk is a lot more configurable and
flexible.
Kyle (K0KN) has an explanation of his txfan script that I have running;
there's a diagram of an interface (1 transistor, 1 diode, 1 resistor, and a
relay) on the DMK site that isolates the uri from the controlled fan. Lots
of ways of doing it...I've been using his script for over 3 years with the
DMK suggested interface with 0 problems...the link doug posted was a mod to
that, but can work just as well. Basically, you run the script in the
initial stand-up of the OS, and it checks for a flag that gets set in the
/tmp directory...using the event function of allstar, when the tx keys up,
it sets the flag, and the script counts off 20 seconds, starts the fan...and
keeps it running until some determined time of no key-ups (I use 2 minutes).
Some may think relay control is old skool. But, nothing like hearing the
snap of it closing to let you know that it's actually engaged.
Since I have 3 repeaters in the same location, all tied together through my
hub, it runs fans on all three tx radios, as well as the power supply heat
sink. Been running that way, as I said, for 3 years.
HTH
Bryan WB0YLE
Morrisville PA
_______________________________________________
arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
Visit the BBB and RPi2 web page - http://hamvoip.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20151030/603c079
e/attachment-0001.html>
------------------------------
Message: 3
Date: Sat, 31 Oct 2015 07:16:39 -0400
From: Doug Crompton <doug at crompton.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: [arm-allstar] GPIO control for ctcss
Message-ID: <BLU171-W6213008E7C851CF71C90C5BA2E0 at phx.gbl>
Content-Type: text/plain; charset="windows-1252"
Jay,
Read the GPIO howto on the hamvoip.org web page. It is easy on the RPi2.
You can access the GPIO pins through a script via DTMF to control anything
you want. Let me know if you are not getting how to do it after you read the
howto. I could give more detail in your specific case.
Remember the GPIO pins on the Pi are 3.3v logic. They would control 5V logic
inputs as long as those inputs were not pulled high to 5V. Otherwise you
need to use either a discrete or chip based level converter.
You could use a bit to turn PL on or off or actually use several bits to
change the PL frequency.
I wrote a script for a ham in FL for a commercial project that controls
radio frequency through RPi2 GPIO using DTMF. It is really quite trivial.
73 Doug
WA3DSP
http://www.crompton.com/hamradio
To: bdboyle at bdboyle.com; arm-allstar at hamvoip.org
From: wt9s at me.com
Date: Fri, 30 Oct 2015 21:57:41 -0700
Subject: Re: [arm-allstar] arm-allstar Digest, Vol 17, Issue 26
Thanks for the info guys. It looks like it should be easy enough to run a
fan. BTW, I?m using an AC fan, AC switched by a solid state relay, which is
turned on by transistor switched DC.
The other thing I just noticed is the URI apparently does not have CTCSS
encode on/off logic, is there some way of doing that with a GPIO pin? My
repeater is a converted MastrExec II from Micro Computer Concepts, it has a
TS-64 board installed for CTCSS encode/decode.
Thanks,
Jay ? WT9S
Sent from Mail for Windows 10
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20151031/cb1dc8a
2/attachment-0001.html>
------------------------------
_______________________________________________
arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
End of arm-allstar Digest, Vol 17, Issue 27
*******************************************
More information about the arm-allstar
mailing list