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;
Message-ID: <53376671.6000303@gmx.net>
Date: Sun, 30 Mar 2014 01:33:53 +0100
From: Tobias DG3LV <DG3LV@gmx.net>
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> <5337475B.7010302@gmx.net> <53375151.2080606@gmail.com>
In-Reply-To: <53375151.2080606@gmail.com>
Subject: Re: LF: Re: MultiPSK, a small introduction to beaconing
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org

Hi Stefan !

It is an emulation of Navtex by use of the macros.
Yes, the sync-tone is simulated by the macro "<TX><TUNE: 100 1415 50>"

Yes,"<UTC DATE/TIME>" inserts current UTC-time.

Yes, part of. At start of each transmission a "Message nnn" text is 
sent. (nnn= [incrementing number]) Unfortunately this text is sent 
before the start of the sequence and not within it. I'm looking for a 
solution or workaround.

("two out of three ain't bad")

Good night & 73 de dg3lv Tobias

Am 30.03.2014 00:03, schrieb DK7FC:
> Hello Tobias,
>
> Thanks for the good explanation.
> Well, i remember some further problems. Do i remember correctly that it
> is no actual NAVTEX mode, i.e. no sync tone to the beginning? The
> message "ZCZC  [incrementing number]" is there, or not? What about the
> automatically updating transmission time in the text? Is it there too?
> These are important functions i find.
> Well, i may give it a try soon, thanks again. But this night is for LF!!
> :-)
>
> 73, Stefan/DK7FC
>
> Am 29.03.2014 23:21, schrieb Tobias DG3LV:
>> 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 <MY CALL>, <MY NAME>, <MY QTH>, <MY LOCATOR>,
>> <ANTENNA>, <RIG>, <WEB ADRESS> 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" <dl4yhf@freenet.de>
>>>>> To: "RSGB LF Group at blacksheep" <rsgb_lf_group@blacksheep.org>
>>>>> 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 .
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>
>