TwoToneDetect New TwoToneDetect in the works - Python based

[WebsterEMA]

Howdy. I've been using TTD for years now with no problems. Version 68. A couple months ago it started sending out pages for department A to both departments A and B. It's not every time, but it's fairly frequent. I've unzipped a fresh copy. I've checked the config files. I've changed radios. I've changed computers. I've taken Department B out of the config file, and run a copy of TTD on a second computer with JUST B. I've run a separate instance of TTD for each department. It's still sending out the page to the correct and the wrong department no matter what I do.

I've downloaded and setup the new version, 73g, and hope it works. But in case it doesn't, any advice on what might be causing this?

Edit: And it just did it again with 73g. This worked for years no problem. I really wish I could figure out why this is happening all of a sudden.

 

[jhsands]

Howdy. I've been using TTD for years now with no problems. Version 68. A couple months ago it started sending out pages for department A to both departments A and B. It's not every time, but it's fairly frequent. I've unzipped a fresh copy. I've checked the config files. I've changed radios. I've changed computers. I've taken Department B out of the config file, and run a copy of TTD on a second computer with JUST B. I've run a separate instance of TTD for each department. It's still sending out the page to the correct and the wrong department no matter what I do.

I've downloaded and setup the new version, 73g, and hope it works. But in case it doesn't, any advice on what might be causing this?

Edit: And it just did it again with 73g. This worked for years no problem. I really wish I could figure out why this is happening all of a sudden.

If you took B out of PC1 and left only A, it's impossible for it to send emails to B.

If you took A out of PC2 and left only B, it's impossible for it to send emails to A.

Make sure the config files saved properly.

Do you have the tones.cfg file before your last edit?

Some other things are that you have a wideband receiver and are getting some noise or dispatch changed paging equipment and it is leaking over. Try turning down your tone tolerance. Have you replaced the mic cord? Do any Windows updates?

 

[DC31]

Post one of your logfiles showing a dual alert.

 

[WebsterEMA]

PC1 had A. It sent the page to A. PC2 had B, and it sent the page to B. Despite the fact it was a page for A. It's acting like they're the same department. This has been going on since mid November, so I'm sure there have been Windows updates, but I can't say which ones. And as I've said, it's doing it across multiple PC's. The config files are all saved correctly at least as far as I can tell.

Dispatch is using the same radio system, but got new computers for their CAD, though they got them in July and as I said this only started in November. Not sure if they're involved with the paging part or not. Our receiver is a base station radio that we had our radio guy wire up with a standard aux cord. But as I said, we've tried a different radio with a different wire, and no good.

There was even one instance where department C triggered this issue.

Department A's tones are
Atone = 634.5
Btone = 707.3

Department B's tones are
Atone = 707.3
Btone = 634.5

Department C's tones are
Atone = 707.3
Btone = 410.8

So, I'm sure A and B being swapped, and C having the same A tone are related to the issue. But they've been that way the entire time. What would you think I should try and set the tone tolerance to?

 

[WebsterEMA]

Post one of your logfiles showing a dual alert.

I hope this is the right info you're wanting. I deleted the email addresses it was sending to for privacy's sake, and found what I hope was the relevant section. If not, please let me know.

 

[NotATechGuy]

PC1 had A. It sent the page to A. PC2 had B, and it sent the page to B. Despite the fact it was a page for A. It's acting like they're the same department. This has been going on since mid November, so I'm sure there have been Windows updates, but I can't say which ones. And as I've said, it's doing it across multiple PC's. The config files are all saved correctly at least as far as I can tell.

Dispatch is using the same radio system, but got new computers for their CAD, though they got them in July and as I said this only started in November. Not sure if they're involved with the paging part or not. Our receiver is a base station radio that we had our radio guy wire up with a standard aux cord. But as I said, we've tried a different radio with a different wire, and no good.

There was even one instance where department C triggered this issue.

Department A's tones are
Atone = 634.5
Btone = 707.3

Department B's tones are
Atone = 707.3
Btone = 634.5

Department C's tones are
Atone = 707.3
Btone = 410.8

So, I'm sure A and B being swapped, and C having the same A tone are related to the issue. But they've been that way the entire time. What would you think I should try and set the tone tolerance to?

