October 2007 - App_rpt-users - lists.keekles.org

[App_rpt] Test message
by Stephen Rodgers 03 Nov '07

03 Nov '07

This is a test message.

2 4

[App_rpt] idtalkover parameter
by Mark Hagler 30 Oct '07

30 Oct '07

One more question... I'm figuring things out as I go along here. So far this is pretty cool! In rpt.conf the idtalkover parameter isn't strongly documented. My guess at it's function is to play a morse code ID underneath the repeated audio if a long-winded user has the repeater keyed up and the ID timer expires completely. So, I set idtime=6000 and then I held the receiver open for well in excess of 6 seconds, but it did not play any morse code I under the audio. I tested several cycles transmitting >6 seconds and it always plays the ID file in tail but never ID's when the timer expires during a transmission. Could somebody enlighten me either to what this parameter really does or show me if I'm using it incorrectly? Thanks, Mark Hagler

2 2

[App_rpt] tail messages not working
by Mark Hagler 30 Oct '07

30 Oct '07

Hello Everyone, I received the Analog Interface board today in the mail (Steve must have shipped it SUPER priority mail). To play with the software quickly I just connected it via two Yaesu FT-7800R mobile radios (via the 6-pin DATA jacks) and it works very nicely. One thing that I can't get to work right is tail messages. I put this in my config file: tailmessagetime=2000 ; Play a tail message every 5 mins tailsquashedtime=1000 ; If squashed by another user tailmessages=tail1,tail2,tail3 ;list of messages to be played for tail message And I have recorded a sample audio file and copied it three times (tail1.gsm, tail2.gsm, tail3.gsm). It doesn't look like app_rpt is even trying to play tail messages, as in I do not get any errors on the Asterisk console about missing audio files. Just for testing I set the value to 2 seconds to get it to try to play the files but it's not. Any thoughts? Thanks, Mark

2 5

Re: [App_rpt] Small Problem with Wiring the connector for USB FOB: [Fixed]
by Stephen Rodgers 30 Oct '07

30 Oct '07

Rev B of usbfob.pdf has been uploaded to the site with the fix to the receive audio input attenuator. Thanks for pointing this out to me. Steve Rodgers, WA6ZFT Roger F. Jordan wrote: > Hi everyone... I am in the process of setting up the CM-108 Sound FOB and > found a discrepancy between the directions and the schematic! > > The directions say to connect the twisted connection of the 68K resister and > the 470K resister to the connectors Pin 3 and the open end of the 470K to > the white wire... However the schematic shows the 470k going to pin 3 and > the 68K going to Pin 5 (ground) and the connection of both the resisters > going to the white wire... > > Before I get this thing together and find it does not work... Can someone > tell me which is correct? > > I have the hard stuff done... IE getting that dadgum resister connected to > the CM108 chip!! Heheh > > Thanks in advance! > Roger W4RFJ > > _______________________________________________ > App_rpt mailing list > App_rpt(a)lists.illiana.net > http://lists.illiana.net/mailman/listinfo/app_rpt >

1 0

Re: [App_rpt] Small Problem with Wiring the connector for USB FOB!!
by Stephen Rodgers 30 Oct '07

30 Oct '07

Roger, The schematic is correct. I will fix and upload a new version of the document. Steve. Roger F. Jordan wrote: > Hi everyone... I am in the process of setting up the CM-108 Sound FOB and > found a discrepancy between the directions and the schematic! > > The directions say to connect the twisted connection of the 68K resister and > the 470K resister to the connectors Pin 3 and the open end of the 470K to > the white wire... However the schematic shows the 470k going to pin 3 and > the 68K going to Pin 5 (ground) and the connection of both the resisters > going to the white wire.. > > Before I get this thing together and find it does not work... Can someone > tell me which is correct? > > I have the hard stuff done... IE getting that dadgum resister connected to > the CM108 chip!! Heheh > > Thanks in advance! > Roger W4RFJ > > _______________________________________________ > App_rpt mailing list > App_rpt(a)lists.illiana.net > http://lists.illiana.net/mailman/listinfo/app_rpt >

