On 3/26/2018 5:44 PM, Mike Besemer wrote:
Wow… there had been so much good discussion here about avoiding interference to
other modes, and then this happens. If nothing else, it’s extremely
inconsiderate and the discussion on the PSK31 lists is not favorable for FT8.
I wish the developers
Thank you very much, Bill! You work very fast. I applied your patch, and the code worked perfectly. I am sure that there will be
developers who will take full advantage of the callsign color list, and those who will use the Highlight Last mode to have more
control.
The reason why I want to
Wow… there had been so much good discussion here about avoiding interference to
other modes, and then this happens. If nothing else, it’s extremely
inconsiderate and the discussion on the PSK31 lists is not favorable for FT8.
I wish the developers would take responsibility for the genie
I understand.
Sorry
Cheers
Serge
On 27/03/2018 01:50, Bill Somerville wrote:
Hi Serge,
I understand your approach but unless you are monitoring all modes the
decodes from WSJT-X alone will not give you enough information to pick
a clear frequency to transmit on. I still assert that the
Hi Serge,
I understand your approach but unless you are monitoring all modes the
decodes from WSJT-X alone will not give you enough information to pick a
clear frequency to transmit on. I still assert that the waterfall is the
best way to do that. For example if you are on 20m or 40m and
Everything from about 7.071 up is useless due to FT8 QRM from stations calling 7Q7EI. Is he running DXPedition Mode?
Pity people don't listen before they transmit. If the FT8 crowd wonders why other modes hate them, this is the answer.
MikeWM4B
Hi Bill,
My server calculates the best Tx frequency for a given QSO using the
DECODE messages.
My rig is a Flex 5000A connected to a PC that is dedicated to run it.
That same PC hosts the WSJT-X client that broadcasts UDP messages to
tell an iMac running my logging program what's happening
Hi Alex,
thanks for reviewing the changes. Some comments in line below.
On 26/03/2018 18:23, Alex, VE3NEA wrote:
1. Some developers may prefer to highlight only the senders'
callsigns, or at least use different colors depending on the callsign
position in the message. Your code does not allow
Hi Serge,
all you need do is leave "Hold Tx Freq" checked and SHIFT+click on the
waterfall in a clear spot, you only need to do this once or until you
loose your clear frequency. Where is a better place to choose a good Tx
frequency other than the WSJT-X waterfall?
73
Bill
G4WJS.
On
Good evening Bill,
Sorry I don't buy your argument: should I have to prepare my QSO on the
WSJT-X client (in order to use the Hold Tx Freq and to input the Tx DF
value on the client) I don't need a UDP type 4 message any more: I use
my keyboard and that's it.
My need for a modified type 4
On 25/03/2018 23:35, F6BHK wrote:
I wish I could specify a DF for TX with the UDP type 4 messsage
different from that of the DECODE message.
Rational behind this request is:
- When I prepare a response to a CQ, I have to check whether the freq
used for TX is clear or busy. When busy, it is
The USB hardware on the Pi, all versions afaik, is kind of lacking. I've
had lots of problems running SDR's, ranging from rtl-sdr, funcube to hackrf
etc. No HF involved at all, not even located in the shack. They all had
stability issues that cause the data to be halted for some reason. Tested
Hi Bill,
I applied your patch to WSJT-X and changed my UDP server to send two QColor parameters, everything works fine. However, there
are a few issues due to storing the list of highlighted calls.
1. Some developers may prefer to highlight only the senders' callsigns, or at least use
So 'm back with some more information.
It's not a HF related issue, it never occurred during TX(everything is
proper grounded, shielded cables etc. ), only during RX.
Sometimes I get an error message like "Data not feed to soundcard
fast enough"(during TX). But this does not stop the decode
Iztok Saje for President! :D
Well done Iztok!
All problems solved.
Each IARU official is to resign at once!
gl de ha6nn
Andras
On Mon, Mar 26, 2018 at 1:09 PM, Iztok Saje wrote:
> Hello!
>
> Summary: Do not over regulate HAM bands!
> Please emphasize in doccumantation:
>
TX2 bug response in v1.9.0-rc3
At times, multiple callers answer my CQs. The decoded red lines from both
callers appear as expected, in both the 'Band Activity' and 'RxFrequency'
columns. After working the first station, if the next station I want to work is
sending me a Tx2 message (Calls &
Hello!
Summary: Do not over regulate HAM bands!
Please emphasize in doccumantation:
"FT8 frequencies are recommendation, not Law".
Few different ideas for "FT8 frequencies" discussion.
1. Fresh from CQ WPX SSB.
On 80 m, somebody kept telling people calling CQ below 3700:
"This frequency is
Hi Alex,
patch works fine for me:
bill@BILLS_LENOVO ~/src/wsjt ((a4e77bb...))
$ patch --dry-run -p1 <~/Dropbox/Public/highlight.diff
patching file `CMakeLists.txt'
patching file `MessageClient.cpp'
patching file `MessageClient.hpp'
patching file `MessageServer.cpp'
patching file
18 matches
Mail list logo