Re: [wsjt-devel] SSL handshake failed

[Black Michael via wsjt-devel]

Did you try searching the archives?  This has been asked and answered numerous 
times.


Known problem with RC3 and it's not fatal...just annoying.

Solution provided by Bill here in #4.

 

https://sourceforge.net/p/wsjt/mailman/message/36443778/

 

de Mike W9MDB



 

On Thursday, October 25, 2018, 11:15:05 PM CDT, Fred Regennitter 
 wrote:  
 
  Guys, I installed v2.0.0-rc3. Previously running v2.0.0-rc1 and I get this 
msg.How do I fix it?
de Fred K4IU
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Flex Split Operation Setup with WSJT-X

[Black Michael via wsjt-devel]

I don't know why you would need separate slices to work split in WSJT-X.  
Aren't slices really for different frequency ranges?
Split in WSJT-X is all inside the audio band pass of one slice.  It just 
adjusts the frequency so that the audio is always in the 1500-2000Hz 
offset.Split is really designed for rigs (or operators) that have harmonics on 
their signal (usually from incorrect audio settings).As long as you aren't 
hitting the ALC on your Flex your signal would be clean and split is not 
needed.But it should work just fine on one slice.
de Mike W9MDB


 

On Thursday, October 25, 2018, 5:55:03 PM CDT, Star Light 
 wrote:  
 
 
Hello, I have WSJT-X (v1.9.1) set up with my Yaseu FTdx9000 to operate full 
(not “fake") split and it works great.  WSJT-X seems to always listen on the A 
side and set Tx on the B side (no matter how it’s set initially) and moves the 
B side Tx freq around in a logical way.

I’m not sure how to set up the corresponding configuration on my Flex.  At 
present I have it set to the A slice and listening through DAX 1 on the B slice 
(to be “split”).  It makes odd freq adjustments that don’t make sense on the A 
Tx slice, never changes Tx to the B slice and never moves the DAX slice choice 
no matter how I set it up.  I don’t know what it is assuming and can’t see any 
way to “tell it” it’s listening on the B slice.  I don’t know if it assumes 
that in setup or something else but seems to work best when set up this way 
from a simply making contacts point of view.

If I set Tx and DAX audio both on the A slice (always choosing split in 
config), it will actually activate the B slice from time to time but never 
set’s DAX audio output from it, or Tx to it.  So it can’t actually be using the 
B slice for anything.  Then shortly after it activates it, it deactivates it.

Flex is a drop-down option so I know WSTJ-X “knows” about it, I just know how 
it expects the physical radio to be set up to use it in split mode.  Any advice 
would be appreciated!  Thanks, Russ KR6W

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] SSL handshake failed

[Fred Regennitter]

Guys, I installed v2.0.0-rc3. Previously running v2.0.0-rc1 and I get this msg.
[cid:1bd14b08-4077-4580-ae90-914d6e208a22]
How do I fix it?

de Fred K4IU
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] FT8 Mock RU Test #2 Observations

[David Bean (KC2WUF) via wsjt-devel]

I participated in the 2nd Mock RU and again found a large number of operators 
starting early. I worked 1 pre-scheduled window and worked 9 more during the 
scheduled window.
I was using v2.0-rc3 as required on a Windows 10 Version 1803. I initialized my 
wsjt_log.adi prior to making any Qs and had the correct exchange "NJ" entered 
for the contest. I forgot to clear the Cabrillo file, but I had no previous 
QSOs in it. I ran 20W to a long-wire as I normally run FT8 mode.

Problem while logging:
I noticed that the exchange fields weren't being populated in the Log QSO box 
and on several occasions I typed them in manually. In both cases, the ADIF file 
did not contain any exchange information. Both the sent and received exchanges 
were displayed on the view contest window and appeared in the Cabrillo file 
generated after the contest. For parts of the test, I tried running JTAlert to 
my regular log both with and without exchanges filled in and no Exchange fields 
were passed. I also had the similar results when I ran N1MM+ for a couple of 
different QSOs and again no exchanges got sent. I saw someone mention that by 
switching from Tab 2 Messages to Tab 1 Messages that it started working. I 
always use Tab 1 Messages, so I didn't think to try switching back and forth.

Worked B4 and DX coloring:I noticed the CQ coloring did change to Green after I 
worked domestic stations, but all DX stations are Green whether they have been 
worked or not. As someone else said with the small number of Qs you can check 
if you've worked a station, but during a 24-hour contest that would be 
difficult at best.
73 David KC2WUF
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FTdx3000

[David Bean (KC2WUF) via wsjt-devel]

Watt,
I use "Yaesu FT-DX5000" for my FTDX3000. It works well.
73 David KC2WUF
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FTdx3000

[Black Michael via wsjt-devel]

Have you tried any others?  Maybe the FTdx5000?
Looks like the 3000 has the same command set.
If it does work we can add a definition for it.
de Mike W9MDB


 

On Thursday, October 25, 2018, 9:45:30 PM CDT, S.WATANABE 
 wrote:  
 
 What radio can I choose for my Yaesu FTdx3000 to interface FT8?
That one seems to be not appeared in the radio list.
Is there any alternative choice?

Thanks and 73!
Watt JA0DAI (also WR3W)


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] RU stuff

[Jim Shorney]

Hi John,

The band was changing it up a bit. You QSBed to nothing after I first heard
you. Good to get you in the log again later.

Have we worked you from W0BJQ yet? Steve WU0F likes to put the shack on the air
on his lunch breaks.

73

-Jim
NU0C




On Thu, 25 Oct 2018 19:36:43 -0400, John T Haworth wrote:

>Hello Jim,
>
>I saw you attempt a call while I was in another QSO. I did have your call in 
>the Next, but by the time it called your signal had disappeared. I noted that 
>some of the confusion stemmed from QSB occurring. 
>
>In either case, I would image a little more time getting to know the contest 
>routines will greatly alleviate the Embarrassment felt.
>
>All calls logged correctly. Only needed to restart the program to reset back 
>to normal operation.
>
>I am looking forward to the next Mock, or real, content with wsjt 2.0!
>
>Setup, MacOS Mojave, JT-Bridge and RUMlogNG.
>
>Thanks and 73 John NU8M
>
>> On Oct 25, 2018, at 00:16, Jim Shorney  wrote:
>> 
>> 
>> That was fun! Makes me think I should get back into contesting some more
>> 
>> I did have a couple of strange things happen. The first happened when I was
>> CQing. Another station called me as I finished up normally with the guy that 
>> I
>> had stacked in the Next: box.. I sent the new caller's report but he did not
>> ack with RR73, In fact in that cycle I saw him calling a DX. So I tried to 
>> bail
>> from that Q and answer another caller but previous station's call was stuck 
>> in
>> the messages. None of the usual methods would clear it, even typing the new
>> caller into the DX Call box didn't help. I did not think to try switching to
>> tab 2, I just restarted the program and it was OK. Meanwhile I lost two 
>> callers
>> while my messages were held hostage.
>> 
>> The second thing happened when I called a DX and worked him. While I was in 
>> QSO
>> with that station someone else started calling me down the band. Well, I got 
>> a
>> little ahead of myself and pulled the trigger on the caller before I copied 
>> the
>> final 73 from the DX I was working. I worked the caller but my TX stayed on 
>> the
>> DX's fequency even though Hold TX was NOT checked. Embarassing, as I do try 
>> my
>> best not to be a frequency thief. I finally managed to finally get the TX to
>> move to the caller's freqency manually before my final transmission but I
>> didn't make a note of how I did it. 
>> 
>> I hope this makes sense. System is Kubuntu Linux 18.10, -rc3 compiled from
>> source. No CAT control, rig does not have it and the four legged furry one 
>> was
>> upstairs sleeping somewhere. 
>> 
>> 73
>> 
>> -Jim
>> NU0C

--
Hold tight and pretend it's a plan. - The Doctor, "The Doctor, the Widow and 
the Wardrobe"




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] FTdx3000

[S.WATANABE]

What radio can I choose for my Yaesu FTdx3000 to interface FT8?
That one seems to be not appeared in the radio list.
Is there any alternative choice?

Thanks and 73!
Watt JA0DAI (also WR3W)


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] RU stuff

[John T Haworth]

Hello Jim,

I saw you attempt a call while I was in another QSO. I did have your call in 
the Next, but by the time it called your signal had disappeared. I noted that 
some of the confusion stemmed from QSB occurring. 

In either case, I would image a little more time getting to know the contest 
routines will greatly alleviate the Embarrassment felt.

All calls logged correctly. Only needed to restart the program to reset back to 
normal operation.

I am looking forward to the next Mock, or real, content with wsjt 2.0!

Setup, MacOS Mojave, JT-Bridge and RUMlogNG.

Thanks and 73 John NU8M

> On Oct 25, 2018, at 00:16, Jim Shorney  wrote:
> 
> 
> That was fun! Makes me think I should get back into contesting some more
> 
> I did have a couple of strange things happen. The first happened when I was
> CQing. Another station called me as I finished up normally with the guy that I
> had stacked in the Next: box.. I sent the new caller's report but he did not
> ack with RR73, In fact in that cycle I saw him calling a DX. So I tried to 
> bail
> from that Q and answer another caller but previous station's call was stuck in
> the messages. None of the usual methods would clear it, even typing the new
> caller into the DX Call box didn't help. I did not think to try switching to
> tab 2, I just restarted the program and it was OK. Meanwhile I lost two 
> callers
> while my messages were held hostage.
> 
> The second thing happened when I called a DX and worked him. While I was in 
> QSO
> with that station someone else started calling me down the band. Well, I got a
> little ahead of myself and pulled the trigger on the caller before I copied 
> the
> final 73 from the DX I was working. I worked the caller but my TX stayed on 
> the
> DX's fequency even though Hold TX was NOT checked. Embarassing, as I do try my
> best not to be a frequency thief. I finally managed to finally get the TX to
> move to the caller's freqency manually before my final transmission but I
> didn't make a note of how I did it. 
> 
> I hope this makes sense. System is Kubuntu Linux 18.10, -rc3 compiled from
> source. No CAT control, rig does not have it and the four legged furry one was
> upstairs sleeping somewhere. 
> 
> 73
> 
> -Jim
> NU0C
> 
> 
> --
> 
> "It's an Earth food. They are called Swedish meatballs! It's a strange thing, 
> but every sentient race has its own version of these Swedish meatballs! I 
> suspect it's one of those great universal mysteries which will either never 
> be explained, or which would drive you mad if you ever learned the truth!" - 
> G'Kar, Babylon 5
> 
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Flex Split Operation Setup with WSJT-X

[Star Light]

Hello, I have WSJT-X (v1.9.1) set up with my Yaseu FTdx9000 to operate full 
(not “fake") split and it works great.  WSJT-X seems to always listen on the A 
side and set Tx on the B side (no matter how it’s set initially) and moves the 
B side Tx freq around in a logical way.

I’m not sure how to set up the corresponding configuration on my Flex.  At 
present I have it set to the A slice and listening through DAX 1 on the B slice 
(to be “split”).  It makes odd freq adjustments that don’t make sense on the A 
Tx slice, never changes Tx to the B slice and never moves the DAX slice choice 
no matter how I set it up.  I don’t know what it is assuming and can’t see any 
way to “tell it” it’s listening on the B slice.  I don’t know if it assumes 
that in setup or something else but seems to work best when set up this way 
from a simply making contacts point of view.

If I set Tx and DAX audio both on the A slice (always choosing split in 
config), it will actually activate the B slice from time to time but never 
set’s DAX audio output from it, or Tx to it.  So it can’t actually be using the 
B slice for anything.  Then shortly after it activates it, it deactivates it.

Flex is a drop-down option so I know WSTJ-X “knows” about it, I just know how 
it expects the physical radio to be set up to use it in split mode.  Any advice 
would be appreciated!  Thanks, Russ KR6W

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] macOS Subprocess error

[David Kaplan via wsjt-devel]

I’m running Mojave and WSJT-X v2 rc3 8A1244

I updated to rc3 when it was announced awhile ago.

Only today have I started having the error "Subprocess failed with exit code 2" 
and the description that it couldn’t open file fort.81.

I did some research and have bypassed the problem by running the program from 
terminal.

My question is why would it just show itself today? Any idea what I might have 
done differently that I haven’t done before?

Thanks,

73,

David, WA1OUI






___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] cabrillo_FT8ru_N2LO_2018OCT25

