April 2010 - App_rpt-users - lists.keekles.org

intermittent problem, TX hangs up
by Kyle Whitney 09 Apr '10

09 Apr '10

Hello all! I am a new user of the app_rpt. I have been having an issue where the repeater will stay keyed until it times out. This usually happens after a transmission, it will stay keyed up until the timeout in the gm300 shuts it down and yet others its like a reeeeealy long squelch tail (about a minute to 1.5) during this time it will pass no audio. I wanted to ask if this has happened to anyone else? what did you do to fix it? Thanks, Kyle

2 1

bulletin mode
by Ken 09 Apr '10

09 Apr '10

Minor point - when I run the "bulletin" control state shown in the example 1 = rptena,lnkena,apdis,totdis,ufena,noice ; Net and news operation I got two things that I did not expect: 1) It still plays the timeout message, but of course it does not actually time out and stop transmitting 2) A user was able to connect (on echolink) - is this considered an "incoming connection"? Ken Jamrogowicz 27021

1 0

important update
by Jim Duuuude 06 Apr '10

06 Apr '10

For a long long long while now, I have had varying reports of some sort of problem where the rxsquelch setting for chan_usbradio changes depending on whether you just did a 'radio tune rxnoise' and then saved it, or you just brouight up chan_usbradio from its saved configuration. In addition, I myself, have seen cases where the RSSI and squelch values seemed just really silly high for some reason. I believe I have found the culprit and have fixed it. It turns out that the hardware gain of the USB sound chip was different depending on whether it just had a 'tune rxnoise' or if it was set up from the config file. It turns out that because of a rounding error, it would often set its value 1 too low (compared with what the 'tune rxnoise' calculated it should have been). Believe me, when you only get a range of 1 to 16, 1 too low makes a big difference (about 1.5 db)!! This has now been fixed in the new version of chan_usbradio that will appear on the SVN this afternoon after about 3:30 PM PDT. Also, because of changes made in the squelch processing a few months ago (hysteresis was added), the squelch turn-off point is at least 60 'RSSI units' (whatever they are) higher then the signal level. Its probably a good idea to set the rxsquelch level to 80-100 higher then the level with no signal. This should both fix and explain a lot of strange things going on. I dont think this deals with some of the weirdness with 12.5 kHz receivers, but it might at least help in this area. JIM WB6NIL

1 0

Re: [App_rpt-users] Anyone using MDC1200 for control?
by KT9AC 05 Apr '10

05 Apr '10

YES! This is working!!!!! I can't thank you enough for the effort. Now I can program up my radios to control the links remotely. The console does what its supposed to, and the mdcmacro works 100% according to it. I think this should be advertised as a major feature of Asterisk/Allstar. Here is my output to confirm: [mdcmacro] 1234 = *7 a555 = *81 astro*CLI> Got MDC-1200 (single-length) packet on node 27129: op: 01, arg: 80, UnitID: a555 Got MDC-1200 ID A555 from local system (27129) -- <Zap/pseudo-503514657> Playing 'rpt/goodmorning' (language 'en') -- Hungup 'Zap/pseudo-1352653485' -- <Zap/pseudo-503514657> Playing 'rpt/thetimeis' (language 'en') -- <Zap/pseudo-503514657> Playing 'digits/11' (language 'en') -- <Zap/pseudo-503514657> Playing 'digits/30' (language 'en') -- <Zap/pseudo-503514657> Playing 'digits/3' (language 'en') -- <Zap/pseudo-503514657> Playing 'digits/a-m' (language 'en') -- Hungup 'Zap/pseudo-503514657' Got MDC-1200 (single-length) packet on node 27129: op: 01, arg: 80, UnitID: 1234 Got MDC-1200 ID 1234 from local system (27129) -- <Zap/pseudo-415945723> Playing 'rpt/node' (language 'en') -- Hungup 'Zap/pseudo-1850177399' -- <Zap/pseudo-415945723> Playing 'digits/2' (language 'en') -- <Zap/pseudo-415945723> Playing 'digits/7' (language 'en') -- <Zap/pseudo-415945723> Playing 'digits/1' (language 'en') -- <Zap/pseudo-415945723> Playing 'digits/2' (language 'en') -- <Zap/pseudo-415945723> Playing 'digits/9' (language 'en') -- <Zap/pseudo-415945723> Playing 'rpt/repeat_only' (language 'en') -- Hungup 'Zap/pseudo-415945723' -- Hungup 'Zap/pseudo-1937793097' Tony Jim Duuuude wrote: > I found a problem with the mdc-1200 decode routine and fixed it. > Please download app_rpt version 0.223 from SVN after it gets put > up there later today (Sunday). > > JIM WB6NIL > >

2 1

Secure Web Control of Allstar nodes
by KT9AC 04 Apr '10

04 Apr '10

Hello to everyone, Just wondering if a secure web-based admin tool exists for our Allstar nodes? Working with a group that wants to use Asterisk/Allstar for a multi-state network, and desire the ability to log in to remotely control the individual nodes. If nothing exists, I'd be willing to write something in Apache/PHP that would simply call macros or control commands (via the asterisk -rx <cmd> feature). If this is a bad idea, or better served by sending codes to remote nodes, please let me know. Thanks, Tony

1 0

Limehy Linux on Intel D945GCLF2 / Atom 330
by Jim Duuuude 04 Apr '10

04 Apr '10

Does anyone have a Limey Linux system running on an Intel D945GCLF2 (ATOM 330, Dual-Core) system?? We have a test version of Limey Linux that supports both Hyperthreaded processors and dual-core, but we dont have any dual-core ATOM boards to test it on. Your help in the matter would be greatly appreciated. Thanks JIM WB6NIL

2 1

LM-34 temperature command?
by Neil Addis (WA5JXY) 03 Apr '10

03 Apr '10

Hi All, I looked through all the archives and the admin manual for app_rpt (as well as trying to decipher rpt.conf) to enable the temperature or other sensor (i/o) functions but I couldn't locate the info; LM-34 temperature wiring and/or function. Can someone that is using this function please copy and paste your section in rpt.conf that makes this work? I already have the LM-34 connected to pin 2 or the URL (as well as + and gnd), but I don't know how to interrogate it. Thanks! Neil

2 1

non-USA-standard repeater offset for freq-agile radios
by Jim Duuuude 02 Apr '10

02 Apr '10

I have added (still experimental) code in app_rpt version 0.211 (available this evening in SVN) to attempt to support non-USA-standard repeater offsets for frequency agile radios. I have tested the code on a TMG-707A, but not on any of the other models supported, which are TM-271, TM-D700, FT-897 and IC-706. The other radios did not seem to support such functionality. There are 2 ways of configuring this: the new rpt.conf parameters (that go into the node clause in rpt.conf), are split2m and split70cm, which specify the default offset for 2 meters and 70 centimeters in kilohertz. split2m = 600 split70cm = 5000 You may also specify the offset in a memory channel by adding an additional parameter before the options, for example: 01 = 147.435,103.5,1035,h-t ; This would be for W6NUT in Los Angeles with input of 146.40 JIM WB6NIL

5 5