- App_rpt-users - lists.keekles.org

IRLP Issue
by Randy 24 Oct '10

24 Oct '10

Hello Group whats this error message telling me [Oct 19 17:50:22] WARNING[2098]: channel.c:3051 ast_request: No channel type registered for 'irlp'

6 12

Parallel Port support in chan_usbradio
by Jim Duuuude 24 Oct '10

24 Oct '10

After having it demonstrated to me that all the 5 input pins are truly safe to use and there are no issues with interrupts that might mess things up, I added support for pin 11 as an input also. This version of chan_usbradio will be available after 14:15 PDT today in the SVN. JIM WB6NIL

1 0

Need help, linking split site repeater over IP
by Chuck Henderson 24 Oct '10

24 Oct '10

I have a split site repeater, currently 2 receive sites and one transmit site. I would like to place a computer at each site and use these to permanently link the sites. Could someone here please help me get started with a link from one receive site to the transmit site. I will save the second receive site till sometime in the distant future. It seems like this can work but so far I have not been able to find anything that tells how to do it. Is there a how-to somewhere for this type of thing? Chuck Henderson, WB9UUS

3 2

900 levels and com port ?
by Paul M. Nannery 24 Oct '10

24 Oct '10

I am putting a up a 900 meg system and would like some guidance on getting the levels right I know dsp is not set up for the narrow band. Also Jim is there any way to use the com port for ptt like you did with the lpt port as most newer computers do not have lpt ports?

5 5

Re: [App_rpt-users] Pico Node
by Dale Weber 24 Oct '10

24 Oct '10

Greetings, I was waiting for something else to finish (another software build), so I got the crazy idea of trying to build AllStarLink on my BeagleBoard. Below shows that I did not get very far in the build before an error ocurred. I bet that if I had a complete install kit, I could make this work. I'll have to take a look at what is actually on the ACID CD to see if I can port stuff over. I'll leave that for a project later in the week. :) 8-Dale root@walter:/usr/src/astsrc# make upgrade-acid (cd zaptel; ./configure) checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for GNU make... make checking for grep... /bin/grep checking for sh... /bin/bash checking for ln... /bin/ln checking for wget... /usr/bin/wget checking for grep that handles long lines and -e... (cached) /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... yes checking curses.h usability... yes checking curses.h presence... yes checking for curses.h... yes checking for initscr in -lncurses... yes checking for curses.h... (cached) yes checking for newtBell in -lnewt... no checking for usb_init in -lusb... no configure: creating ./config.status config.status: creating build_tools/menuselect-deps config.status: creating makeopts config.status: creating build_tools/make_firmware_object configure: *** Zaptel build successfully configured *** (MAKELEVEL=0; make -C zaptel install) make: Entering directory `/usr/src/astsrc/zaptel' make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' checking build system type... armv7l-unknown-linux-gnu checking host system type... armv7l-unknown-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for GNU make... make checking for asprintf... yes checking for getloadavg... yes checking for setenv... yes checking for strcasestr... yes checking for strndup... yes checking for strnlen... yes checking for strsep... yes checking for strtoq... yes checking for unsetenv... yes checking for vasprintf... yes checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... yes checking curses.h usability... yes checking curses.h presence... yes checking for curses.h... yes checking for initscr in -lncurses... yes checking for curses.h... (cached) yes checking for pkg-config... pkg-config Package gtk+-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `gtk+-2.0.pc' to the PKG_CONFIG_PATH environment variable No package 'gtk+-2.0' found configure: creating ./config.status config.status: creating makeopts config.status: creating autoconfig.h configure: configuring in mxml configure: running /bin/bash './configure' --prefix=/usr/local 'CC=' 'LD=' 'AR=' 'CFLAGS=' --cache-file=/dev/null --srcdir=. checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for ar... /usr/bin/ar checking for cp... /bin/cp checking for ln... /bin/ln checking for mkdir... /bin/mkdir checking for nroff... no checking for groff... no checking for rm... /bin/rm checking for strdup... yes checking for vsnprintf... yes configure: creating ./config.status config.status: creating Makefile config.status: creating mxml.list config.status: creating mxml.pc config.status: creating config.h configure: Menuselect build configuration successfully completed make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Entering directory `/usr/src/astsrc/zaptel/menuselect' make[2]: Entering directory `/usr/src/astsrc/zaptel/menuselect' gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_curses.o menuselect_curses.c make[3]: Entering directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -O -Wall -c mxml-attr.c gcc -O -Wall -c mxml-entity.c gcc -O -Wall -c mxml-file.c gcc -O -Wall -c mxml-index.c gcc -O -Wall -c mxml-node.c gcc -O -Wall -c mxml-search.c gcc -O -Wall -c mxml-set.c gcc -O -Wall -c mxml-private.c gcc -O -Wall -c mxml-string.c /bin/rm -f libmxml.a /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml -string.o a - mxml-attr.o a - mxml-entity.o a - mxml-file.o a - mxml-index.o a - mxml-node.o a - mxml-search.o a - mxml-set.o a - mxml-private.o a - mxml-string.o ranlib libmxml.a make[3]: Leaving directory `/usr/src/astsrc/zaptel/menuselect/mxml' gcc -o menuselect menuselect.o strcompat.o menuselect_curses.o mxml/libmxml.a mxml/libmxml.a -lncurses make[2]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' make[1]: Leaving directory `/usr/src/astsrc/zaptel/menuselect' Generating input for menuselect ... *********************************************************** The existing menuselect.makeopts file did not specify that 'zttool' should not be included. However, either some dependencies for this module were not found or a conflict exists. Either run 'make menuselect' or remove the existing menuselect.makeopts file to resolve this issue. *********************************************************** make: *** [menuselect.makeopts] Error 255 make: Leaving directory `/usr/src/astsrc/zaptel' make: *** [upgrade-acid] Error 2 root@walter:/usr/src/astsrc# -- I can handle complexity. It's the simple things that confound me. Open your mind, Read, Learn, Think, Apply. 73, from NPKT! http://www.hybotics.com - NEW main site Just because we can, does it follow that we should?

