The other option was perhaps it was a true FT8 signal, but running the legacy mode, maybe overmodulated or excessive hum on their transmission. Try unchecking the receive ONLY 77bit and see if you can decode it then. If you can, don't forget to uncheck the ALWAYS transmit 77bit to work them.
On Tue, Oct 23, 2018 at 11:05 AM Jordan Sherer <jordan.she...@gmail.com> wrote: > Interesting. Could be, but I don't think this instance was exactly this. > FT8Call (JS8Call now) doesn't use an every other tx cycle when calling CQ, > so it seems that this was indeed an FT8 signal. They called every other > cycle for about 2 minutes on the same frequency until I was able to decode > the responding station to their CQs (which I couldn't decode). > > Any other thoughts? Any other reason for a really strong station to fail > decoding? > > Best, > Jordan > > On Tue, Oct 23, 2018 at 11:50 AM WB5JJJ <wb5...@gmail.com> wrote: > >> If you are on the 77bit frequencies on 40 or 20, then the most likely >> culprit is you are seeing the non-conforming FT8Call (now JS8Call) >> signals. They are totally incompatible with the standard FT8 either old >> school or RC3 77bit. I see these all the time and are usually very strong >> when compared to the rest of the real FT8 signals. Also, the decode you >> were able to see was probably a real FT8 encoded signal at about the same >> frequency. >> >> Most likely there is nothing wrong with your setup, it's just rogue >> signals that "look" like FT8. In reality, there are very few 77bit signals >> right now as the bulk of the testing has already been carried out some >> weeks back. Exception is MSK144, which is only 77bit in RC3, I still see >> some users there early in the morning on 6m. And remember the DXPeditions >> are still using v1.9.1 as RC3 is a beta and not in wide usage as of yet. >> >> On Tue, Oct 23, 2018 at 10:12 AM Jordan Sherer <jordan.she...@gmail.com> >> wrote: >> >>> Hi Folks, >>> >>> Testing out RC3 today and 77-bit FT8 I found some very strong signals in >>> the band that were troublesome to decode. >>> >>> Now, I'm fairly fluent in FT8 and I keep my Elecraft station configured >>> properly. NTP for time synchronization (ony a few ms divergence), AGC Off, >>> RF gain/ATTN set so the in-app audio meter sits at ~30dB. >>> >>> Most signals are perfect. But this one today eluded me. It decoded once >>> at +10dB with a time delta less than 0.3. Then, subsequent cycles did not >>> decode. >>> >>> It seems like the decoder might have been getting a bad sync. Curious if >>> this might just be a case of that station over-driving their transmit audio >>> or if something else might be afoul? Perhaps there's drift involved here >>> too? I've seen this happen with strong signals on 1.9 as well, so I know >>> its not entirely related to RC3, but do know that 2.0 changed the >>> synchronization scheme so am curious to dig in deeper. >>> >>> I know y'all are busy so what's likely the best way to diagnose this >>> myself to help y'all out? >>> >>> Best, >>> Jordan >>> _______________________________________________ >>> wsjt-devel mailing list >>> wsjt-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>> >> >> >> -- >> George Cotton, WB5JJJ >> PO Box 1025 >> Russellville, AR 72811 >> >> 479.968.7737 Home >> 479.857.7737 Cell >> >> DMR K5CS (Local Repeater) - 310515, CC1, TS2 >> DMR Arkansas - 3105 >> >> 4 >> _______________________________________________ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > -- George Cotton, WB5JJJ PO Box 1025 Russellville, AR 72811 479.968.7737 Home 479.857.7737 Cell DMR K5CS (Local Repeater) - 310515, CC1, TS2 DMR Arkansas - 3105 4
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
