TwoToneDetect New TwoToneDetect in the works - Python based
- Thread starter aaknitt
- Start date
-
- Tags
- twotonedetect
My guess is that the level (loudness) of the tone may have also changed when they changed the tone duration. High tone frequencies like 2804 are especially prone to this. Check to make sure your Audio Squelch (slider on the main screen) is set low enough to let the A tone through.
Andy
firemedicmcse
Member
Andy
I just put v69a on my RPi3 tonight. I left v68 on there just in case I ran into issues with v69. The issue I am having is v69a is reading my config and tones files from the TwoToneDetect68 folder instead of the TwoToneDetect69 folder. Do I need to just delete the TwoToneDetect68 folder to get v69 to read from the TwoToneDetect69 folder?
RPi3 running Ubuntu Mate
Thanks
Michael
I just put v69a on my RPi3 tonight. I left v68 on there just in case I ran into issues with v69. The issue I am having is v69a is reading my config and tones files from the TwoToneDetect68 folder instead of the TwoToneDetect69 folder. Do I need to just delete the TwoToneDetect68 folder to get v69 to read from the TwoToneDetect69 folder?
RPi3 running Ubuntu Mate
Thanks
Michael
No, you shouldn't have to delete anything. It should look for config.cfg and tones.cfg in the same directory as the program itself (unless you're using a remote.cfg file to read in tone file from a remote location).
Andy
firemedicmcse
Member
Strange. I went ahead and deleted the v68 directory just for grins, and when I tried to start v69 it griped at me about not being able to find the v68 directory. Also, when I restart my RPi3 v69 will not automatically load like v68 would. Any ideas?
One more question, is it possible to run 3 instances of TTD on a Windows 10 PC with 3 seperate USB sound cards? If so, how would one go about that?
Thank you for EVERYTHING you have done with this project! It is AMAZING!
Michael
I've been having a problem with the program hanging. It's been happening back to v65 I think but for sure with v68_testbuild2 and v69a. Nothing showing in the logs and it doesn't actually quit so the Keep Running program won't help. The only indication I get is that the Audio Input Level bar pegs at max and no more pages are received. It may happen 2 days or may happen after 10 days, there's no discernible pattern. Up until now I just close it and restart. I'd like to see if anyone has any idea what could be the cause and solution. I'm using Win 10 Pro 64 bit desktop with the internal sound card as input. Not sure how to troubleshoot with nothing relevant in the log?
If the solution isn't found easily, does anyone have a way to have the program restart on a regular basis? I'm thinking of using task scheduler with a script to close the program and re-open it moments later. If this is done at 3am the chances of missing a page is pretty low, and it's much better than missing 12 hours or a day when the program stops receiving and I'm not paying attention. Anyone have an idea how to implement?
Many thanks in advance.
Pete
If the solution isn't found easily, does anyone have a way to have the program restart on a regular basis? I'm thinking of using task scheduler with a script to close the program and re-open it moments later. If this is done at 3am the chances of missing a page is pretty low, and it's much better than missing 12 hours or a day when the program stops receiving and I'm not paying attention. Anyone have an idea how to implement?
Many thanks in advance.
Pete
I recommend using Task Scheduler to restart the whole PC nightly, not just TwoToneDetect. Then put a shortcut to TwoToneDetect in your Startup folder so it will start automatically on reboot.
Andy
Westernbound
Member
Try putting the info below into notepad and save it as a .bat file. Test it and see if it works for you. If it does, then set a scheduled task for 3am and run the batch file. Remember to put your file path for the folder that contains TTD v69a between the quotes - marvin
:: This will Kill TTD v69a
taskkill /F /IM TwoToneDetect69a.exe
:: This will wait for 30 seconds, change the number if you want more or less
TIMEOUT /T 30
:: This will restart TTD v69a, you must put your file path for the folder that contains TTD between the quotes
START /d "C:\TwoToneDetect69a" TwoToneDetect69a.exe
Thanks. Tested and working great. I think this should hold me over until I can figure out what's causing the problem.
steve0622
Member
In reference to my issue with TTD not detecting 1 tone set...i followed advise on here and set A tone to the same as B Tone and did not have a positive result. I then adjusted the volume on the scanner from 4 to 8 and the tone set worked. I then changed the A tone to 2804 as original and the tone set failed. So, the resolution for my issue was to increase the volume on the scanner itself AND set the A tone to the same as B Tone.
TTD on Raspberry Pi from RTL SDR dongle ?
Re: TTD on raspberry pi - does anyone know how to do it from an RTL SDR dongle rather than a USB sound card? I tried searching this thread but came up with nothing.
rtl_fm is outputting the audio to stdio/pipe/buffer, so I imagine there are 2 main ways to go about this:
(a) get TTD to read from that buffer, rather than from ALSA. Is this possible?
(b) create a virtual ALSA input from that pipe, and have TTD use that virtual input.
It looks like some combination of jack/PulseAudio/Gstreamer can do this, but haven't quite figured out the details yet. Capturing few bits of my own research thus far:
- Virtual ALSA input from a PulseAudio stream: https://wiki.archlinux.org/index.ph...ulseAudio_sources.2C_sinks_and_mixers_to_ALSA
- maybe padsp is what I want, based on https://www.raspberrypi.org/forums/viewtopic.php?f=66&t=120369
Re: TTD on raspberry pi - does anyone know how to do it from an RTL SDR dongle rather than a USB sound card? I tried searching this thread but came up with nothing.
rtl_fm is outputting the audio to stdio/pipe/buffer, so I imagine there are 2 main ways to go about this:
(a) get TTD to read from that buffer, rather than from ALSA. Is this possible?
(b) create a virtual ALSA input from that pipe, and have TTD use that virtual input.
It looks like some combination of jack/PulseAudio/Gstreamer can do this, but haven't quite figured out the details yet. Capturing few bits of my own research thus far:
- Virtual ALSA input from a PulseAudio stream: https://wiki.archlinux.org/index.ph...ulseAudio_sources.2C_sinks_and_mixers_to_ALSA
- maybe padsp is what I want, based on https://www.raspberrypi.org/forums/viewtopic.php?f=66&t=120369
Hi Andy
I am using V69a that I downloaded on 1/29. If I am following the thread correctly, is there a newer or updated version that is still V69a? I have the emails going out sequentially and most are not receiving their texts. I just switched to only Verizon going out separately and I will see how that works. Anybody else having the same issues? Did the update, if there is one, take care of any email issues? Thanks.
Joe
I am using V69a that I downloaded on 1/29. If I am following the thread correctly, is there a newer or updated version that is still V69a? I have the emails going out sequentially and most are not receiving their texts. I just switched to only Verizon going out separately and I will see how that works. Anybody else having the same issues? Did the update, if there is one, take care of any email issues? Thanks.
Joe
I started working on a version of TTD to do (a). I got close to having it working but it's been several weeks since I've been able to devote any time to it. One of the problems I was running into was that the squelch feature of rtl_fm seems to work very poorly, and to get consistent audio out of it I had to disable squelch completely. That breaks any of the features of TTD that use the audio_squelch setting (like VOX-based recording), so it would be limited to fixed-time recording.
Andy
can we do this easily.
a) primary TTD software detects the tone and sends the emails,
b) if primary can not connect to the email server, the secondary TTD copy will send the email.
it would seem like we just setup the FTP access, if primary can not connect to the FTP server, secondary should pick up the email sending right?
a) primary TTD software detects the tone and sends the emails,
b) if primary can not connect to the email server, the secondary TTD copy will send the email.
it would seem like we just setup the FTP access, if primary can not connect to the FTP server, secondary should pick up the email sending right?
Yes, that's what the redundancy feature of TTD does. If the primary can't access the FTP server to confirm that it sent the emails, then the secondary will attempt to send after a delay period. Note that the secondary will also attempt to send if it can't access the FTP server to get confirmation that the primary sent, but in most cases the root cause of problems is an internet connection issue which takes down both FTP and email server access. So it's not entirely foolproof, but it works pretty well for most typical failure scenarios.
Andy
maybe the wrong place to ask, using TTD (i dont think its a two tone issue) but is anyone else no longer able to send messages to ##########@vzwpix.com i get "421 vzw-ibgw-5003a.stratus.cloudmark.com cmsmtp ESMTP server temporarily not available" from my mail server.
putterizer
Member
Verizon is working fine for me.
TTD not sending emails.
I recently set up the new 69a version and it was working great till over the weekend in which it stopped sending out emails for 1 set of tones. I have 9 sets of tones for different departments set up and only 1 of them is have this problem. It is the biggest set with 30 plus emails in it. Systems receives the tones but never sends MP3 file out. Looking for help.
I recently set up the new 69a version and it was working great till over the weekend in which it stopped sending out emails for 1 set of tones. I have 9 sets of tones for different departments set up and only 1 of them is have this problem. It is the biggest set with 30 plus emails in it. Systems receives the tones but never sends MP3 file out. Looking for help.
If eight of nine are working, you system is likely not get good tone samples on No. 9. Go through the recent .txt file in your logfiles folder and see if you can find their tones in the freq column. All it will take is one sample out of spec and you won't decode.
You may also need to increase your tone tolerance setting a little or perhaps a little more volume from the radio would fix it.
Last edited:
