November 2012 - App_rpt-users - lists.keekles.org

Re: [App_rpt-users] Node Freezing
by Steve Schulze 16 Nov '12

16 Nov '12

Yeah, that's what I'm thinking too. Right now doing memory stick swaps to see if that's it. On round 2! Amateur Radio - The Original Social Media Steve Schulze - Radio Amateur, General Class - N9UDO Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ Administrator, Baraboo, Wisconsin AllStarLink Systems - 27616, 27727 Treasurer, Badgerland Amateur Television Society - KB9SFS http://yellowthunder.org/dstar.html On 11/15/2012 13:23, Tim Sawyer wrote: > I'd bet it's your hardware, maybe RAM. It's pretty unlikely Asterisk would totally lock up your machine. > -- > Tim > :wq > > On Nov 15, 2012, at 5:27 AM, Steve Schulze <n9udo(a)yellowthunder.org> wrote: > >> I had recently moved node 27727 to a new box using the latest full install of ACID. >> >> I'm now seeing random freezing of Asterisk, or one of it's components, as the node just stops responding. Sometime the node will run for several hours, longest run was almost 12 hours, I have seen it as short as 1 or 2 hours. When this occurs, I cannot reboot the machine from the prompt. When I attempt, the PC speaker just squeals until I force the power off. >> >> Below is a capture of what usually occurs when the node freezes. >> >> >> [KWB9FDZ*CLI> >> [Nov 14 17:31:03] ERROR[2364]: chan_usbradio.c:2599 usbradio_read: HID process has died or something!! >> >> [KWB9FDZ*CLI> >> -- Hungup 'Zap/pseudo-1321073272' >> -- Hungup 'Zap/pseudo-1923931712' >> -- Hungup 'Zap/pseudo-471354119' >> -- Hungup 'Zap/pseudo-1974549115' >> -- Hungup 'Zap/pseudo-938459000' >> -- Hungup 'Zap/pseudo-360012123' >> [Nov 14 17:33:08] WARNING[2361]: app_rpt.c:21836 rpt_master: rpt_thread restarted on node 27727 >> >> [KWB9FDZ*CLI> >> -- Re-Loading config for repeater 27727 >> >> [KWB9FDZ*CLI> >> -- rpt (Rx) initiating call to Radio/usb27727 on Radio/usb27727 >> >> [KWB9FDZ*CLI> >> [Nov 14 17:33:12] ERROR[5383]: chan_usbradio.c:2599 usbradio_read: HID process has died or something!! >> >> [KWB9FDZ*CLI> >> -- Hungup 'Zap/pseudo-1356185696' >> -- Hungup 'Zap/pseudo-1200975276' >> -- Hungup 'Zap/pseudo-1694965886' >> -- Hungup 'Zap/pseudo-1185873296' >> -- Hungup 'Zap/pseudo-353324112' >> -- Hungup 'Zap/pseudo-956752671' >> == Set device 4-1 to usb27727 >> [Nov 14 17:33:40] WARNING[5384]: chan_usbradio.c:1700 hidthread: Loaded parameters from usbradio_tune_usb27727.conf for device usb27727 . >> >> [KWB9FDZ*CLI> >> [Nov 14 17:35:49] WARNING[2361]: app_rpt.c:21836 rpt_master: rpt_thread restarted on node 27727 >> -- Re-Loading config for repeater 27727 >> -- rpt (Rx) initiating call to Radio/usb27727 on Radio/usb27727 >> [Nov 14 17:35:49] WARNING[5399]: chan_usbradio.c:2674 usbradio_read: Possibly stuck USB read channel. [usb27727] >> [Nov 14 17:35:53] ERROR[5399]: chan_usbradio.c:2599 usbradio_read: HID process has died or something!! >> >> [KWB9FDZ*CLI> >> -- Hungup 'Zap/pseudo-1234779841' >> -- Hungup 'Zap/pseudo-823024661' >> -- Hungup 'Zap/pseudo-128844783' >> -- Hungup 'Zap/pseudo-1477433026' >> -- Hungup 'Zap/pseudo-47743459' >> == Set device 4-1 to usb27727 >> [Nov 14 17:36:22] WARNING[5400]: chan_usbradio.c:1700 hidthread: Loaded parameters from usbradio_tune_usb27727.conf for device usb27727 . >> -- Hungup 'Zap/pseudo-358092408' >> [Nov 14 17:37:59] WARNING[2361]: app_rpt.c:21836 rpt_master: rpt_thread restarted on node 27727 >> -- Re-Loading config for repeater 27727 >> -- rpt (Rx) initiating call to Radio/usb27727 on Radio/usb27727 >> [Nov 14 17:38:03] ERROR[5415]: chan_usbradio.c:2599 usbradio_read: HID process has died or something!! >> >> [KWB9FDZ*CLI> >> -- Hungup 'Zap/pseudo-959192474' >> -- Hungup 'Zap/pseudo-119995292' >> -- Hungup 'Zap/pseudo-910823610' >> -- Hungup 'Zap/pseudo-1271419211' >> -- Hungup 'Zap/pseudo-1514445782' >> -- Hungup 'Zap/pseudo-1885015791' >> == Set device 4-1 to usb27727 >> [Nov 14 17:38:31] WARNING[5416]: chan_usbradio.c:1700 hidthread: Loaded parameters from usbradio_tune_usb27727.conf for device usb27727 . >> >> [KWB9FDZ*CLI> >> [Nov 14 17:40:08] WARNING[2361]: app_rpt.c:21836 rpt_master: rpt_thread restarted on node 27727 >> >> [KWB9FDZ*CLI> >> -- Re-Loading config for repeater 27727 >> >> [KWB9FDZ*CLI> >> -- rpt (Rx) initiating call to Radio/usb27727 on Radio/usb27727 >> >> [KWB9FDZ*CLI> >> [Nov 14 17:40:12] ERROR[5431]: chan_usbradio.c:2599 usbradio_read: HID process has died or something!! >> >> [KWB9FDZ*CLI> >> -- Hungup 'Zap/pseudo-123945640' >> -- Hungup 'Zap/pseudo-1914243603' >> -- Hungup 'Zap/pseudo-1904931772' >> -- Hungup 'Zap/pseudo-1252634755' >> -- Hungup 'Zap/pseudo-1804246462' >> -- Hungup 'Zap/pseudo-569032085' >> == Set device 4-1 to usb27727 >> [Nov 14 17:40:40] WARNING[5432]: chan_usbradio.c:1700 hidthread: Loaded parameters from usbradio_tune_usb27727.conf for device usb27727 . >> >> [KWB9FDZ*CLI> >> [Nov 14 17:42:17] WARNING[2361]: app_rpt.c:21836 rpt_master: rpt_thread restarted on node 27727 >> >> [KWB9FDZ*CLI> >> -- Re-Loading config for repeater 27727 >> >> [KWB9FDZ*CLI> >> -- rpt (Rx) initiating call to Radio/usb27727 on Radio/usb27727 >> >> [KWB9FDZ*CLI> >> [Nov 14 17:42:21] ERROR[5456]: chan_usbradio.c:2599 usbradio_read: HID process has died or something!! >> >> [KWB9FDZ*CLI> >> -- Hungup 'Zap/pseudo-1625376915' >> -- Hungup 'Zap/pseudo-1332043632' >> -- Hungup 'Zap/pseudo-1082279744' >> -- Hungup 'Zap/pseudo-1304564785' >> -- Hungup 'Zap/pseudo-976351035' >> -- Hungup 'Zap/pseudo-2003986033' >> == Set device 4-1 to usb27727 >> [Nov 14 17:42:49] WARNING[5457]: chan_usbradio.c:1700 hidthread: Loaded parameters from usbradio_tune_usb27727.conf for device usb27727 . >> >> [KWB9FDZ*CLI> >> [Nov 14 17:44:26] WARNING[2361]: app_rpt.c:21836 rpt_master: rpt_thread restarted on node 27727 >> >> [KWB9FDZ*CLI> >> -- Re-Loading config for repeater 27727 >> >> [KWB9FDZ*CLI> >> -- rpt (Rx) initiating call to Radio/usb27727 on Radio/usb27727 >> >> [KWB9FDZ*CLI> >> [Nov 14 17:44:30] ERROR[5481]: chan_usbradio.c:2599 usbradio_read: HID process has died or something!! >> >> [KWB9FDZ*CLI> >> -- Hungup 'Zap/pseudo-562695817' >> -- Hungup 'Zap/pseudo-41485895' >> -- Hungup 'Zap/pseudo-674125634' >> -- Hungup 'Zap/pseudo-1681055800' >> -- Hungup 'Zap/pseudo-1172360100' >> -- Hungup 'Zap/pseudo-2074122207' >> == Set device 4-1 to usb27727 >> [Nov 14 17:44:59] WARNING[5483]: chan_usbradio.c:1700 hidthread: Loaded parameters from usbradio_tune_usb27727.conf for device usb27727 . >> >> [KWB9FDZ*CLI> >> [Nov 14 17:46:36] WARNING[2361]: app_rpt.c:21836 rpt_master: rpt_thread restarted on node 27727 >> >> [KWB9FDZ*CLI> >> -- Re-Loading config for repeater 27727 >> >> [KWB9FDZ*CLI> >> -- rpt (Rx) initiating call to Radio/usb27727 on Radio/usb27727 >> >> [KWB9FDZ*CLI> >> [Nov 14 17:46:40] ERROR[5506]: chan_usbradio.c:2599 usbradio_read: HID process has died or something!! >> >> [KWB9FDZ*CLI> >> -- Hungup 'Zap/pseudo-81739412' >> -- Hungup 'Zap/pseudo-933811143' >> -- Hungup 'Zap/pseudo-1900592699' >> -- Hungup 'Zap/pseudo-873450041' >> -- Hungup 'Zap/pseudo-1455015117' >> -- Hungup 'Zap/pseudo-1502090246' >> == Set device 4-1 to usb27727 >> [Nov 14 17:47:07] WARNING[5507]: chan_usbradio.c:1700 hidthread: Loaded parameters from usbradio_tune_usb27727.conf for device usb27727 . >> >> >> The system just keep spewing this string every couple of minutes. >> >> >> Anybody run across this or have any thoughts what might be causing it. >> >> >> >> Thank you for your time. >> >> -- >> Amateur Radio - The Original Social Media >> >> Steve Schulze - Radio Amateur, General Class - N9UDO >> Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ >> Administrator, Baraboo, Wisconsin AllStarLink Systems - 27616, 27727 >> Treasurer, Badgerland Amateur Television Society - KB9SFS >> >> http://yellowthunder.org/dstar.html >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users(a)ohnosec.org >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > >

1 0

Re: [App_rpt-users] Configuring Asterisk for the first time...
by Shane Morris 16 Nov '12

16 Nov '12

Thats ok about not knowing - I'd started Asterisk thus: "asterisk -vvvgc" and I still don't get enough detail >.< What I might do is try unplugging the URI, then if that doesn't work, restarting the RPi. Lets see how we go...! Many thanks! On Fri, Nov 16, 2012 at 9:08 PM, Buddy Brannan <buddy(a)brannan.name> wrote: > Just a guess, but it sounds like your URI isn't being detected properly. I've seen something like that when my USB dongle isn't plugged in. I wonder if there's some issue with uSB audio or something? > > Sorry, I don't have a RPi, and I really wish I knew more than i currently do. > -- > Buddy Brannan, KB5ELV - Erie, PA > Phone: (814) 860-3194 or 888-75-BUDDY > > > > On Nov 16, 2012, at 4:55 AM, Shane Morris <edgecomberts(a)gmail.com> wrote: > >> Or - "Has this been asked a million times?" >> >> After following the PDF: >> >> http://kd3su.us/allStar/acid-sysadmin.pdf >> >> To configure my RaspberryPi, I get the following error message: >> >> WARNING[18342]: app_rpt.c:21848 rpt_master: rpt_thread restarted on node 099 >> -- Re-Loading config for repeater 099 >> rpt:Sorry unable to obtain Rx channel >> [Jan 7 13:46:12] ERROR[18342]: app_rpt.c:21831 rpt_master: Continual >> RPT thread restarts, killing Asterisk >> >> And Asterisk promptly dies. After searching around on Google, and the >> usual places, I'm not able to find much on this, so I'm wondering if >> anyone can help me? >> >> I've made the URI extension "099" and my two phones "101" and "102." >> Voicemail is "900" I believe (so its out of the way...). >> >> Any insight will be welcomed, and I'll post up the contents of my >> config files if needed. I'm using Arch Linux on the RPi, with the >> latest SVN checkout from ohnosec. >> >> If you need anything else to help diagnose the problem, let me know... >> >> Many thanks! >> >> Shane. >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users(a)ohnosec.org >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >

1 0

Configuring Asterisk for the first time...
by Shane Morris 16 Nov '12

16 Nov '12

Or - "Has this been asked a million times?" After following the PDF: http://kd3su.us/allStar/acid-sysadmin.pdf To configure my RaspberryPi, I get the following error message: WARNING[18342]: app_rpt.c:21848 rpt_master: rpt_thread restarted on node 099 -- Re-Loading config for repeater 099 rpt:Sorry unable to obtain Rx channel [Jan 7 13:46:12] ERROR[18342]: app_rpt.c:21831 rpt_master: Continual RPT thread restarts, killing Asterisk And Asterisk promptly dies. After searching around on Google, and the usual places, I'm not able to find much on this, so I'm wondering if anyone can help me? I've made the URI extension "099" and my two phones "101" and "102." Voicemail is "900" I believe (so its out of the way...). Any insight will be welcomed, and I'll post up the contents of my config files if needed. I'm using Arch Linux on the RPi, with the latest SVN checkout from ohnosec. If you need anything else to help diagnose the problem, let me know... Many thanks! Shane.

1 0

Help PTT
by FERNANDO VILLARROEL 16 Nov '12

16 Nov '12

Dear. I have a local ACID config connected with a Motorola GM300 and URI I am using the follow cable: URI (USB Radio Interface) to Motorola Maxtrac, GM300 or M120 16 Pin Repeater I am trying to doing PTT from a Zoiper Softphone to handy device, but not works (*99), i am follow the next howto: http://allstarnode.com/viewtopic.php?f=5&t=67 But *99 not works for me. My usbradio.conf: [general] [usb] hdwtype=0 ; Leave this set to 0 for USB sound fobs modified using ; the instructions from usbfob.pdf. Use a setting of ; 1 is for Dingotel/Sph interfaces. rxboost=1 ; 0 = 20db attenuator inserted, 1= 20db attenuator removed ; Set to 1 for additonal gain if using a low-level receiver output rxctcssrelax=1 ; reduce talkoff from radios w/o CTCSS Tx HPF ; Do not change this, leave this as a 1 txctcssdefault=100.0 ; default tx ctcss freq, any frequency permitted ;rxctcssfreqs=100.0 ; rx ctcss freqs in floating point. must be in table ;txctcssfreqs=100.0 ; tx ctcss freqs, any frequency permitted carrierfrom=dsp ; no,usb,usbinvert,dsp,vox ; no - no carrier detection at all ; usb - from the COR line on the modified USB sound fob ; usbinvert - from the inverted COR line on the modified USB sound fob ; dsp - from RX noise using dsp techniques ; vox - voice activated from RX audio ctcssfrom=usb ; no,usb,dsp ; no - CTCSS decoding, system will be carrier squelch ; usb - CTCSS decoding using input from USB FOB ; (currently not supported) ; dsp - CTCSS decoding using RX audio in DSP. ; rxdemod option must be set to flat for this to work. rxdemod=flat ; input type from radio: no,speaker,flat ; no - RX audio input not used ; flat - Use RX audio from discriminator ; speaker - use de-emphasized audio txprelim=no ; Audio processing on left output channel: no,yes ; no - Audio is not pre-emphasized and limited. ; Suitable for use on a microphone input ; yes - Audio is pre-emphasized and limited. txprelim=no ; Audio processing on left output channel: no,yes ; no - Audio is not pre-emphasized and limited. ; Suitable for use on a microphone input ; yes - Audio is pre-emphasized and limited. ; Suitable for direct connection to an FM modulator txtoctype=notone ; Transmit tone control type: no,phase,notone ; no - CTCSS tone encoding with no hang time ; phase - encode CTCSS and reverse phase ; AKA ("reverse burst") before unkeying TX ; notone - encode CTCSS and stop sending tone before unkeying TX ; AKA ("chicken burst") txmixa=composite ; Left channel output: no,voice,tone,composite,auxvoice ; no - Do not output anything ; voice - output voice only ; tone - CTCSS tone only ; composite - voice and tone ; auxvoice - auxiliary voice output at headphone level for monitoring txmixb=no ; Right channel output: no,voice,tone,composite, auxvoice ; See txmixa above. invertptt=0 ; Invert PTT 0 = ground to transmit, 1 = open to transmit ; This is the collector lead of the 2n4401 on the modified ; usb sound fob. ; please refer to the howto for the procedure to do this. duplex=2 ; Full Duplex I hope you could tell me how i can do or what is the best config for usbradio.conf, URI and Motorola GM300? I hope any idea. Fernando.

1 0

Re: [App_rpt-users] App_rpt-users Digest, Vol 45, Issue 24
by Paul Yeager 15 Nov '12

15 Nov '12

For clarification, "over the XIPAR install" is intended to indicate that XIPAR is what is currently on the laptop. Also, my apologies for not truncating the email. 73 de W4SKI

1 0

ACID install hangs at running /sbin/loader
by Paul Yeager 15 Nov '12

15 Nov '12

I am trying to install ACID over the XIPAR install on a Compaq Evo N610C laptop. The install process hangs at "running /sbin/loader". I have tried a few of the remedies suggested for the same problem with other distros, but no luck. Any ideas? 73 de W4SKI On Nov 15, 2012 12:00 PM, <app_rpt-users-request(a)ohnosec.org> wrote: > Send App_rpt-users mailing list submissions to > app_rpt-users(a)ohnosec.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > or, via email, send a message with subject or body 'help' to > app_rpt-users-request(a)ohnosec.org > > You can reach the person managing the list at > app_rpt-users-owner(a)ohnosec.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of App_rpt-users digest..." > > > Today's Topics: > > 1. Lost conn to RTCM (Fran) > 2. RTCM for Sale (Jim W7RY) > 3. Re: RTCM for Sale (Jim W7RY) > 4. Node Freezing (Steve Schulze) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 14 Nov 2012 17:46:47 -0800 (PST) > From: Fran <baldwin88(a)yahoo.com> > To: "App_rpt-users(a)ohnosec.org" <App_rpt-users(a)ohnosec.org> > Subject: [App_rpt-users] Lost conn to RTCM > Message-ID: > <1352944007.82204.YahooMailNeo(a)web120302.mail.ne1.yahoo.com> > Content-Type: text/plain; charset="iso-8859-1" > > I lost connection to my 2 remote RTCM units....Recently my router was > rebooted by accident and it went back to all default settings, my IP > changed. I reloaded all the port forwarding info but still cant connect to > my 2 remote RTCM units. > ? > I checked the RTCM settings and the only thing I can think of is that the > Voter Server Address was hard coded with my Old IP, however reading the > RTCM manual it states the following:? > The RTCM does a DNS resolution once per minute and resolves the IP address > for the RTCM server, based upon the FQDN specified in this configuration. > Therefore, the actual IP address of the RTCM server may be changed (and its > associated DNS entry), and the RTCM > firmware will continue to be aware of its current IP address (thus not > requiring re-configuration of the RTCM firmware if the IP address of the > RTCM server changes). > ? > ? > So even if my IP on my router changed shouldnt it be transparent to the > RTCM????? > ? > Frank >

1 0

Node Freezing
by Steve Schulze 15 Nov '12

15 Nov '12

I had recently moved node 27727 to a new box using the latest full install of ACID. I'm now seeing random freezing of Asterisk, or one of it's components, as the node just stops responding. Sometime the node will run for several hours, longest run was almost 12 hours, I have seen it as short as 1 or 2 hours. When this occurs, I cannot reboot the machine from the prompt. When I attempt, the PC speaker just squeals until I force the power off. Below is a capture of what usually occurs when the node freezes. [KWB9FDZ*CLI> [Nov 14 17:31:03] ERROR[2364]: chan_usbradio.c:2599 usbradio_read: HID process has died or something!! [KWB9FDZ*CLI> -- Hungup 'Zap/pseudo-1321073272' -- Hungup 'Zap/pseudo-1923931712' -- Hungup 'Zap/pseudo-471354119' -- Hungup 'Zap/pseudo-1974549115' -- Hungup 'Zap/pseudo-938459000' -- Hungup 'Zap/pseudo-360012123' [Nov 14 17:33:08] WARNING[2361]: app_rpt.c:21836 rpt_master: rpt_thread restarted on node 27727 [KWB9FDZ*CLI> -- Re-Loading config for repeater 27727 [KWB9FDZ*CLI> -- rpt (Rx) initiating call to Radio/usb27727 on Radio/usb27727 [KWB9FDZ*CLI> [Nov 14 17:33:12] ERROR[5383]: chan_usbradio.c:2599 usbradio_read: HID process has died or something!! [KWB9FDZ*CLI> -- Hungup 'Zap/pseudo-1356185696' -- Hungup 'Zap/pseudo-1200975276' -- Hungup 'Zap/pseudo-1694965886' -- Hungup 'Zap/pseudo-1185873296' -- Hungup 'Zap/pseudo-353324112' -- Hungup 'Zap/pseudo-956752671' == Set device 4-1 to usb27727 [Nov 14 17:33:40] WARNING[5384]: chan_usbradio.c:1700 hidthread: Loaded parameters from usbradio_tune_usb27727.conf for device usb27727 . [KWB9FDZ*CLI> [Nov 14 17:35:49] WARNING[2361]: app_rpt.c:21836 rpt_master: rpt_thread restarted on node 27727 -- Re-Loading config for repeater 27727 -- rpt (Rx) initiating call to Radio/usb27727 on Radio/usb27727 [Nov 14 17:35:49] WARNING[5399]: chan_usbradio.c:2674 usbradio_read: Possibly stuck USB read channel. [usb27727] [Nov 14 17:35:53] ERROR[5399]: chan_usbradio.c:2599 usbradio_read: HID process has died or something!! [KWB9FDZ*CLI> -- Hungup 'Zap/pseudo-1234779841' -- Hungup 'Zap/pseudo-823024661' -- Hungup 'Zap/pseudo-128844783' -- Hungup 'Zap/pseudo-1477433026' -- Hungup 'Zap/pseudo-47743459' == Set device 4-1 to usb27727 [Nov 14 17:36:22] WARNING[5400]: chan_usbradio.c:1700 hidthread: Loaded parameters from usbradio_tune_usb27727.conf for device usb27727 . -- Hungup 'Zap/pseudo-358092408' [Nov 14 17:37:59] WARNING[2361]: app_rpt.c:21836 rpt_master: rpt_thread restarted on node 27727 -- Re-Loading config for repeater 27727 -- rpt (Rx) initiating call to Radio/usb27727 on Radio/usb27727 [Nov 14 17:38:03] ERROR[5415]: chan_usbradio.c:2599 usbradio_read: HID process has died or something!! [KWB9FDZ*CLI> -- Hungup 'Zap/pseudo-959192474' -- Hungup 'Zap/pseudo-119995292' -- Hungup 'Zap/pseudo-910823610' -- Hungup 'Zap/pseudo-1271419211' -- Hungup 'Zap/pseudo-1514445782' -- Hungup 'Zap/pseudo-1885015791' == Set device 4-1 to usb27727 [Nov 14 17:38:31] WARNING[5416]: chan_usbradio.c:1700 hidthread: Loaded parameters from usbradio_tune_usb27727.conf for device usb27727 . [KWB9FDZ*CLI> [Nov 14 17:40:08] WARNING[2361]: app_rpt.c:21836 rpt_master: rpt_thread restarted on node 27727 [KWB9FDZ*CLI> -- Re-Loading config for repeater 27727 [KWB9FDZ*CLI> -- rpt (Rx) initiating call to Radio/usb27727 on Radio/usb27727 [KWB9FDZ*CLI> [Nov 14 17:40:12] ERROR[5431]: chan_usbradio.c:2599 usbradio_read: HID process has died or something!! [KWB9FDZ*CLI> -- Hungup 'Zap/pseudo-123945640' -- Hungup 'Zap/pseudo-1914243603' -- Hungup 'Zap/pseudo-1904931772' -- Hungup 'Zap/pseudo-1252634755' -- Hungup 'Zap/pseudo-1804246462' -- Hungup 'Zap/pseudo-569032085' == Set device 4-1 to usb27727 [Nov 14 17:40:40] WARNING[5432]: chan_usbradio.c:1700 hidthread: Loaded parameters from usbradio_tune_usb27727.conf for device usb27727 . [KWB9FDZ*CLI> [Nov 14 17:42:17] WARNING[2361]: app_rpt.c:21836 rpt_master: rpt_thread restarted on node 27727 [KWB9FDZ*CLI> -- Re-Loading config for repeater 27727 [KWB9FDZ*CLI> -- rpt (Rx) initiating call to Radio/usb27727 on Radio/usb27727 [KWB9FDZ*CLI> [Nov 14 17:42:21] ERROR[5456]: chan_usbradio.c:2599 usbradio_read: HID process has died or something!! [KWB9FDZ*CLI> -- Hungup 'Zap/pseudo-1625376915' -- Hungup 'Zap/pseudo-1332043632' -- Hungup 'Zap/pseudo-1082279744' -- Hungup 'Zap/pseudo-1304564785' -- Hungup 'Zap/pseudo-976351035' -- Hungup 'Zap/pseudo-2003986033' == Set device 4-1 to usb27727 [Nov 14 17:42:49] WARNING[5457]: chan_usbradio.c:1700 hidthread: Loaded parameters from usbradio_tune_usb27727.conf for device usb27727 . [KWB9FDZ*CLI> [Nov 14 17:44:26] WARNING[2361]: app_rpt.c:21836 rpt_master: rpt_thread restarted on node 27727 [KWB9FDZ*CLI> -- Re-Loading config for repeater 27727 [KWB9FDZ*CLI> -- rpt (Rx) initiating call to Radio/usb27727 on Radio/usb27727 [KWB9FDZ*CLI> [Nov 14 17:44:30] ERROR[5481]: chan_usbradio.c:2599 usbradio_read: HID process has died or something!! [KWB9FDZ*CLI> -- Hungup 'Zap/pseudo-562695817' -- Hungup 'Zap/pseudo-41485895' -- Hungup 'Zap/pseudo-674125634' -- Hungup 'Zap/pseudo-1681055800' -- Hungup 'Zap/pseudo-1172360100' -- Hungup 'Zap/pseudo-2074122207' == Set device 4-1 to usb27727 [Nov 14 17:44:59] WARNING[5483]: chan_usbradio.c:1700 hidthread: Loaded parameters from usbradio_tune_usb27727.conf for device usb27727 . [KWB9FDZ*CLI> [Nov 14 17:46:36] WARNING[2361]: app_rpt.c:21836 rpt_master: rpt_thread restarted on node 27727 [KWB9FDZ*CLI> -- Re-Loading config for repeater 27727 [KWB9FDZ*CLI> -- rpt (Rx) initiating call to Radio/usb27727 on Radio/usb27727 [KWB9FDZ*CLI> [Nov 14 17:46:40] ERROR[5506]: chan_usbradio.c:2599 usbradio_read: HID process has died or something!! [KWB9FDZ*CLI> -- Hungup 'Zap/pseudo-81739412' -- Hungup 'Zap/pseudo-933811143' -- Hungup 'Zap/pseudo-1900592699' -- Hungup 'Zap/pseudo-873450041' -- Hungup 'Zap/pseudo-1455015117' -- Hungup 'Zap/pseudo-1502090246' == Set device 4-1 to usb27727 [Nov 14 17:47:07] WARNING[5507]: chan_usbradio.c:1700 hidthread: Loaded parameters from usbradio_tune_usb27727.conf for device usb27727 . The system just keep spewing this string every couple of minutes. Anybody run across this or have any thoughts what might be causing it. Thank you for your time. -- Amateur Radio - The Original Social Media Steve Schulze - Radio Amateur, General Class - N9UDO Administrator, Baraboo, Wisconsin D-Star System - WB9FDZ Administrator, Baraboo, Wisconsin AllStarLink Systems - 27616, 27727 Treasurer, Badgerland Amateur Television Society - KB9SFS http://yellowthunder.org/dstar.html

1 0

RTCM for Sale
by Jim W7RY 15 Nov '12

15 Nov '12

I have a new in the box, never hooked up or used RTCM. $250.00 shipped. PayPal accepted. Thanks 73 Jim W7RY

1 1

Lost conn to RTCM
by Fran 15 Nov '12

15 Nov '12

I lost connection to my 2 remote RTCM units....Recently my router was rebooted by accident and it went back to all default settings, my IP changed. I reloaded all the port forwarding info but still cant connect to my 2 remote RTCM units. I checked the RTCM settings and the only thing I can think of is that the Voter Server Address was hard coded with my Old IP, however reading the RTCM manual it states the following: The RTCM does a DNS resolution once per minute and resolves the IP address for the RTCM server, based upon the FQDN specified in this configuration. Therefore, the actual IP address of the RTCM server may be changed (and its associated DNS entry), and the RTCM firmware will continue to be aware of its current IP address (thus not requiring re-configuration of the RTCM firmware if the IP address of the RTCM server changes). So even if my IP on my router changed shouldnt it be transparent to the RTCM????? Frank

1 0

Re: [App_rpt-users] ALLMON help….
by Ramesh Dhami, VA3UV/M 14 Nov '12

14 Nov '12

Great, will add that tomorrow. Cheers! Ramesh. ------Original Message------ From: Scott Weis To: 'Ramesh Dhami $VA3UV$' To: app_rpt-users Subject: RE: [App_rpt-users] ALLMON help…. Sent: Nov 13, 2012 10:37 PM In the general stanza of the manager.conf file put: displayconnects = no -----Original Message----- From: app_rpt-users-bounces(a)ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Ramesh Dhami (VA3UV) Sent: Tuesday, November 13, 2012 8:53 PM To: app_rpt-users(a)ohnosec.org Subject: Re: [App_rpt-users] ALLMON help…. On 13/11/2012 8:36 PM, Bradley Haney wrote: > Hello all.. > > getting ALLMON working i think but should i get this over and over on my box > > == Manager 'admin' logged off from 207.179.213.22 > == Manager 'admin' logged on from 207.179.213.22 > == Manager 'admin' logged off from 207.179.213.22 > == Manager 'admin' logged on from 207.179.213.22 > == Manager 'admin' logged off from 207.179.213.22 > == Manager 'admin' logged on from 207.179.213.22 > == Manager 'admin' logged off from 207.179.213.22 > == Manager 'admin' logged on from 207.179.213.22 > == Manager 'admin' logged off from 207.179.213.22 > == Manager 'admin' logged on from 207.179.213.22 > == Manager 'admin' logged off from 207.179.213.22 > == Manag > > > > > It appears to log on and the log right off log on and then off. > > Am I missing a step? <-- Nope - this is how it works! - hence my earlier posting about suppressing these messages. Cheers, Ramesh. _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users Sent on the TELUS Mobility network with BlackBerry

1 0