[robert evans LAST_NAME]

running abt 20W (near linear sweet spot) into low dipole.

heard quite a few DX stns that i spent time trying to work.

Ukraine and Slovenia among them.


the top standard msg that had the my FN20 grid faded

setting contest to none did not recover.

restarting wsjtx2r3 recovered.


thank you for this opportunity.

log is attached..

DE N2LO~>


cabrillo_FT8ru_N2LO_2018OCT25

QSO:  7078 DG 2018-10-25 0153 N2LO 569 NJTG9ANF   539 0016
QSO:  7078 DG 2018-10-25 0154 N2LO 579 NJK1JT 569 NJ
QSO:  7078 DG 2018-10-25 0157 N2LO 599 NJKV4T 549 AL

QSO:  7077 DG 2018-10-25 0203 N2LO 579 NJK2PS 589 FL
QSO:  7077 DG 2018-10-25 0209 N2LO 539 NJVE6WQ529 AB
QSO:  7077 DG 2018-10-25 0216 N2LO 559 NJIQ1ZW559 0003
QSO:  7079 DG 2018-10-25 0250 N2LO 549 NJAJ6T 529 AL
QSO:  7077 DG 2018-10-25 0258 N2LO 559 NJXE1MEX   559 0018

QSO:  7078 DG 2018-10-25 0304 N2LO 559 NJHH2AA539 0001
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X & JTSDK future?

[Marco Calistri via wsjt-devel]

Hi Adam,

I go by "top posting" as it is easier to read the reply for everybody.

Do you think is existing any relationship between "asciidoc/texlive"
missing packages on my system and the specific "hamlib not found" error
faced during the building?

I'm not a software developer, but honestly I don't see any relation, so
my first obstacle is to resolve the hamlib issue which I think is being
produced by this parse:

-- Checking for module 'hamlib'
--   Found hamlib, version 4.0~git
-- Found hamlib
CMake Error at
/usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
  Could NOT find hamlib (missing: hamlib_LIBRARY_DIRS) (Required is at least
  version "3")
Call Stack (most recent call first):
  /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:378
(_FPHSA_FAILURE_MESSAGE)
  CMake/Modules/Findhamlib.cmake:81 (find_package_handle_standard_args)
  CMakeLists.txt:852 (find_package)

Are there any verifications I should do on cmake in order to get rid of
this error?

Cheers,

Marco, PY1ZRJ

Il 25/10/2018 12:40, Adam Schaible ha scritto:
> Hi Marco,
>
> Yes I saw the 2,000+ texlive packages on my computer too, I let zypper
> go ahead and install them, each one by itself is quite small. I didn't
> see this action in other Linux distros (Debian and Solus) that I made
> build scripts for earlier, maybe they already pre-installed texlive,
> or possibly they put all the very small pieces of texlive code for
> each language into one very large package.
>
> If you can get WSJT-X 2.0.0 RC3 to build on Tumbleweed without texlive
> please share your results, I am going to stay with what I have on
> Tumbleweed since it is working great.
>
> Ciao!
>
> -- 
>   Adam Schaible
>   kb3...@schibes.com
>
>
>
> On Thu, Oct 25, 2018, at 11:16 AM, Adam Schaible wrote:
>> Hi Marco,
>>
>> Yes I saw the 2,000+ texlive packages on my computer too, I let
>> zypper go ahead and install them, each one by itself is quite small.
>> I didn't see this action in other Linux distros (Debian and Solus)
>> that I made build scripts for earlier, maybe they already
>> pre-installed texlive, or possibly they put all the very small pieces
>> of texlive code for each language into one very large package.
>>
>> If you can get WSJT-X 2.0.0 RC3 to build on Tumbleweed without
>> texlive please share your results, I am going to stay with what I
>> have on Tumbleweed since it is working great.
>>
>> Ciao!
>>
>> --
>>   Adam Schaible
>>   a...@schibes.com
>>
>>
>>
>> On Thu, Oct 25, 2018, at 10:20 AM, Marco Calistri via wsjt-devel wrote:
>>>
>>>
>>> Il 22/10/18 17:31, Adam Schaible ha scritto:
 Buonasera Marco,

 OpenSUSE Tumbleweed you say? Sure I can handle that. Here is a tested and 
 working script to build WSJT-X 2.0.0 RC3 on that distro. 

 First, disclaimers/notes and then, the script:

 1) I am NOT a WSJT-X developer, I am just a regular ham radio operator who 
 loves Linux. (I did meet K1JT once a few years ago at a speech he gave, it 
 was fun!) So if you run my script below and it breaks your computer don't 
 blame the wonderful WSJT-X devs, blame only me. By the way I have never 
 tried Tumbleweed before today and I am very impressed, enough so that I 
 may even use it to make a few contacts in WSJT-X :)

 2) You do know there is an .rpm binary download of WSJT-X 2.0.0 RC3 
 available right? So we don't actually "need" to do any of this except for 
 "educational" purposes. 
  
 3) The WSJT-X 2.0.0 RC3 build script below is tested and working on a 6 
 hours old bare metal install of OpenSUSE Tumbleweed (KDE) on my Lenovo 
 ThinkPad T440. For purpose of comparison I also built it on OpenSUSE Leap 
 15 running in a VM (AWS t2.micro), process was almost identical with just 
 a few small differences that keep it from being able to run as a 
 non-interactive script on Leap (repo update and devel-basis install both 
 need command-line interventions, and Leap compilers are g++-7/gfortran-7), 
 but it still builds fine. Given these positive results, without any 
 further knowledge I can only guess your previous build issues were caused 
 by (as usual) missing dependencies.

 GL es 73 de Adam KB3ZUV


 #!/bin/bash
 #-wsjtx2rc3-opensuseTW-build-script.sh---
 #--RUN ME WITH SUDO-
 #
 #first the obligatory OS patching
 #since this is Tumbleweed we do full distro upgrade
 zypper ref && zypper dup -y
 #add user to dialout group allowing rig CAT control on next login
 #(if you use VOX you don't actually need this)
 usermod -a -G dialout $SUDO_USER
 #install a whole bunch of dependencies to compile WSJT-X
 #g++, git, and automake are all in devel_basis
 zypper in -y --type pattern devel_basis && zypper in -y fftw3-devel \
 fftw3-threads-devel gcc-fortran cmake libqt5-qtbase-devel \
 libqt5-qtmultimedia-devel 

