Re: [App_rpt-users] RPi 3 controller problem (Steve Zingman)
I haven't figured out how to do replies when I only get the digest in gmail. Anyway, Steve, re this:
I don't THINK the receiver dropout and the EchoLink inbound are related. The problem COULD be radio_relax. (The DTMF decoder is falseing) Though I wonder about the duration of the dropout. How did you set receive levels?
Steve
I was monitoring the Asterisk console this morning during a QSO on the repeater and DID see a number of DTMF false messages. They were all just a matter of 10-100 milliseconds, but there did seem to be a disruption of the audio when they came along. I didn't tie the two together in my head because there didn't seem to be a one to one correlation, if you get my drift. I set the receive levels using radio-tune-menu. It was all done onsite at the repeater with MINIMAL equipment (an HT.) I have since done some tuning on it (especially the receive levels) from home during typical QSOs. Bill
Your replies are fine. Setting levels with a HT on usbradio might be a little iffy. Be that as it may here is the procedure to "tighten up" the DTMF decoder. 1: shut down asterisk 2: cd /usr/src/astsrc-1.4.23-pre/asterisk/ 3: edit line 10 of menuselect.makeopts 4: change MENUSELECT_CFLAGS=RADIO_RELAX LOADABLE_MODULES 5: to MENUSELECT_CFLAGS=LOADABLE_MODULES 6: save 7: make 8: get coffee 9: make install 10 restart asterisk Please let me know if this helps. 73, Steve N4IRS On 3/16/2017 2:40 PM, William Higgins wrote:
I haven't figured out how to do replies when I only get the digest in gmail.
Anyway, Steve, re this:
I don't THINK the receiver dropout and the EchoLink inbound are related. The problem COULD be radio_relax. (The DTMF decoder is falseing) Though I wonder about the duration of the dropout. How did you set receive levels?
Steve
I was monitoring the Asterisk console this morning during a QSO on the repeater and DID see a number of DTMF false messages. They were all just a matter of 10-100 milliseconds, but there did seem to be a disruption of the audio when they came along. I didn't tie the two together in my head because there didn't seem to be a one to one correlation, if you get my drift.
I set the receive levels using radio-tune-menu. It was all done onsite at the repeater with MINIMAL equipment (an HT.) I have since done some tuning on it (especially the receive levels) from home during typical QSOs.
Bill
_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.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.
Here's another suggestion I use all the time and I don't get any false dtmf's since doing this, this is an email sent by chuck Henderson, I do not do it the official way. I found the 2 official settings each had problems, Either too much falsing, or some TT pads would not decode. The official way changes a value in a config file that lets the compile choose between a value of 26 when relaxed and 42 when not relaxed. Default is relaxed. My method allows to fine tune and select the just right value somewhere between 26 and 42. 26 being too relaxed (voice falsing) and 42 being to strict (some TT pads will not work over the air on less than perfect signals. So that being said, I edit the main/dsp.c file and this is the line I edit. Without and with the change. #define DTMF_TO_TOTAL_ENERGY ((digitmode & DSP_DIGITMODE_RELAXDTMF) ? 26.0 : 42.0) /* before change */ #define DTMF_TO_TOTAL_ENERGY ((digitmode & DSP_DIGITMODE_RELAXDTMF) ? 38.0 : 42.0) /* CAH after I changed 26 to 38 */ To find it just search main/dsp.c for RELAXDTMF Then when you find the line, change the 26 to a 38, leave the 42 as it is. then recompile You can fine tune the value by experimentation but the value that was the best compromise for me was 38. Add a comment as I did so that in a year or two when you can't remember what that change was to fix the TT problem, you can just grep for your initials in the source files and find the file and line that has the changes. You also have to remember to redo your edit every time that you upgrade the code. Chuck
participants (3)
-
Bryan Taylor -
Steve Zingman -
William Higgins