- App_rpt-users - lists.keekles.org

Alinco DR-135
by K7ILO 01 Jan '13

01 Jan '13

Hello all. I know I have seen a few threads on using the DR-135 as a node radio so I decided to ask this question. Has anyone using this radio had problems with a crackling noise or popping noise when the radio transmits? It doesn't matter if you are using the data port (for audio) or the mike and speaker jacks. Its not all the time but happens more than it doesn't. Thanks for any input into this matter. Harold K7ilo

4 5

URIx Now Repeating Fine But Only Carrier Squelch Mode
by Chris K7AZ 01 Jan '13

01 Jan '13

First a big thank you to those that helped get my URIx module to key the repeater transmitter and allow audio to pass through. Meanwhile... somewhere it has lost the CTCSS (PL) input requirement or in other words, it is now a carrier squelch repeater. Is there a setting to re-enable the CTCSS (PL) logic? Manually grounding the CTCSS input does not key the system but grounding the COS input does blow squelch noise through just fine. Chris K7AZ

2 1

gps change beacon rate
by James Smith 31 Dec '12

31 Dec '12

howdy all! i have been on the page to setup gps for my node http://ohnosec.org/drupal/node/179 it works great. but then i noticed it beacons every 60 seconds. http://aprs.fi/?c=raw&call=KD5OXM-29 any idea where the parameter is located or where to put it? in the new gps.conf i assume. thanks james kd5oxm

2 1

TM-G707 boards
by Jim Duuuude 31 Dec '12

31 Dec '12

I really dont get it. I made a single run of those TM-G707 interface boards and had most of them just sit there for years. Now, all of a sudden, people are getting interested in them, despite the fact that the radio has hot been made in years!! There seems to be, at this moment, about 5 requests for boards over and above what is available. If anyone is interested in being the "chairman of the board(s)" (as in putting up the money for a board fab run, then selling them much like I did), it might be a good idea so that everyone can get what they want. You generally have to make 10 boards at a time. If youre into doing this, let me know. Jim WB6NIL

1 0

Allmon / astdb.php
by Ramesh Dhami (VA3UV) 30 Dec '12

30 Dec '12

Hi Guys; Thanks to Jon, VA3RQ, for pointing out that the astdb on node 2248 is not updating. On investigation, I see the following issue when trying to run the astdb.php script: PHP Warning: fopen(astdb.txt): failed to open stream: Success in /var/www/html/allmon/astdb.php on line 16 astdb.txt does exist; I have tried playing around with the permissions but no luck! Looking at the astdb.php script I see the following: $db = "astdb.txt"; #$db1 = "/var/www_tnp/html/astdb.txt"; if (! $fh = fopen($db, 'c')) { die("Cannot open $db."); I have tried to set the explicit path for $db as well - but no luck. Any ideas? Thx! Ramesh.

1 0

My Repeater is getting AllStar for Christmas!
by Randy Neals 30 Dec '12

30 Dec '12