1 0

[App_rpt] Small Problem with Wiring the connector for USB FOB!!
by Roger F. Jordan 30 Oct '07

30 Oct '07

Hi everyone... I am in the process of setting up the CM-108 Sound FOB and found a discrepancy between the directions and the schematic! The directions say to connect the twisted connection of the 68K resister and the 470K resister to the connectors Pin 3 and the open end of the 470K to the white wire... However the schematic shows the 470k going to pin 3 and the 68K going to Pin 5 (ground) and the connection of both the resisters going to the white wire... Before I get this thing together and find it does not work... Can someone tell me which is correct? I have the hard stuff done... IE getting that dadgum resister connected to the CM108 chip!! Heheh Thanks in advance! Roger W4RFJ

1 0

[App_rpt] Still Looking for help to get the anode backup and
by Will 26 Oct '07

26 Oct '07

Steve, I've played around with the permisson and have made it work as you stated. I will revisit The audio now is my concern and can't figure out why the ARIB card is not processing it. I have measure a least 250 millvolt on pin 3 (RX), the input pin on the ARIB and will not pass audio for processing. I have turn the RX gain with no respones in the audio levels.. could there be a programable adjustment in the zapata.conf? Look like I need to go back and read hi hi but Where?

2 1

[App_rpt] radio interface question
by Will 26 Oct '07

26 Oct '07

Hello Mark, I use two Moto's GM300 as a repeater thats work great on a ARCOM RC210 controller. They will also work great on the app_rpt program, which is a excelent confirguration to use. I will be configuring my two GM300 shortly to finally take advantage of the full duplex system offered by the app_rpt program/hardware. As far as your 6 pin din some do not deliver enough audio on the output. So It depends on the radio in use. Most likely when in use you would use 1200 bps. The GM300 has 16 pins and depending if you have the 8 or 16 channel the more pins are programmble for what signals you need to connect up the app_rpt program that run the hardware. Will / W4WWM

1 0

[App_rpt] radio interface question
by Mark Hagler 25 Oct '07

25 Oct '07

Hello all I'm new to the group and just starting to assemble pieces to make a working app_rpt repeater system. To get up and running quickly I was thinking of using two mobile radios + a duplexer (a setup like the Motorola GR300 repeater, minus the crappy controller). When I look at all of the newer radios I own they all have a 6-pin DIN jack on the back often labeled "DATA" as it's intended to connect to a TNC for packet radio. A further look shows that the pins in this jack are all the right ones (COR, PTT, audio in, and two types of audio-out). I was wondering if anybody has attempted to hack together a simple working duplex system by just tapping into two mobile radios via this 6-pin connector? There's two types of audio available on that connector as far as I can tell, one suitable for 1200bps packet and the other for 9600. It looks like the "1200" pin carries de-emphasized audio, and the 9600 carries non-de-emphasized audio (discrimator direct output). As far as I can tell either one of these would work with the radio interface cards available. Thanks, Mark Hagler W7WMH

1 0

[App_rpt] issue with hid interface in chan_usbradio
by K3XH 23 Oct '07

23 Oct '07

Greetings everyone: Was curious if anyone has run into an issue with the usbradio channel driver when running Asterisk under it's own user and group? I have run up against what I think is a permissions issue of sorts. I did have everything running briefly when Asterisk was set up to run under root access, but really want to avoid that if possible. The chan_usbradio driver errors when claiming the (usb) hid interface from the kernel. Apparently, it's getting an error at what would be line 791 in the chan_usbradio.c source code. Which then results in a call to 'usb_detach_kernel_driver_np', on line 793, in an attempt to detach the kernel interface, where it ultimately fails. I've tried a couple simple approaches to resolve this, like setting the dsp and usb device to have asterisk as their owner/group and also set permissions (with '666') for the devices. I would look at modifiying udev.rules and PAM configurations, but at this point, I'm clueless as to what is conflicting with the hid interface for the usb soundfob. Whew! Anyone have any suggestions? Thanks! Mike, K3XH

3 5