June 2013 - App_rpt-users - lists.keekles.org

Allstar ACID compatibility with Intel Atom D2500?
by Paul Schlacter 13 Jun '13

13 Jun '13

Hello Group, Does anyone have experience running Allstar ACID on an Intel Atom D2500 mini-ITX PC? I have found a very attractive fanless PC on ebay, and want to take the jump, using it as an app_rpt and chan_voter server . Here is a link to the machine: http://www.ebay.com/itm/Intel-Atom-D2500-Dual-LAN-Dual-COM-Fanless-Mini-ITX… Have a nice day. Paul

3 2

Addendum to Systel Repeater interface message
by Bryan D. Boyle 13 Jun '13

13 Jun '13

Well....digging into building a more robust (and at the suggestion of Scott KB2EAR) or fault tolerant sense mechanism (ie it's better to be active high for the COR in case the radio goes tango uniform or looses power than active low to prevent dead keying)...so... Dug into the Systel with a digital meter...(it was handy and didn't want to go into the next room to get the 260; I usually like to see swinging needles rather than flipping LCD numbers...), and hitting the points on the receiver side of the board along the same connector as I was using to pick up the CTCSS (active low signal on pin 5), found the pad next (Pin 4) to it, marked on the schematic as, strangely enough, carrier detect, which in testing was an active HIGH pin with a valid carrier. Light bulb over the head time. Duh, even I get it sometimes.... So...ran another lead from carrier detect on the Systel receiver interface pin 4, moved the lead that was on the COR detect pin on the URI as a pseudo-detect inverted signal from the COR detect on the radio to its rightful place of pin 7 on the URI, new lead to pin 8...and in usbradio.conf changed the carrier detect from usbinvert to usb, ctcssdetect to usbinvert from no, restarted asterisk. Nice. Came right up. I was joking with KB2EAR on Monday night that there doesn't really seem to be any radios that you can't interface with the URI. I've even hooked up Wouxun HTs and gotten them to work (albeit with VOX...friends don't let friends use VOX, but it was to prove a point). Moral of the story: keep hacking at it. You CAN get it to work. Thinking it might be a problem on my TS830S, but you Never Know. Oh, and in investigating the input to the transmit side...Systel injects audio after what would normally have been the pre-emph circuit in the HT audio stage. So, added in some txpre-emph. Sounds A Whole Lot Better. Keep on burning rosin, folks. 73 BB WB0YLE

1 0

Changing default language
by Orland Lopez 13 Jun '13

13 Jun '13

Hey fellas I am setting up a node for a friend and we woulg like to change the default english language to spanish or portuguese..The question is, The voices have been recorded and have the proper format. how ca we change it? -- Gracias y 73's Hasta la Vista KI6LNX

1 0

G707 Remote Base Locking Up on URI
by Monty 12 Jun '13

12 Jun '13

Hello Everyone, I have tried two Kenwood G707s with three of Jim's URI Adapter cards and two URIs on two different computers. I am able to get three or four commands (freq, pl tone, etc) then I will get Allison saying "Invalid Frequency" and the CLI shows: "WARNING[7925]: app_rpt.c:13876 serial_remote_io: -99999 Serial device not responding on node 1010" The radio will not steer or accept commands anymore until I power cycle the 707. The after power cycle three or four commands and will not steer again. I have tried the same computer with a VHF Syntor with an xcat and will accept every command without issue. Also one of my 707s now lives on a Quad PCI card and steers with every command without issue. Has anyone else seen this or know the remedy? Below is my rpt.conf with the URI: [1010] archivedir=/etc/asterisk/qso rxchannel = simpleusb/usb1010 duplex=0 ioport = /dev/ttyS0 remote = kenwood authlevel = 1 memory=memory remote_inact_timeout=5400 remote_timeout=5400 functions=remote-functions phone_functions=remote-functions link_functions=remote-functions Monty KE7JVX

2 1

RTCM to ICOM FR5000 / FR6000 Cable
by Randy Neals 11 Jun '13

11 Jun '13

Hi, I recently connected a Micro-Node RTCM to an ICOM FR6000 UHF repeater. The FR5000/6000 has a DB25 auxiliary connector on the rear. Here is the sable pin-out I used. Maybe this helps someone else. FR6000 RTCM ---------------------------------------------------------------------- Pin 11 - 12VDC Out ------------------ Pin 1 +V In Pin 8 - MOD IN ------------------------- Pin 2 TX Audio Pin 9 Discriminator ------------------- Pin 3 RX Audio Pin 21 Analog Audible Out -------- Pin 4 CTCSS In Pin 14 GND------------------------------ Pin 5 GND Pin 19 EPTT ---------------------------- Pin 7 PTT DB25 Shell --- soldered to braid---DB9 Shell Programming FR6000. Configured for CTCSS on Receive, no CTCSS on transmit. Program Pin 21 I/O for Audible Out which is a signal indication when the receiver is unmuted by squelch/tone. Program Pin 19 I/O for EPTT - External PTT Best, Randy W3RWN / VE3RWN San Antonio, TX

1 0

DMK URI to Motorola R100
by Geoff 11 Jun '13