Have you tried adjusting your trigger times for the A tone and/or B tone? Depending on the type of paging system your dispatch is using depends on the timings. For a typical QCII system the A tone should broadcast for 1 second and the B tone for 3 second.

I recommend increasing the trigger time of your B tone. Start low at something like 0.5 seconds and work your way up. You don't want to increase it too much because there is a chance TTD could miss the tone if it doesn't see the frequency long enough due to poor tone decoding.

 

[jhsands]

PC1 had A. It sent the page to A. PC2 had B, and it sent the page to B. Despite the fact it was a page for A. It's acting like they're the same department. This has been going on since mid November, so I'm sure there have been Windows updates, but I can't say which ones. And as I've said, it's doing it across multiple PC's. The config files are all saved correctly at least as far as I can tell.

Dispatch is using the same radio system, but got new computers for their CAD, though they got them in July and as I said this only started in November. Not sure if they're involved with the paging part or not. Our receiver is a base station radio that we had our radio guy wire up with a standard aux cord. But as I said, we've tried a different radio with a different wire, and no good.

There was even one instance where department C triggered this issue.

Department A's tones are
Atone = 634.5
Btone = 707.3

Department B's tones are
Atone = 707.3
Btone = 634.5

Department C's tones are
Atone = 707.3
Btone = 410.8

So, I'm sure A and B being swapped, and C having the same A tone are related to the issue. But they've been that way the entire time. What would you think I should try and set the tone tolerance to?

You realize dept A and dept B are just reversed A/B tones? If dispatch drops the tones twice in a row, you get both departments triggered.

 

[WebsterEMA]

You realize dept A and dept B are just reversed A/B tones? If dispatch drops the tones twice in a row, you get both departments triggered.

I realize that, but they don't drop the tones twice in a row. Dixon and only Dixon is paged, but it triggers Clay too.

 

[WebsterEMA]

Have you tried adjusting your trigger times for the A tone and/or B tone? Depending on the type of paging system your dispatch is using depends on the timings. For a typical QCII system the A tone should broadcast for 1 second and the B tone for 3 second.

I recommend increasing the trigger time of your B tone. Start low at something like 0.5 seconds and work your way up. You don't want to increase it too much because there is a chance TTD could miss the tone if it doesn't see the frequency long enough due to poor tone decoding.

It's currently set at .6 for both, the default. I can scale them both up a bit. I'll also pay attention and maybe try to record the tones next time they go off, to find out how long they go for.

 

[jhsands]

It's currently set at .6 for both, the default. I can scale them both up a bit. I'll also pay attention and maybe try to record the tones next time they go off, to find out how long they go for.

You can setup Audacity (free) with VOX recording and it will be substantially easier.

 

[WebsterEMA]

You can setup Audacity (free) with VOX recording and it will be substantially easier.

Have you tried adjusting your trigger times for the A tone and/or B tone? Depending on the type of paging system your dispatch is using depends on the timings. For a typical QCII system the A tone should broadcast for 1 second and the B tone for 3 second.

I recommend increasing the trigger time of your B tone. Start low at something like 0.5 seconds and work your way up. You don't want to increase it too much because there is a chance TTD could miss the tone if it doesn't see the frequency long enough due to poor tone decoding.

Thanks for Audacity recommendation. Hadn't even heard of it. But I downloaded it and found a copy of both tones and checked. Tone A is about 1 second. Tone 2 is about 3. So I left tone A at .6 and set tone B to 2.5 seconds. Since I wasn't sure how close I should get to the actual length. If I'm understanding things right, it just has to play at least that length right? So if it doesn't catch a bit of the tone, it'll still trigger with the slightly shorter tone lengths? I'm just guessing here though, so if I'm assuming wrong please let me know.

I appreciate the aid of everyone who's helped with this. I should've asked months ago, but I've been stuborning it out in the hopes I could fix things on my own.

 

[NotATechGuy]

Thanks for Audacity recommendation. Hadn't even heard of it. But I downloaded it and found a copy of both tones and checked. Tone A is about 1 second. Tone 2 is about 3. So I left tone A at .6 and set tone B to 2.5 seconds. Since I wasn't sure how close I should get to the actual length. If I'm understanding things right, it just has to play at least that length right? So if it doesn't catch a bit of the tone, it'll still trigger with the slightly shorter tone lengths? I'm just guessing here though, so if I'm assuming wrong please let me know.