Re: [wsjt-devel] UDP to HRD Logbook

[Bill Somerville]

On 25/10/2018 17:27, Chris Getman wrote:


I thought it was send be WSJTx.exe

Is this the correct exe for sending the ADIF file ?


Hi Chris,

that is correct.

73
Bill
G4WJS.

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] UDP to HRD Logbook

[Chris Getman]

I am trying to set up auto logging to Ham Radio Deluxe Logbook

 

I have set the ADIF broadcast in WSJT settings under N1MM Loggger +
Broadcasts

For 127.0.0.1  port 2333

And I have set the receive under HRD Logbook.

 

Everything works fine if Malwarebytes is turned off, but won't work when it
is on.

 

I have added all the exclusions that Malwarebytes suggested,

 

Except they said to be sure to exclude the .exe program that actually sends
the ADIF broadcast

 

I thought it was send be WSJTx.exe

 

Is this the correct exe for sending the ADIF file ?

Or is it some other program ?

 

 

Or are there any other suggestions ?

 

 

Chris  -  N3PLM

chris.getman...@gmail.com

 

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] mock RU test

[John Nogatch]

Using WSJT-X v2.0.0-rc3 8a1244 on  linux Ubuntu 18.04 :

0. "Settings:Radio:Split Operation:Rig" puts the old Yaesu FT-847 into
"SAT" mode (full duplex crossband), which is not desired. "Fake It"
seemed to work correctly, but did not take advantage of SPLIT. This
may be a hamlib issue.

1. Answering someone's CQ, wsjtx was sending correctly, but the
"Enable Tx" button was not red. Most of the time it behaved normally.
This happened after calling CQ for a while, then hitting "Halt Tx",
then answering someone else's CQ.

2. I received an incorrect exchange, and did not know what to do about it:
QSO:  7078 DG 2018-10-25 0103 AC6SL569 CAK5GQ K5GQ R

3. Twice, when a contact failed to complete, wsjtx was retrying and
created an entry with blank exchange field:
QSO:  7078 DG 2018-10-25 0203 AC6SL559 CAK6LL 529 AZ
QSO:  7078 DG 2018-10-25 0205 AC6SL559 CAK6LL
QSO:  7078 DG 2018-10-25 0229 AC6SL549 CAK6EU 529 CA
QSO:  7078 DG 2018-10-25 0231 AC6SL549 CAK6EU

4. Many times, while apparently sending the correct messages, the
"Next" bullet was indicating "Tx 6", the CQ message. I did not have
"Settings:General:Tx messages to Rx frequency window" enabled, so I
was unsure if I was sending the correct message.

5. This morning, restarting wsjtx to check the version number, it did
not repopulate the "Contest Log" window. If I had to restart wsjtx
during a contest, I would want the log restored.

6. To avoid changing my regular computer while VP6D was still using
wsjtx 1.9.1, I was using a different radio with a new soundcard
interface, 20W to a 40m delta loop. I was hearing well, but not being
heard, except by stations in the western half of the US. Perhaps my
transmit audio was not right, or I needed to run more power. While
transmitting, the dB thermometer was empty, or a small red value. Does
this mean that my transmit audio level was weak?

-John AC6SL


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Callsign recorded as signal report in RU

[Bill]

I observed the same thing here when I answered a station calling CQ in
standard sequence not RU contest sequence (I was in RU Mode). The QSO was
logged with the received signal RPT as W7XYZ R-01.

Also my station never logged my sent reports in either the contest log or
in WSJT-X QSO log.

Bill - AK6A

On Thu, Oct 25, 2018 at 9:14 AM Al  wrote:

> ( WSJT-X 2.0.0 RC3)
>
> Reviewing logs for the RU test I discovered a contact (busted) which
> recorded a call sign as a received signal report.  The was a strung out
> contact that began when I answered a CQ from ADxxx with TX2, and ADxxx
> engaged another station.  I then began calling CQ to be answered a bit
> later by ADxxx with RR73. I auto responded with RR73 and logged the
> contact.  It really wasn't a contact since I never received my report from
> him but it went into the log with 'ADxxx' as the received signal report.
>
> AL, K0VM
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Callsign recorded as signal report in RU

[Al]

( WSJT-X 2.0.0 RC3)

Reviewing logs for the RU test I discovered a contact (busted) which 
recorded a call sign as a received signal report.  The was a strung out 
contact that began when I answered a CQ from ADxxx with TX2, and ADxxx 
engaged another station.  I then began calling CQ to be answered a bit 
later by ADxxx with RR73. I auto responded with RR73 and logged the 
contact.  It really wasn't a contact since I never received my report 
from him but it went into the log with 'ADxxx' as the received signal 
report.


AL, K0VM
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] RTTY RU: Tx Messages stuck after using "TU; ..." message format

[Matt Henry]

Hardware: iMac, IC-7300, 80m OCF Dipole
Software: macOS Mojave, WSJT-X 2.0 RC3, JTBridge, MacLoggerDX
 
In general I found my participation in the Mock "FT8 Roundup" Contest to be 
quite successful and highly enjoyable.  I made 22 contacts and only encountered 
one issue of significance:
 
After one of my CQ calls I received a reply from two stations.  While working 
the first station I double-clicked the second station to add its callsign to 
the work next queue.  I then successfully worked the second station using the 
"TU;..." message format.  From that point on however, the Tx Messages would not 
update.  I tried selecting the "Generate Std Msgs" button, switching Tx Message 
tabs, and double-clicking on other station messages.  Restarting WSJT-X cleared 
the issue.

73
Matt - NR3M


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X & JTSDK future?

[Adam Schaible]

Hi Marco,

Yes I saw the 2,000+ texlive packages on my computer too, I let zypper
go ahead and install them, each one by itself is quite small. I didn't
see this action in other Linux distros (Debian and Solus) that I made
build scripts for earlier, maybe they already pre-installed texlive, or
possibly they put all the very small pieces of texlive code for each
language into one very large package.
If you can get WSJT-X 2.0.0 RC3 to build on Tumbleweed without texlive
please share your results, I am going to stay with what I have on
Tumbleweed since it is working great.
Ciao!

