Lock TX and RX was removed back in the evolution of 1.8 (RC2 if memory serves).
Jim S.
N2ADV
From: Edfel Rivera [mailto:edfelj...@gmail.com]
Sent: Wednesday, September 19, 2018 12:26 PM
To: WSJT software development
Subject: [wsjt-devel] WSJTX 2 RC1 - Feedback and Question
Hi:
Hi:
Have tried FT8 2 and achieved QSO 20m. Seems to work fine. Some
observations, notice lock TX and RX buttom no longer available? Tried
MSK144 but I know there is a fix so will wait RC2 to test more.
Finally, I left program monitoring - open (was not present because upset
stomach) and got th
I agree John. But I'd like to wait until rc2 comes out next week. Then after
kicking the tires we can try a mock trial Special Operating Activity as you
suggest.
Don AA5AU
From: John Zantek [mailto:j...@zantek.net]
Sent: Wednesday, September 19, 2018 3:23 PM
To: 'Don AA5AU'; 'WSJT softwa
If anyone in or around the Pacific North West wants to try the VHF contesting
related features prior to the next contest let me know. I have a reasonably
good path into the metro Seattle area and beyond on 144 MHz from my home QTH in
greater Vancouver.
73
Mark Spencer
VE7AFZ
netsyn...@gmail.
Don, et al,
As mentioned in the Quick Start Guide, I think it would be wise to set up a
mock trial Special Operating Activity and check out any issues with rc1 before
we plunge into changing existing contests so that they open the door for 2.0.
I’m among that eager bunch and would be will
For a minute, I thought the authors had added a new “zombie mode” feature that
allows the sender to take over everyone else’s radio. Kind of a fun idea with
Halloween around the corner!
On a serious note, v2.0 seems pretty solid so far.
73,
Eric NC6K
From: Andras Bato
Sent: Wedn
Also, the sounds in JTAlert are now missing, even though I didn't do
anything specifically with them.
On Wed, Sep 19, 2018 at 4:36 PM Frank Kirschner
wrote:
> Mike,
>
> I don't seem to be able to get it to work. Any PTT Method in WSJT-X other
> than CAT won't key the transmitter. I can't find co
Hi Keith and all,
There is a very good reason why you won't see any example of two
nonstandard callsigns working each other in these documents posted on
Monday:
http://physics.princeton.edu/pulsar/k1jt/New_Features_WSJT-X_2.0.txt
http://physics.princeton.edu/pulsar/k1jt/77bit.txt
The fully g
Mike,
I don't seem to be able to get it to work. Any PTT Method in WSJT-X other
than CAT won't key the transmitter. I can't find common COM ports between
WSJT-X and SmartSDR CAT. Some combinations give me an error, others just
don't work. I assume if I could figure out how to create another COM po
Hi Dezider,
I want trying you with a non standard EI100MCV earlier but auto seq would
not progress the qso after you sent your call sign.
Keith
EI5KO
On Wed 19 Sep 2018 at 20:23, Joe Taylor wrote:
> Hi Dezider,
>
> On 9/19/2018 3:03 PM, Dezider OM5NA wrote:
>
> > I had an opportunity to test t
Hi Al,
See my message posted here yesterday:
###
1. If a message's first callsign contains only characters 0-9 and A-F it
will be interpreted as a hexadecimal number. The message will be
transmitted and decoded as if the
My call sign is AF4FA and I am using the vn 2.0 RC1 of the program and when I
set the encode and decode to 77 bit
messages I only see the calsign of the responding station to my CQ. I was also
told that they only see my callsign also.
When I reset the program to not encode and decode 77 bit me
Tried a non standard CQ earlier.
CQ EI100MCV (no locator)
Answered
EI100MCV OM100CSR
*Sent back*
OM100CSR EI100MCV
Auto seq would not progress past this.
Keith
EI5KO
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourcef
Hi Richard,
Thanks for your report. See my message posted here earlier today (at
11:37, according to my email client):
#
Many thanks to all the MSK144 gang who helped to identify a bug in
WSJT-X 2.0.
I believe the bug
It's the high time to check AV and Avast!
Sellers made a lot of advertisement stating they were the best, i.e. #1
virus scanners!
It is not true!
gl de ha6nn
Andras
On Wed, Sep 19, 2018 at 12:12 PM Claude Frantz
wrote:
> On 9/19/18 12:52 PM, Hasan al-Basri wrote:
>
> Hi Hasan,
>
> > When running
Ed, W0YK, and I are thinking of changing our Ten-Meter RTTY Contest, which
normally takes place the first weekend in December, to an all-band FT8 contest.
If you think it might be done before then, we can certainly wait. Our thinking
is that there may be some operators who would like to use it fo
To: WSJTx Development Group
From: Richard Bumgardner KV8S
Subj: WSJT V2.0 MSK144 Tx Field Issue
This morning several users of WSJT V2.0 MSK144 operating on 50.280
experienced critical failures within the Tx field which rapidly propagated
among all who decoded the corrupted frames. The frame whi
Hi Don,
On 9/19/2018 2:53 PM, Don AA5AU wrote:
From the 2.0 Quick Start guide "A basic Cabrillo log is generated in
the log directory, but it does not yet include the heading information
needed when submitting a contest log."
How is a Cabrillo log generated in this version?
When do you expe
>From the 2.0 Quick Start guide "A basic Cabrillo log is generated in the log
>directory, but it does not yet include the heading information needed when
>submitting a contestlog."
How is a Cabrillo log generated in this version?
When do you expect Cabrillo output to be full-featured?
Thanks,Don
Hi Dezider,
On 9/19/2018 3:03 PM, Dezider OM5NA wrote:
I had an opportunity to test the new -rc1 release of the WSJT-X v 2 with
a non-standard callsign OM100CSR.
Unfortunately I find out, that the SENT report and a gridsquare of the
counterpart station is not stored to the ADIF or WSJTX log
On 19/09/2018 08:47, Jesús Gutiérrez Rodríguez wrote:
Buenas noches, disculpas por expresarme en español...
Acabo de probar la nueva versión, en 7078 y 14078..
Realicé siete contactos sin ningún problema...
También lo probé en FT8 antiguo en las frecuencias habituales y
funciona todo ok.
Cordia
When I initiate a QSO with a station calling CQ, if I double-click on the call
sign in the 'Band
Activity' window, the display in the 'RX Activity' window is normal, i.e. 'CQ,
call sign, grid
square, DX entity'.
However if you click on the station in the JTAlert display (I'm using Ver
2.1.2.5),
Hello group ,
I had an oportunity to test the new -rc1 release of the WSJT-X v 2 with
a non-standard callsign OM100CSR.
Unfortunately I find out, that the SENT report and a gridsquare of the
counterpart station is not stored to the ADIF or WSJTX log file with a
non-standard calsign only
I
You should be able to do it by setting up a new port in PowerSDR under the CAT
control for PTT Control RTS or DTR.Then pick that COM port and method in WSJT-X
Radio setup.
de Mike W9MDB
On Wednesday, September 19, 2018, 1:44:57 PM CDT, Frank Kirschner
wrote:
I am slowly getting al
I am slowly getting all my programs to work with my new Flex 6600/SmartSDR.
One glitch left is that there is a three-second delay in transmit. I'm
using Ham Radio Deluxe as the rig, and PTT is via CAT. How do I change that
so WSJT-X sends PTT directly to the Flex?
73,
Frank
KF6E
_
Hi Wolfgang,
On 9/19/2018 4:37 AM, Wolfgang wrote:
Tried to reply to a CQ of EI100MCV
In TX1 to TX3 his call sign was in brackets
but TX4 has: EI100MCV RR73
and TX5 is: EI100MCV 73
so, is my call sign sent in hash code at the end of a QSO?
73 de Wolfgang
OE1MWW
Yes, the behavior you
Hi Erik,
Thanks for your report. The problem you observed is a manifestation of
a known limitation of the -rc1 release of WSJT-X 2.0.
From the "Quick-Start Guide to WSJT-X 2.0", top of page 3:
http://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf
"To make FT8 QSOs with stations
Yes, I did read that info yesterday and forgot it.
Someone tried that binary and of course I fell for it.
Joe replied of this and made me to slap to my forehead :o)
Thanks Jim for the note.
Rgds,
: Jari / oh2fqv
On Wed, Sep 19, 2018 at 6:54 PM James Shaver wrote:
> From Joe’s post y
That's why I said "virus-like" in that anyone receiving the bad tone set
would begin transmitting it.
...but it pays to be careful., I don't want anyone thinking I was saying
that the team unleashed a computer virus :-)
Thanks for the quick attention.
73, N0AN
Hasan
On Wed, Sep 19, 2018 at 10:
>From Joe’s post yesterday about known bugs:
“1. If a message's first callsign contains only characters 0-9 and A-F it
will be interpreted as a hexadecimal number. The message will be
transmitted and decoded as if the first callsign were telemetry data;
the remaining parts are lost. (Ap
Many thanks to all the MSK144 gang who helped to identify a bug in
WSJT-X 2.0.
I believe the bug is now fixed in our development code. We will post a
-rc2 candidate release very soon, probably next week. In the meantime,
it's best to use v1.9.1 for MSK144 QSOs.
BTW: this was a rather ordin
Hi Steve,
This bug seems to have been caused by unitialized values of i3, n3
before calling pack77() in subroutine genmsk_128_90.
I believe the bug is fixed in commit 618fc05a.
-- Joe
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforg
Jari --
See my message posted here yesterday:
1. If a message's first callsign contains only characters 0-9 and A-F it will be interpreted as a hexadecimal number. The message will be transmitted and decoded as if the first callsign were telemetry data; the remaining parts are lost. (Apologies
14.078
af4fa tx at 1496Hz , no locator with the call sign.
Tried to double click to the call AF4FA at band activity window, not copied.
I type call manually to DX Call field, set manually locator and I made
Generate Std Msgs, it move it to TX1-5 fields.
This cause WSJT-X2 to transmit AF4FA only
Steve,
In addition to a lot of programming I have done a lot of field service over the
years. One of the things I had the good fortune to learn very early on is
that even seemingly trivial reports from the customer should not be ignored.
Hasan’s report, which you have deemed not very
Good morning Steve,
I too have had this happen and quite frankly I am not sure how to reproduce it
because I am not sure how it happened. Once it happens it appears to be
locked in to this mode and even a program restart will not clear it. This has
happened to several folks and as a consequ
Steve,
First of alla large group of people had migrated to 280. We ran a bunch
yesterday, and this showed up out of the blue this morning...and it
"infected" everyone who heard those tones.
So, I was in a hurry to let someone know that this was happening on 280
where a lot of people were usi
Hasan,
Unfortunately, your report isn’t very useful as it stands. To you and others
who are testing the recent beta release of v2.0: when making a bug report,
please carefully document and report a sequence of steps needed to reproduce
the problem. When running a beta release, always run with “
On 9/19/18 12:52 PM, Hasan al-Basri wrote:
Hi Hasan,
When running MSK144, the program will start tx'ing some weird sounding
tones...they will "infect" any V2 MSK144 station that hears them and
they will start sending the same strange tones.
5 of us have experienced this same bug...all simult
When running MSK144, the program will start tx'ing some weird sounding
tones...they will "infect" any V2 MSK144 station that hears them and they
will start sending the same strange tones.
5 of us have experienced this same bug...all simultaneously upon hearing
those "odd" tones.
I'm betting it is
Tried to reply to a CQ of EI100MCV
In TX1 to TX3 his call sign was in brackets
but TX4 has: EI100MCV RR73
and TX5 is: EI100MCV 73
so, is my call sign sent in hash code at the end of a QSO?
73 de Wolfgang
OE1MWW
--
___
wsjt-devel mai
-- Forwarded message -
From: Jesús Gutiérrez Rodríguez
Date: mar, 18 de septiembre de 2018 23:06
Subject: Test 2.0
To: <-de...@lists.sourceforge.net >
Buenas noches, disculpas por expresarme en español...
Acabo de probar la nueva versión, en 7078 y 14078..
Realicé siete contactos
Hi,
I came across a straight program exit after double clicking on a prefixed
callsign in the band activity window.
The message was CQ PJ4/PA3BWK FK52 and I was using the 75 bit FT8 mode on
V2.0.0-rc1
The saved audio file can be found at
https://1drv.ms/u/s!AtBGol2-BnqRgtYHuw7GHWphzRBWtg
and th
43 matches
Mail list logo
