February 2015 - App_rpt-users - lists.keekles.org

Issue with Repeater Keying Up on its own
by David Dean K0PWO 06 Feb '15

06 Feb '15

Hello to everyone, I have a problem with my repeater and hub. When my repeater node is standing alone and not connected to any other nodes it works perfectly. However, when I connect my repeater node to my hub, the repeater then will then just randomly transmit every couple of minutes (it just keys up for a second and then drops the carrier). When I disconnect from the hub the repeater then works correctly. Both the repeater node and hub were downloaded from the allstar site and have not been modified (especially the hub node) at all. Any thoughts as to where I should look to correct this issue? Thanks for your help, David David Dean, K0PWO Arapahoe County Colorado (720) 350-203 cell

1 0

Audio level for 2.5 KHz narrow band FM?
by Bryan Fields 06 Feb '15

06 Feb '15

I'm playing with a 900 mhz repeater and most FM on 902mhz is narrow band. As this is a converted uniden LTR repeater it's setup for narrow band. Looking at http://docs.allstarlink.org/drupal/node/92 which is the allstarlink network standard, rather than 3khz of deviation before CTCSS/DCS, what's the value I should be shooting for here in a NBFM system? I've been researching it and there are some posts from 2009 by Steve, WA6ZFT saying that 1.5 KHz of deviation should be the target. Is there anything more official than this? Can we add some info on this to the docs site? 73's W9CR -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net

4 3

Re: [App_rpt-users] Raspberry pi status
by Steve Zingman 05 Feb '15

05 Feb '15

Doug, With all due respect, The BBB is a fine board, and there are a lot of other boards available today. Some of us want to do our own thing, We are quite capable of experimenting with different platforms. Not everyone needs a image to load. I've been running Allstar a long time on many hardware and software versions. We have been running the Pi on a few nodes since Christmas 24 x 7. with no failures. As they say on TV, your mileage may vary. 73, Steve N4IRS >Be very careful running Allstar on the Pi. It is subject to all kinds of problems including hangups. We already >went through all the testing on that platform a year ago and that is why we are using the Beaglebone Black. >I can't understand why anyone would want to run Allstar on the Pi when you have a perfectly good and very easy to >use setup with all the bells and whistles on the BBB that just works. Is it just because you have it sitting there >and you want to use it? All of this stuff is so cheap. Buy a BBB!!! >73 Doug >WA3DSP -- "Anything is possible if you don't know what you are talking about." 1st Law of Logic

3 2

Raspberry pi status
by Skyler F 04 Feb '15

04 Feb '15

This is probably something that has been asked a lot before, but with new advances to the pi, more ram etc. I am curious if anyone has it working. A lot of people who want to set up a node keep ask me if it works on the pi. Does AllStar work on the raspberry pi for a simple node? 73 Kd0whb Skyler -- Skyler Fennell amsatnet.info KDØWHB electricity440(a)gmail.com

4 3

Re: [App_rpt-users] rpt.conf questions
by Geoff 04 Feb '15

04 Feb '15

[root@W5OMR /etc/asterisk/custom]# /usr/sbin/safe_asterisk: line 125: 7375 Segmentation fault (core dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} >&/dev/${TTY} < /dev/${TTY} Asterisk ended with exit status 139 Asterisk exited on signal 11. Automatically restarting Asterisk. mpg123: no process killed /usr/sbin/safe_asterisk: line 125: 17574 Segmentation fault (core dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} >&/dev/${TTY} < /dev/${TTY} Asterisk ended with exit status 139 Asterisk exited on signal 11. Automatically restarting Asterisk. mpg123: no process killed /usr/sbin/safe_asterisk: line 125: 18918 Segmentation fault (core dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} >&/dev/${TTY} < /dev/${TTY} Asterisk ended with exit status 139 Asterisk exited on signal 11. Automatically restarting Asterisk. mpg123: no process killed [root@W5OMR /etc/asterisk/custom]# dmesg | grep hd ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA hda: LITE-ON CD-ROM LTN-4891S, ATAPI CD/DVD-ROM drive hdb: WDC WD800JB-00CRA1, ATA DISK drive hdb: max request size: 128KiB hdb: 156301488 sectors (80026 MB) w/8192KiB Cache, CHS=65535/16/63, UDMA(100) hdb: cache flushes not supported hdb: hdb1 hdb2 hda: ATAPI 48X CD-ROM drive, 96kB Cache, UDMA(33) EXT3 FS on hdb1, internal journal Adding 1020116k swap on /dev/hdb2. Priority:-1 extents:1 across:1020116k [root@W5OMR /etc/asterisk/custom]# You linux gurus... here's my Achilles heel ... harddrive tuning. Scares the hell out of me. I instinctively went to e2fsck /dev/hdb2 and I get WARNING!!! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage. Do you really want to continue (y/n)? uhm ... I guess 'no' ... maybe... {{{shudder}}} what to do, what to do... I asked the system for help ... Usage: e2fsck [-panyrcdfvstDFSV] [-b superblock] [-B blocksize] [-I inode_buffer_blocks] [-P process_inode_size] [-l|-L bad_blocks_file] [-C fd] [-j external_journal] [-E extended-options] device Emergency help: -p Automatic repair (no questions) -n Make no changes to the filesystem -y Assume "yes" to all questions -c Check for bad blocks and add them to the badblock list -f Force checking even if filesystem is marked clean -v Be verbose -b superblock Use alternative superblock -B blocksize Force blocksize when looking for superblock -j external_journal Set location of the external journal -l bad_blocks_file Add to badblocks list -L bad_blocks_file Set badblocks list Hmmm... ok. -n. Go check it, and make no changes, just report back what's going on. Sounds like the option to try. [root@W5OMR /sys/power]# e2fsck -n /dev/hdb2 e2fsck 1.39 (29-May-2006) Warning! /dev/hdb2 is mounted. Couldn't find ext2 superblock, trying backup blocks... e2fsck: Bad magic number in super-block while trying to open /dev/hdb2 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> ... and, it just did it again ... :/usr/sbin/safe_asterisk: line 125: 21504 Segmentation fault (core dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} >&/dev/${TTY} < /dev/${TTY} Asterisk ended with exit status 139 Asterisk exited on signal 11. Automatically restarting Asterisk. mpg123: no process killed /usr/sbin/safe_asterisk: line 125: 22464 Segmentation fault (core dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} >&/dev/${TTY} < /dev/${TTY} Asterisk ended with exit status 139 Asterisk exited on signal 11. Automatically restarting Asterisk. mpg123: no process killed