-- 
  Adam Schaible
  kb3...@schibes.com



On Thu, Oct 25, 2018, at 11:16 AM, Adam Schaible wrote:
> Hi Marco,
> 
> Yes I saw the 2,000+ texlive packages on my computer too, I let zypper
> go ahead and install them, each one by itself is quite small. I didn't
> see this action in other Linux distros (Debian and Solus) that I made
> build scripts for earlier, maybe they already pre-installed texlive,
> or possibly they put all the very small pieces of texlive code for
> each language into one very large package.> 
> If you can get WSJT-X 2.0.0 RC3 to build on Tumbleweed without texlive
> please share your results, I am going to stay with what I have on
> Tumbleweed since it is working great.> 
> Ciao!
> 
> --
>   Adam Schaible
>   a...@schibes.com
> 
> 
> 
> On Thu, Oct 25, 2018, at 10:20 AM, Marco Calistri via wsjt-
> devel wrote:>> 
>> 
>> Il 22/10/18 17:31, Adam Schaible ha scritto:
>>> Buonasera Marco,  OpenSUSE Tumbleweed you say? Sure I can handle
>>> that. Here is a tested and working script to build WSJT-X 2.0.0 RC3
>>> on that distro.  First, disclaimers/notes and then, the script:  1)
>>> I am NOT a WSJT-X developer, I am just a regular ham radio operator
>>> who loves Linux. (I did meet K1JT once a few years ago at a speech
>>> he gave, it was fun!) So if you run my script below and it breaks
>>> your computer don't blame the wonderful WSJT-X devs, blame only me.
>>> By the way I have never tried Tumbleweed before today and I am very
>>> impressed, enough so that I may even use it to make a few contacts
>>> in WSJT-X :)  2) You do know there is an .rpm binary download of WSJT-
>>> X 2.0.0 RC3 available right? So we don't actually "need" to do any
>>> of this except for "educational" purposes.  3) The WSJT-X 2.0.0 RC3
>>> build script below is tested and working on a 6 hours old bare metal
>>> install of OpenSUSE Tumbleweed (KDE) on my Lenovo ThinkPad T440. For
>>> purpose of comparison I also built it on OpenSUSE Leap 15 running in
>>> a VM (AWS t2.micro), process was almost identical with just a few
>>> small differences that keep it from being able to run as a non-
>>> interactive script on Leap (repo update and devel-basis install both
>>> need command-line interventions, and Leap compilers are g++-7/gfortran-
>>> 7), but it still builds fine. Given these positive results, without
>>> any further knowledge I can only guess your previous build issues
>>> were caused by (as usual) missing dependencies.  GL es 73 de Adam
>>> KB3ZUV   #!/bin/bash #-wsjtx2rc3-opensuseTW-build-script.sh---
>>> #--RUN ME WITH SUDO- # #first the obligatory
>>> OS patching #since this is Tumbleweed we do full distro upgrade
>>> zypper ref && zypper dup -y #add user to dialout group allowing rig
>>> CAT control on next login #(if you use VOX you don't actually need
>>> this) usermod -a -G dialout $SUDO_USER #install a whole bunch of
>>> dependencies to compile WSJT-X #g++, git, and automake are all in
>>> devel_basis zypper in -y --type pattern devel_basis && zypper in -y
>>> fftw3-devel \ fftw3-threads-devel gcc-fortran cmake libqt5-qtbase-
>>> devel \ libqt5-qtmultimedia-devel libqt5-qtconnectivity-devel \ 
>>> libqt5-qtserialport-
>>> devel libusb-1_0-devel asciidoc hamlib-devel \ ruby2.5-rubygem-
>>> asciidoctor libpulse-devel libudev-devel #create some directories
>>> for WSJT-X sudo -u $SUDO_USER mkdir /home/$SUDO_USER/jtsource sudo
>>> -u $SUDO_USER mkdir /home/$SUDO_USER/.wsjtx #grab and unzip the
>>> source code from Princeton wget --no-check-certificate \
>>> https://physics.princeton.edu/pulsar/k1jt/wsjtx-2.0.0-rc3.tgz sudo
>>> -u $SUDO_USER tar -xzvf wsjtx-2.0.0-rc3.tgz \ -C
>>> /home/$SUDO_USER/jtsource cd /home/$SUDO_USER/jtsource/wsjtx-2.0.0-
>>> rc3 #set build options sudo -u $SUDO_USER cmake -D 
>>> CMAKE_CXX_COMPILER="/usr/bin/g++-
>>> 8" \ -D CMAKE_Fortran_COMPILER="/usr/bin/gfortran-8" \ -D
>>> CMAKE_INSTALL_PREFIX=/home/$SUDO_USER/.wsjtx . #build WSJT-X on
>>> OpenSUSE sudo -u $SUDO_USER cmake --build . --target install #after
>>> build, to run wsjtx2 RC3 type:  ~/.wsjtx/bin/wsjtx #-EOF---

> Hello Adam,
>> 
>> I verified on my system and I had already all dependencies installed,
>> but ruby2.5-rubygem-asciidoctor and  asciidoc.>> 
>> When I tried to install the latter package, zypper answers with a
>> warning that to accompany this, I would need to install *2207*
>> 

Re: [wsjt-devel] WSJT-X & JTSDK future?

[Marco Calistri via wsjt-devel]

Reply is at the bottom.

