Timeline for Receiving without configuring CTCSS
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:59 | history | edited | CommunityBot |
replaced http://ham.stackexchange.com/ with https://ham.stackexchange.com/
|
|
| Sep 12, 2015 at 8:20 | history | edited | user | CC BY-SA 3.0 |
added 179 characters in body
|
| Sep 12, 2015 at 8:12 | history | edited | user | CC BY-SA 3.0 |
added 85 characters in body
|
| Sep 12, 2015 at 8:08 | comment | added | user | @Andrew As an aside, you are of course free to accept any answer you prefer (and I appreciate that you picked mine), this is why it's usually a good idea to wait a while before accepting an answer. Acceptance indicates to the community that you feel your question has been satisfactorily answered; this tends to reduce the chance of it receiving further answers. Particularly on low-traffic sites, it can be a good idea to wait up to a few days before accepting an answer. | |
| Sep 12, 2015 at 8:06 | history | edited | user | CC BY-SA 3.0 |
added 142 characters in body
|
| Sep 11, 2015 at 21:55 | comment | added | Andrew | A much better description and does help me re-affirm what I thought was going on with the concept of CTCSS. Thank you. | |
| Sep 11, 2015 at 21:52 | vote | accept | Andrew | ||
| Sep 11, 2015 at 19:44 | history | edited | user | CC BY-SA 3.0 |
added 87 characters in body
|
| Sep 11, 2015 at 16:36 | history | answered | user | CC BY-SA 3.0 |