1 0

Re: [App_rpt-users] rpt.conf questions
by Geoff 04 Feb '15

04 Feb '15

I believe I found my gremlin... sitting here this morning, and asterisk restarted. hmmm... I happened to be logged into the node box via ssh (backyard repeater -is- at the house, just in a different room, with no monitor) and got the 'Segmentation fault' error messages scrawled across the screen... time to fsck that drive! (did that for you, Duuuuuuuude) ;-)

1 0

BBB multiple simpleUSB nodes?
by Sean Smith 04 Feb '15

04 Feb '15

Hi everyone, Has anyone tried having multiple simpleusb nodes running on one BBB? I'm interested in running up to 4 for a linking controller. Thanks Sean VE6SAR

2 6

Listener
by Luc Drolet VE2 LUQ 04 Feb '15

04 Feb '15

Hello to you all, I have people who would like to listen to amateur repeater without having an amature radio I would like to have a method to do it, so they can listen only, either with IAXRPT or with Zoiper without giving them access to the PTT so they can't pass onto amateur bands. Does anyone have an idea that would have a solution to use IAXRPT without giving them access to the PTT? Thank you and Happy Day Luc VE2LUQ

3 2

Re: [App_rpt-users] rpt.conf questions
by Geoff 04 Feb '15

04 Feb '15

I've been asked the same by others, as well... > Did you reload or restart asterisk after making the changes? > > Did you do a rpt reload at the asterisk cli and you commented it out? Even though, as a seasoned Linux guy (I don't know *everything* about Linux, but I know how to find what I need) and it goes against my Linux teachings, but I even (*gasp*) REBOOTED the node box, and have the same tone, after -all- of them were commented out in rpt.conf. Next?

1 0

rpt.conf questions
by Geoff 04 Feb '15

04 Feb '15

So, I've got some defines ... ;****************** ;* Stanza Defines * ;vvvvvvvvvvvvvvvvvv ; ;controlstates=controlstates29655 scheduler=schedule29655 morse=morse29657 macro=macro29655 functions=functions29655 phone_functions=functions29655 link_functions=functions29655 telemetry=telemetry29655 wait_times=wait-times29655 ; idtalkover=|iW5OMR R unlinkedct=ct2 ;Courtesy tone sound the node makes when not linked remotect=ct3 ;Courtesy tone sound the node makes when linked linkunkeyct=ct8 ;Courtesy tone sound the node makes when a remote linked system unkeys nolocallinkct=0 eannmode=2 echolinkdefault=0 echolinkdynamic=0 nounkeyct=0 telemdefault=2 ;temetry mode ; 0 = telemetry output off, ; 1 = telemetry output on, ; 2 = timed telemetry output on command execution and for a short time thereafter specifically, at this time, I'm concerned about Courtesy tones. So, let's go down to the telemetry stanza for 29655... [telemetry29655] ; ;when NOT linked ct2=|t(0,0,10,0)(350,440,10,2048)(0,0,10,0)(350,440,10,2048)(0,0,10,0)(350,440,10,2048)(0,0,10,0)(350,440,100,2048) ; ;when Linked ct3=|t(0,0,10,0)(880,440,150,2048)(0,0,10,0)(440,660,150,2048)(0,0,10,0)(880,440,150,2048)(0,0,10,0)(440,660,150,2048) ; ct4=|t(550,0,150,1048)(550,0,150,1048) ct5=|t(660,0,150,2048) ct6=|t(880,0,150,2048) ct7=|t(660,440,150,2048) ; When remote link unkeys ct8=|t(0,0,10,0)(350,440,50,2048)(0,0,50,0)(880,440,50,2048)(0,0,50,0)(350,440,50,2048) ; ct9=|t(660,680,100,4000)(0,0,100,0)(660,680,100,1000)(0,0,100,0)(660,680,100,250) remotetx=|t(500,0,10,1048)(0,0,10,0)(1000,0,10,1048) remotemon=|t(1009,0,50,2048) cmdmode=|icm ;(220,247,262,294,330,350,392,2048) functcomplete=|iEN patchup=rpt/callproceeding patchdown=rpt/callterminated ; ; ; This section allows wait times for telemetry events to be adjusted ; A section for wait times can be defined for every repeater ; [wait-times29655] telemwait=150 idwait=10 unkeywait=650 calltermwait=150 but, regardless of how I change the CT's, it remains the same, when asterisk is stopped and restarted, even when the machine is rebooted, the courtesy tone remains the same.

5 7