Il 25/10/18 11:20, Marco Calistri via wsjt-devel ha scritto:
>
>
> Il 22/10/18 17:31, Adam Schaible ha scritto:
>> Buonasera Marco,
>>
>> OpenSUSE Tumbleweed you say? Sure I can handle that. Here is a tested and 
>> working script to build WSJT-X 2.0.0 RC3 on that distro. 
>>
>> First, disclaimers/notes and then, the script:
>>
>> 1) I am NOT a WSJT-X developer, I am just a regular ham radio operator who 
>> loves Linux. (I did meet K1JT once a few years ago at a speech he gave, it 
>> was fun!) So if you run my script below and it breaks your computer don't 
>> blame the wonderful WSJT-X devs, blame only me. By the way I have never 
>> tried Tumbleweed before today and I am very impressed, enough so that I may 
>> even use it to make a few contacts in WSJT-X :)
>>
>> 2) You do know there is an .rpm binary download of WSJT-X 2.0.0 RC3 
>> available right? So we don't actually "need" to do any of this except for 
>> "educational" purposes. 
>>  
>> 3) The WSJT-X 2.0.0 RC3 build script below is tested and working on a 6 
>> hours old bare metal install of OpenSUSE Tumbleweed (KDE) on my Lenovo 
>> ThinkPad T440. For purpose of comparison I also built it on OpenSUSE Leap 15 
>> running in a VM (AWS t2.micro), process was almost identical with just a few 
>> small differences that keep it from being able to run as a non-interactive 
>> script on Leap (repo update and devel-basis install both need command-line 
>> interventions, and Leap compilers are g++-7/gfortran-7), but it still builds 
>> fine. Given these positive results, without any further knowledge I can only 
>> guess your previous build issues were caused by (as usual) missing 
>> dependencies.
>>
>> GL es 73 de Adam KB3ZUV
>>
>>
>> #!/bin/bash
>> #-wsjtx2rc3-opensuseTW-build-script.sh---
>> #--RUN ME WITH SUDO-
>> #
>> #first the obligatory OS patching
>> #since this is Tumbleweed we do full distro upgrade
>> zypper ref && zypper dup -y
>> #add user to dialout group allowing rig CAT control on next login
>> #(if you use VOX you don't actually need this)
>> usermod -a -G dialout $SUDO_USER
>> #install a whole bunch of dependencies to compile WSJT-X
>> #g++, git, and automake are all in devel_basis
>> zypper in -y --type pattern devel_basis && zypper in -y fftw3-devel \
>> fftw3-threads-devel gcc-fortran cmake libqt5-qtbase-devel \
>> libqt5-qtmultimedia-devel libqt5-qtconnectivity-devel \
>> libqt5-qtserialport-devel libusb-1_0-devel asciidoc hamlib-devel \
>> ruby2.5-rubygem-asciidoctor libpulse-devel libudev-devel
>> #create some directories for WSJT-X
>> sudo -u $SUDO_USER mkdir /home/$SUDO_USER/jtsource 
>> sudo -u $SUDO_USER mkdir /home/$SUDO_USER/.wsjtx
>> #grab and unzip the source code from Princeton
>> wget --no-check-certificate \
>> https://physics.princeton.edu/pulsar/k1jt/wsjtx-2.0.0-rc3.tgz
>> sudo -u $SUDO_USER tar -xzvf wsjtx-2.0.0-rc3.tgz \
>> -C /home/$SUDO_USER/jtsource
>> cd /home/$SUDO_USER/jtsource/wsjtx-2.0.0-rc3
>> #set build options
>> sudo -u $SUDO_USER cmake -D CMAKE_CXX_COMPILER="/usr/bin/g++-8" \
>> -D CMAKE_Fortran_COMPILER="/usr/bin/gfortran-8" \
>> -D CMAKE_INSTALL_PREFIX=/home/$SUDO_USER/.wsjtx .
>> #build WSJT-X on OpenSUSE
>> sudo -u $SUDO_USER cmake --build . --target install
>> #after build, to run wsjtx2 RC3 type:  ~/.wsjtx/bin/wsjtx
>> #-EOF---
>>
> Hello Adam,
>
> I verified on my system and I had already all dependencies installed,
> but ruby2.5-rubygem-asciidoctor and  asciidoc.
>
> When I tried to install the latter package, zypper answers with a
> warning that to accompany this, I would need to install *2207*
> additional "texlive packages",
> then of course I didn't hit 'yes'!
>
> I suppose this requirement of having asciidoc installed can be easily
> omitted by telling to "configure" script to not install the
> "man-pages" and the "html docs".
>
> Thus I will try to build the WSJT-X source again following only
> partially your guidelines.
>
> Regards,
> -- 
> 73 de P1ZRJ
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
The error is exactly the same I faced all the times I tried to compile
WSJT-X from source.

It is related to hamlib and not to docs files as it should be due the
missing asciidocs package, so for now I will suspend my unsuccesfull
attempts

-- Building wsjtx-2.0.0-rc3
-- **
-- Building for for: Linux-x86_64
-- **
-- Boost version: 1.63.0
-- Found OpenMP_C: -fopenmp (found version "4.5")
-- Found OpenMP_CXX: -fopenmp (found version "4.5")
-- Found OpenMP_Fortran: -fopenmp (found version "4.5")
-- Found OpenMP: TRUE (found version "4.5") 
-- Found FFTW3: /usr/lib64/libfftw3_threads.so 
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.2")
-- Checking for module 'hamlib'
--   Found 

Re: [wsjt-devel] WSJT-X & JTSDK future?

[Marco Calistri via wsjt-devel]