Hi All, A progress report.. I now have node 2257, 2258, and 2462 ready to make the trip up the hill. (It's only been 2 years of testing!) This will be going to the VE3RTR repeater site about an hours drive east of Toronto. We have a VHF-FM, 2 x UHF-FM, and a D-star VHF repeater at the site. Our Internet is via Wireless ISP. The node has been on the bench burning in and rebooted several times over the last week. I've tried various PCs in my earlier "testing phase", and have settled on the ACID install on a Shuttle Mini-PC. ACID installs issue-free on this hardware, and has given me no problems. The ICH7 I/O controller on the K45 supports 8 USB 2.0 interfaces, and the K45 Motherboard has 4 on the back and 4 internal, via double-header USB connectors. Shuttle K45 Mini-Computer (about 3 years old) Intel Core 2 DUO E7600 3GHz Intel 945 GC + ICH7 chipset 2GB RAM Emphase SATA Flash Module (8GB) 8 USB ports. (4 externally on the back, and 4 from motherboard headers extended to back) The shuttle PC has a Fan. [I've had another Shuttle PC running the D-star gateway at the repeater site for 3 years. The SSD in the gateway died, the fan in that PC is still fine!) There are 3 USB Radio Interfaces - URIx with eeprom. Planning to use these in Simple USB mode, extending the COS and PL lines from the repeater. This will be interfaced to FR-5000 ICOM on VE3RTR VHF, FR-6000 ICOM repeater on VE3RTR UHF, and an FR-4000 Icom on VE3MXR. Each have a DB-25 interface connector on the back with I/O connections, some of which are programmable as to function in the radio service software. Best, Randy VE3RWN / W3RWN a hour east of Toronto.

1 1

playing greatings..
by pete M 29 Dec '12

29 Dec '12

Hi! Is there a way to play a MP3 file to nodes that connect to the echolink node of a allstar server? only the user that just connected would receive the gretings... Would it also be possible to do the same with the user that connect with the web portal?

1 0

Re: [App_rpt-users] Command Mode use
by Ken 29 Dec '12

29 Dec '12

*4 is used to run commands on a remote node. (Assuming you have and use more than one node). Possibilities are really endless. One place I use it: I have a weather script on my 440 node … it’s a nifty one that gets MP3 podcasts from NOAA and plays them on the air using the Asterisk MP3 player. The podcast files, the player and the script are on the 440 machine. I did not want to put all of that on the other systems. The 440 and 224 machines are “perma-linked” together. So when a user punches in the code for weather on the 224 machine, it just issues a remote command to the 440 machine and the weather plays on both. I also do weekly bulletin transmissions – on three systems simultaneously. This requires disabling the TOT (etc) on all three machines, for the duration. The bulletin script runs on one machine and issues remote commands to the other machines to make them go into “bulletin mode” and then back to normal again, at the end. 73 Ken From: Kent Ochs [mailto:kentochs@sbcglobal.net] Sent: Saturday, December 29, 2012 9:25 PM To: Ken; 'Monty' Cc: app_rpt-users(a)ohnosec.org Subject: Re: [App_rpt-users] Command Mode Timeout Ken, Thank you for a second set of eyes on this problem. I am very aware of the Radio_Relax parameter and it is not my intention to reopen those discussions. I am willing to accept an occasional false decode. Changing the code to 4123 would certainly resolve the issue, as would disabling it altogether. The real problem is the fact that *40 opens the last node a command was issued on, otherwise it would take at least *4XXXX to start a command session. I'm still try to understand under what circumstances I would need to put a node into Command Mode. Can anyone confirm, that as Monty has indicated, totime it is watching the receive side? If it is, then it would be nice if there was a timeout timer that actually watched the transmit side. Kent _____ From: Ken <ke2n(a)cs.com> To: 'Kent Ochs' <kentochs(a)sbcglobal.net>; 'Monty' <monty(a)ke7jvx.com> Cc: app_rpt-users(a)ohnosec.org Sent: Saturday, December 29, 2012 6:20 PM Subject: RE: [App_rpt-users] Command Mode Timeout I spent some time looking the other night and I could not find anything either. The only timer seems to be one that clears out the digits – but does not exit the mode. If we rule out modifications to app_rpt.c, there are two other things you could try: 1) Make the function calling the cop command more complex – like 4123 – and let people know 2) Reduce the sensitivity of the DTMF decode – one way is to remove the “RADIO_RELAX” compiler flag in /usr/src/astsrc/asterisk/menuselect.makeopts There have been previous posts on the latter subject. GL Ken W4BRM/R From: app_rpt-users-bounces(a)ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Kent Ochs Sent: Saturday, December 29, 2012 6:30 PM To: Monty Cc: app_rpt-users(a)ohnosec.org Subject: Re: [App_rpt-users] Command Mode Timeout Monty, Thanks for the reply. I have spent considerable time, and try as a I may, have not found anything in the source that provides command mode timeout. My inclination at this point is to disable the ilink,4 command mode option. Kent _____ From: Monty <monty(a)ke7jvx.com> To: Kent Ochs <kentochs(a)sbcglobal.net> Cc: "app_rpt-users(a)ohnosec.org" <app_rpt-users(a)ohnosec.org> Sent: Thursday, December 27, 2012 2:24 PM Subject: Re: [App_rpt-users] Command Mode Timeout Hi Kent, I have come across this before, and I do believe there is a timeout to kill the Transmitter when there is no activity while in command mode, just not as short as the timeout timer. Not sure what it is set to, but you should be able to search the source file and see. From my experience, the Timeout Timer is looking at the Receiver activity and not the Transmitter activity, and does still operate while in command mode. My situation was someone put a repeater in command mode while traveling and went out of range of the repeater and could not take out of command mode. I brought up the repeater later and it was not keyed, but as soon as I keyed the repeater it gave the command telemetry and stayed keyed, so I took it out of command mode. Hope this helps. Monty On Wed, Dec 26, 2012 at 7:16 PM, Kent Ochs <kentochs(a)sbcglobal.net> wrote: Our repeater (A two node system consisting of VHF 27833 node linked to a UHF receiver on node 1998) recently experienced a random false dtmf *40 decode. This put the repeater into transmit mode. What bothers me most, is that while in command mode, the transmit timeout parameter (totime) appears to be ignored, not good if there isn't someone around that knows to send "#" or otherwise shutdown the machine. In normal operating mode, totime works as expected, and try as I may, I have not been able to find a "command mode timeout" parameter. Have I missed or mis-configured something to cause this behavior? Is there a problem with the command function not honoring the transmit timeout parameter? I understand that *4 is a mandatory command, but could someone enlighten me as to why I shouldn't just disable this command altogether? An inquired mind wants to know and appreciates your feedback. Thanks. Kent W9KAO _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

1 0

Command Mode Timeout
by Kent Ochs 29 Dec '12

29 Dec '12

Our repeater (A two node system consisting of VHF 27833 node linked to a UHF receiver on node 1998) recently experienced a random false dtmf *40 decode. This put the repeater into transmit mode. What bothers me most, is that while in command mode, the transmit timeout parameter (totime) appears to be ignored, not good if there isn't someone around that knows to send "#" or otherwise shutdown the machine. In normal operating mode, totime works as expected, and try as I may, I have not been able to find a "command mode timeout" parameter. Have I missed or mis-configured something to cause this behavior? Is there a problem with the command function not honoring the transmit timeout parameter? I understand that *4 is a mandatory command, but could someone enlighten me as to why I shouldn't just disable this command altogether? An inquired mind wants to know and appreciates your feedback. Thanks. Kent W9KAO

3 4

TM-G707 Interface board
by Jim Duuuude 29 Dec '12

29 Dec '12

For those who have asked, I un-earthed 4 (although 1 is already spoken for, I think) blank TM-G707 to URI/PCI Radio card interface boards. If anyone is interested, they are available for $20 plus shipping. Just send me an email privately. Jim WB6NIL

2 2