With all of the discussion about the QRM to 40 Meter PSK users from 7Q7EI's use
of the FT8 DXpedition mode, it is now time to take a serious look at
alternative DXpedition frequencies.
IARU Regions 1, 2 & 3 already have drawn up 'Bandplan Recommendations'. You can
read about their 40 Meter re
Hi Bill,
Your latest message aggregator works perfectly, both in the highlight-last and list-based modes. WSJTX now does all that I want,
in terms of callsign highlighting. I used the new message to highlight the countries not worked this year, and improved my DX
Marathon score significantly in
Like or not, the inconsistency exists. I'm not the one who set it up that way
and neither of our opinions really matters anyway; the fact is that 7070 has
been in use by PSK for over 15 years in Region 2 and there is no reason NOT to
know that; it is widely published for anyone to see. If you
Yay!
From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Tuesday, March 27, 2018 11:54 AM
To: WSJT Software Development
Cc: Black Michael
Subject: [wsjt-devel] tx4 RR73 patch
Allow user to shift-double-click TX4 to make RR73 last across band changes.
ht
FT8 for 2018 Field Day
Regarding the use of FT8 on Field Day, you can do what I did during the recent
VA QSO Party, that is, use the Tx5 (73) message to send contest data. The VQP
exchange sent was number, county & State, "nnn CUL VA 73", where 'nnn' was my
QSO number and 'CUL' was the abbrevia
Hi,
... obviously there are no UDP transmissions while being in DXpedition mode as a HOUND. I
first realized this behavior in RC2 while working TY7C. Same just now happened under RC3
while working 7Q7EI on 10132KHz.
UDP messages are urgently required for highlighting purposes in user
applicat
On 27/03/2018 04:10, Alex, VE3NEA wrote:
When I was initially experimenting with callsign highlighting, I
painted all instances of the call that appeared after the last
separator. I searched for "" backwards from the end of the text,
then searched forward for the callsign, starting at that
Allow user to shift-double-click TX4 to make RR73 last across band changes.
https://www.dropbox.com/s/qav6d92gllu9ktc/tx4.patch?dl=1
de Mike W9MDB
--
Check out the vibrant tech community on one of the world's most
engag
Yeah, that'd even work with the 3 letter location codes as long as didn't
have any modifiers on your callsign. But when you get up to the 10+
transmitter categories it starts to fail for 6 letter callsigns . If you
coded it like the maidenhead grid, you could get up to 64 transmitter clubs
insid
At that very least you can use a free text message for the exchange, Don:
"KN4CRD 1B GA"
You just won't be able to use auto sequencing when operating FT8 during field
day.
Best,
Jordan
KN4CRD
On Mar 27, 2018, 7:40 AM -0400, Don Goldston , wrote:
> Any chance that an FT8 mode that performs the
It doesn't matter how inconvenient it is to code in various region's FT8
"sub band". The DXp mode created the problem, it is already very
complicated code. The further complication of exclusion zones for DXp by
region, is a pittance compared to the initial investment.
Otherwise all we have is the
Except it's NOT going away. The DXP fiasco last night was just the
icing on the cake; the intrusion downward is pretty much ongoing - just
not to the extent we say last night.
Funny thing is, most DXPeditions do a pretty good job of choosing
frequencies. Not sure how it's gotten so mucked
Not going to work.
Taking 40m as example - What is the ‘FT8 allocation’ ? - all that could be
coded would be the MGM allocation - nothing says FT8 needs to be 7.074 - UK
band plan has digi modes 7.053 - 7.060 and the rest of the 7 Mhz allocation is
‘All Modes’. PSK31 starts from 7.040 - whic
My suggestions were specifically about the DXp mode, not FT8 in general.
..and it isn't a popularity contest, it's about observing the existing
watering holes.
PSK31 is in use, it will recover somewhat when more people get bored with
"wham bam , thankyou ma'am" operating style.
I enjoy both FT8
Hasan,
Thank you for that very eloquent post! I think your suggestions are
spot-on and I'd LOVE to see all of them implemented.
73,
Mike
WM4B
On Tue, Mar 27, 2018 at 7:46 AM, Hasan al-Basri wrote:
I agree with every point that Mike (WM4B) made. DXpedition mode is
becoming a scourge on
Everybody needs to realize a little math here.
In the last 2 hours there were 488 PSK reports showing on pskreporter.Compare
that to 516,312 FT8 reports.
516,312/488 = 1058 times more.
Now...let's say the odds of finding a bad actor in all those PSK reports is
1-in-488 over that 2 hour period.
Has anyone contacted the parties that are miss-using the DXP mode and try to
rein them in explain to them what they are doing wrong tell them how to put the
correct freqs into the program. It would be good if the developers did this it
might make a real impression on the user if he heard from s
I agree with every point that Mike (WM4B) made. DXpedition mode is becoming
a scourge on the bands w/r to other modes.
Another person asked for suggestion instead of complaints.
OK, try this on:
1.Disable the mode until *real* precautions are taken to observe the
current watering holes for other
Any chance that an FT8 mode that performs the required exchange of
information for the 2018 Field Day could be created?
I know y'all are wrapped up in DXP mode, but thought it was worth asking.
Thanks,
Don
--
Check out th
Gary,
As I said, I've recently heard some very good conversation here about
the need to avoid QRM to other modes; that's part of the reason it was
so disappointing to see 40 meters get trashed last night all the way
down to 7068 - or perhaps lower.
The reason I address the developers is twof
20 matches
Mail list logo
