Don,
I have played with FT8Call a bit over the past two weeks or so and the signals 
look like FT8 on the waterfall. They can extend over several consecutive 15 
second cycles depending upon the length of the message, but they can also be 
just one 15 second cycle for a short call or message, so they can be easily 
confused with FT8.

Ed, K0KC
[email protected]http://k0kc.us/ 

    On Tuesday, September 18, 2018, 10:56:01 AM EDT, Don AA5AU 
<[email protected]> wrote:  
 
 I think It's an issue having FT8Call on the same frequency as 2.0 beta 
testing. I was confused yesterday when I saw several strong signals on 7.078 
not decode. I "guessed" they could be FT8Call signals and I have yet to try 
FT8Call so I didn't have a means to see. I didn't know whether or not there was 
a problem with WSJT-X.
Is there a way to differentiate the difference between FT8 and FT8Call signals 
just by looking at them on the waterfall? I did notice that possibly the 
signals I was not decoding didn't seem to have the same "cycle" time  as FT8 
but not sure. Any insight?
Don AA5AU

      From: Ed Wilson via wsjt-devel <[email protected]>
 To: "[email protected]" <[email protected]> 
Cc: Ed Wilson <[email protected]>
 Sent: Tuesday, September 18, 2018 9:44 AM
 Subject: Re: [wsjt-devel] Ver. 2.0 problems
  
Maijan,
It is possible that the strong signals that you could not decode were FT8Call 
signals. The developer of this "experimental" application recommends 14.078 as 
a default dial frequency just like WSJT-X 2.0 -rc1 with the 77 bit option. Both 
applications also recommend using 7.078 on 40 meters.

Ed, K0KC
[email protected]http://k0kc.us/ 

    On Tuesday, September 18, 2018, 10:12:51 AM EDT, Marijan Miletic via 
wsjt-devel <[email protected]> wrote:  
 
 I am sorry about previous callsigns message with in-line JPG attachments.  
Dozen QSO made with 77 bits at 14078 kHz!  Several strong signals NOT decoded 
although legacy bits were enabled.  I just experienced several WSJT-X crashes 
while dealing with DU6/PE1NSQ.Both 77 bit options unchecked at 14074 kHz.  
Standard messages showed brackets but all TX attempt were in vain.  QSO made 
with plain Dutch call. 180918_135515  Transmitting 14.075 MHz  FT8:  PE1NSQ 
S56A R-24      135500 -10  0.7  749 ~  CQ LA2IZ JO49                           
135500 -13 -0.2  788 ~  SP8BPX JH7XRG -03                       135500 -16  0.3 
 843 ~  CQ K2TV FN30                            135500 -10  0.3  898 ~  IS0YHV 
BI8CZM RRR                       135500  -2  0.9  971 ~  CQ RW7M KN97           
                 135500  -3  0.2 1121 ~  DJ7XB RA3QH RR73                       
 135500  -6  0.3 1161 ~  RU9SA EB3JT JN01                        135500  -9  
0.2 1287 ~  SV3BLX EB3AM -02                        135500 -21  0.3 1370 ~  
OZ6LK YC3AJ R-18                        135500  -9  0.7 1451 ~  JF2ERJ ON8ZA 
JO20                       135500 -18  0.4 1515 ~  SQ6VIA W8KF 73               
           135500 -14  0.3 1684 ~  S56A PE1NSQ RR73                      
a3180918_135515  Transmitting 14.075 MHz  FT8:  DU6/PE1NSQ 73           Sent 
from Mail for Windows 10  _______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  

|  | Virus-free. www.avast.com  |

_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


     
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to