Il 22/10/18 17:31, Adam Schaible ha scritto:
> Buonasera Marco,
>
> OpenSUSE Tumbleweed you say? Sure I can handle that. Here is a tested and 
> working script to build WSJT-X 2.0.0 RC3 on that distro. 
>
> First, disclaimers/notes and then, the script:
>
> 1) I am NOT a WSJT-X developer, I am just a regular ham radio operator who 
> loves Linux. (I did meet K1JT once a few years ago at a speech he gave, it 
> was fun!) So if you run my script below and it breaks your computer don't 
> blame the wonderful WSJT-X devs, blame only me. By the way I have never tried 
> Tumbleweed before today and I am very impressed, enough so that I may even 
> use it to make a few contacts in WSJT-X :)
>
> 2) You do know there is an .rpm binary download of WSJT-X 2.0.0 RC3 available 
> right? So we don't actually "need" to do any of this except for "educational" 
> purposes. 
>  
> 3) The WSJT-X 2.0.0 RC3 build script below is tested and working on a 6 hours 
> old bare metal install of OpenSUSE Tumbleweed (KDE) on my Lenovo ThinkPad 
> T440. For purpose of comparison I also built it on OpenSUSE Leap 15 running 
> in a VM (AWS t2.micro), process was almost identical with just a few small 
> differences that keep it from being able to run as a non-interactive script 
> on Leap (repo update and devel-basis install both need command-line 
> interventions, and Leap compilers are g++-7/gfortran-7), but it still builds 
> fine. Given these positive results, without any further knowledge I can only 
> guess your previous build issues were caused by (as usual) missing 
> dependencies.
>
> GL es 73 de Adam KB3ZUV
>
>
> #!/bin/bash
> #-wsjtx2rc3-opensuseTW-build-script.sh---
> #--RUN ME WITH SUDO-
> #
> #first the obligatory OS patching
> #since this is Tumbleweed we do full distro upgrade
> zypper ref && zypper dup -y
> #add user to dialout group allowing rig CAT control on next login
> #(if you use VOX you don't actually need this)
> usermod -a -G dialout $SUDO_USER
> #install a whole bunch of dependencies to compile WSJT-X
> #g++, git, and automake are all in devel_basis
> zypper in -y --type pattern devel_basis && zypper in -y fftw3-devel \
> fftw3-threads-devel gcc-fortran cmake libqt5-qtbase-devel \
> libqt5-qtmultimedia-devel libqt5-qtconnectivity-devel \
> libqt5-qtserialport-devel libusb-1_0-devel asciidoc hamlib-devel \
> ruby2.5-rubygem-asciidoctor libpulse-devel libudev-devel
> #create some directories for WSJT-X
> sudo -u $SUDO_USER mkdir /home/$SUDO_USER/jtsource 
> sudo -u $SUDO_USER mkdir /home/$SUDO_USER/.wsjtx
> #grab and unzip the source code from Princeton
> wget --no-check-certificate \
> https://physics.princeton.edu/pulsar/k1jt/wsjtx-2.0.0-rc3.tgz
> sudo -u $SUDO_USER tar -xzvf wsjtx-2.0.0-rc3.tgz \
> -C /home/$SUDO_USER/jtsource
> cd /home/$SUDO_USER/jtsource/wsjtx-2.0.0-rc3
> #set build options
> sudo -u $SUDO_USER cmake -D CMAKE_CXX_COMPILER="/usr/bin/g++-8" \
> -D CMAKE_Fortran_COMPILER="/usr/bin/gfortran-8" \
> -D CMAKE_INSTALL_PREFIX=/home/$SUDO_USER/.wsjtx .
> #build WSJT-X on OpenSUSE
> sudo -u $SUDO_USER cmake --build . --target install
> #after build, to run wsjtx2 RC3 type:  ~/.wsjtx/bin/wsjtx
> #-EOF---
>
Hello Adam,

I verified on my system and I had already all dependencies installed,
but ruby2.5-rubygem-asciidoctor and  asciidoc.

When I tried to install the latter package, zypper answers with a
warning that to accompany this, I would need to install *2207*
additional "texlive packages",
then of course I didn't hit 'yes'!

I suppose this requirement of having asciidoc installed can be easily
omitted by telling to "configure" script to not install the "man-pages"
and the "html docs".

Thus I will try to build the WSJT-X source again following only
partially your guidelines.

Regards,
-- 
73 de P1ZRJ
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Ability to quickly and precisely set my transmission frequency

[Bill]

Thanks John,

  I understand about the program decoding anywhere on the waterfall. I have
just found in practice that if I move away from my original frequency the
other station can not hear me unless I go back to the original transmission
slot. I attribute this to QRM on his side that I can not see on mine. Often
when I go back to where he originally heard me the QSO can be completed
with no problem. As far as scenario 2, I usually never call someone on
their own frequency except in that particular circumstance. It seems easier
to quickly move off of the original station's frequency and go to the
caller's then find another empty frequency and start the response (and risk
the issue of landing on another "clear on my side, QRM on his frequency". I
usually assume that the other station is on a QRM free frequency on his
side or he won't be using it.

Anyway, just minor issues that I've been working around. This program is
AMAZING!!!

Thanks!

Bill - AK6A

On Thu, Oct 25, 2018 at 5:09 AM John  wrote:

> Bill,
>
> WSJT-X does not require you to transmit on the sender’s frequency, or to
> set your frequency precisely.  In fact it is often the case that it is best
> to select your transmit frequency where there is a clear region and then
> click “Hold Tx Freq”.   Your signal will be decoded by the sender - and, in
> particular, if many people are transmitting on his/her frequency you will
> have a better chance of getting a reply.
>
> — John G4KLA___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X RU Contest Observations 10-24-18 - AK6A

[Bill]

WSJT-X RU Contest Observations 10-24-18 - AK6A


The band conditions were very poor for me here in Oregon (it was still
daylight and a bit early for 40m). I made a few contacts and here are my
observations.


1. My sent report was never logged into either the WSJT-X Contest Log or
the Log QSO. I had to manually enter the Sent RPT into the Log QSO window
for it to be logged correctly. In no case did it ever show in the Contest
Log.


2. I responded to W7XYZ who was sending a CQ in Non-Contest mode (I was in
RU Mode). My responses were in “Contest Sequence”, his were in ’Standard
Sequence”. The contact was logged with a RCVD RPT of “W7XYZ R-01” and again
no sent report. A subsequent contact with W7XYZ being in RU mode resulted
in the correct exchange (but no logged Sent RPT.)


3. I saw numerous strong signals on the waterfall that did not decode.
These looked like standard FT8 broadcasts (Not the multiple time slot
JS8CALL).


4. The contest log allowed DUPS. The QSO rate stayed at zero. (I know these
are known issues)


The contest was fun, I just wish there were more people to contact.


SW: WSJT-X 2.0 RC3

OS: Mac OS X Mojave

Additional SW: JTBridge, MacLoggerDX


Running WSJT-X from the desktop using terminal as outlined in the
limitations.


Thanks!


Bill - AK6A
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Mock FT8 Test #2 Comments

[Thomas Webb]

I was one of the 'early bird' participants; started around Z and pulled the 
plug around 0230Z
when 40m went south.

Got 23 QSO's total.  I used JTAlert for logging into MixW.  Noticed early on my 
received report was
not being posted to the log automatically so I entered it manually.  I was 
using 'Tab 2' for message
generation at the time. I switched to 'Tab 1' (Generate Std Msg), the received 
reports then
automatically posted to the log.

All in all, the program performed well.  Some glitches, but I credit that to 
operator error.  A vast
majority of the QSO's were short, snappy, and efficient which will play well in 
a real contest
environment.

Tom Webb, WA9AFM/5



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 RU Test #2 Observations

[Joe Taylor]

On 10/25/2018 9:27 AM, Joe WB8SBD wrote:


