TwoToneDetect TTD with IAR Integration Random Issues

portroyalbirdy

Member
Premium Subscriber
Joined
Feb 17, 2010
Messages
252
Location
Central PA
Hello everyone!

As a heads up, this may be/ seem like a long winded post, and I apologize if so, but I want to make sure I "Cover all my Bases" to explain my issue(s).


Currently, I have TTD setup on my stations Windows 10 Lenovo Tower PC, connected to its "Line In" jack. The scanner/radio being used is a Uniden BC355N, (453.4125Mhz is our countywide dispatch frequency) connected to a Motorola UHF Quarter wave antenna outside of the building/station for better/clearer reception. When I first set this up, it worked flawlessly! Then, it seemed like when my county went to a new paging console a while back, it has random issues! (Note: I also program our Unication G1 Voice Pagers, so I know our tones, programming, etc.

The new console made all tones have a 100 ms Tone Gap, so I've added that, which seemed to help in some cases, adjusted the scanners volume and squelch, to make sure tones aren't being "washed out", and made sure there was no traffic while idle on/in TTD Debug, unplugged/re-plugged audio cable. I've done this multiple times, to see if one of this was the issue, and it still repeats!

The issue I'm having is, at random the tones won't "trip" our TTD! Example: Early this morning (12/24/22), we had a MVA we were mutual aid on, and it "caught" all 3 of the pages/dispatches just fine! Had another MVA this afternoon, and it didn't catch a thing! It doesn't matter if the tones are "stacked" or "hand picked", multiple or single tones at one time. This occurs on multiple tone sets of ours! One time our "Beale Alert" will activate 1 of 3, dispatches, next call it may get 2 out of the 3, next call all 3 are captured or it may miss our "Alert" tone all 3 times, but get our "Non-Emergency/Cancel" Tone. Or during a storm/bad weather, our county will hit our "Countywide" tone, and just like above, sometimes it will capture it, and sometimes miss it entirely!

I wanted to see if I could "Rack your brain" on the issue(s) to see what may be the problem, and hopefully a fix! All tones are A/B format.

Again, sorry for being long winded, and thank you in advance!
 

DC31

Member
Feed Provider
Joined
Feb 19, 2011
Messages
1,547
Location
Massachusetts
Can you post a screen shot of the debug screen showing a successful decode and another of a tone set that did not decode?

what version of TTD are you running?
 

portroyalbirdy

Member
Premium Subscriber
Joined
Feb 17, 2010
Messages
252
Location
Central PA
Can you post a screen shot of the debug screen showing a successful decode and another of a tone set that did not decode?

what version of TTD are you running?

I can try to post the debug next time we get a call. The PC I have it on is also the "Station Screen/Board" for the IAR webpage, so I will try and look/watch next time we have something!

Ironically enough, we had a call this AM (12/25/22) and it made a liar out of me, and capture the 2 initial pages for our engine, and the later single page for our tanker on a residential fire just fine!

Version I have on the PC is 73f
 

portroyalbirdy

Member
Premium Subscriber
Joined
Feb 17, 2010
Messages
252
Location
Central PA
The debug info is also saved in the logfiles folder in the TTD directory

Thank you!

I found the log file for the MVA it missed all together on 12/24/22 in the afternoon! I will post it below! Our mutual aid company's tone (Not shown 100% correct, but close) shows/went first, which is 1357.6/716.1 The actual tone for our mutual aid company.

My/our actual "Beale Alert" tone is 582.1/716.1, which looks like the close "580" and "715" in the data below.



1355.2682926829268 1758 1671902229.0203476
1355.2682926829268 1481 1671902229.2232647
1355.2682926829268 1515 1671902229.4043868
1355.2682926829268 1514 1671902229.5933306
1355.2682926829268 1496 1671902229.773627
1355.2682926829268 1438 1671902229.9629211
715.280487804878 1656 1671902230.152549
715.280487804878 1579 1671902230.3202984
715.280487804878 1596 1671902230.5211039
715.280487804878 1575 1671902230.6940284
715.280487804878 1584 1671902230.8869736
715.280487804878 1598 1671902231.0701878
715.280487804878 1577 1671902231.252473
715.280487804878 1556 1671902231.452143
715.280487804878 1601 1671902231.6204338
715.280487804878 1575 1671902231.8206813
715.280487804878 1547 1671902232.0030956
715.280487804878 1551 1671902232.1872926
715.280487804878 1585 1671902232.3708878
715.280487804878 1544 1671902232.554015
715.280487804878 1555 1671902232.753908
715.280487804878 1617 1671902232.9207144
715.280487804878 1698 1671902233.120658
247.390243902439 1131 1671902233.3039036
252.76829268292684 348 1671902233.4928198
247.390243902439 352 1671902233.6705837
252.76829268292684 338 1671902233.854075
247.390243902439 329 1671902234.0539367
247.390243902439 1837 1671902234.224885
580.829268292683 1421 1671902234.4207308
580.829268292683 1404 1671902234.6039028
580.829268292683 1417 1671902234.7931488
580.829268292683 1403 1671902234.983722
580.829268292683 1381 1671902235.1636834
247.390243902439 2052 1671902235.3537378
715.280487804878 1569 1671902235.5336459
715.280487804878 1616 1671902235.7206638
715.280487804878 1554 1671902235.9038525
715.280487804878 1555 1671902236.0874128
715.280487804878 1591 1671902236.2703905
715.280487804878 1570 1671902236.4539437
715.280487804878 1560 1671902236.6539114
715.280487804878 1567 1671902236.8210175
715.280487804878 1553 1671902237.020652
715.280487804878 1564 1671902237.2039278
715.280487804878 1533 1671902237.386886
715.280487804878 1564 1671902237.5830493
715.280487804878 1583 1671902237.7632914
715.280487804878 1575 1671902237.9535482
715.280487804878 1605 1671902238.1335156
715.280487804878 1939 1671902238.323384
 
Last edited:

DC31

Member
Feed Provider
Joined
Feb 19, 2011
Messages
1,547
Location
Massachusetts
Thank you!

I found the log file for the MVA it missed all together on 12/24/22 in the afternoon! I will post it below! Our mutual aid company's tone (Not shown 100% correct, but close) shows/went first, which is 1357.6/716.1 The actual tone for our mutual aid company.

My/our actual "Beale Alert" tone is 582.1/716.1, which looks like the close "580" and "715" in the data below.



1355.2682926829268 1758 1671902229.0203476
1355.2682926829268 1481 1671902229.2232647
1355.2682926829268 1515 1671902229.4043868
1355.2682926829268 1514 1671902229.5933306
1355.2682926829268 1496 1671902229.773627
1355.2682926829268 1438 1671902229.9629211
715.280487804878 1656 1671902230.152549
715.280487804878 1579 1671902230.3202984
715.280487804878 1596 1671902230.5211039
715.280487804878 1575 1671902230.6940284
715.280487804878 1584 1671902230.8869736
715.280487804878 1598 1671902231.0701878
715.280487804878 1577 1671902231.252473
715.280487804878 1556 1671902231.452143
715.280487804878 1601 1671902231.6204338
715.280487804878 1575 1671902231.8206813
715.280487804878 1547 1671902232.0030956
715.280487804878 1551 1671902232.1872926
715.280487804878 1585 1671902232.3708878
715.280487804878 1544 1671902232.554015
715.280487804878 1555 1671902232.753908
715.280487804878 1617 1671902232.9207144
715.280487804878 1698 1671902233.120658
247.390243902439 1131 1671902233.3039036
252.76829268292684 348 1671902233.4928198
247.390243902439 352 1671902233.6705837
252.76829268292684 338 1671902233.854075
247.390243902439 329 1671902234.0539367
247.390243902439 1837 1671902234.224885
580.829268292683 1421 1671902234.4207308
580.829268292683 1404 1671902234.6039028
580.829268292683 1417 1671902234.7931488
580.829268292683 1403 1671902234.983722
580.829268292683 1381 1671902235.1636834
247.390243902439 2052 1671902235.3537378
715.280487804878 1569 1671902235.5336459
715.280487804878 1616 1671902235.7206638
715.280487804878 1554 1671902235.9038525
715.280487804878 1555 1671902236.0874128
715.280487804878 1591 1671902236.2703905
715.280487804878 1570 1671902236.4539437
715.280487804878 1560 1671902236.6539114
715.280487804878 1567 1671902236.8210175
715.280487804878 1553 1671902237.020652
715.280487804878 1564 1671902237.2039278
715.280487804878 1533 1671902237.386886
715.280487804878 1564 1671902237.5830493
715.280487804878 1583 1671902237.7632914
715.280487804878 1575 1671902237.9535482
715.280487804878 1605 1671902238.1335156
715.280487804878 1939 1671902238.323384
Well, the 247.390243902439 2052 1671902235.3537378 sample between the Atone and Btone of the second set definitely killed that one. There are lots of 247/252 samples. Maybe you have some noise in your audio? Then the gap between tone sets isn’t silence so the gap length parameter doesn’t work. This might cause haphazard misses.
 

portroyalbirdy

Member
Premium Subscriber
Joined
Feb 17, 2010
Messages
252
Location
Central PA
Well, the 247.390243902439 2052 1671902235.3537378 sample between the Atone and Btone of the second set definitely killed that one. There are lots of 247/252 samples. Maybe you have some noise in your audio? Then the gap between tone sets isn’t silence so the gap length parameter doesn’t work. This might cause haphazard misses.

I saw this too! The only "sound" I can think of that could/would causing those numbers is the 250.3 PL Tone my county uses, which on any device, you can for sure hear its distinctive hum on every transmission, no matter what. I can see if I can pull an audio sample.
 

portroyalbirdy

Member
Premium Subscriber
Joined
Feb 17, 2010
Messages
252
Location
Central PA
Ironically enough, we had a call this AM (12/25/22) and it made a liar out of me, and capture the 2 initial pages for our engine, and the later single page for our tanker on a residential fire just fine!



I apologize for how long this log string is, but this shows the first of 3 successful alert(s) for our residential fire this AM on 12/25/22.

See Google Doc link below to view the string. Too Long for thread text.

(TTD Alert Successful 12/25/22)
 

DC31

Member
Feed Provider
Joined
Feb 19, 2011
Messages
1,547
Location
Massachusetts
A couple things to try:

1. move your audio squelch slider bar in TTD a little to the right. the second number in the sample lines is volume level. Most of the PL tone samples are 500-700 while most of the tone/voice samples are 2000-3000. Moving the slider may help to get rid of the samples in the low range.

2. see if you can somehow use a highpass or a notch filter on the audio coming in to TTD. Filter out the 247 hz tone. There is a forum member here @xicarusx who has some experience with this.

I see that you are an IaR subscriber. Have you contacted their Support about this issue?
 

portroyalbirdy

Member
Premium Subscriber
Joined
Feb 17, 2010
Messages
252
Location
Central PA
A couple things to try:

1. move your audio squelch slider bar in TTD a little to the right. the second number in the sample lines is volume level. Most of the PL tone samples are 500-700 while most of the tone/voice samples are 2000-3000. Moving the slider may help to get rid of the samples in the low range.

2. see if you can somehow use a highpass or a notch filter on the audio coming in to TTD. Filter out the 247 hz tone. There is a forum member here @xicarusx who has some experience with this.

I see that you are an IaR subscriber. Have you contacted their Support about this issue?


Thank you! I will try adjusting the slider some, I will also put in here, the screenshot of my current GUI settings, so you can see right where my slider is.

As far as reaching out to the IAR support team, I have not YET. I wanted to see if any others had this issue as well with any possible solutions, but I may in the next few days.



IARTTDGUI12.26.22.jpg
 

portroyalbirdy

Member
Premium Subscriber
Joined
Feb 17, 2010
Messages
252
Location
Central PA
12/29/22 Update:

After talking to IAR support via phone and email, and sending both successful and unsuccessful debug logs, the rep had me change the A/B tones to what TTD actually "hears" versus the actual tones given. I tested that awhile ago, and it worked! Going to keep an eye on it the next few days/calls!
 

Deziel0495

PE/NB Database Guy
Database Admin
Joined
Feb 11, 2008
Messages
908
Location
PEI
12/29/22 Update:

After talking to IAR support via phone and email, and sending both successful and unsuccessful debug logs, the rep had me change the A/B tones to what TTD actually "hears" versus the actual tones given. I tested that awhile ago, and it worked! Going to keep an eye on it the next few days/calls!

Interesting you mention that. 9 times out of 10 ours work great but it does miss one every once in awhile. I looked at my debug log and what should be 368.5/330.5 for A/B, TTD is actually hearing 365.7/328.06. Rather than changing the tones I just bumped up my tone tolerance to 3% [0.03].
 

DC31

Member
Feed Provider
Joined
Feb 19, 2011
Messages
1,547
Location
Massachusetts
Interesting you mention that. 9 times out of 10 ours work great but it does miss one every once in awhile. I looked at my debug log and what should be 368.5/330.5 for A/B, TTD is actually hearing 365.7/328.06. Rather than changing the tones I just bumped up my tone tolerance to 3% [0.03].
Low frequency tones are particularly troublesome because a percentage of a low number is a low number. One local FD uses a 290 hz tone. If I set the tolerance at 1%, it will decode only between 287-293. Compare to a 2800 hz tone that will decode in a range of 2772-2828. Yes, you will get most reliable decodes using the actual tones that you find in the debug files rather than the spec tones.
 

portroyalbirdy

Member
Premium Subscriber
Joined
Feb 17, 2010
Messages
252
Location
Central PA
Yeah, IAR Support had me change my Beale Alert tone from the given 582.1/716.1 to 580.8/715.2 and that worked when the had me do a tone/pager test yesterday, and it worked! Will be listening/watching over the next few days/calls to make sure all is well! Also have to find and adjust the other tone sets in our system, as we have 4 more tones that I need to fix yet!

Thanks to all in the thread for the help, and a big thanks to @DC31 for steering me in the right direction! The issue was really getting to me at times! Haha!
 

aaknitt

Member
Feed Provider
Joined
Aug 27, 2005
Messages
1,300
Another thing to tweak:
If the new paging consoles have a 100 ms gap in between tones, set the gap length parameter in TTD to 0.2 or 0.4. TTD samples audio in 200 ms increments, so setting the gap length to 100 ms may not do what you expect. It's better to have the gap length parameter set longer than the actual gap.

Andy
 

aaknitt

Member
Feed Provider
Joined
Aug 27, 2005
Messages
1,300
Well, the 247.390243902439 2052 1671902235.3537378 sample between the Atone and Btone of the second set definitely killed that one. There are lots of 247/252 samples. Maybe you have some noise in your audio? Then the gap between tone sets isn’t silence so the gap length parameter doesn’t work. This might cause haphazard misses.
Actually the gap length parameter should work for this scenario...it doesn't care what happens in the "gap", it basically should ignore whatever happens during that time. I think the issue is perhaps a gap length that's shorter than the chunk of audio that TTD is sampling (200 ms).
 
Top