2 1

Parallel Printer Port support in chan_usbradio
by Jim Duuuude 24 Oct '10

24 Oct '10

It was suggested (and a good suggestion it was) to add support for using a Parallel Printer Port to do I/O, including PTT, COR, CTCSS, and general-purpose uses if you have some need to do so. It will be available in SVN after 21:15 PDT this evening. If you are interested you will at least need to get a new copy of chan_usbradio and app_rpt. Please see http://app-rpt.qrvc.com/node/177 for documentation reflecting these changes. JIM WB6NIL

3 2

RE Parellal Port
by Randy 24 Oct '10

24 Oct '10

I should have said Port 10 for (COR) low Not Port 2 Randy

2 1

Re: [App_rpt-users] Parallel Printer Port Config
by Randy 24 Oct '10

24 Oct '10

How excatly do I configure the Parallel Port for PTT and COS I read over some of the information and were still not sure on what to do. Say I need say Parallel port 2 for (COR) low and Parallel Port 3 for (PTT) How doe,s one configure it Randy

1 0

Removal of IRLP off my Allstar nodes
by keith handscombe 24 Oct '10

24 Oct '10

Is it a case of a re-install and then not to then add the IRLP install script? Or can I remove the IRLP configuration easier from a working node and keep this as a vanilla Allstar node. I have a backup of the asterisk folder already just in case. Many thanks Keith G7DNT 2498/27333 www.g7dnt.co.uk

1 0

Re: [App_rpt-users] App_rpt-users Digest, Vol 20, Issue 44
by K&R Yoksh 24 Oct '10

24 Oct '10

Many, many thanks, Jim! Once I figure out how, I'll be using this! This will make switching over from IRLP or EchoIRLP to Echolink/Asterisk much, much easier for all of us! 73, Kyle K0KN --- Original Message --- Date: Sat, 23 Oct 2010 20:39:43 -0700 From: Jim Duuuude Subject: [App_rpt-users] Parallel Printer Port support in chan_usbradio To: app_rpt mailing list It was suggested (and a good suggestion it was) to add support for using a Parallel Printer Port to do I/O, including PTT, COR, CTCSS, and general-purpose uses if you have some need to do so. It will be available in SVN after 21:15 PDT this evening. If you are interested you will at least need to get a new copy of chan_usbradio and app_rpt. Please see http://app-rpt.qrvc.com/node/177 for documentation reflecting these changes. JIM WB6NIL

1 0