new simplex node, can't connect in transceive mode
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.
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@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.
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@w7ldn.com Date: Sat, 10 Jan 2015 03:48:00 +0000 To: app_rpt-users@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@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@ohnosec.org http://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.
I was just chatting with a local repeater owner and he also felt like it was a level issue. Funny thing is, I just switched over to using simpleusb and it now works just fine. The DTMF no longer is a problem. I'm afraid I don't know enough about my radio and interface to know which audio settings are correct. It's a Yaesu radio with a data port on the back. That port is connected to a URI via a purchased cable. The volume control does not effect the output level (I would assume the setting for that would be "flat"). However, when I tried the two steps in the tuning instructions that say "skip this if not set to flat" both steps failed with errors. So I was a little lost. I finally settled on flat rx and pre-emphasized/limited tx. It seemed to work fine except for not interpreting the '3'. Thanks for your response Doug. On Fri Jan 09 2015 at 8:34:02 PM Doug Crompton <doug@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 DougWA3DSPhttp://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
------------------------------ From: w7ldn@w7ldn.com Date: Sat, 10 Jan 2015 03:48:00 +0000 To: app_rpt-users@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@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@ohnosec.org http://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.
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@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 <http://www.crompton.com/hamradio>
From: w7ldn@w7ldn.com <mailto:w7ldn@w7ldn.com> Date: Sat, 10 Jan 2015 03:48:00 +0000 To: app_rpt-users@ohnosec.org <mailto:app_rpt-users@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@w7ldn.com <mailto:w7ldn@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@ohnosec.org <mailto:App_rpt-users@ohnosec.org>http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://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 <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 list App_rpt-users@ohnosec.org <mailto:App_rpt-users@ohnosec.org> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://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 <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.
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@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@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 DougWA3DSPhttp://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
------------------------------ From: w7ldn@w7ldn.com Date: Sat, 10 Jan 2015 03:48:00 +0000 To: app_rpt-users@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@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@ohnosec.org http://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 list App_rpt-users@ohnosec.org http://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.
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@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@mac.com; doug@crompton.com CC: app_rpt-users@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@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@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@w7ldn.com Date: Sat, 10 Jan 2015 03:48:00 +0000 To: app_rpt-users@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@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@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@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.
Yes, switching to simpleusb seemed to fix the problem of not being able to interpret a DTMF key of "3". But I'd kinda like to figure out how to use the normal usbradio.conf rather than the simpleusb. I cannot for the life of me figure out how to get it to interpret a '3'. I tried all sorts of various level settings. I did try a different radio to send the DTMF with, it had the same issue. Could not get a '3' to register. Also, according to my instructions I did set the carrierfrom=usb and ctcssfrom=no. On Sat Jan 10 2015 at 5:11:10 PM Doug Crompton <doug@crompton.com> wrote:
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 DougWA3DSPhttp://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
------------------------------ From: w7ldn@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@mac.com; doug@crompton.com CC: app_rpt-users@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@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@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 DougWA3DSPhttp://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
------------------------------ From: w7ldn@w7ldn.com Date: Sat, 10 Jan 2015 03:48:00 +0000 To: app_rpt-users@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@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@ohnosec.org http://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 list App_rpt-users@ohnosec.org http://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.
Elden, As a newcomer I would suggest just using simpleusb. In most cases there is no real advantage to using usbradio and in many it actually degrades the audio. So don't feel like you are missing out on something, enjoy your new node. Many use simpleusb and it works perfectly fine. If you were using the BBB I would only suggest simpleusb. 73 Doug WA3DSP http://www.crompton.com/hamradio From: w7ldn@w7ldn.com Date: Sun, 11 Jan 2015 01:59:19 +0000 Subject: Re: [App_rpt-users] new simplex node, can't connect in transceive mode To: doug@crompton.com CC: app_rpt-users@ohnosec.org Yes, switching to simpleusb seemed to fix the problem of not being able to interpret a DTMF key of "3". But I'd kinda like to figure out how to use the normal usbradio.conf rather than the simpleusb. I cannot for the life of me figure out how to get it to interpret a '3'. I tried all sorts of various level settings. I did try a different radio to send the DTMF with, it had the same issue. Could not get a '3' to register. Also, according to my instructions I did set the carrierfrom=usb and ctcssfrom=no. On Sat Jan 10 2015 at 5:11:10 PM Doug Crompton <doug@crompton.com> wrote: 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@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@mac.com; doug@crompton.com CC: app_rpt-users@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@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@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@w7ldn.com Date: Sat, 10 Jan 2015 03:48:00 +0000 To: app_rpt-users@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@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@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@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.
Thank you Doug! Then I will be happy with simpleusb and call it good. On Sat Jan 10 2015 at 6:48:20 PM Doug Crompton <doug@crompton.com> wrote:
Elden,
As a newcomer I would suggest just using simpleusb. In most cases there is no real advantage to using usbradio and in many it actually degrades the audio. So don't feel like you are missing out on something, enjoy your new node. Many use simpleusb and it works perfectly fine. If you were using the BBB I would only suggest simpleusb.
*73 DougWA3DSPhttp://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
------------------------------ From: w7ldn@w7ldn.com Date: Sun, 11 Jan 2015 01:59:19 +0000
Subject: Re: [App_rpt-users] new simplex node, can't connect in transceive mode To: doug@crompton.com CC: app_rpt-users@ohnosec.org
Yes, switching to simpleusb seemed to fix the problem of not being able to interpret a DTMF key of "3". But I'd kinda like to figure out how to use the normal usbradio.conf rather than the simpleusb. I cannot for the life of me figure out how to get it to interpret a '3'. I tried all sorts of various level settings. I did try a different radio to send the DTMF with, it had the same issue. Could not get a '3' to register.
Also, according to my instructions I did set the carrierfrom=usb and ctcssfrom=no.
On Sat Jan 10 2015 at 5:11:10 PM Doug Crompton <doug@crompton.com> wrote:
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 DougWA3DSPhttp://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
------------------------------ From: w7ldn@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@mac.com; doug@crompton.com CC: app_rpt-users@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@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@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 DougWA3DSPhttp://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
------------------------------ From: w7ldn@w7ldn.com Date: Sat, 10 Jan 2015 03:48:00 +0000 To: app_rpt-users@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@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@ohnosec.org http://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 list App_rpt-users@ohnosec.org http://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.
Actually simpleUSB does have CTCSS filtering. It even has deemphasis. Surprised the heck out of me when I learned it. [usbXXXX] ... plfilter=yes deemphasis=yes -- Tim :wq
On Jan 10, 2015, at 5:10 PM, Doug Crompton <doug@crompton.com> wrote:
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 <http://www.crompton.com/hamradio>
From: w7ldn@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@mac.com; doug@crompton.com CC: app_rpt-users@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@mac.com <mailto:tim.sawyer@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@crompton.com <mailto:doug@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 <http://www.crompton.com/hamradio>
From: w7ldn@w7ldn.com <mailto:w7ldn@w7ldn.com> Date: Sat, 10 Jan 2015 03:48:00 +0000 To: app_rpt-users@ohnosec.org <mailto:app_rpt-users@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@w7ldn.com <mailto:w7ldn@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@ohnosec.org <mailto:App_rpt-users@ohnosec.org>http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://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 <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 list App_rpt-users@ohnosec.org <mailto:App_rpt-users@ohnosec.org> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users <http://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 <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 list App_rpt-users@ohnosec.org http://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.
Thanks Tim. I will add the plfilter. BTW, like your sig. VIM FTW. On Sat Jan 10 2015 at 7:08:59 PM Tim Sawyer <tim.sawyer@mac.com> wrote:
Actually simpleUSB does have CTCSS filtering. It even has deemphasis. Surprised the heck out of me when I learned it.
[usbXXXX] ... plfilter=yes deemphasis=yes
-- Tim :wq
On Jan 10, 2015, at 5:10 PM, Doug Crompton <doug@crompton.com> wrote:
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 DougWA3DSPhttp://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
------------------------------ From: w7ldn@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@mac.com; doug@crompton.com CC: app_rpt-users@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@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@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 DougWA3DSPhttp://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
------------------------------ From: w7ldn@w7ldn.com Date: Sat, 10 Jan 2015 03:48:00 +0000 To: app_rpt-users@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@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@ohnosec.org http://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 list App_rpt-users@ohnosec.org http://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 list App_rpt-users@ohnosec.org http://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.
participants (3)
-
Doug Crompton -
Elden Fenison -
Tim Sawyer