where does the exported cabrillo get saved?


Use the command "File -> Export Cabrillo log".  You can save it wherever you 
choose.

Thats what I thought would happen. But after the test last night I did 
do that sequence, and the usual popup asking where to save it never 
appeared. So I thought it just does it to some default location.


You need to click the "Save As" button.

-- Joe, K1JT


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Mock FT8 Roundup Observations

[Joe Taylor]

Everyone seems to have had fun exercising the RTTY RU features in 
WSJT-X.  I did, too, making 37 QSOs in a little over an hour using 100 W 
and a dipole.


I found more things wrong than others have reported, so far.  I will 
document them carefully and report here more fully in a little over a 
week.  (I will be busy with other commitments from Oct 26 through Nov 1.)


Bottom line, as I see it today:

It's clear that the new FT8 message formats can work well for RTTY 
contesting.  We still have work to do on improving the contest-oriented 
user convenience features.


-- 73, Joe, K1JT


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 RU Test #2 Observations

[Joe]

Hi Joe,
Thats what I thought would happen. But after the test last night I did 
do that sequence, and the usual popup asking where to save it never 
appeared. So I thought it just does it to some default location.


Joe WB9SBD
Sig
The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com
http://www.idle-tyme.com
On 10/25/2018 8:21 AM, Joe Taylor wrote:

On 10/25/2018 8:32 AM, Joe WB9SBD wrote:

where does the exported cabrillo get saved?


Use the command "File -> Export Cabrillo log".  You can save it 
wherever you choose.

    -- Joe, K1JT




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 RU Test #2 Observations

[Joe Taylor]

On 10/25/2018 8:32 AM, Joe WB9SBD wrote:

where does the exported cabrillo get saved?


Use the command "File -> Export Cabrillo log".  You can save it wherever 
you choose.

-- Joe, K1JT




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Mock FT8 Roundup Observations

[mail]

I also played the entire hour, only worked 7 stations. My recieved signal reports were mostly 539, 549 so maybe I could have bumped up the power to be heard better. I spent most of the hour calling CQ with 5 responses although plenty of stations decoding/scrolling in the band activity window. No multiple calls to try out the "TU". I managed S on 2 stations that the color coding showed were needed grids.May have been my low power, twice a station that had answered my CQ did not respond with RR73 (or mine did not decode it) my side stayed in report sending mode waiting for the RR73 while they had moved off to another qso and did not respond to my reports until several minutes later, by then I had stopped the TX and cleared the qso to try to start calling CQ again, the resulting "2nd attempt" qso going to my log showing their call instead of rst & state in the rcvd field. Therefore I spent some time getting my log reports straightened out before getting back to TX CQ. That would be frustrating in a contest. Probably not the software's problem, just how it sometimes goes in a contest.I unchecked the RTTY box right after the mock contest to try out the 77 bit, but remaining stations were still in RU sending, so I only managed to have 1 "post contest" qso in 77 bit which resulted in me sending a -10 report and the other station sending 549 FL. Activity heard died off pretty quickly, and I got no response to further CQs in 77 bit.73Doug KV4ZY


 Original Message 
Subject: [wsjt-devel] Mock FT8 Roundup Observations
From: "Ed Muns" 
Date: Wed, October 24, 2018 11:46 pm
To: "'WSJT software development'" 

 I played the entire hour but only worked 7 stations.  There seemed to be a lot of participants, which is great, but I was not able to work very many of them.  I’m not sure if (1) my signal strength was too low, or (2) if my signal quality was poor, or (3) if I was running WSJT-X RC3 incorrectly.  Regardless, I felt I could enjoy HF FT8 contesting with WSJT-X at some point in the future.   My notes:   1.  Some people called me on my Tx frequency.  In general, I think it is better if people call on a different (clear) frequency.  I would add this to the “tips”, that is, encourage folks to check ‘Hold Tx’.   2.  I could never figure out how to call a CQer on the cycle following their CQ.  My Tx cycle had already started by the time I could click on their call from their CQ in the prior cycle.  Is there a technique I’m missing or is this an inherent issue (delay of 30 seconds)?   3.  I really missed the ability to call multiple stations.  Yes, I know it is not part of current contest rules, but I think it should be in the case of FT8.  This is a chicken vs. egg problem.  What changes first: the rules or WSJT-X?  Knowing that it is possible to easily have multiple parallel QSOs but being artificially restricted, is frustrating for an HF contester.  I advocate FT8 contests allow multiple parallel QSOs with the same audio passband.   4.  When my Tx frequency was less than 1000 Hz, WSJT-X dropped my Tx carrier frequency from 7.078 to 7.077.  I assume WSJT-X then added 1000 Hz to my Tx audio frequency but I couldn’t be sure.  This is probably explained in the documentation but I haven’t found it.   5.  I was hoping to try the ‘TU;’ sequencing but never got called by more than one station at a time.  The only stations I saw doing this were VP8LP and K1JT.   6.  The vast majority of stations were between 1000-2000 Hz on the 7.078 carrier frequency.  Is this coincidence or a function of something I don’t yet understand?  Why aren’t they lower and higher?   7.  When I’m CQing and getting no response, what happens if I click on another CQer in my Rx cycle?  I tried this a couple times and couldn’t be sure what I was transmitting in the next cycle: another CQ or my exchange to the other CQer?   73, Ed W0YK___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Ability to quickly and precisely set my transmission frequency

[John]

Bill,

WSJT-X does not require you to transmit on the sender’s frequency, or to set 
your frequency precisely.  In fact it is often the case that it is best to 
select your transmit frequency where there is a clear region and then click 
“Hold Tx Freq”.   Your signal will be decoded by the sender - and, in 
particular, if many people are transmitting on his/her frequency you will have 
a better chance of getting a reply.

— John G4KLA

smime.p7s
Description: S/MIME cryptographic signature
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Mock FT8 Roundup Observations

[Jim Brown]

On 10/24/2018 8:46 PM, Ed Muns wrote:
*/My Tx cycle had already started by the time I could click on their 
call from their CQ in the prior cycle.  Is there a technique I’m missing 
or is this an inherent issue (delay of 30 seconds)?/*


Experience has been that if you have a good signal at the other end, a 
TX that begins in the first 2-5 seconds is often decoded.


73, Jim K9YC


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel