Hi folks. I may have to change from AT&T to Charter/Spectrum cable ISP.
Anybody use them or know of any restrictions/limitations as far as
Allstar is concerned?
GeorgeC
W2DB
2360 (when AT&T makes my internet work)
--
George Csahanin
10100 Carson Ranch Rd.
Crowley, TX 76036
682-708-5716 home
401-338-0568 cel
http://dyb.com
Hi folks,
After dozens of trips to the mountains to get all the physical
infrastructure upgraded and changed out to Allstar/RTCM, I am finally
getting back to some little cleanup items.
I've written before on the "squelch crash" issue, and found that once
things were tuned up, no one really had any issues with it. We are having
severe issues with it and I am trying to narrow it down.
All sites consist of:
Kenwood TKR750 (or 850 if UHF) repeater.
RTCM
Local on-site PC (micro itx PC with Intel Atom D2500 1.8Ghz Dual core CPU
and 2GB ram)
Local mikrotik router (RB2011 in most cases, some CRS125) Except for
voters, all repeaters are using the DIAL box plugged into the same local
router as the RTCMs (ie, just about zero network latency)
Some sites have 1 repeater, some 2, the biggest site has 2 repeaters and 2
voters.
Squelch and Diode calibration was done per RTCM manual
RX level set per manual
TX level set by generating 1khz tone with "cop 4" command in asterisk and
adjusting output for 3khz on service monitor.
All sites are running DIAL, everything is private node numbers and private
IP space (no network congestion since we aren't sharing with anything else).
The RTCM is using external CTCSS input from the Kenwood on pin 24 of the
AUX connector and pin 24 is set to "TOR".
The squelch crash is usually only a problem on weak signals, or very short
(kerchunk) bursts.
I have included a short video showing the problem on a test bench. The
video shows the transmit/receive LED on the HT, and the LEDs on the RTCM.
It's very clear that the receive signal is gone and CTCSS has dropped while
the transmitter is still held on to transmit the squelch crash. The video
shows a clean transmission, followed by 2 crashes simulated with a double
"kerchunk". The mountain top repeaters squelch crashes are upwards of 1
full second of audio after the incoming transmission has stopped.
I am wondering if I don't have enough CPU on the DIAL box? Is it possible
that I just don't have enough to do the DSP processing fast enough?
Any tips after seeing the video much appreciated. Thanks!!
James
KI0KN
video url: http://ki0kn.com/wp/blog/
(please excuse the barely setup wordpress page!!)
I noticed that some of the content from ohnosec drupal has not been
mirrored to allstarlink.
For example HowTo's/Using URI's/Adjusting Audio Levels is missing
<http://docs.allstarlink.org/drupal/node/140>.
What's the deal here? I get the impression that the intent is to migrated
from ohnosec to allstarlink but it's incomplete?
73 de N2YGK
I am helping another ham to set up a back-to-back remote base setup to help
provide communication to a shaded area for a public service event. We have
a working remote base setup with hamvoip.org distribution and now want to
hook two of these back to back. I am helping with the Linux knowledge and
got the current remote base working. I am looking for some pointers about
how to do this, and timing is short. We need this running in 2 weeks.
Here's his request in his own words:
> I’ve got an event the first weekend of June that I want the linked radio
> system for, so that is kind of what is driving my “rush”.
>
> I would like to take the basic (final) software setup/configuration for
> ASC-North and archive it so we always have that foundation. (Doesn’t need
> to be by June 1).
>
> I would like to learn how to modify that foundation to create a different
> remote base. Different Asterisk Name (1998, 1997, 1996, etc.), and whatever
> other changes are necessary so an independent base can be established.
> (Doesn’t need to be by June 1).
>
> I would like to set up two Pi’s with the USB interface and radios, so they
> automatically, and exclusively, talk to each other. One I imagine (I’ll
> call the primary base) would have to broadcast it’s IP (dyndns), the other
> (I’ll call remote) would need to want to connect to that. This is the need
> for the start of June. I have all of the needed hardware for both stations
> (Pi, USB interface, radio). This specific request is totally unrelated to
> ACS, but is in support of Special Olympics Washington Spring Games, which
> are being conducted June 2, 3, 4 (and will probably be on non-amateur
> radios/frequencies). They operate multiple venues which this year are more
> geographically separated than they have been in the past, and we’ll no
> longer be able to utilize simplex to talk between them. No reasonable
> repeater option is available and putting up a temporary one is all but
> impossible as it would have to be on JBLM someplace.
>
> Once this is set up, but not necessarily immediately, I would like to know
> the specific programming for these that could be changed to add another
> unique pair, or to add another single (remote) radio as a link to the
> primary base.
Any pointers would be most appreciated. I assume this will require
defining some sort of default call, but I am new to asterisk.
-Doug-, KD7DK
Hi Steve, et. al.:
A couple of errata for RAT_RC1.img on a Pi 3B:
*firsttime:*
1) Does not happen on first boot after copying the img to CF and first
login as root. Still investigating reproducing this but it seems that means
the img is missing /etc/asterisk/firsttime. Maybe I'll try opening this
with a loopback FS to see what's in the image before it boots.
2) Hit enter instead of Y or N at password change prompt and get a syntax
error. PR #3 <https://github.com/AllStarLink/DIAL/pull/3>submitted and I
see you already merged it!
*nonoload:*
The unanchored sed commands in /usr/local/sbin/pcf.sh cause "noload" to
become "nonoload", "nononoload" and so on each time nodesetup is run.
# grep nono /etc/asterisk/modules.conf
nononoload => chan_simpleusb.so ; CM1xx USB Cards with Radio Interface
Channel Driver (No DSP)
Here's where this happens in /usr/local/sbin/pcf.sh:
691: sed -i 's/noload => chan_simpleusb.so/load => chan_simpleusb.so/g'
/etc/asterisk/modules.conf
692: sed -i 's/load => chan_usbradio.so/noload => chan_usbradio.so/g'
/etc/asterisk/modules.conf
695: sed -i 's/load => chan_simpleusb.so/noload => chan_simpleusb.so/g'
/etc/asterisk/modules.conf
696: sed -i 's/noload => chan_usbradio.so/load => chan_usbradio.so/g'
/etc/asterisk/modules.conf
Fix is to change them to: sed -i 's/^...' to anchor the pattern but I was
unable to find where this happens in the source code so didn't submit a PR.
It looks like pcf.sh is derived from
https://allstarlink.org/config/portalconfig.sh but I'm missing something...
*one-way audio with rb-usb-rim lite-scom 7330
<http://www.repeater-builder.com/products/usb-rim-lite.html>:*
We seemed to have one-way audio where audio from the SCOM was not being
heard via the (763) phone dialup but phone audio was being transmitted by
the SCOM. In the process of debugging this, we decided to see if there were
packets flowing outbound and tried to "apt-get install tcpdump" and saw
that it needed some updates, so we did an "apt-get update" and, lo and
behold, the one-way audio problem went away. (Could be app_rpt saw we were
getting ready to watch it;-) So perhaps there was just an update that
needed to get installed, or it was just gremlins. Maybe just an Asterisk
restart needed. Always frustrating when "circuit tested, no trouble found"
after 4 hours of head-scratching. We had done many service asterisk
stop/start cycles. So if firsttime isn't already, it should probably do an
apt-get update.
We had also played around with "radio tune rxvoice" with a service monitor
(and saved the tune config) to make sure there was actually audio going in
to the RIM and at the right level.
Anyway, the good news is I believe we got this stuff working and the
firsttime/nodesetup stuff makes it really easy.
Thanks & 73 de N2YGK & N2DVQ
i have an acid box in a data center i want to dial x86 version
how should do go abt this i need echolink support alllmom 2 i run
swisary by k0kn and inodes by wa3dsp tge dial install fails as i can't
use dhcp i have full ipmi access 2 the box and full backup of the box so
of we kill it trying stuff i dont carej
jimmy
Yes the RTCM can be used behind a firewall and does not require any port forwarding for normal operation. There is a telnet console for configuration and if you want to configure the RTCM remotely you will need to forward that port.
From: App_rpt-users [mailto:app_rpt-users-bounces@lists.allstarlink.org] On Behalf Of Doug Kingston
Sent: Tuesday, April 25, 2017 10:54 PM
To: Users of Asterisk app_rpt
Subject: Re: [App_rpt-users] Micro-Node RTCM
Thank you Mark, that was very informative.
My guess is that this device is unlikely to be able to "defend" itself very well and should probably be placed behind a restrictive firewall. Do you concur?
-Doug-
On Tue, Apr 25, 2017 at 10:26 PM, Mark Guibord <mark(a)micro-node.com> wrote:
The RTCM uses a 16 bit DSP with a tightly integrated interrupt driven firmware package written in c
http://www.microchip.com/wwwproducts/en/dsPIC33FJ128GP804
If you're interested here is a link to the open-source software for the RTCM..
http://svn.ohnosec.org/viewvc/projects/allstar/voter/board-firmware/?root=s…
From: App_rpt-users [mailto:app_rpt-users-bounces@lists.allstarlink.org] On Behalf Of Doug Kingston
Sent: Tuesday, April 25, 2017 9:41 PM
To: Users of Asterisk app_rpt
Subject: Re: [App_rpt-users] Micro-Node RTCM
I know that I would have a GPS with 1pps feed to get the timing. Once you have that, what is different in an RTCM other than nice packaging?
What is the core processor technology inside the RTCM. I am assuming is some form of ARM processor. Can you can you get a root shell and use SSH to access?
-Doug-
On Tue, Apr 25, 2017 at 7:50 PM, Fredric Moses <fred(a)moses.bz> wrote:
You seem confused… you still need a linux system running app_rpt with the RTCM’s… think of the RTCM as an ethernet based radio interface vs usb.. But that radio interface when you add GPS to each one can do voting with others.. and with some more work simulcast transmitting…
We have some 50-60 RTCM’s deployed and love them… Getting ready to rebuild another clubs VHF repeater voter system with a 6 site RTCM based voting system. I just started testing the new hamvoip rPi3 image with some rtcm’s myself...
--
Fredric Moses - W8FSM - WQOG498
fred(a)moses.bz
> On Apr 25, 2017, at 22:32, Doug Kingston <dpk(a)randomnotes.org> wrote:
>
> I am considering using these for a amateur repeater voting application. The alternative would be to roll my own with a Raspberry Pi 3 and probably the HamVOIP.org distribution. Who out there is using the RTCM? I can find very little information beyond the manual and I am concerned that the software may not be maintained and that there is not enough access to the underlying Linux system.
>
> Who can tell me more about the RTCM?
>
> Has anyone rolled their own with a Pi3? Any advice there?
>
> -Doug-
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users(a)lists.allstarlink.org
> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
>
> To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
> You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
_______________________________________________
App_rpt-users mailing list
App_rpt-users(a)lists.allstarlink.org
http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
_______________________________________________
App_rpt-users mailing list
App_rpt-users(a)lists.allstarlink.org
http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
I am considering using these for a amateur repeater voting application.
The alternative would be to roll my own with a Raspberry Pi 3 and probably
the HamVOIP.org distribution. Who out there is using the RTCM? I can find
very little information beyond the manual and I am concerned that the
software may not be maintained and that there is not enough access to the
underlying Linux system.
Who can tell me more about the RTCM?
Has anyone rolled their own with a Pi3? Any advice there?
-Doug-
Steve,
Answers to your three questions:
If I power on the Pi with the second RIM unplugged from USB, the unit boots up and the heart beat on the first RIM is normal. If I subsequently plug in the second RIM, its heartbeat flashes normally (after about 2 seconds) and the first RIM stays up, both heartbeats are flashing, not quite synchronously, but appear to wig-wag. Life is good.
If I power up the node with both RIMs connected, the first RIM heartbeat comes on first, much slower than normal, and blinks irregularly for about 3-4 seconds. Then the second RIM heartbeat starts to flash normally, and the first RIM stops flashing with the heartbeat LED on steady.
(this lsusb report is with both RIMs plugged in, and the Pi powered up – RIM #1 heartbeat on steady, RIM #2 heartbeat flashing normally)
root@28336:~# lsusb
Bus 001 Device 005: ID 0d8c:013a C-Media Electronics, Inc.
Bus 001 Device 004: ID 0d8c:013a C-Media Electronics, Inc.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@28336:~#
(this lsusb report is with the Pi booted with RIM #1 only, and the second RIM plugged in after boot. Both RIM heartbeats flashing normally)
root@28336:~# lsusb
Bus 001 Device 004: ID 0d8c:013a C-Media Electronics, Inc.
Bus 001 Device 005: ID 0d8c:013a C-Media Electronics, Inc.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@28336:~#
(this lsusb report is with the Pi booted with RIM #1 only, the second RIM was left unplugged)
root@28336:~# lsusb
Bus 001 Device 004: ID 0d8c:013a C-Media Electronics, Inc.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@28336:~#
In all three cases, no other usb devices were connected. No keyboard, no mouse. The 3rd and 4th USB connectors are empty.
channel driver is usbradio
in rpt.conf, rxchannel = radio/usb for first node, and rxchannel = radio/usb2 for the second node.
** This does not match the instructions in the allstarlink.org “setting up a two node system” how-to page. **
In usbradio.conf (at the end of [usb] stanzas) I added these lines since I am using the RIM interface pins to control a set of 4 relays. Prior to adding these lines, USB communications would fail because output was not declared.
The second RIM on node 2 has no relay board, so these lines are not present in the [usb2] section of usbradio.conf
gpio5=out1 ; in, out0 or out1
gpio6=out1 ; in, out0 or out1
gpio7=out1 ; in, out0 or out1
gpio8=out1 ; in, out0 or out1
28336*CLI> core show version
Asterisk 1521 built by root @ repeater on a armv7l running Linux on 2015-10-17 03:09:22 UTC
28336*CLI>
Rpi2_dial.img was downloaded 11/26/2016 from allstarlink.org portal
Thank you,
Tom Cooney, Jr., W3SF
tom(a)cooneyjr.com
Home: (814)626-1531
Cell: (814)931-0060
