Discussion in 'Amateur Radio News' started by NN2X, Aug 12, 2018.
KA1BSZ VT USA?
Thanks. Funny you should mention that. 14.068 was my first choice until a bunch of CW ops found me
Yes, you could send all of these.
OR UP FURTHER...14.105.00?
Got to get mu laptop lenovo 110s with windows 10 serviced and have your new program installed. Just will wait for the release date.
I've tried other 'ragchew digital modes' in the past and have always had difficulty finding any activity on the bands. The fact that an hour after getting setup I had already made contact with others is a testament that FT8Call has use.
I still like to experiment with the modes FLDigi offers but tuning around, trying to 'get lucky' and find someone that I can hear who can also hear me is a pain.
FT8, while I love it, get's a little too mundane and automated. For the anti-social crowd like myself, who doesn't like to use voice modes very often, it's a fun way to rack up rows in the logbook and collect awards.
FT8Call is nice for a short, casual chat/contact. Example below:
13:08:41 - (1211) - N1AAE: CQCQCQ EM78
13:09:29 - (1212) - WA2DE: N1AAE SNR -15 ⌁
13:09:37 - (1212) - N1AAE: WA2DE SNR -01
13:11:27 - (1212) - N1AAE: WA2DE SNR -01
13:13:04 - (1397) - N1AAE: WA2DE QSL?
13:14:59 - (1397) - WA2DE: N1AAE GM NAME WAYDE IN BROOKLYN NY BTU ⌁
13:16:05 - (1390) - GM WAYDE NAME IS CURTIS IN MADISON IN. GOOD SIG 2 EM78 BTU
13:18:29 - (1397) - WA2DE: N1AAE CURTIS USING IC-7300 INTO HOME MADE DIPOLE ABT 6FT ABOVE 2 STORY ROOF BTU ⌁
13:21:18 - (1390) - FT-450 W/ G5RV HUNG LOW HERE W/ 20W OUT. BTU
13:23:44 - (1398) - WA2DE: N1AAE FB NICE TO MEET YOU HOPE U ENJOY THE NEW MODE WILL LOG QRZ & LOTW ⌁
13:25:29 - (1390) - N2IPH: BEACON FM29 N2IPH: BEACON FM29 ⌁
13:25:40 - (1336) - N1AAE: WA2DE TNX AND HAVE A GOOD DAY. WILL LOG ALSO. 73
13:27:29 - (1398) - WA2DE: N1AAE TAKE CARE CURTIS 73 ⌁
Could this exchange have happened quicker with other modes? Probably. Would I have ever found someone a minute after tuning to the desired frequency to log a contact with? Probably not.
Jordan...read through the thread quickly did not see any reference to having accurate time on the computer is it correct that timing is not an issue as in FT8 since the operator and not the software controls the transmit/receive interval ?
Looking forward to trying it this weekend. Thank you for putting in all the hard work! Another tool in the toolbox, is a great thing to have, for those of us that love digital conversational modes.
Accurate, yes. Precise, no.
Specifically, you still need an accurate timing source to be +/- 2 seconds on a 15 second interval. But, the actual precise specific minute or which 15 second interval you sync to is not required. Does that make sense?
An example. If the current time is 15:00:15 UTC and your clock is set to 15:01:30 UTC, the program will still decode because you're within 2 seconds of ANY 15 second interval. If your clock was set to 15:00:17.5, or something however, you wouldn't be able to decode.
I'm working on removing this timing accuracy as a requirement, since we likely can detect the rising edge of a transmission and synchronize to that. Transmissions happen back-to-back, so there's no EVEN/ODD offset to worry about.