- App_rpt-users - lists.keekles.org

Remote base
by Michael Hebert 12 Nov '13

12 Nov '13

Good afternoon Allstars! Has anyone tried to get a Yaesu FT-857D working as a remote base? I am interested in using it to change frequency bands, modes, etc. Thanks, Mike - KD5DFB

2 1

Motorola SYNTOR and GE MASTR II Manuals
by Benjamin L. Naber 12 Nov '13

12 Nov '13

GE MASTR II Maintenance Manual LBI30740 A, LBI 4450G Motorola SYNTOR VHF manual 68P81043E40-A $10 Priority mail to all of the great USA. Anywhere else, please state what country when replying off-list. ~Benjamin, KB9LFZ

1 0

Please set port for 28138 to 4570
by buck 12 Nov '13

12 Nov '13

Please force bindport for node 28138 to 4570. Thank You, N6UG

2 1

Watchdog timer in Pickle linux (remove omap_wdt?)
by Mike Hugo 11 Nov '13

11 Nov '13

Hi, A bit of investigation with Dr. Google found that the beagleboard XM boards have a known issue with the omap_wdt driver. Instead of rebooting the board it holds it in reset. The easy solution is to not use the omap_wdt watchdog timer driver but rather the TLW4030 watchdog timer driver. Looking at the latest pickle Linux kernel I see there are currently 4 watchdog timer drivers built into the kernel including the working TLW4030. Since it loads after the omap_wdt timer it doesn't get used. The TLW4030 reportedly works on all version of the beagleboard. lib/modules/2.6.33-500-omap/kernel/drivers/watchdog/softdog.ko lib/modules/2.6.33-500-omap/kernel/drivers/watchdog/twl4030_wdt.ko lib/modules/2.6.33-500-omap/kernel/drivers/watchdog/omap_wdt.ko lib/modules/2.6.33-500-omap/kernel/drivers/watchdog/pcwd_usb.ko Therefore would it be possible to get pickle rebuilt without the omap_wdt built in? That should then cause the twl4030 driver to be used whenever the /dev/watchdog file is written to and hopefully solve the problem. Anyone wanting to use the timer would still need to install the watchdog user space program as I don't think it makes sense to include that in pickle. A quick way to test the watchdog timer is to just cat /dev/watchdog and wait a minute. Current XM boards with the omap_wdt timer will crash after a minute. Newer beagleboards will restart. If my theory is correct after removing the omap_wdt driver all boards will restart Thanks Mike Here is reference where someone did the research on the watchdog timer: http://gumstix.8.x6.nabble.com/Watchdog-timer-not-working-in-gumstix-overo-… Look near the bottom with the solution. I also saw references on the TI site and perhaps the omap_wdt driver has been updated as well since these posts are old.

1 1

XIPAR question
by Lu Vencl 11 Nov '13

11 Nov '13

