Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by klubnl.pl (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id w15IPcka015693 for ; Mon, 5 Feb 2018 19:25:39 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1eilOE-0000jV-73 for rs_out_1@blacksheep.org; Mon, 05 Feb 2018 18:21:14 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1eilOD-0000jL-Kb for rsgb_lf_group@blacksheep.org; Mon, 05 Feb 2018 18:21:13 +0000 Received: from smtp-out-5.talktalk.net ([62.24.135.69]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1eilOA-0001fm-QV for rsgb_lf_group@blacksheep.org; Mon, 05 Feb 2018 18:21:12 +0000 Received: from mal ([2.98.121.32]) by smtp.talktalk.net with SMTP id ilO9eHac8pb8rilO9elslW; Mon, 05 Feb 2018 18:21:09 +0000 X-DKIM-Result: Domain=talktalk.net Result=Signature OK DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=talktalk.net; s=cmr1711; t=1517854869; bh=rCAVoIGjWNLV0JYsjddRmk9gDco9LfkGRGAxrJs9JJQ=; h=From:To:References:In-Reply-To:Subject:Date; b=hEvu8d5p9fEHXsn9J4uCCv1Fnlop5vA9I6jWDxIe07U3g0D1dYha6NN9pRKXN2ZsI jjcaLEnZ7EVqMHPZJwtkK9rey9quxXfb8FM8eec7t8ThH9oWSH71fkQXBitUIFZlSw 4XFrNHpIZpOlQlLboFYANiG+lpDrtDerL1myUj9M= X-Originating-IP: [2.98.121.32] X-Spam: 0 X-OAuthority: v=2.2 cv=ZM2noTzb c=1 sm=1 tr=0 a=6/O84cueCPZQWFRE4vJs9g==:117 a=6/O84cueCPZQWFRE4vJs9g==:17 a=8nJEP1OIZ-IA:10 a=pGLkceISAAAA:8 a=ip7sg-qylHq9BxZHuqQA:9 a=wPNLvfGTeEIA:10 Message-ID: From: To: References: <473da6a1-0b7d-1af6-5d0c-355b1c7bfe81@n1bug.com> <1E6A4083-58B4-455A-BEA5-64084858FF69@talktalk.net> <1517845014772.54341@kuleuven.be> <809882652.20180205161611@gmail.com> <1517848469797.2746@kuleuven.be> <797250428.20180205164428@gmail.com> <1178094692.20180205174213@gmail.com> In-Reply-To: <1178094692.20180205174213@gmail.com> Date: Mon, 5 Feb 2018 18:21:11 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 16.4.3528.331 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331 X-CMAE-Envelope: MS4wfCUAJoQsuYeMyMnk/WksRu3ysKCSVmhqHSwnEr+CJRx7dFP7noANXIr6EV6lStp2xpz/vXvOc9UFZk4g5ezb+TleyEmXI/cqXCG+7yGtNwHzeY8Dlwe3 VztNUeLE9JovSFh+x4339RCCEKZDZo3r/NkBe2Gq++3sYaoQ8JOcP01u X-Spam-Score: 1.8 (+) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: That is why CW or QRSS is the preferred mode ie THE REAL DEAL-NO TOYS OR GUESSWORK G3KEV Content analysis details: (1.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.2 STOX_REPLY_TYPE No description available. 1.6 SUBJ_ALL_CAPS Subject is all capitals -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: ce0e5a4ae990e5a63db3ab7aea21191b Subject: LF: Re: MF/630M BAND Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.4 required=5.0 tests=MISSING_OUTLOOK_NAME, NO_REAL_NAME autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false That is why CW or QRSS is the preferred mode ie THE REAL DEAL-NO TOYS OR GUESSWORK G3KEV -----Original Message----- From: Chris Wilson Sent: Monday, February 5, 2018 5:42 PM To: N1BUG Cc: dead.fets@gmail.com Subject: Re: LF: MF/630M BAND Hello Paul, great explanation, I understand now, these little black box "toys" have their limitations :) Thank you, sorry to doubt you Rik! Monday, February 5, 2018, 4:57:02 PM, you wrote: > On 02/05/2018 11:44 AM, Chris Wilson wrote: >> >> Hello Rik, >> >> Thanks, but hmmm, when I TX in JT-9 on LF N1BUG doesn't have spots >> uploaded to PSK reporter site, although he receives me well. I asked >> on the WSJT group and they said it wouldn't as no proper QSO was >> completed. > That is because the U3S cannot transmit a standard formatted CQ > message. They may appear standard but they are not, they are sent as > free text messages which WSJT-X does not recognize as a CQ, thus > refuses to upload to PSK Reporter. > Put another way, the WSJT-X software compresses CQ messages into a > special format which the U3S does not do. > Tonight we will all be using WSJT-X, thus our CQ messages should be > properly encoded for recognition and upload to PSK Reporter at the > receiving end. > 73, > Paul N1BUG FN55mf -- Best regards, Chris mailto:dead.fets@gmail.com