Page 2 of 2

Re: TX136/500 V1.08 CWID and Script mode added

PostPosted: 28 May 2016 09:15
by F4GCB
Hello Mori,

In WSPR 2 and 15, there is the possibility of special message formats which allows to send compound callsigns and 6-digits locators.
But its use is restrictive because it requires 2 transmission cycles. That is why I did not add this WSPR extended mode.

Fore more information, I return you on the excellent analysis written by Hans G0UPL : http://w7ekb.com/pipermail/600mrg_w7ekb.com/2014-August/003220.html

73 Patrick F4GCB

Re: TX136/500 V1.08 CWID and Script mode added

PostPosted: 28 May 2016 11:56
by JH1GVY
Hell Patrick,
thanks for the reply.

Many stations who are sending WSPR is using the 6-digit locator. Is there any other way to deliver the 6-digit locator to WSPRnet database server?
Since WSPR database server stores a 6-digit locator, I know that in time in 4-digit locator usually.
Users will hope the selection of the 6-grid or 4-grid.

Mori

Re: TX136/500 V1.08 CWID and Script mode added

PostPosted: 28 May 2016 12:53
by F4GCB
Hello Mori,

Most stations which are reported with a 6-digits locator have either a recorded profil or have
already sent a report with their RX locator. The profils and the RX locators are 6-digits.
I think that WSPRnet looks for the callsign into its data base and if this last is found, displays a 6-digits locator even if the TX locator has 4-digits.

73 Patrick F4GCB

Re: TX136/500 V1.08 CWID and Script mode added

PostPosted: 28 May 2016 14:13
by JH1GVY
Hell Patrick,

I'll try them.

Mori

Re: TX136/500 V1.08 CWID and Script mode added

PostPosted: 29 May 2016 13:37
by LA6LU
Hello Mori,

Yes, that is correct. There is only 6 digit locator support in WSPR-15, not in WSPR-2.
I have missed this too, but that is how the WSPR protocol is defined.

73 from
Geir, LA6LU

Re: TX136/500 V1.08 CWID and Script mode added

PostPosted: 29 May 2016 14:07
by LA6LU
F4GCB wrote:Hello Geir,

Just to answer your question.
The script can be looped continuously or n times (1 to 99) via the script frame parameter.
However in the script, a command beacon (=B1) runs the TX once regardless of the frame
configuration of the concerned mode.

73 Patrick F4GCB


Hello Patrick,

Could this possibly be changed in a future version perhaps, so that =B1 did not stop the whole script at one time only if a =B1 command is included in the script?
Can't it just return when the finished CW message is sent and then execute the next command in the script? and... when the last script command is executed, the script loops according to how the looping is set up for it? I understand there may be hidden and good reasons for why a =B1 command stops a script's looping, but that reason is not obvous to me.

If you may allow it, I also have another suggestion. The CW ident, I would like it to have support for suffixes, like LA6LU/B, LA6LU/P or whatever I choose as a suffix.

Anyway, thanks for a all you do. It is a big plus with all the new modes and that everything can be set without a PC now.

73 from
Geir, LA6LU

Re: TX136/500 V1.08 CWID and Script mode added

PostPosted: 29 May 2016 17:25
by F4GCB
Helo Geir,

Where did you see that the command =B1 stops the script ?

I take as example the default script in eeprom : =G1=D3=B1=ZT10
You select the Script mode, you set the script frame to 5 ( TX x5 displayed ) then you run the script by pushing the OPER button.
The script =G1=D3=B1-ZT10 will be executed 5 times even if the frame of the QRSS mode has been set on continuously.

So it gives us :
=G1 mode QRSS
=D3 dot time to 3 s
=B1 short message sent in QRSS (dot time 3 s) once
=ZT10 10 s wait
=G1 …. loop 5 times

Is it more clear ?

73 Patrick F4GCB

Re: TX136/500 V1.08 CWID and Script mode added

PostPosted: 29 May 2016 21:37
by LA6LU
Hello Patric,

I saw it here: "However in the script, a command beacon (=B1) runs the TX once regardless of the frame"

But I understand now that I misunderstood that statement. So the correct way seeing this is, if I set the script to run indefinitely, it will, but each command within that script will only run once for each time the script loops. I think this it and that might be what I am looking for if the =Gn mode command (\gn Mode, n = 0 to 5) also supports the WSPR mode (i.e. it will start WSPR once for each loop). That way I can alternate between CW beacon mode and WSPR mode, since the WSPR mode also just waits until the correct time if the CW message is short. I will try testing this soon and see.

Anyway, Just as you probably already know now, I can confirm your software also works fine on a TX500.

Thank you for you patience :)

All the best and 73's from

Geir, LA6LU

Re: TX136/500 V1.08 CWID and Script mode added

PostPosted: 30 May 2016 22:06
by JH1GVY
Hello Patrick,

I was confirmed, for people using TX136/500 to be portable operating, report of using its own RX_locator is convenient.
Thank you very much for your help.

Mori

Re: TX136/500 V1.08 CWID and Script mode added

PostPosted: 19 Jun 2016 18:17
by F6CWA
Hello LF'ER
I switched from V1.06 to V1.08 everything works except the message transmission from the juma control interface.
message via interface only works with the CW mode in other modes QRSS/ dfcw it is the beacon message transmitted.

that is the method to send message by JUMA control interface in modes QRSS / DFCW ?
Hubert // F6CWA JN24NI / IN78WA