I have a question regarding XIPAR telemetry (courtesy Tones) and Echolink Telemetry. Under ACID, I have always been able to tweak the courtesy tones to a custom set of tones I prefer. But when I try to make changes under the XIPAR build, it seems to ignore them completely and do it's own set of courtesy tones. See example below. Also, for echolink, I have used eannmode=0 to completely inhibit echolink telemetry and for some reason the =0 is the same as =1. Is there a work around or a known bug with these two items? Thanks in advance. Lu, KA4EPS ;idtalkover=|iid ; Talkover ID (optional) default is none unlinkedct=ct2 ; unlinked courtesy tone (optional) default is none remotect=ct3 ; remote linked courtesy tone (indicates a remote is in the list of links) linkunkeyct=ct8 ; sent when a transmission received over the link unkeys ;nolocallinkct=0 ; Send unlinkedct instead if another local node is connected to this node (hosted on the same PC). ;irplann=1 ; Default: 1 = Play IRLP connect and disconnect announcements ; 0 = Disable IRLP connect and disconnect announcements eannmode=0 ; Default: 1 = Say only node number on EchoLink connects nounkeyct=0 holdofftelem=1 ; 2 = say phonetic call sign only on EchoLink connects ; 3 = say phonetic call sign and node number on EchoLink connects ;connpgm=yourconnectprogram ; Default: Disabled. Execute a program you specify on connect. ; passes 2 command line arguments to your program: ; 1. node number in this stanza (us) ; 2. node number being connected to us (them) ;discpgm=yourdisconnectprogram ; Default: Disabled. Execute a program you specify on disconnect. ; passes 2 command line arguments to your program: ; 1. node number in this stanza (us) ; 2. node number being disconnected from us (them) ;linkactenable=0 ; Set to 1 to enable the link activity timer. Applicable to standard nodes only. ;lnkacttime=1800 ; Link activity timer time in seconds. ;lnkactmacro=*52 ; Function to execute when link activity timer expires. ;lnkacttimerwarn=30seconds ; Message to play when the link activity timer has 30 seconds left. ;remote_inact_timeout=1800 ; Inactivity timer for remote base nodes only (set to 0 to disable). ;remote_timeout=3600 ; Session time out for remote base. (set to 0 to disable) ; program and options to send information to stats server statpost_program=/usr/bin/wget,-q,--output-document=/dev/null statpost_url=http://stats.allstarlink.org/uhandler.php irxgain=-10 ; IRLP receive gain adjustment ; Note: Gain is in db-volts (20logVI/VO) itxgain=10 ; IRLP transmit gain adjustment ; Note: Gain is in db-volts (20logVI/VO) erxgain=-3 ; Echolink receive gain adjustment ; Note: Gain is in db-volts (20logVI/VO) etxgain=3 ; Echolink transmit gain adjustment ; Note: Gain is in db-volts (20logVI/VO) ;telemnomdb=0 ; Telemetry Nominal Amplitude reference in dB telemduckdb=-12 ; Telemetry Ducking in dB when local or link voice tx in progress [telemetry] ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048) ct2=|t(2175,0,2,1112)(0,0,2,0)(2175,0,2,700)(0,0,99,0)(350,440,75,1048) ct3=|t(440,0,150,4096) ct4=|t(550,0,150,2048) ct5=|t(660,0,150,2048) ct6=|t(880,0,150,2048) ct7=|t(660,440,150,2048) ct8=|t(350,440,75,1048)(0,0,80,0)(350,440,75,1048) ;ct8=|t(2175,0,2,1112)(0,0,2,0)(2175,0,2,700)(0,0,99,0)(350,440,75,1048)(0,0 ,80,0)(350,440,75,1048) ;ct8=|t(2175,0,80,512)(0,0,5,0)(1950,0,40,1048)(0,0,5,0)(1850,0,40,1048) ;ct8=|t(350,440,75,1048)(0,0,80,0)(350,440,75,1048) remotetx=|t(440,0,50,3000)(0,0,80,0)(350,0,50,3000) remotemon=|t(1209,0,50,2048) cmdmode=|t(900,903,200,2048) functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048)

5 12

Echolink packet loss issues
by Lu Vencl 11 Nov '13

11 Nov '13

Came across the first XIPAR node that seems to have issues with packet loss only on inbound echolink transmissions. Another box with ACID proves to be fine. Not sure if this is a PC issue or a software issues.. Allstar transmissions are perfectly fine. No issues with that at all. Just strange that only inbound echolink has major breakup issues. Anyone reunning echolink under xipar? Any thoughts or ideas would be appreciated. Going to hold off for at least a couple days before reimaging the box. Thanks KA4EPS

1 0

Playing sounds locally
by Doug Crompton 11 Nov '13

11 Nov '13

I have a question about playing sounds locally. When I play a sound - WA3DSP_Allstar*CLI> rpt localplay 27225 /var/lib/asterisk/sounds/repeater [Nov 11 01:11:25] NOTICE[9032]: app_rpt.c:8502 wait_interval: Delay interval = 2000 [Nov 11 01:11:27] NOTICE[9032]: app_rpt.c:8506 wait_interval: Delay complete -- <Zap/pseudo-560835011> Playing '/var/lib/asterisk/sounds/repeater' (language 'en') -- Hungup 'Zap/pseudo-560835011' There is a delay inserted and of course this has to keyup and unkey the radio. If one wants to formulate a sentence with a series of asterisk sounds (from the sound directory) and send them over the radio how would that be done as one complete series without delays or unkeys? 73 Doug WA3DSP http://www.crompton.com/hamradio