11 Jun '13

It -really- can't be this hard... The Service manual for the R100 is at http://www.repeater-builder.com/motorola/r100/uhf-r100-service-manual-68810… On page 58 is the output of Jaux I'm using pins 14 - gnd 15 - spk hi 16 - Mic hi 17 - Mic gnd 18 - PL monitor (active low) 19 - PTT (active low) Corresponding Pins on the DMX URI ~should~ be (I would think) URI R100 Jaux 1 PTT 19 PTT 8 COR 18(*) PL Monitor 24 Ain 15 Spk Hi 12 Aout 16 Mic Hi 13 gnd 17 Mic gnd 13 gnd 14 gnd So... when I plug it in, the R100 keys up, and running radio-tune-menu, nothing works. (* = I use COR for PL monitor, because my R100 uses DPL (DCS) and not CTCSS.) Thoughts? -Geoff/W5OMR (29655)

5 5

on-board audio
by K&R Yoksh 10 Jun '13

10 Jun '13

Analog sound cards are not supported, especially not the on-board variety. The parallel port support is handy, and I am probably it's biggest supporter! It certainly makes it easy to homebrew an interface for COS/PTT/AUX (or even use an IRLP board), but you'll still need a CM108 or CM119 USB fob to handle the audio. You won't need to modify the fob under most circumstances. 73, Kyle Yoksh K0KN Olathe, KS Allstar 2210-2219 --- Original Message --- For bench testing / monitoring / whatever purposes, can I use on-board audio devices? I see the chan_simpleusb/usbradio can use the parallel port for COR and PTT, I'm wondering if I can also use on-board audio... Assume the on-board device is supported by OSS. Couple use-cases: * bench-test / local monitor -- computer speakers, computer microphone * base-station / dispatch console * audio to a control-RX input on a collocated repeater controller -Matt-

2 1

on-board audio
by KB0KZR 09 Jun '13

09 Jun '13

For bench testing / monitoring / whatever purposes, can I use on-board audio devices? I see the chan_simpleusb/usbradio can use the parallel port for COR and PTT, I'm wondering if I can also use on-board audio... Assume the on-board device is supported by OSS. Couple use-cases: * bench-test / local monitor -- computer speakers, computer microphone * base-station / dispatch console * audio to a control-RX input on a collocated repeater controller -Matt-

1 0

Batwing Systel conversion Success! (LONG)
by Bryan D. Boyle 09 Jun '13

09 Jun '13

