[App_rpt-users] new simplex node, can't connect in transceive mode

Sun Jan 11 01:10:57 UTC 2015

Elden,

 I thought you said you were using simpleusb. If so ctcss is not done in software. It is done in the radio and the cos or squelch line out of the radio will follow the ctcss that the radio receives. There are two input bits in simpleusb - carrierfrom  and ctcssfrom. They both are just bits you read to determine there is a received signal. It does not matter which one you use but we generally use the carrierfrom which corresponds to pin 8 on the DMK URI. Pin 8 would be connected to the radio COS detect. 

So if you are using the DMK URI you connect pin 8 to the radio cos detect - made true by PL into the radio - and then you set the carrierfrom=   either  usb      or usbinvert     depending on the direction the incoming signal goes in when the rx gets carrier.  If it goes low then usbinvert and if it goes high then usb.

The ctcssfrom would be set to no meaning it is ignored. 
73 Doug
WA3DSP
http://www.crompton.com/hamradio

From: w7ldn at w7ldn.com
Date: Sun, 11 Jan 2015 00:36:29 +0000
Subject: Re: [App_rpt-users] new simplex node, can't connect in transceive mode
To: tim.sawyer at mac.com; doug at crompton.com
CC: app_rpt-users at ohnosec.org

I'm afraid I don't know how to control the CTCSS filtering. I thought CTCSS controlled the interaction between radios. I totally don't get all the references to it in the config files or why asterisk has anything to do with that. But there is obviously a lot I don't know.

On Sat Jan 10 2015 at 7:02:24 AM Tim Sawyer <tim.sawyer at mac.com> wrote:
I would add one thing to what Doug said. Make sure you have CTCSS filtering. PL really messes with TT decoding. 

--Tim WD6AWP

On Jan 9, 2015, at 8:33 PM, Doug Crompton <doug at crompton.com> wrote:
Elden,

Before you do anything make sure the rig you are transmitting the DTMF from is doing it correctly and the TX levels are good. Substitute another rig if you can.

 This is almost always caused by equalization or level problems. 

First of all make sure your levels are correct. If they are then:

Allstar can use either flat (non pre/deemphasized) or pre/deemphasized audio. Depending on what radio you are using and how you have it connected would determine how to set this in the configuration file. If you are using simpleusb take the audio from the pre/deemphasized points. This can get a little complicated for a beginner so if you need more explanation let me know.

The bottom line is if you are pre/deemphasizing in the radio then you don't want to do it again in the SW.

73 Doug
WA3DSP
http://www.crompton.com/hamradio

From: w7ldn at w7ldn.com
Date: Sat, 10 Jan 2015 03:48:00 +0000
To: app_rpt-users at ohnosec.org
Subject: Re: [App_rpt-users] new simplex node,	can't connect in transceive mode

Found a clue on this...
It appears that asterisk is not able to properly interpret a '3' DTMF tone in my particular setup. Below is part of my log, where I keyed 123456789 123 123. You will see that there are no threes. Wonder what is up with that?[Jan  9 19:32:23] NOTICE[25376] chan_usbradio.c: Got DTMF char 1 duration 319 ms[Jan  9 19:32:24] NOTICE[25376] chan_usbradio.c: Got DTMF char 2 duration 320 ms[Jan  9 19:32:26] NOTICE[25376] chan_usbradio.c: Got DTMF char 4 duration 278 ms[Jan  9 19:32:26] NOTICE[25376] chan_usbradio.c: Got DTMF char 5 duration 276 ms[Jan  9 19:32:27] NOTICE[25376] chan_usbradio.c: Got DTMF char 6 duration 235 ms[Jan  9 19:32:28] NOTICE[25376] chan_usbradio.c: Got DTMF char 7 duration 277 ms[Jan  9 19:32:29] NOTICE[25376] chan_usbradio.c: Got DTMF char 8 duration 256 ms[Jan  9 19:32:30] NOTICE[25376] chan_usbradio.c: Got DTMF char 9 duration 256 ms[Jan  9 19:32:44] NOTICE[25376] chan_usbradio.c: Got DTMF char 1 duration 213 ms[Jan  9 19:32:44] NOTICE[25376] chan_usbradio.c: Got DTMF char 2 duration 213 ms[Jan  9 19:32:46] NOTICE[25376] chan_usbradio.c: Got DTMF char 1 duration 276 ms[Jan  9 19:32:46] NOTICE[25376] chan_usbradio.c: Got DTMF char 2 duration 255 ms
On Fri Jan 09 2015 at 8:10:52 AM Elden Fenison <w7ldn at w7ldn.com> wrote:
Greetings,
I just setup a new simplex node (first time). I'm using the URI and a cable that I bought that should work with my Yaesu FT-7900. I did the radio tuning. I don't have a service monitor, so I did the best I could.
The problem I'm having is... I can make outbound connections to systems in monitor mode, but I seem to be unable to connect in transceive mode. When I try to connect in monitor mode, I get instant feedback saying I'm connected. When I try to connect in transceive mode, I get nothing at all.
_______________________________________________ App_rpt-users mailing list App_rpt-users at ohnosec.orghttp://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem._______________________________________________App_rpt-users mailing listApp_rpt-users at ohnosec.orghttp://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-usersTo unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.  		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20150110/150e75af/attachment.html>