CDTbolt10033
Member
No, I didn't do that.
TwoToneDetect New TwoToneDetect in the works - Python based
- Thread starter aaknitt
- Start date
-
- Tags
- twotonedetect
Ok thanks... I can't recall if I tried the password as is or not, I'll give that a twirl.
Ok.... got it working now!
For anyone else looking to set this up... I did as posted above. Turned on 2FA, generated an app password. Cut/Paste that password into the TTD Settings Editor. Bingo, worked.
Previously I was pasting the password right into the config.txt file after Base64 encoding it. Clearly this isn't the way to go! Thanks for the tips CDTbolt10033!
For anyone else looking to set this up... I did as posted above. Turned on 2FA, generated an app password. Cut/Paste that password into the TTD Settings Editor. Bingo, worked.
Previously I was pasting the password right into the config.txt file after Base64 encoding it. Clearly this isn't the way to go! Thanks for the tips CDTbolt10033!
smokeater474
Member
I have done this and still not working. What did you choose under select app? I chose other and generate and it gave me a 16 digit string of letters that I copy/paste into TTD.
smokeater474
Member
This is what is showing in the log:
SMTPServerDisconnected: Connection unexpectedly closed: timed out
Email not sent via smtp.gmail.com on port 465 using STARTTLS
CDTbolt10033
Member
Try port 587 that's what I have it set to.
smokeater474
Member
Ok thx, changed it. Now we wait.
smokeater474
Member
Well it finally worked! Thx for the info
CDTbolt10033
Member
No problem!
Worked for meas well. Thanks.
Im having the same gmail issues described here. tried the app password raw and encoded. My system is running on version 67 that has been running for years on a raspberry a. Looks like i need to upgrade to latest version. Is there a command line solution for this? Will the raspberry a handle the newer software or should i use a different email service? Any help would be highly appreciated.
So i am going to answer my own question here. On the older versions of TTD (mine was 67) you can still use gmail with app passwords. The only difference from above is the 16 digit password needs to encoded with base64encode. Use copy and paste dont try to type it in like me and get it wrong.
MikeOrlando02
Member
- Joined
- Oct 8, 2015
- Messages
- 97
Missed Pages
Any idea why the first set of tones were a missed detection, but the second identical set were detected? Actual tones are at 422.0/399.8 with a 2% tolerance.
Any idea why the first set of tones were a missed detection, but the second identical set were detected? Actual tones are at 422.0/399.8 with a 2% tolerance.
Code:
Missed page 7/2 0856
419.4878048780488 14732 1656770191.8364851
419.4878048780488 15224 1656770192.026597
419.4878048780488 14661 1656770192.2064476
419.4878048780488 15063 1656770192.3968883
419.4878048780488 14640 1656770192.587134
419.4878048780488 14759 1656770192.766709
397.9756097560976 14103 1656770192.957144
397.9756097560976 13999 1656770193.136722
397.9756097560976 13980 1656770193.3267977
397.9756097560976 14354 1656770193.5069826
397.9756097560976 13877 1656770193.6962798
397.9756097560976 13966 1656770193.8859634
397.9756097560976 14274 1656770194.0662282
397.9756097560976 13859 1656770194.2568226
397.9756097560976 14265 1656770194.436014
397.9756097560976 13776 1656770194.626457
397.9756097560976 13865 1656770194.8069973
397.9756097560976 14337 1656770194.996538
397.9756097560976 13814 1656770195.1862087
397.9756097560976 14292 1656770195.367146
397.9756097560976 14357 1656770195.5570107
397.9756097560976 22171 1656770195.7368524
Code:
419.4878048780488 17175 1656793502.9560063
419.4878048780488 15172 1656793503.1410685
419.4878048780488 15136 1656793503.3253798
419.4878048780488 15477 1656793503.519708
419.4878048780488 15220 1656793503.704017
419.4878048780488 15557 1656793503.889028
397.9756097560976 14557 1656793504.0735924
397.9756097560976 14581 1656793504.2585323
397.9756097560976 14819 1656793504.4432893
397.9756097560976 13997 1656793504.62765
397.9756097560976 14208 1656793504.8220284
397.9756097560976 14317 1656793504.9911177
397.9756097560976 14830 1656793505.1919127
397.9756097560976 14245 1656793505.376767
397.9756097560976 14277 1656793505.5614293
397.9756097560976 14182 1656793505.7454157
397.9756097560976 14014 1656793505.9304159
397.9756097560976 14575 1656793506.1244678
397.9756097560976 14038 1656793506.3096309
397.9756097560976 13844 1656793506.493936
397.9756097560976 14427 1656793506.678662
Silver Cliff Rescue Tone Set Found
starting new alert at 1656793506.694287
[[['Tone10', 'Silver Cliff Rescue', 1656793506.678662, 0]]]
delay timer Silver Cliff Rescue 15:25:06 on 07/02/22
dmason04
I support our police.
I posted about integrating a feature like this into SDRTrunk on the Discord last week. I'll be sure to pass this along to them!
Perhaps the radio transmission broke up just a little on the first one causing it to miss one sample.
it appears that you have your btone length set to 3. This requires that it hear fifteen 200 ms samples to decode. A hiccup in there can cause it to miss. I use 0.6 for both tone lengths. Then it only needs to hear 3 samples of the Atone followed by 3 samples of the Btone. Your tones look solid enough so I doubt you would have falses with the shorter lengths.
MikeOrlando02
Member
- Joined
- Oct 8, 2015
- Messages
- 97
Do you set a tone gap then? If the A tone is longer than expected (0.6 vs 1) how does it not fail with the B-tone not immediately following?
The last three samples of the Atone are folllowed immediately by the first three samples of the Btone resulting in a successful decode.
i am not really sure how the gap parameter works. It is designed to handle a gap between the Atone and the Btone. Whether it will handle a gap within the Btone string, I don’t know
i am not really sure how the gap parameter works. It is designed to handle a gap between the Atone and the Btone. Whether it will handle a gap within the Btone string, I don’t know
Anyone all of a sudden having issues with TTD 73M not sending emails to mms addresses? Using the version from IAR meant for Non-IAR receivers. Don't know if this means anything but I'm getting this message on some returned emails:
Yet when I input a straight email address it goes through. Sometimes the message does go through but many hours later.
Any ideas?
Joe
| Delivery incomplete |
| There was a temporary problem delivering your message to xxxxxxxxxx@vzwpix.com. Gmail will retry for 27 more hours. You'll be notified if the delivery fails permanently. |
The response from the remote server was: 421 4.1.0 <pfddispatch1@gmail.com> server temporarily unavailable AUP#MXRT |
Yet when I input a straight email address it goes through. Sometimes the message does go through but many hours later.
Any ideas?
Joe
CDTbolt10033
Member
Is TTD 73M a new version from 73L?
I too have had users (Verizon only) reporting delayed messages within the past two weeks. Reporting they are about 24hrs after the tones. We too are sending from a Gmail address.
A reference on Verizon support site seems as if Verizon might be blocking Gmail address from sending to Verizon numbers due to spamming.Verizon Forum link. See the last comment on that thread. Seems the recommendation is moving away from Gmail address to send.
A reference on Verizon support site seems as if Verizon might be blocking Gmail address from sending to Verizon numbers due to spamming.Verizon Forum link. See the last comment on that thread. Seems the recommendation is moving away from Gmail address to send.
Similar threads