Well, thanks to a trade with a fellow participant (KC2VRJ, thanks Paul!) I am working with a Motorola Systel SE stand-alone repeater on the 440 band. For those unfamiliar with this box, it's a stand alone repeater, meant for local (real local) usage; it's 2 gutted GP300 HTs, a mobile duplexer, and control board in a single box, meant for interfacing to a phone line for autopatch, and is basically a plug-and-play solution for campgrounds, amusement parks, etc. in the Low Power Industrial band right above our 440 allotment. Programmed the radios with the proper RSS, and with the onboard controller into a dummy load, confirmed the thing works before smoking rosin and flowing solder. Problem is...it works well, but it IS a stand-alone device. No ID, real easy to bring up autopatch (a "*" character forces phone off hook..."#" goes on-hook), and meant for true appliance operators So, simplistically, the question becomes how to use the radios in the box for what they are, some of the circuitry (COR, RX Out, TX audio In, PTT) while bypassing the controller in the box. Turns out it was simpler than can be imagined. What I thought would work was two things: 1. Prevent the internal controller from seeing a valid COR signal, and redirecting (or using the other active HI signal, CTCSS detect, which would work since our local Coord folks require some access method besides carrier, so, CTCSS will be sufficient) that signal or using the PL detect as a "COR" for the URI. Breaking the circuit for both would essentially disable the on-board controller from ever seeing a valid signal. So, yeah, it just sits there munching on electrons from the power supply. 2. Inject non-processed mic level audio to the transmit side as close to the xmt brick as possible. It should be noted that I'm depending on the radios themselves to do the CTCSS detection (and raising a signal on one of the lines) as well as the de/pre-emphasis which simplifies the processing in the app_rpt application. And, with 6 nodes running on a 1.5gig Althon mini-tower...need to preserve some processing headroom. Anyway, turns out it's simpler than can be imagined. Just had to think about what I was looking at (and buying a magnifying work light...darn 57-year-old presbyopic eyes...). The modifications I made can be turned back (didn't cut any traces) or used with a TPDT switch to re-enable the signals to re-work with the onboard if the box is going to be used as a low-power portable repeater. It should be noted that, along with the circuit changes I made, I also built a couple of chassis-mount N Female to BNC jumpers with RG-142 to bring both RF signals out to the rear panel. This lets me us one of my higher-power duplexers (I have both a Decibel Prods and a Kathrein that are good up to about 100W vice the low-power one that was onboard...), add an amp on the xmt side, or preselectors and AR or Chip's amp on the inbound side...). So...circuitry changes to the "SRTP Phone Patch/Control Board" (and this references the SRTP schematic on page 39 of the service manual) 1. I lifted ONE leg of R73, which feeds from pin 4 of jack P3 to the base of Q10, and is in the Carrier Detect signal path. 2. I lifted ONE leg of R74, which feeds from pin 5 of jack P3 to the base of Q12, and is in the PL/DPL Detect signal path. 3. I lifted ONE leg of R107, which feeds from the wiper of the repeat audio level pot to the xmt brick. 4. I lifted ONE leg of R106, which feeds from the wiper of the telco line audio level pot to the xmt brick (essentially a mixing circuit, the back sides of both these resistors are common and then feed to an isolation amp to the xmt brick. Those are the ONLY circuit changes I made on board. Remember, the less you change things, the fewer variables you have to work with. So...where to pick up the signals I wanted to use to interface to the URI. Well, the URI has AC coupling caps on the AC side, so, normal Moto practice is to have biasing on audio lines. So first thing is to use the AC coupled audio paths on both sides. Second, using a digital meter, with the radio properly programmed, and receiving a valid signal with the proper CTCSS code, I verified that the signal went in the right direction so I could configure the sense in asterisk properly. So...used a couple hunks of belden 8451 (1pr shielded) left over from a radio studio project, and divided up the two lines to receive and transmit paths. Tied the shields together at one end (the URI end, if it must be known...:)) and hooked up the leads as follows: 1. RX audio from a test point on the circuit board labeled "RX IN". Big test pad. Easy to find. Easier to get to. 2. COR signal, active low, from Pin 5 (PL/DPL Detect) on socket P3 at the rear left of the board (front towards you). 3. Transmit audio from the URI to the radio to pin 10 on socket P4 (labeled TX+ on schematic) at rear right of the board. 4. PTT (active Low) to pin 7 on socket P4 at rear right of the board. 5. Ground to the ground connector in the center of the rear edge of the board. Connection of the DB-25 is as normal for these signals, and is left as an exercise to figure out which ones (hint...Pin 1 is PTT, etc...) Configuration of the usbradio.conf file, that worked for me (remember, the radios themselves are doing the ctcss and pre/de-emphasis, so, don't need to do it in app_rpt); if there are things I don't need here...well..that's ok...it works, so, still fiddling with it... ;440 Repeater [usbxxxxx] hdwtype=0 rxboost=1 txboost=1 carrierfrom=usb ctcssfrom=no rxdemod=speaker txprelim=no txlibonly=no txmixa=voice txmixb=no invertptt=0 duplex=1 rxondelay=0 rxnoisefiltype=0 eeprom=0 Hooked it all up, URI is blinking...and ran radio-tune-menu while watching on my shack CE6 service monitor to set the levels. What worked for me, in my config, and yours may be different, is RX voice is set at 600 (1K @3kc deviation from the SM to give 3k indication on the screen display) TX voice is set at 300 (generating internal to the tune program 1K signal to show 3K deviation on the CE6) and that's it (rest of the options are not enabled due to the usbradio configuration). Remember, not depending on the software to do any of the processing, just routing plain audio around and seeing that the pin Modifications to rpt.conf are dependent on what you want it to do. But, it works just fine with most of the standard config I use on other repeaters on my hub. So...hope this helps someone somewhere along the line. Only change I'm thinking of adding in is putting in a switch to re-connect the lifted legs of the resistors back to their connection pads so I can disconnect this from the URI and throw in my car with the mobile duplexer and take it on the road. But for now...it is working (node 27710) at low power (about 2 mile radius, low antenna), and sounds pretty good. 73 all Bryan WB0YLE 27294 etc.

1 0

Simplex Node Help
by Robert Garcia 09 Jun '13

09 Jun '13

All, I am a new Allstarlink user and I am experimenting with a simplex node at the moment. Hardware: PC -> URIx -> GM300 I quickly ran through the usb audio tune menu the system will transmit while in the test menu. However, when I try to get the system to tell me the time or otherwise transmit under normal conditions, I get no output and the transmitter is not keyed. I have included this log snippet below. It demonstrates the reception and decoding of the DTMF digits and it appears to think it is transmitting a response, but nothing is heard and the transmitter is not keyed. Any suggestions? Thanks, Robert N5QM [Jun 9 10:24:26] NOTICE[2757]: chan_usbradio.c:3015 usbradio_read: Got DTMF char * duration 169 ms [Jun 9 10:24:27] NOTICE[2757]: chan_usbradio.c:3015 usbradio_read: Got DTMF char 8 duration 127 ms [Jun 9 10:24:27] NOTICE[2757]: chan_usbradio.c:3015 usbradio_read: Got DTMF char 1 duration 191 ms -- <Zap/pseudo-2190193> Playing 'rpt/goodmorning' (language 'en') -- <Zap/pseudo-2190193> Playing 'rpt/thetimeis' (language 'en') -- <Zap/pseudo-2190193> Playing 'digits/10' (language 'en') -- <Zap/pseudo-2190193> Playing 'digits/20' (language 'en') -- <Zap/pseudo-2190193> Playing 'digits/4' (language 'en') -- <Zap/pseudo-2190193> Playing 'digits/a-m' (language 'en') -- Hungup 'Zap/pseudo-2190193'

1 0