I appreciate the aid of everyone who's helped with this. I should've asked months ago, but I've been stuborning it out in the hopes I could fix things on my own.

You don't want the tonelength set too long, the decoder isn't exact and it could lead it it not picking up the tone at all. Your interpretation is correct. The tone won't trigger until it sees the B tone frequency for X amount of seconds you set it for. In your case, you set btonelength = 2.5 the tone won't trigger until it sees your B tone frequency for 2.5 seconds.

My recommendation for you, since the A tone is only broadcast for a maximum of 1 second, your btonelength only needs to be greater than 1 second in order to not get a false positive. Setting your btonelength to ~1.2 should be sufficient. Trial and error at this point IMO.

 

[aaknitt]

I hope this is the right info you're wanting. I deleted the email addresses it was sending to for privacy's sake, and found what I hope was the relevant section. If not, please let me know.

Looking at your log file, it appears that your sound card is picking up noise at about 639 Hz when there is no radio traffic present. This is within the tolerance band of the 634 Hz tone so when the 707.3 Hz B tone is sent and then there is silence, the silence is detected as 639 Hz and triggers the other tone set. The solution may be as simple as increasing the Audio Squelch slider a bit on the main screen to prevent that low level 639 Hz noise from being detected. You want the main screen to say "No Audio" when there is no radio traffic and show the frequencies when there is radio traffic present.

Andy

 

[jhsands]

I appreciate the aid of everyone who's helped with this. I should've asked months ago, but I've been stuborning it out in the hopes I could fix things on my own.

This filter has fixed EVERY line noise problem I have had, which might aid is what @aaknitt has mentioned about the 639 Hz always present. I have several around the area. https://www.amazon.com/Mpow-Ground-Isolator-Stereo-System/dp/B019393MV2/


Also, you may be running a mono plug into a stereo female on your PC. That can be where your noise is coming from, a line short. Use this to eliminate that issue: https://www.amazon.com/Monoprice-107129-Stereo-Adaptor-Plated/dp/B005E2XZYC/

 

[DC31]

I think that Andy is onto it. Increase your squelch slider a little. Your 639 hz noise is at a very low level (<1000) and the 634 hz tone well above 1000 so you should be able to remove the noise. In addition, set all your btonelength parameters to 1.2 or 1.4 and leave the atonelengths at 0.6. This combination of tweaks I bet will fix it.

 

[WebsterEMA]

I just wanted to thank everyone again for their help. We've ordered the static isolating items jhsands recommended. We've also increased the tone lengths as discussed, and increased squelch a bit. So far no extra pages, though our departments don't get paged out often enough that's a guarantee things are fixed. I will update in a few weeks when I'm sure things are fixed.

That said, I've got another problem. The pages being sent now are being recorded very slowly. Like, at half rate or more. It's just an issue with the Two Tone recording though. I was running Audacity and recorded the audio feed at the same time through the same source, and it recorded just fine. So that must mean the soundcard is fine. Just something about the recording/encoding of the software is wrong? It was working fine, and I'm not sure what setting I could've hit to mess with this. I've included a zip with an MP3 of the page.

 

[jhsands]

I just wanted to thank everyone again for their help.

Sent you a PM.

 

[kb2ear]

Is there a hi pass filter in the software, We have several sets of tones in use here that are in the 2.5k to 3.1k range. And they never seem to be detected. See attached for example.

Thanks,
Scott

 

[jhsands]

Is there a hi pass filter in the software, We have several sets of tones in use here that are in the 2.5k to 3.1k range. And they never seem to be detected. See attached for example.

What type of receiver are you using? Speaker or filtered audio?

 

[mattnelson26]

I lost power and computer shut down, i now cant get any tones to send. i get the in log file
HANOVER Tone Set Found
Traceback (most recent call last):
File "TwoToneDetect70.py", line 543, in alert
File "site-packages\pyaudio.py", line 747, in open
IOError: [Errno Device unavailable] -9985

0
after record
delay timer HANOVER 10:12:01 on 02/15/21
Traceback (most recent call last):
File "TwoToneDetect70.py", line 675, in alert
UnboundLocalError: local variable 'recordstream' referenced before assignment

anyone help with this issue.

thanks,
matt