3 3

Re: [App_rpt-users] DMR or D-Star software module for AllStarLink
by Ken 11 Nov '13

11 Nov '13

Thomas It is quite possible to run one of the DSTAR repeaters on the same Linux box as Allstar - I did that for a while using an Atom D525 board. I was using the sound card repeater, which is quite demanding of the processor's time. Using DVRPTR it is easier still. It is even possible to make a repeater that switches between analog and digital modes. Look for VA3UV web site. 73 Ken Attached Message From: Thomas Delmonego <delmonego(a)hotmail.de> To: app_rpt-users(a)ohnosec.org <app_rpt-users(a)ohnosec.org> Subject: Re: [App_rpt-users] DMR or D-Star software module for AllStarLink? Date: Mon, 11 Nov 2013 15:18:46 +0100 Hi Matthew, many thanks for your reply! I found a german software for D-Star running with CentOS and with an USB-Fob USB soundcard, also like AllStarLink! See here: http://shop.dvrptr.de/index.php?language=en Ok, it's not a software module within AllStarLink, but i think, it's possible to run both on an CentOS - Linux PC! I want to try this solution with my AllStarLink PC in next weeks and let know all group ... 73! Thomas, IW3AMQ P.S.: perhaps in a few year we find a sofware for Linux for DMR with an URI-Fob USB soundcard, it's technical possible ...

1 0

Re: [App_rpt-users] DMR or D-Star software module for AllStarLink?
by Thomas Delmonego 11 Nov '13

11 Nov '13

Hi Matthew, many thanks for your reply! I found a german software for D-Star running with CentOS and with an USB-Fob USB soundcard, also like AllStarLink! See here: http://shop.dvrptr.de/index.php?language=en Ok, it's not a software module within AllStarLink, but i think, it's possible to run both on an CentOS - Linux PC! I want to try this solution with my AllStarLink PC in next weeks and let know all group ... 73! Thomas, IW3AMQ P.S.: perhaps in a few year we find a sofware for Linux for DMR with an URI-Fob USB soundcard, it's technical possible ... Date: Sun, 10 Nov 2013 15:42:19 -0800 From: n8ohu(a)yahoo.com Subject: Re: [App_rpt-users] DMR or D-Star software module for AllStarLink? To: delmonego(a)hotmail.de Thomas, The only module I know of is actually intended to pass audio from AllStar into the DV-Dongle to be passed on to a digital system. Most people that build D-Star repeaters use software that is designed to function in that environment, and to the best of my knowledge, there isn't anything equivalent out there for DMR; that, as far as I know will require hardware to implement properly. Matthew Pitts N8OHU From: Thomas Delmonego <delmonego(a)hotmail.de> To: "app_rpt-users(a)ohnosec.org" <app_rpt-users(a)ohnosec.org> Sent: Wednesday, November 6, 2013 6:26 AM Subject: [App_rpt-users] DMR or D-Star software module for AllStarLink? Hi anyone! Know anyone about a software module for AllStarLink with DMR or D-Star digital modulation? I think, for only repeater operation is not necessary the AMBE coder, because the system must only receive the digital code and retransmit it without compression of the data via AMBE coder and so is no violation of protection by patent ... Perhaps is in elaboration? 73! Thomas, IW3AMQ _______________________________________________App_rpt-users mailing listApp_rpt-users@ohnosec.orghttp://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

1 1

Stand alone repeater
by Richard Szajkowski 11 Nov '13

11 Nov '13

Hello to the group I am rebuilding my 220 repeater , can I use the uri and allstar as a stand alone repeater controller ? I don't want any links at this time to the 220 repeater , maybe down the road I will link the VHF to the 220 So do I need a node number ? I have read about the remote base , and how to do that Thanks Richard Szajkowski

4 4