FT8 DXpedition mode

8 posts / 0 new
Last post
oh1kh
FT8 DXpedition mode

HI !

Worked today TY7C at 18,096 using FT8 DXpedition/hound mode.
I have version 1.9.0.rc2 of wsjtx downloaded from official site (it is NOT latest version compiled from svn).

Working went quite easily with 50W and dipole. Some notes:

Cq-monitor does not have any contents (well...I think I did not see any of his CQ anyway).

But more interesting notice was that even wsjt-x logging window opened as usual, and I confirmed it with OK later I found out that there were 3 loggings in log.
Qso times of them had few minutes difference.

This is rc2, not actual release so it is not time to do anything with cqrlog yet.
If you see similar action, be warned and just remove additional loggings leaving only the first one.

We see what happens when official release is out.

oh1mrr
You did'n see, because you

You did'n see, because you should have set in wsjtx freqs 18096
into list

Jarmo

oh1kh
You did'n see, because you

I doubt that because seeing CQ is not related to list of fixed frequencies.
At the time there was so many stations to work that no CQ was needed to send by TY7C.

There is no mention about it in DXpedition mode manual. The part that says abt. setting given freq to list of frequencies is just for those who can not dial with vfo knob. Maybe a CAT issue also for some rigs.

My IC706 stays on manually set frequency and uses split for TX freq, as should. How ever using some functions of wsjt-x may return it back to conventional band frequency if DXpedition frequency dialed by manual is not included to list of frequencies (and maybe that is why it is mentioned in DXpediition mode manual).

I often work on conventional frequencies so that I dial manually 1kHz up or down from base frequency. That gives relief for my IC706 poor front end that gets overloaded by big signals ( when using this weak signal mode , hi hi).

But I will confirm the CQ issue later when I can again hear DXpedition mode station on air.

--
Saku
OH1KH

km4hqe
You did'n see, because you

Revisiting an old topic... I managed to get in the log for KH1/KH7Z on several bands, but they too didn't send many CQ's and I didn't have CQ monitor on since what little testing I did it doesn't seem to display CQ's when WSJT-X is in DXpedition mode. I know when I have WSJT-X set for DXpedition mode and listening to non DXpedition FT8 transmissions, CQ monitor doesn't display the CQ's. Anyone else had success with CQ monitor and DXpedition mode?

73

Stan
KM4HQE

oh1kh
You did'n see, because you

Hi!
There is no success and that is because wsjt-x does not send UDP information like it sends in normal FT8 mode.
There has been some conversations about this subject in wsjt-x developer list during past months.
https://sourceforge.net/projects/wsjt/lists/wsjt-devel

--
Saku
OH1KH

km4hqe
FT8 DXpedition mode

Oh. That's a bummer. I don't subscribe to the wsjtx developers list, just the wsjtx users list. Wonder why it doesn't send UDP info while in DXpedition mode?

73

Stan
KM4HQE

km4hqe
FT8 DXpedition mode

I found out from the WSJT-X folks that they decided it was not worth the effort to rewrite the code that decodes the messages while in DXpedition mode since the only one sending is the fox. Most UDP messages are still sent though. My question was whether or not logging would work and it looks like it does based on the test I did of putting WSJT-X in hound mode, typing a call in the DX call box, clicking on log QSO then click Ok to log it. The test callsign was logged in CQRLOG. Will find out for sure if it works after a real QSO when the TF/VE2DX DXpedition takes place. Or sooner if another DXpedition happens to run that mode.

73

Stan
KM4HQE

oh1kh
FT8 DXpedition mode

Hi!
You do not need DX pedition to thest logging.
Your test is perfect without actual DX pediton.

There just will not be any CQ, or other traffic monitoring when in hound mode because there are no UDP messages for that.

--
Saku
OH1KH