Delivered-To: daveyxm@virginmedia.com Received: by 10.50.203.68 with SMTP id ko4csp38506igc; Sat, 29 Mar 2014 15:43:19 -0700 (PDT) X-Received: by 10.194.236.9 with SMTP id uq9mr4868939wjc.31.1396132998405; Sat, 29 Mar 2014 15:43:18 -0700 (PDT) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id dm2si4807991wib.72.2014.03.29.15.43.17 for ; Sat, 29 Mar 2014 15:43:18 -0700 (PDT) Received-SPF: neutral (google.com: 195.171.43.25 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) client-ip=195.171.43.25; Authentication-Results: mx.google.com; spf=neutral (google.com: 195.171.43.25 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) smtp.mail=owner-rsgb_lf_group@blacksheep.org Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1WU1d2-0002lv-TB for rs_out_1@blacksheep.org; Sat, 29 Mar 2014 22:21:28 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1WU1d2-0002lm-0F for rsgb_lf_group@blacksheep.org; Sat, 29 Mar 2014 22:21:28 +0000 Received: from mout.gmx.net ([212.227.15.18]) by relay1.thorcom.net with esmtp (Exim 4.82) (envelope-from ) id 1WU1cz-0000zU-Mv for rsgb_lf_group@blacksheep.org; Sat, 29 Mar 2014 22:21:26 +0000 Received: from [127.0.0.1] ([91.38.34.94]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0M50aI-1XH3og03SA-00zH6h for ; Sat, 29 Mar 2014 23:21:24 +0100 Message-ID: <5337475B.7010302@gmx.net> Date: Sat, 29 Mar 2014 23:21:15 +0100 From: Tobias DG3LV User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: <53368946.1060608@freenet.de> <8B7B46E116D8417BA83C841B9317F0AC@your91hoehfy9g> <5336B25B.70806@gmx.net> <5336F585.6050503@iup.uni-heidelberg.de> In-Reply-To: <5336F585.6050503@iup.uni-heidelberg.de> X-Provags-ID: V03:K0:NTbImsmeWm+yld/n1aVI2avfBEN+eF8HRBgWlQEj3U63IsYXNlG ZpktcMXlb3lH/HbHMHFFXAHy+20JRni6t9OUKVIfP3FkfsXkkaF87NXeGMPs1IDAgmpBDbO SoXw2LNgu1n+k2T3XWHrHp0RWowFLyZroDnOFMrEpDfG5OrWHt8jrfXZkDtQ1/icAilcjCx TFlUEkzvsHNzqCja1LiKQ== X-Spam-Score: -0.4 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hi Stefan, MF ! A small introduction to beaconing by MultiPSK (for any mode): MultiPSK calls its long macros "sequences". There can be 1 to 24 sequences, each stored in a file named "Fxx.SER", where xx is the sequence number ranging from 1 to 24. My example file is called "F1.SER", it is a replacement for the original file. [...] Content analysis details: (-0.4 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [212.227.15.18 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (dg3lv[at]gmx.net) -0.0 SPF_PASS SPF: sender matches SPF record -0.4 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Scan-Signature: 13abe497adcf17a4e25c5e2a2ff79111 Subject: LF: Re: MultiPSK, a small introduction to beaconing Content-Type: multipart/mixed; boundary="------------090902060607060700040005" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.1 required=5.0 tests=CLICK_BELOW,LINES_OF_YELLING, LINES_OF_YELLING_2 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 This is a multi-part message in MIME format. --------------090902060607060700040005 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit Hi Stefan, MF ! A small introduction to beaconing by MultiPSK (for any mode): MultiPSK calls its long macros "sequences". There can be 1 to 24 sequences, each stored in a file named "Fxx.SER", where xx is the sequence number ranging from 1 to 24. My example file is called "F1.SER", it is a replacement for the original file. Install MultiPSK, then first replace old "F1.SER" file in the programs directory by the supplied one. Start MultiPSK and go to "configuration screen" (=first screen at startup), set your soundcard settings for "input" and "output" and define your PTT-COMport at "serial port". At the left middle of the configuration screen there is a panel for "beacon mode (all modes)". Set both sequence numbers to "1". Set "pause" to a suitable time between two consecutive transmissions. Set "duration" to several hours, if you want to stay in beacon-mode all night long. (meant is NOT the duration of the single transmission!!!) When setting "prior serial number", there will be a "Message nnn" at the start of each beacon transmission, where "nnn" is incremented automatically starting at "1". Leave configuration screen by a click on "rx/tx screen". Now you are in the main window. Select "AMTOR-FEC-Navtex" in the mode-selection-panel at the upper right. (and please select Shift = 170 at the panel just above the middle of the waterfall.) Next click on the item "configuration" in the main menu line on top of the screen. Select/click on "personal Data" and set your call, name, city etc. Your texts for , , , , , , are used by the F1.SER sequence. Please enter your personal data. After completion click on "save" and you are back in the main window. That's all for configuration. (the audio frequency used -1500 Hertz- is defined in the F1.SER file already, = need not be set) Now we can test it for a first time : Start a first single beacon transmit by pressing the "F1" function key on the keyboard, or by clicking on "Call 1 F1" at the very left just below the waterfall. You can watch the echo of the transmitted characters at the Tx-area. Verify that the text of the message is ok. ("Message nnn" is not shown yet, it is inserted later at beaconing) Now we are ready to start beaconing. There is a "Beacon" button situated just below the "help" item of the main menu. You start the beacon-mode by clicking on this "Beacon" button (click again to stop). A big yellow band with "Beacon : AMTOR transmission" just below the weaterfall verifies that the beacon-mode is on. That's it. Beaconing-mode will stop automatically after "duration" time is over, or at a click on the "beacon" button. (There is a help function on the right mouse button for most items used here, but you are warned : the help function of MultiPSK is extensive and detailled, you could end up reading a manual) Give it a try, maybe it's worth it. 73 de dg3lv Tobias Am 29.03.2014 17:32, schrieb Stefan Schäfer: > Hi Tobias, > > Thanks for the report. > How do i use this macro? Last night i tried to use MultiPSK again but it > takes a long time to get a rough overview over the > 100000000000000000000000000000000000000000000000000000000000 buttons. > BTW decoding works well in fldigi here... > About the 170 Hz shift, still the old problem. Actually i informed an OM > who is in the group of people who work/improve the program. However i > did not try to look for a recent update. I'm going to ask him again if > the change has been done. > > 73, Stefan/DK7FC > > Am 29.03.2014 12:45, schrieb Tobias DG3LV: >> Hi Mal ! >> Hi Wolf ! >> >> To use MultiPSK for transmission of an AMTOR-FEC beacon in the style >> received yesterday, here comes a MACRO file to be used as a template. >> MultiPSK is capable of sending standard-conform AMTOR-FEC at 170 Hertz >> shift. This can be decoded by all programs/Decoders (including >> "fldigi") that decode "NAVTEX" aka "AMTOR-FEC". >> >> That signal of yesterday was received from sequence number 19 >> (2014-03-27, 2349 UTC) to 25 (2014-03-28, 0014 UTC) with some QSB. >> Sequences 23 and 24 were decoded just partly because of deep QSB. >> (After seq 25 I was QRT) >> >> 73 de dg3lv Tobias >> >> Am 29.03.2014 10:07, schrieb mal hamilton: >>> I heard this Wolf it was hi speed rtty possibly 75 or 100 baud. I did >>> not try a decode >>> It was a strong signal >>> >>> 73 MAL/G3KEV >>> ----- Original Message ----- From: "wolf_dl4yhf" >>> To: "RSGB LF Group at blacksheep" >>> Sent: Saturday, March 29, 2014 8:50 AM >>> Subject: LF: MF : RTTY ? >>> >>> >>>> Greetings all, >>>> >>>> There was a powerful RTTY signal around 476.4 (?) kHz yesterday, >>>> european night, which didn't look like the military stuff but an >>>> amateur transmission. Tone spacing about 200 Hz. >>>> I tried -in vain- to decode it with MMTTY but no luck, whatever >>>> combination of buttons on the main screen were clicked. >>>> Anyone with more luck here ? Try another software ? >>>> It's been many years since I last used that mode, with a DJ6HP >>>> "Filter-Konverter"... >>>> >>>> 73, Wolf DL4YHF . >>>> >>>> >>>> >>> >>> >>> > > --------------090902060607060700040005 Content-Type: text/plain; charset=windows-1252; name="F1.SER" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="F1.SER" PFRYPjxUVU5FOiAxMDAgMTQxNSA1MD48SFoxNTAwPg0KWkNaQyBEVDAxDQo8VVRDIERBVEUv VElNRT4NCgoKVlZWIFZWViBWVlYgVlZWDQoKTkFWVEVYIFRFU1QgVFJBTlNNSVNTSU9OIE9O IFRIRSA2MzBNIEJBTkQgQlkgQU1BVEVVUiBSQURJTyBTVEFUSU9ODQpDQUxMOiA8TVkgQ0FM TD4gPE1ZIENBTEw+IDxNWSBDQUxMPg0KCk9QRVJBVE9SOiA8TVkgTkFNRT4gPE1ZIE5BTUU+ IDxNWSBOQU1FPg0KUVRIOiA8TVkgUVRIPiA8TVkgUVRIPiA8TVkgUVRIPg0KCkxPQ0FUT1I6 IDxNWSBMT0NBVE9SPiA8TVkgTE9DQVRPUj4gPE1ZIExPQ0FUT1I+DQpBTlRFTk5BOiA8QU5U RU5OQT4NCgpSSUc6IDxSSUc+DQoKDQpSRVBPUlRTIFdFTENPTUUgVklBIExGIFJFRkxFQ1RP UiAoQkxBQ0tTSEVFUC5PUkcpDQoKT1IgNjMwTSBCQU5EIERYIENMVVNURVINCgpPUiBFTUFJ TCBUTzogPFdFQiBBRFJFU1M+DQoNCgpGVVJUSEVSIElORk9STUFUSU9OUzogSFRUUDovL1dX Vy5RUlouQ09NL0RCLzxNWSBDQUxMPg0KDQoKClROWCBGT1IgUkVDRVBUSU9OIFJFUE9SVFMg VE86DQoKDQoNCgoKNzMgNzMgNzMgNzMgNzMNCg0KTk5OTg0KDQo8Ulg+ --------------090902060607060700040005--